From: Dave Chinner <david@fromorbit.com>
To: David Raffelt <david.raffelt@florey.edu.au>
Cc: "stefanrin@gmail.com" <stefanrin@gmail.com>,
Brian Foster <bfoster@redhat.com>,
"xfs@oss.sgi.com" <xfs@oss.sgi.com>
Subject: Re: XFS corrupt after RAID failure and resync
Date: Wed, 7 Jan 2015 11:27:29 +1100 [thread overview]
Message-ID: <20150107002729.GB25000@dastard> (raw)
In-Reply-To: <CAOFq7B6t8jrBBu81CuT2tqTyPEYROqkCJ4ChnxCtCvMGiGb7wg@mail.gmail.com>
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@fromorbit.com
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2015-01-07 0:27 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-06 6:12 XFS corrupt after RAID failure and resync David Raffelt
2015-01-06 12:47 ` Brian Foster
[not found] ` <44b127de199c445fa12c3b832a05f108@000s-ex-hub-qs1.unimelb.edu.au>
2015-01-06 20:34 ` David Raffelt
2015-01-06 23:16 ` Brian Foster
[not found] ` <8cc9a649ec2240faa4e38fd742437546@000S-EX-HUB-NP2.unimelb.edu.au>
2015-01-06 23:47 ` David Raffelt
2015-01-07 0:27 ` Dave Chinner [this message]
2015-01-07 16:16 ` Brian Foster
2015-01-07 2:35 ` Chris Murphy
-- strict thread matches above, loose matches on Subject: below --
2015-01-08 8:09 Chris Murphy
2015-01-06 5:39 David Raffelt
2015-01-06 12:36 ` Stefan Ring
2015-01-06 12:41 ` Brian Foster
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20150107002729.GB25000@dastard \
--to=david@fromorbit.com \
--cc=bfoster@redhat.com \
--cc=david.raffelt@florey.edu.au \
--cc=stefanrin@gmail.com \
--cc=xfs@oss.sgi.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox