From: Dave Chinner <david@fromorbit.com>
To: Alex Lyakas <alex@zadarastorage.com>
Cc: Brian Foster <bfoster@redhat.com>,
Eric Sandeen <sandeen@sandeen.net>,
xfs@oss.sgi.com
Subject: Re: XFS corruption
Date: Wed, 24 Dec 2014 07:36:39 +1100 [thread overview]
Message-ID: <20141223203639.GE4521@dastard> (raw)
In-Reply-To: <CAOcd+r3Y3ZcnzcdXtk58oSKq7okN0V8fRHfd-phqJ+OwuGZ-sQ@mail.gmail.com>
On Tue, Dec 23, 2014 at 11:57:13AM +0200, Alex Lyakas wrote:
> Hi Dave,
>
> On Tue, Dec 23, 2014 at 2:39 AM, Dave Chinner <david@fromorbit.com> wrote:
> > commit 40194ecc6d78327d98e66de3213db96ca0a31e6f
> > Author: Ben Myers <bpm@sgi.com>
> > Date: Fri Dec 6 12:30:11 2013 -0800
> >
> > xfs: reinstate the ilock in xfs_readdir
> >
> > Although it was removed in commit 051e7cd44ab8, ilock needs to be taken in
> > xfs_readdir because we might have to read the extent list in from disk. This
> > keeps other threads from reading from or writing to the extent list while it i
> > being read in and is still in a transitional state.
> >
> > This has been associated with "Access to block zero" messages on directories
> > with large numbers of extents resulting from excessive filesytem fragmentation
> > as well as extent list corruption. Unfortunately no test case at this point.
> >
> > Signed-off-by: Ben Myers <bpm@sgi.com>
> > Reviewed-by: Dave Chinner <dchinner@redhat.com>
> >
> > Seems to match the behaviour being seen.
> >
> > Alex, what type of inode is the one that is reporting the "access to
> > block zero" errors?
> I have just searched the relevant file system for this inode, but such
> inode was not found:(
> # find /export/XXX -mount -inum 1946454529
> did not find anything. Perhaps it got deleted since the incident.
It probably got cleared by xfs_repair because it was corrupt....
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-12-23 20:36 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-21 11:42 XFS corruption Alex Lyakas
2014-12-21 18:13 ` Eric Sandeen
2014-12-21 23:08 ` Dave Chinner
2014-12-22 10:09 ` Alex Lyakas
2014-12-22 14:42 ` Brian Foster
2014-12-23 0:39 ` Dave Chinner
2014-12-23 9:57 ` Alex Lyakas
2014-12-23 20:36 ` Dave Chinner [this message]
-- strict thread matches above, loose matches on Subject: below --
2015-09-03 11:09 xfs corruption Danny Shavit
2015-09-03 13:22 ` Eric Sandeen
2015-09-03 14:26 ` Danny Shavit
2015-09-03 14:55 ` Eric Sandeen
2015-09-03 16:14 ` Eric Sandeen
2015-09-06 10:19 ` Alex Lyakas
2015-09-06 21:56 ` Eric Sandeen
2015-09-07 8:30 ` Alex Lyakas
2016-02-24 6:12 XFS Corruption fangchen sun
2016-02-24 22:23 ` Eric Sandeen
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=20141223203639.GE4521@dastard \
--to=david@fromorbit.com \
--cc=alex@zadarastorage.com \
--cc=bfoster@redhat.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox