| 14 Mar 2026 |
 matthewcroughan | If not, then where did I mis-step? | 19:34:33 |
 lassulus | no, It was the clanker | 19:35:09 |
| lassulus | stop arguing :D | 19:35:12 |
| lassulus | I'm on my phone and didn't check | 19:35:18 |
 Mic92 | You criticized a work in progress pr that tries to solve one of your problems. | 19:35:43 |
| matthewcroughan | No, I've been debugging for 4 hours, the cause of an issue, successfully. | 19:36:00 |
| matthewcroughan | I'll just leave the reproducer on a PR, you can solve it yourself. Thanks. | 19:36:35 |
| Mic92 | I did debug this issue before and back than with zfs but arc back than looked normal while something consumed memory | 19:38:42 |
| matthewcroughan | It is not arc, it's kernel changes | 19:38:55 |
| matthewcroughan | it only happens with 6.12+ | 19:39:02 |
| lassulus | not sure it's changes, because we had this happen in the past as well | 19:39:09 |
| matthewcroughan | well it's some part of the kernel that gets poked often enough to cause the issue to occur across time | 19:39:27 |
| matthewcroughan | 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 tets | 19:40:04 |
| Mic92 | 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 | * 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 tests | 19:40:07 |
| lassulus | do we have a reproducer now? | 19:40:24 |
| matthewcroughan | The current tests only allocate 64M for the ESP for example, which is not realistic | 19:40:26 |
| Mic92 | Some client work. It was worse with xcp | 19:40:27 |
| matthewcroughan | Yes, but I'm formatting it as a new test now | 19:40:37 |
| matthewcroughan | that will be a draft and won't pass CI until someone takes it over | 19:40:47 |
| lassulus | ok, thanks | 19:41:17 |
| Mic92 | 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 | It's not large images that cause the issue | 19:43:22 |
| matthewcroughan | they cause a different issue, but the main issue (cannot allocate memory) is caused by the kernel versions | 19:43:54 |
| Mic92 | Okay but in my testing I had issues only with larger images | 19:44:09 |
| matthewcroughan | you don't need a particularly large image to make it happen | 19:44:10 |
| Mic92 | In any case, I know a project where this was triggered. | 19:45:14 |
| Mic92 | @lassulus:lassul.us: the dirty page sysctl doesn't sound like ads related to me | 19:46:39 |
| Mic92 | * @lassulus:lassul.us: the dirty page sysctl doesn't sound like zfs related to me | 19:46:56 |
| lassulus | is it only with zfs? | 19:48:13 |
