!oNSIfazDqEcwhcOjSL:matrix.org

disko

391 Members
disko - declarative disk partitioning - https://github.com/nix-community/disko105 Servers

Load older messages


SenderMessageTime
14 Mar 2026
@lassulus:lassul.uslassulusnot sure it's changes, because we had this happen in the past as well19:39:09
@matthewcroughan:defenestrate.itmatthewcroughanwell it's some part of the kernel that gets poked often enough to cause the issue to occur across time19:39:27
@matthewcroughan:defenestrate.itmatthewcroughanI have a reproducer, I will put it as a PR for a new test, to test real usage instead of the optimistic usage of the current tets 19:40:04
@joerg:thalheim.ioMic92
In reply to @lassulus:lassul.us
not sure it's changes, because we had this happen in the past as well
Yeah I had this on my plate at least a year ago
19:40:07
@matthewcroughan:defenestrate.itmatthewcroughan* I have a reproducer, I will put it as a PR for a new test, to test real usage instead of the optimistic usage of the current tests19:40:07
@lassulus:lassul.uslassulusdo we have a reproducer now?19:40:24
@matthewcroughan:defenestrate.itmatthewcroughanThe current tests only allocate 64M for the ESP for example, which is not realistic19:40:26
@joerg:thalheim.ioMic92Some client work. It was worse with xcp19:40:27
@matthewcroughan:defenestrate.itmatthewcroughanYes, but I'm formatting it as a new test now19:40:37
@matthewcroughan:defenestrate.itmatthewcroughanthat will be a draft and won't pass CI until someone takes it over19:40:47
@lassulus:lassul.uslassulusok, thanks19:41:17
@joerg:thalheim.ioMic92
In reply to @lassulus:lassul.us
do we have a reproducer now?
There is some ci, I could add this potentially to which runs this on large images
19:43:11
@matthewcroughan:defenestrate.itmatthewcroughanIt's not large images that cause the issue19:43:22
@matthewcroughan:defenestrate.itmatthewcroughanthey cause a different issue, but the main issue (cannot allocate memory) is caused by the kernel versions19:43:54
@joerg:thalheim.ioMic92Okay but in my testing I had issues only with larger images 19:44:09
@matthewcroughan:defenestrate.itmatthewcroughanyou don't need a particularly large image to make it happen19:44:10
@joerg:thalheim.ioMic92In any case, I know a project where this was triggered.19:45:14
@joerg:thalheim.ioMic92 @lassulus:lassul.us: the dirty page sysctl doesn't sound like ads related to me 19:46:39
@joerg:thalheim.ioMic92* @lassulus:lassul.us: the dirty page sysctl doesn't sound like zfs related to me19:46:56
@lassulus:lassul.uslassulusis it only with zfs?19:48:13
@lassulus:lassul.uslassulusI have a vague memory that it also happens on other FS19:48:25
@joerg:thalheim.ioMic92But not 100 percent sure. Would have to check the Kernel code19:49:02
@joerg:thalheim.ioMic92Also this should probably take into account how much memory we give to the vm19:49:58
@lassulus:lassul.uslassulusprobably, but we don't need any cache for paths we copy once from one fs to the other?19:50:21
@joerg:thalheim.ioMic92Well it might also hurt Io scheduling19:50:57
@joerg:thalheim.ioMic92If you flush more often 19:51:09
@joerg:thalheim.ioMic92CP/rsync are probably doing direct I/o as well19:52:10
@joerg:thalheim.ioMic92This usually by passes page cache19:52:32
@lassulus:lassul.uslassuluscp doesn't seem to do it, otherwise this would not happen?19:52:50
@lassulus:lassul.uslassulusor it's a different issue19:53:08

Show newer messages


Back to Room ListRoom Version: 10