Also, #fsck had run a ridiculous amount of times for me this year already... Maybe like 20 times, once or twice a week?
It's pretty cool that we have these very powerful and flexible sleep/suspend systems thanks to the #Linux kernel, #upowerd, #systemd etc. now. But it also feels like their configurable parameters might not be fully fleshed out yet, causing a risk for data integrity.
Now /sys/power/image_size and before it had been the too low percentages in upowerd for me.
@T_X Which fs? What are your SMART stats?

@nwcs luckily the quite robust #ext4. I had a few additions to /lost+found due to the lost power issues with a failing hibernation though.
SMART values: https://paste.linuxlounge.net/2Y

Edit: Plus a #ZFS partition for #OpenWrt / #Gluon + #Linux kernel dev stuff, mainly for the deduplication + compression features to keep having multiple git worktrees around feasible with these.

View paste 2Y

@T_X not a lot of info that, should be able to pull nvme log data though. I rarely have to fsck (only on power outage). Makes me wonder if you have some kind of hardware issue if it's occurring randomly without power being pulled?
@nwcs it is on power outage. That's what I ment with "their configurable parameters might not be fully fleshed out", the default 3% battery in PercentageAction in #UPowerd was typically too low for me for a clean hibernation. And kernel image_size now being too low to hibernate in the first place.
So I was running out of laptop battery quite often this year, resulting in an unclean shutdown, leading to many fsck runs.
@nwcs and I'm running into low battery quite often because I'm using #xmonad and haven't set up proper battery notifications with it yet... also by accident had been plugging in a 5V #USBC cable instead of the 20V one in the #Nobreakspace a few times...
Yesterday forgot to plug in the laptop AC or to close the lid for standby before going to sleep. 😅
@T_X Ah I see, gotcha. I was just lacking context.