Greetings,
On Friday, 2024-01-05 18:46:09 +0100, I myself wrote:
> ...
> since a few month or so off and on my laptop fails to resume from hiber-
> nation due to the "dirty bit" being set on the ext4 "/home" partition.
I was reading this flickering by on the screen, and it wasn't quite cor-
rect. Meanwhile I found this in my "openrc.log":
fsck.fat 4.2 (2021-01-31)
There are differences between boot sector and its backup.
This is mostly harmless. Differences: (offset:original/backup)
65:01/00
Not automatically fixing this.
Dirty bit is set. Fs was not properly unmounted and some data may be corrupt.
Automatically removing dirty bit.
*** Filesystem was changed ***
Writing changes.
/dev/sda1: 368 files, 116600/258078 clusters
/dev/sdb1: recovering journal
/dev/sdb1: Clearing orphaned inode 54789026 (uid=1000, gid=1000,
mode=0100600, size=32768)
/dev/sdb1: Clearing orphaned inode 54788311 (uid=1000, gid=1000,
mode=0100600, size=553900)
/dev/sdb1: clean, 172662/61054976 files, 36598898/244190385 blocks
* Filesystems repaired
So one cause always is some problem on disk "/dev/sda1/" ("/boot/") and
another cause are one or more orphaned inodes on disk "/dev/sdb1/"
("/home/"). But while the values of offset, original and backup for
"/dev/sda1/" are always the same when this happens, the number of or-
phaned inodes on "/dev/sdb1/" and the inodes itself change from occur-
rence to occurrence. Besides it only happens sporadically when resuming
from hibernation, not every time. More precisely, the problem surfaces
when resuming from hibernation but could as well be caused during the
hibernation process itself.
Does this ring some bell somewhere what could cause this?
Sincerely,
Rainer
