From: Dave Chinner <david@fromorbit.com>
To: Nick Hollingsworth <nick.hollingsworth@neulion.com>
Cc: xfs@oss.sgi.com
Subject: Re: XFS restored to lost and found
Date: Fri, 20 Apr 2012 18:21:27 +1000 [thread overview]
Message-ID: <20120420082127.GF9541@dastard> (raw)
In-Reply-To: <4F90F45F.2010507@neulion.com>
On Thu, Apr 19, 2012 at 10:30:07PM -0700, Nick Hollingsworth wrote:
> Hi all,
>
> So I've managed to corrupt an XFS files system running on software
> RAID. How exactly I'm not sure....it may have been when using CentOS
> rescue when trying to get the system to boot.
>
> Using xfs_repair with various options I've managed to get the FS to
> a state where it'll mount but there are no directories only inode
> numbers in the lost and found directory.
Sounds like the root directory got corrupted/overwritten by
something and so the entire directory heirarchy got moved into
lost+found. The inode numbers are used because the names are held
in the directory blocks and they couldn't be found.
> Is there any way to remap these back to directories?
You'll need to examine the contents of every directory and file in
lost+found to work out where they cames from. if you are lucky,
it'll only be the root directory entries that are in lost_found and
the rest of the directories heirarchy will still be intact....
> Any ideas how I may have gotten into this mess?
No. It's too late to try an diagnose now, too.
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:[~2012-04-20 8:21 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-20 5:30 XFS restored to lost and found Nick Hollingsworth
2012-04-20 8:21 ` Dave Chinner [this message]
[not found] ` <4F919A63.7080101@neulion.com>
2012-04-21 0:32 ` Dave Chinner
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=20120420082127.GF9541@dastard \
--to=david@fromorbit.com \
--cc=nick.hollingsworth@neulion.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