Message-ID: <41A48395.60100@sgi.com>
Date: Wed, 24 Nov 2004 06:50:29 -0600
From: Eric Sandeen <sandeen@sgi.com>
User-Agent: Mozilla Thunderbird 0.9 (Macintosh/20041103)
MIME-Version: 1.0
To: "Prakash K. Cheemplavam" <prakashkc@gmx.de>
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
References: <200411221530.30325.lkml@kcore.org> <20041122155106.GG2714@holomorphy.com> <41A30D3E.9090506@gmx.de> <20041124082736.E6205230@wobbly.melbourne.sgi.com> <41A44071.9040101@gmx.de>
In-Reply-To: <41A44071.9040101@gmx.de>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 937
Lines: 24

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.

-Eric
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/