Luigi Fabio <luigi.fabio@xxxxxxxxx> writes: > Well, I found SOMETHING of decided interest: when I run dumpe2fs with > any backup superblock, this happens: > > --- > Filesystem created: Tue Nov 4 08:56:08 2008 > Last mount time: Thu Aug 18 21:04:22 2022 > Last write time: Thu Aug 18 21:04:22 2022 > --- > > So the backups have not been updated since boot-before-last? That > would explain why, when fsck tries to use those backups, it comes up > with funny results. That's funny. IIRC, the backups virtually never get updated. The only thing e2fsck needs to get from them is the location of the inode tables and block groups, and that does not change during the life of the filesystem. I might have something tickling the back of my memory that when e2fsck is run, it updates the first backup superblock, but the others never got updated.
