|To:||Eric Sandeen <sandeen@xxxxxxx>|
|Subject:||Re: [2.6.10-rc2] XFS filesystem corruption|
|From:||"Prakash K. Cheemplavam" <prakashkc@xxxxxx>|
|Date:||Thu, 25 Nov 2004 08:28:38 +0100|
|Cc:||Nathan Scott <nathans@xxxxxxx>, linux-kernel@xxxxxxxxxxxxxxx, linux-xfs@xxxxxxxxxxx|
|References:||<200411221530.30325.lkml@xxxxxxxxx> <20041122155106.GG2714@xxxxxxxxxxxxxx> <41A30D3E.9090506@xxxxxx> <20041124082736.E6205230@xxxxxxxxxxxxxxxxxxxxxxxx> <41A44071.9040101@xxxxxx> <41A48395.60100@xxxxxxx>|
|User-agent:||Mozilla Thunderbird 0.9 (X11/20041114)|
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?
|<Prev in Thread]||Current Thread||[Next in Thread>|
|Previous by Date:||Re: Is xfsdump operation atomic?, Michael Locher|
|Next by Date:||Re: [REPOST] [PATCH] fs/xfs/linux-2.6/kmem.c, Miquel van Smoorenburg|
|Previous by Thread:||Re: [2.6.10-rc2] XFS filesystem corruption, Eric Sandeen|
|Next by Thread:||Re: [2.6.10-rc2] XFS filesystem corruption, Eric Sandeen|
|Indexes:||[Date] [Thread] [Top] [All Lists]|