I remember after updating to one of the later versions I got flooded with alerts (a few emails an hour):
Quota exceeded on dataset <…>/.system/cores. Used 97.86% (1002.13 MiB of 1 GiB)
So I reverted back to the version I was using and waited for another update and alerts disappeared. I was using 24.04 and then upgraded to 24.10.0 and there were no such alerts, but after updating to 24.10.1 these alerts came back and I’m getting them multiple times a week.
It seems I can’t find anything on the topic
Anything I should look into? Should I change some settings?
I’m also getting this issue periodically, Quota exceeded on dataset tank/.system/cores. Used 98.02% (1003.77 MiB of 1 GiB) - yet not on a pool that manages booting or anything.
For me it seems to be qbit (?) which seems to stay relatively stable… although am monitoring whether it grows, or whether it was another app that’s now been cleared.
Did anyone find a way to increase core size, or troubleshoot what this means/what is generating them? I’m using mainly trueNAS-store apps, so not a heap of custom ones (e.g. the one showing up, qbit, is a TrueNAS store app), so I thought they’d play nice with the system cores given they’re purpose-built for it… has anyone had any success in why apps are generating/behaving like this?
So, if it’s not the app (which i feel it may be…), would be a tad worried about the other two options you mentioned ( 2. failing boot device, 3. unexpected OS changes) and thought I’d ask if you had any advice on where to go next to troubleshoot/diagnose these as they’re both quite vague. I haven’t had boot issues or really any signs of system-level issues - my disk checks are all good, routine scrubbing for boot drive, data drives, etc…
Am booting off a single NVMe 476GB SSD… but the dataset that is throwing the space concerns, tank of tank/.system/cores, is referring to my 1 x RAIDZ1 | 3 wide | 21.68 TiB HDD pool which I use for data storage, so I don’t see how it would be a boot issue?