xfs_repair keeps reporting errors
Hi,
I just had a problem with a RAID array, now that the rebuild process is complete, as I run xfs_repair (v 5.0) again and again it keeps reporting problems (here running xfs_repair for the 3rd time in a row):
bad CRC for inode 861144976062
bad magic number 0x0 on inode 861144976062 bad magic number 0x0 on inode 217316006460 bad version number 0x0 on inode 217316006460 inode identifier 0 mismatch on inode 217316006460 bad version number 0x0 on inode 861144976062 bad CRC for inode 217316006461
bad magic number 0x0 on inode 217316006461 inode identifier 0 mismatch on inode 861144976062 bad version number 0x0 on inode 217316006461 inode identifier 0 mismatch on inode 217316006461 bad CRC for inode 217316006462
bad magic number 0x0 on inode 217316006462 bad CRC for inode 861144976063
bad magic number 0x0 on inode 861144976063 bad version number 0x0 on inode 861144976063 bad version number 0x0 on inode 217316006462 inode identifier 0 mismatch on inode 217316006462 bad CRC for inode 217316006463
bad magic number 0x0 on inode 217316006463 inode identifier 0 mismatch on inode 861144976063 bad version number 0x0 on inode 217316006463 inode identifier 0 mismatch on inode 217316006463
Is there anything else to do?
Signature · 6 lines
------------------------------------------------------------------------
Emmanuel Florac | Direction technique
| Intellique
| <[email protected]>
| +33 1 78 94 84 02
------------------------------------------------------------------------Quoted 6 lines · Emmanuel Florac
Hi,
I just had a problem with a RAID array, now that the rebuild process is complete, as I run
xfs_repair(v 5.0) again and again it keeps reporting problems (here runningxfs_repairfor the 3rd time in a row):
Problems with the same inodes or the same general issue with different inodes after repeated repair runs?
What kind of RAID event was involved? Was the filesystem known healthy prior to the event?
Quoted 25 lines
bad CRC for inode 861144976062
bad magic number0x0on inode 861144976062 bad magic number0x0on inode 217316006460 bad version number0x0on inode 217316006460 inode identifier 0 mismatch on inode 217316006460 bad version number0x0on inode 861144976062 bad CRC for inode 217316006461
bad magic number0x0on inode 217316006461 inode identifier 0 mismatch on inode 861144976062 bad version number0x0on inode 217316006461 inode identifier 0 mismatch on inode 217316006461 bad CRC for inode 217316006462
bad magic number0x0on inode 217316006462 bad CRC for inode 861144976063
bad magic number0x0on inode 861144976063 bad version number0x0on inode 861144976063 bad version number0x0on inode 217316006462 inode identifier 0 mismatch on inode 217316006462 bad CRC for inode 217316006463
bad magic number0x0on inode 217316006463 inode identifier 0 mismatch on inode 861144976063 bad version number0x0on inode 217316006463 inode identifier 0 mismatch on inode 217316006463
Quoted 2 lines
Is there anything else to do?
I think it's hard to say what might be going on here without some view into the state of the fs. Perhaps some large chunk of the fs has been zeroed given all of the zeroed out on-disk inode fields? We'd probably want to see a metadump of the fs to get a closer look.
Brian
Quoted 7 lines
Signature · 6 lines
------------------------------------------------------------------------ Emmanuel Florac | Direction technique | Intellique | <[email protected]> | +33 1 78 94 84 02 ------------------------------------------------------------------------
Le Fri, 1 Nov 2019 06:45:51 -0400
Brian Foster <[email protected]> écrivait:
Quoted 5 lines
I think it's hard to say what might be going on here without some view into the state of the fs. Perhaps some large chunk of the fs has been zeroed given all of the zeroed out on-disk inode fields? We'd probably want to see a metadump of the fs to get a closer look.
Alas, the metadump is 28 GB... (this is a 500 TB filesystem). So far it seems to behave better with no background RAID controller operation.
Signature · 6 lines
------------------------------------------------------------------------
Emmanuel Florac | Direction technique
| Intellique
| <[email protected]>
| +33 1 78 94 84 02
------------------------------------------------------------------------Quoted 11 lines · Emmanuel Florac
Le Fri, 1 Nov 2019 06:45:51 -0400
Brian Foster <[email protected]> écrivait:Quoted 5 lines
I think it's hard to say what might be going on here without some view into the state of the fs. Perhaps some large chunk of the fs has been zeroed given all of the zeroed out on-disk inode fields? We'd probably want to see a metadump of the fs to get a closer look.
Alas, the metadump is 28 GB... (this is a 500 TB filesystem). So far it seems to behave better with no background RAID controller operation.
They sometimes compress quite well FWIW.
-Eric