XFS corrupt after RAID failure and resync

Dave Chinner david at fromorbit.com
Tue Jan 6 18:27:29 CST 2015


On Wed, Jan 07, 2015 at 10:47:00AM +1100, David Raffelt wrote:
> Hi Brain,
> Below is the root inode data. I'm currently running xfs_metadump and will
> send you a link to the file.
> Cheers!
> David
> 
> 
> 
> 
> xfs_db> sb
> xfs_db> p rootino
> rootino = 1024
> xfs_db> inode 1024
> xfs_db> p
> core.magic = 0
> core.mode = 0
> core.version = 0
> core.format = 0 (dev)

It's a zero'd block. Even an unallocated inode should have the
magic number, inode version and data fork format stamped in it.
This is something we typically see when RAID rebuilds have not
worked correctly, even though they say they were "successful"....

Cheers,

Dave.
-- 
Dave Chinner
david at fromorbit.com



More information about the xfs mailing list