| To: | David Raffelt <david.raffelt@xxxxxxxxxxxxx> |
|---|---|
| Subject: | Re: XFS corrupt after RAID failure and resync |
| From: | Dave Chinner <david@xxxxxxxxxxxxx> |
| Date: | Wed, 7 Jan 2015 11:27:29 +1100 |
| Cc: | Brian Foster <bfoster@xxxxxxxxxx>, "stefanrin@xxxxxxxxx" <stefanrin@xxxxxxxxx>, "xfs@xxxxxxxxxxx" <xfs@xxxxxxxxxxx> |
| Delivered-to: | xfs@xxxxxxxxxxx |
| In-reply-to: | <CAOFq7B6t8jrBBu81CuT2tqTyPEYROqkCJ4ChnxCtCvMGiGb7wg@xxxxxxxxxxxxxx> |
| References: | <CAOFq7B5PaPCJdAxyYa6feCXgGbkz+1Qs+Gfb2WG=5af=A+WOQg@xxxxxxxxxxxxxx> <44b127de199c445fa12c3b832a05f108@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxx> <CAOFq7B5HnEZFtVvoRORRwOxPhx5Txf9xJW=BG6GFbLMNk+_CEw@xxxxxxxxxxxxxx> <8cc9a649ec2240faa4e38fd742437546@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxx> <CAOFq7B6t8jrBBu81CuT2tqTyPEYROqkCJ4ChnxCtCvMGiGb7wg@xxxxxxxxxxxxxx> |
| User-agent: | Mutt/1.5.21 (2010-09-15) |
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@xxxxxxxxxxxxx |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: [PATCH 17/18] xfs: implement pnfs export operations, Dave Chinner |
|---|---|
| Next by Date: | Re: XFS corrupt after RAID failure and resync, Chris Murphy |
| Previous by Thread: | Re: XFS corrupt after RAID failure and resync, David Raffelt |
| Next by Thread: | Re: XFS corrupt after RAID failure and resync, Brian Foster |
| Indexes: | [Date] [Thread] [Top] [All Lists] |