From: David Chinner <dgc@sgi.com>
To: Eric Sandeen <sandeen@sandeen.net>
Cc: Greg Martyn <greg.martyn@gmail.com>, xfs@oss.sgi.com
Subject: Re: mount: /dev/md0: can't read superblock
Date: Mon, 22 Oct 2007 10:52:58 +1000 [thread overview]
Message-ID: <20071022005258.GX995458@sgi.com> (raw)
In-Reply-To: <471BEDCD.3040104@sandeen.net>
On Sun, Oct 21, 2007 at 07:24:45PM -0500, Eric Sandeen wrote:
> Greg Martyn wrote:
> > Hi all,
> > After running "xfs_fsr -v /home", I got a bunch of error messages
> > saying that certain files (/home/.[three letters that i forgot])
> > couldn't be removed. After that, my system stopped working properly,
> > so I restarted. Now:
> >
> > [root@localhost ~]# mount /dev/md0 /home/
> > mount: /dev/md0: can't read superblock
> >
> > uh oh.
>
> dmesg says it's corrupted.
>
> You should probably run repair on it. But being raid, if something went
> wrong w/ the raid, that could make it worse... run xfs_repair -n and see
> what it *would* fix.
xfs_repair does not check everything in the filesystem - some things it
simply rebuilds - like the free space btrees. you want to run xfs_check
to determine if the free space btrees are corrupt on disk or not.... ;)
Cheers,
Dave.
--
Dave Chinner
Principal Engineer
SGI Australian Software Group
next prev parent reply other threads:[~2007-10-22 0:53 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-21 1:02 mount: /dev/md0: can't read superblock Greg Martyn
2007-10-21 23:27 ` David Chinner
2007-10-22 0:24 ` Eric Sandeen
2007-10-22 0:52 ` David Chinner [this message]
2007-10-22 3:47 ` Greg Martyn
2007-10-22 11:16 ` Justin Piszcz
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=20071022005258.GX995458@sgi.com \
--to=dgc@sgi.com \
--cc=greg.martyn@gmail.com \
--cc=sandeen@sandeen.net \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.