We had unexpectedly heavy snowfall the other day and, as always, the
mains power supply came back only after a few days of repairing broken
power lines in the forest. Meanwhile, the days were so overcast that the
solar inverter couldn't charge the batteries enough to keep up with our
minimal domestic load.
Which meant that when the sun came out again, I was left staring at
something like this for a long time:
root@soot:~# ps -eo pid,cmd|grep '[f]sck'
756 /lib/systemd/systemd-fsck /dev/mapper/sdb1_crypt
757 /sbin/fsck -a -T -l -M -C4 /dev/mapper/sdb1_crypt
758 /lib/systemd/systemd-fsckd
759 fsck.ext4 -a -C4 /dev/mapper/sdb1_crypt
Long enough, in fact, that I began to wonder if I could tell what it was
doing. (The volume in question is exported via iSCSI from a Synology NAS
and fsck is still running long after the machine has otherwise finished
booting up, so I have ordinary shell access.)
Read more…