public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: David Chinner <dgc@sgi.com>
To: Chris Eddington <chrise@synplicity.com>
Cc: "xfs@oss.sgi.com" <xfs@oss.sgi.com>
Subject: Re: xfs_repair - what's the damage?
Date: Wed, 14 Nov 2007 08:08:53 +1100	[thread overview]
Message-ID: <20071113210853.GY995458@sgi.com> (raw)
In-Reply-To: <4739F2CD.2020800@synplicity.com>

On Tue, Nov 13, 2007 at 10:54:05AM -0800, Chris Eddington wrote:
> Hi,
> 
> Can someone point me to instructions on how to understand the scope of
> damage to this filesystem based on the output from xfs_repair below?
> What is it repairing, and what data is lost?  I'm not sure how to interpret
> these messages or where to go to find out.

Looks like you had something write crap over various parts of
the filesystem. Both AG 2 and ag 24 have header problems, and
then there's a bunch of freespace and allocated inode problems
because the indexes were lost due ot the header corruption.

Who knows how much else is broken - it depends on how much
bad data got written into the filesystem. best you can do is
to run xfs_repair and sift through the debris in lost+found
and try to work out what the lost data is...

As I always ask - how did the filesytem get into this state?

Cheers,

Dave.
-- 
Dave Chinner
Principal Engineer
SGI Australian Software Group

  reply	other threads:[~2007-11-13 21:09 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-11-13 18:54 xfs_repair - what's the damage? Chris Eddington
2007-11-13 21:08 ` David Chinner [this message]
2007-11-17  5:13   ` Chris Eddington

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=20071113210853.GY995458@sgi.com \
    --to=dgc@sgi.com \
    --cc=chrise@synplicity.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