From: Dave Chinner <david@fromorbit.com>
To: Zachary Kotlarek <zach@kotlarek.com>
Cc: xfs@oss.sgi.com
Subject: Re: Files with non-ASCII names inaccessible after xfs_repair
Date: Tue, 14 Jan 2014 06:27:32 +1100 [thread overview]
Message-ID: <20140113192732.GI3469@dastard> (raw)
In-Reply-To: <E2EE0AEA-ED22-4D3B-8550-88F2ED1F8314@kotlarek.com>
On Sun, Jan 12, 2014 at 07:47:29PM -0800, Zachary Kotlarek wrote:
>
> On Jan 12, 2014, at 7:19 PM, Dave Chinner <david@fromorbit.com>
> wrote:
>
> > IOWs, xfs-repair wrote new contents to those blocks, and now the
> > kernel cannot read them from disk.
>
>
> Sure, but I don’t understand why it would have re-written them
> in the first place. I know corruption happens, but this seems
> awfully pattern-tastic to be random errors.
Neither do I, but I'm trying to find out.
> > Try using xfs_db to read and parse the blocks that the
> > fielsystem is choking on. If it can't read them from xfs_db,
> > then there's something gone wrong below XFS. If you can read
> > them, use xfs_db to parse the block as a directory block and see
> > what the raw directory entries are the block contains....
Based on the xfs-db output, these warnings are not related to the
problem you are seeing. It's likely just a result of readahead being
cancelled due to load, and the error set by the DM layer not being
handled properly.
So, you need to find the inode number of a directory with a corrupt
entry, and dump the inode and any data fork blocks that it belongs
to with xfs_db similar to what you have just done.
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:[~2014-01-13 19:27 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-12 13:28 Files with non-ASCII names inaccessible after xfs_repair Zachary Kotlarek
2014-01-12 18:47 ` Stan Hoeppner
2014-01-12 19:53 ` Zachary Kotlarek
2014-01-13 1:50 ` Dave Chinner
2014-01-13 2:36 ` Zachary Kotlarek
2014-01-13 3:19 ` Dave Chinner
2014-01-13 3:47 ` Zachary Kotlarek
2014-01-13 19:27 ` Dave Chinner [this message]
2014-01-13 23:07 ` Zachary Kotlarek
2014-01-14 2:24 ` Dave Chinner
2014-01-14 3:12 ` Zachary Kotlarek
2014-01-15 1:53 ` Dave Chinner
2014-01-15 1:59 ` Zachary Kotlarek
2014-01-15 3:48 ` Dave Chinner
2014-01-15 5:30 ` Zachary Kotlarek
2014-01-15 6:37 ` Dave Chinner
2014-01-15 8:21 ` Zachary Kotlarek
2014-01-15 15:54 ` Eric Sandeen
2014-01-15 21:08 ` Dave Chinner
2014-01-16 20:55 ` Michael Weissenbacher
2014-01-16 21:11 ` Shaun Gosse
2014-01-13 15:40 ` Michael Weissenbacher
2014-01-13 18:33 ` Zachary Kotlarek
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=20140113192732.GI3469@dastard \
--to=david@fromorbit.com \
--cc=xfs@oss.sgi.com \
--cc=zach@kotlarek.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.