From: David Chinner <dgc@sgi.com>
To: Enrico Maria Crisostomo <enrico.m.crisostomo@gmail.com>
Cc: xfs@oss.sgi.com
Subject: Re: xfs_repair -d doesn't work
Date: Mon, 11 Sep 2006 11:09:16 +1000 [thread overview]
Message-ID: <20060911010916.GM10950339@melbourne.sgi.com> (raw)
In-Reply-To: <4504A3A9.4080704@gmail.com>
On Mon, Sep 11, 2006 at 01:45:45AM +0200, Enrico Maria Crisostomo wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> Hi.
>
> I'm running a slackware-current with xfsprogs-2.8.10_1. On some
> machine I ran many 2.6.17 kernel and one machine is showing the
> "directory problem": I cannot get rid of many "Filesystem "hda3": XFS
> internal error xfs_da_do_buf(2) at line 2212 of file
> fs/xfs/xfs_da_btree.c. Caller 0xe0ac57d9". As I'm now running
> 2.6.17.13 I think I'm at safe from this bug and the last thing to do
> is... repairing my root filesystem. Unfortunately xfs_repair -d and
> xfs_repair -n does not work, and it returns saying it could not
> initialize XFS library because the filesystem is mounted AND writable.
> What I did:
> - - remounted the file system read only: did not work, not even
> xfs_repair -n, which I expect to succeed always
> - - hacked /etc/mtab to change rw to ro: did not work, error is the same
> as before.
IIRC, we recently updated libxfs to look at /proc/mounts rather than
/etc/mtab to fix these sorts of problems.
As it is, to fix the "directory problem" you need a more recent
xfsprogs (2.8.11 IIRC), so I'd suggest the first thing to do is
upgrade your xfsprogs and try again.
> Can you suggest me some way to repair my file system
You should be able to boot to single user mode, remount the root
filesystem readonly and then "xfs_repair -d <dev>" to fix it. You
need to reboot after doing this....
Cheers,
Dave.
--
Dave Chinner
Principal Engineer
SGI Australian Software Group
prev parent reply other threads:[~2006-09-11 1:10 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-10 23:45 xfs_repair -d doesn't work Enrico Maria Crisostomo
2006-09-11 1:09 ` David Chinner [this message]
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=20060911010916.GM10950339@melbourne.sgi.com \
--to=dgc@sgi.com \
--cc=enrico.m.crisostomo@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