From: Nathan Scott <nathans@sgi.com>
To: "Prakash K. Cheemplavam" <prakashkc@gmx.de>
Cc: William Lee Irwin III <wli@holomorphy.com>,
Jan De Luyck <lkml@kcore.org>,
linux-kernel@vger.kernel.org, linux-xfs@oss.sgi.com
Subject: Re: [2.6.10-rc2] XFS filesystem corruption
Date: Wed, 24 Nov 2004 08:27:36 +1100 [thread overview]
Message-ID: <20041124082736.E6205230@wobbly.melbourne.sgi.com> (raw)
In-Reply-To: <41A30D3E.9090506@gmx.de>; from prakashkc@gmx.de on Tue, Nov 23, 2004 at 11:13:18AM +0100
On Tue, Nov 23, 2004 at 11:13:18AM +0100, Prakash K. Cheemplavam wrote:
>
> While we are at it: Is xfs known to be broken while preempt is on? (Esp
Nope.
> using ck's preemp big kernel lock?) I got following using a raid0 setup
> with xfs. I thought it would be a driver issue, but reformatting to ext3
> the stripe array runs now w/o probs for a few days. (xfs crapped out
> after a few hours on heavy disk activity.)
> ...
> Nov 21 10:10:45 tachyon end_request: I/O error, dev sdb, sector 10480855
> Nov 21 10:10:45 tachyon I/O error in filesystem ("md0") meta-data dev
> md0 block 0x13fd990 ("xfs_trans_read_buf") error 5 buf count 8192
This looks like your driver passed an error back up to the
filesystem while it was doing metadata IO and XFS chose to
shut it down to prevent further damage. It's unlikely to
be a preempt/xfs problem. Possibly hardware. Did you see
any of those device errors since switching to ext3?
cheers.
--
Nathan
next prev parent reply other threads:[~2004-11-23 21:30 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-22 14:30 [2.6.10-rc2] XFS filesystem corruption Jan De Luyck
2004-11-22 15:51 ` William Lee Irwin III
2004-11-23 10:13 ` Prakash K. Cheemplavam
2004-11-23 19:13 ` Lee Revell
2004-11-23 19:22 ` Prakash K. Cheemplavam
2004-11-23 21:27 ` Nathan Scott [this message]
2004-11-24 8:04 ` Prakash K. Cheemplavam
2004-11-24 12:50 ` Eric Sandeen
2004-11-25 7:28 ` Prakash K. Cheemplavam
2004-11-22 23:34 ` Eric Sandeen
2004-11-23 6:36 ` Jan De Luyck
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=20041124082736.E6205230@wobbly.melbourne.sgi.com \
--to=nathans@sgi.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-xfs@oss.sgi.com \
--cc=lkml@kcore.org \
--cc=prakashkc@gmx.de \
--cc=wli@holomorphy.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.