!oNSIfazDqEcwhcOjSL:matrix.org

disko

382 Members
disko - declarative disk partitioning - https://github.com/nix-community/disko100 Servers

Load older messages


SenderMessageTime
14 Mar 2026
@matthewcroughan:defenestrate.itmatthewcroughanI'm sorry but what is the offense for?19:32:33
@matthewcroughan:defenestrate.itmatthewcroughanI asked if something was clankered, why get upset?19:32:40
@bandithedoge:zimward.moebandithedogeare you always so damn confrontational?19:32:56
@matthewcroughan:defenestrate.itmatthewcroughanWhere is the confrontation above?19:33:13
@matthewcroughan:defenestrate.itmatthewcroughanI asked if the PR was made by an LLM, because it seemed like it was19:33:26
@matthewcroughan:defenestrate.itmatthewcroughanIs that in and of itself, offensive?19:33:41
@matthewcroughan:defenestrate.itmatthewcroughanIf not, then where did I mis-step?19:34:33
@lassulus:lassul.uslassulusno, It was the clanker19:35:09
@lassulus:lassul.uslassulusstop arguing :D19:35:12
@lassulus:lassul.uslassulusI'm on my phone and didn't check19:35:18
@joerg:thalheim.ioMic92You criticized a work in progress pr that tries to solve one of your problems. 19:35:43
@matthewcroughan:defenestrate.itmatthewcroughanNo, I've been debugging for 4 hours, the cause of an issue, successfully.19:36:00
@matthewcroughan:defenestrate.itmatthewcroughanI'll just leave the reproducer on a PR, you can solve it yourself. Thanks.19:36:35
@joerg:thalheim.ioMic92I did debug this issue before and back than with zfs but arc back than looked normal while something consumed memory 19:38:42
@matthewcroughan:defenestrate.itmatthewcroughanIt is not arc, it's kernel changes19:38:55
@matthewcroughan:defenestrate.itmatthewcroughanit only happens with 6.12+19:39:02
@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

Show newer messages


Back to Room ListRoom Version: 10