From: Dave Chinner <david@fromorbit.com>
To: Keith Keller <kkeller@wombat.san-francisco.ca.us>
Cc: linux-xfs@oss.sgi.com
Subject: Re: xfs_repair misses an fs error?
Date: Wed, 17 Apr 2013 02:25:57 +1000 [thread overview]
Message-ID: <20130416162557.GD13938@destitution> (raw)
In-Reply-To: <k5gu3axace.ln2@goaway.wombat.san-francisco.ca.us>
On Mon, Apr 15, 2013 at 04:47:32PM -0700, Keith Keller wrote:
> Hi all,
>
> I recently had a filesystem stop, and went through the usual umount,
> mount, umount, xfs_repair path. xfs_repair didn't find any errors, but
> I noticed that I was still getting some strange issues where a file in a
> directory didn't have an inode and was resulting in IO errors. Thinking
> to address the problem later, I moved the directory to a different
> location on the filesystem so that future backups could proceed
> normally.
>
> Later, in an attempt to collect log errors, I re-ran xfs_repair on the
> filesystem. It then found errors and corrected them, and on remount, I
> found that the directory in question was repaired and no longer had a
> file entry with no inode. (So I can't reproduce that output; I didn't
> save it, thinking that the second xfs_repair wouldn't fix the issue, and
> I'd generate it again before posting.)
>
> Has anyone else seen a situation where xfs_repair misses a filesystem
> problem, but then finds it if a file or directory is moved? And more
Not recently. What version of xfs_repair are you using?
> generally, is there a way to use xfs_db or similar to try to find other
> inodes that might be causing similar problems?
xfs_repair -n is the usual way to find broken stuff without
modifying anything....
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:[~2013-04-16 16:25 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-15 23:47 xfs_repair misses an fs error? Keith Keller
2013-04-16 16:25 ` Dave Chinner [this message]
2013-04-16 18:44 ` Keith Keller
2013-04-16 19:19 ` Roger Willcocks
2013-04-16 22:05 ` 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=20130416162557.GD13938@destitution \
--to=david@fromorbit.com \
--cc=kkeller@wombat.san-francisco.ca.us \
--cc=linux-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.