| To: | "Prakash K. Cheemplavam" <prakashkc@xxxxxx> |
|---|---|
| Subject: | Re: [2.6.10-rc2] XFS filesystem corruption |
| From: | Eric Sandeen <sandeen@xxxxxxx> |
| Date: | Wed, 24 Nov 2004 06:50:29 -0600 |
| Cc: | Nathan Scott <nathans@xxxxxxx>, linux-kernel@xxxxxxxxxxxxxxx, linux-xfs@xxxxxxxxxxx |
| In-reply-to: | <41A44071.9040101@xxxxxx> |
| References: | <200411221530.30325.lkml@xxxxxxxxx> <20041122155106.GG2714@xxxxxxxxxxxxxx> <41A30D3E.9090506@xxxxxx> <20041124082736.E6205230@xxxxxxxxxxxxxxxxxxxxxxxx> <41A44071.9040101@xxxxxx> |
| Sender: | linux-xfs-bounce@xxxxxxxxxxx |
| User-agent: | Mozilla Thunderbird 0.9 (Macintosh/20041103) |
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 |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: Is xfsdump operation atomic?, Olaf Frączyk |
|---|---|
| Next by Date: | 2.6.9 Oops: Major problems with XFS and ext3 (VFS related?), Anders Saaby |
| Previous by Thread: | Re: [2.6.10-rc2] XFS filesystem corruption, Prakash K. Cheemplavam |
| Next by Thread: | Re: [2.6.10-rc2] XFS filesystem corruption, Prakash K. Cheemplavam |
| Indexes: | [Date] [Thread] [Top] [All Lists] |