On Sun, Mar 02, 2025 at 10:49:41AM -0500, Eben King wrote:
So. This time, while the backup was in process, I mounted /home read-only to check something out. Apparently that's not good enough to keep the filesystem intact, because at the end when I resumed, several things in $HOME didn't work right.
Correct. Even mounted read-only, the driver will replay the journal and resolve any outstanding actions--but the hibernated system doesn't know that, and will proceed without taking any changes into account. You could have mounted with "-o ro,norecovery" which will prevent the journal replay and make the mount truly read-only. Your best bet at this point is to force an fsck to at least ensure that the filesystem is consistent, but if there was any data corruption that won't uncorrupt it. To be certain that all the data is ok you'll have to restore to the last backup made before this happened.
