From: "Prakash K. Cheemplavam" <prakashkc@gmx.de>
To: Eric Sandeen <sandeen@sgi.com>
Cc: Nathan Scott <nathans@sgi.com>,
linux-kernel@vger.kernel.org, linux-xfs@oss.sgi.com
Subject: Re: [2.6.10-rc2] XFS filesystem corruption
Date: Thu, 25 Nov 2004 08:28:38 +0100 [thread overview]
Message-ID: <41A589A6.6020406@gmx.de> (raw)
In-Reply-To: <41A48395.60100@sgi.com>
[-- Attachment #1: Type: text/plain, Size: 875 bytes --]
Eric Sandeen schrieb:
> Prakash K. Cheemplavam wrote:
>
>> Nathan Scott schrieb:
>>
>>> Did you see
>>> any of those device errors since switching to ext3?
>>
>>
>>
>> No. That's why I am wondering. I read about such errors like I got
>> before in lkml and usually they were not fs related but libata siimage
>> driver related. It could be just a coincidence that it came up with
>> xfs, but till now (I guess 5 days now, though not 24/7 running) ext3
>> is behaving nicely.
>
>
> It's almost certainly not a filesystem problem, but an IO layer problem.
> Maybe you only see it with xfs due to different disk IO patterns with
> xfs vs. ext3... the two will certainly be allocating & writing to the
> disk in different ways.
Hmm, OK. When I have some hd space again. I might try to reproduce this
error. Whom should I bug then if it reappears?
Cheers,
Prakash
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2004-11-25 7:28 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
2004-11-24 8:04 ` Prakash K. Cheemplavam
2004-11-24 12:50 ` Eric Sandeen
2004-11-25 7:28 ` Prakash K. Cheemplavam [this message]
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=41A589A6.6020406@gmx.de \
--to=prakashkc@gmx.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-xfs@oss.sgi.com \
--cc=nathans@sgi.com \
--cc=sandeen@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