From: David Chinner <dgc@sgi.com>
To: Greg Martyn <greg.martyn@gmail.com>
Cc: xfs@oss.sgi.com
Subject: Re: mount: /dev/md0: can't read superblock
Date: Mon, 22 Oct 2007 09:27:43 +1000 [thread overview]
Message-ID: <20071021232743.GU995458@sgi.com> (raw)
In-Reply-To: <6e0c99d0710201802v2f41577dv38281b936a2389bf@mail.gmail.com>
On Sat, Oct 20, 2007 at 09:02:14PM -0400, 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:
A corrupted freespace btree, by the look of it.
What errors occurred you syslog when the system started playing
up? I/O errors? Corruption errors?
xfs_repair will probably be the only thing you can do here to correct
the problem....
Cheers,
Dave.
--
Dave Chinner
Principal Engineer
SGI Australian Software Group
next prev parent reply other threads:[~2007-10-21 23:28 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 [this message]
2007-10-22 0:24 ` Eric Sandeen
2007-10-22 0:52 ` David Chinner
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=20071021232743.GU995458@sgi.com \
--to=dgc@sgi.com \
--cc=greg.martyn@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 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.