Ignore the new superblock fields fs_pendingblocks and fs_pendinginodes
when comparing with the alternate superblock. These fields are used for temporary in-core information only. This should fix the "VALUES IN SUPER BLOCK DISAGREE WITH THOSE IN FIRST ALTERNATE" error from fsck_ffs that has been seen a lot recently.
This commit is contained in:
parent
753d49786e
commit
e23faa1027
@ -421,6 +421,8 @@ readsb(listerr)
|
||||
altsblock.fs_contigdirs = sblock.fs_contigdirs;
|
||||
altsblock.fs_avgfilesize = sblock.fs_avgfilesize;
|
||||
altsblock.fs_avgfpdir = sblock.fs_avgfpdir;
|
||||
altsblock.fs_pendingblocks = sblock.fs_pendingblocks;
|
||||
altsblock.fs_pendinginodes = sblock.fs_pendinginodes;
|
||||
memmove(altsblock.fs_fsmnt, sblock.fs_fsmnt, sizeof sblock.fs_fsmnt);
|
||||
memmove(altsblock.fs_snapinum, sblock.fs_snapinum,
|
||||
sizeof sblock.fs_snapinum);
|
||||
|
Loading…
Reference in New Issue
Block a user