public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Mark Goodwin <goodwinos@gmail.com>
To: xfs@oss.sgi.com
Subject: Re: xfs and raid5 - "Structure needs cleaning for directory open"
Date: Mon, 10 May 2010 16:53:54 +1000	[thread overview]
Message-ID: <4BE7AD82.90300@gmail.com> (raw)
In-Reply-To: <20100510022033.GB7165@dastard>

On 05/10/2010 12:20 PM, Dave Chinner wrote:
> On Sun, May 09, 2010 at 08:48:00PM +0200, Rainer Fuegenstein wrote:
>>
>> today in the morning some daemon processes terminated because of
>> errors in the xfs file system on top of a software raid5, consisting
>> of 4*1.5TB WD caviar green SATA disks.
>
> Reminds me of a recent(-ish) md/dm readahead cancellation fix - that
> would fit the symptoms of (btree corruption showing up under heavy IO
> load but no corruption on disk. However, I can't seem to find any
> references to it at the moment (can't remember the bug title), but
> perhaps your distro doesn't have the fix in it?

If it's the bug that Dave's thinking of, it's an issue with md
error handling and the BIO_UPTODATE flag, see :
http://www.mail-archive.com/linux-raid@vger.kernel.org/msg06628.html

For RHEL, this is addressed in Red Hat BZ 512552
https://bugzilla.redhat.com/show_bug.cgi?id=512552

upstream commit c2b00852fbae4f8c45c2651530ded3bd01bde814

Cheers
-- Mark

_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs

  reply	other threads:[~2010-05-10  6:51 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-05-09 18:48 xfs and raid5 - "Structure needs cleaning for directory open" Rainer Fuegenstein
2010-05-09 19:07 ` Rainer Fuegenstein
2010-05-09 23:35 ` Rainer Fuegenstein
2010-05-10  2:20 ` Dave Chinner
2010-05-10  6:53   ` Mark Goodwin [this message]
2010-05-10 10:22     ` Re[2]: " Rainer Fuegenstein
2010-05-10 14:08       ` Stan Hoeppner
2010-05-17 21:28   ` Doug Ledford
2010-05-17 21:45     ` Dave Chinner
2010-05-17 22:18       ` Doug Ledford
2010-05-17 23:04         ` 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=4BE7AD82.90300@gmail.com \
    --to=goodwinos@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