| To: | Hendrik Visage <hvisage@xxxxxxxxxxxxxx> |
|---|---|
| Subject: | Re: [Evms-devel] XFS + evms + x86_64 + network hangs... |
| From: | Nathan Scott <nathans@xxxxxxx> |
| Date: | Tue, 1 Jun 2004 19:30:38 +1000 |
| Cc: | Jord Tanner <jord@xxxxxxxxxxxxx>, evms-devel@xxxxxxxxxxxxxxxxxxxxx, linux-xfs@xxxxxxxxxxx |
| In-reply-to: | <20040601083234.GB4347@hvs.envisage.co.za>; from hvisage@envisage.co.za on Tue, Jun 01, 2004 at 10:32:34AM +0200 |
| References: | <40BB48A3.1050205@indygecko.com> <20040601083234.GB4347@hvs.envisage.co.za> |
| Sender: | linux-xfs-bounce@xxxxxxxxxxx |
| User-agent: | Mutt/1.2.5i |
On Tue, Jun 01, 2004 at 10:32:34AM +0200, Hendrik Visage wrote: > On Mon, May 31, 2004 at 08:00:51AM -0700, Jord Tanner wrote: > > > > This may or may not be related, however, I had trouble running XFS on > > top of LVM2 on top of linux RAID0, running on gentoo 2.6.5 amd64. The > > problems went away after switching to JFS. I was experiencing database > > Beware that I had troubles with JFS around 2.6.0-rc? which made me test XFS > ;^) > > but thanx, so I'm now feeling better that I'm not the only person that'll > convert away from > XFS for the moment... We (XFS folks) would really like to hear if anyone has a reproducible test case that shows us how to produce this corruption. Particularly if its with a stock kernel from kernel.org; that'd be a _really_ huge help to us. thanks. -- Nathan |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: [Evms-devel] XFS + evms + FS Corruption, Jan De Landtsheer |
|---|---|
| Next by Date: | Re: [Evms-devel] XFS + evms + x86_64 + network hangs..., Jan De Landtsheer |
| Previous by Thread: | Re: [Evms-devel] XFS + evms + FS Corruption, Jan De Landtsheer |
| Next by Thread: | Re: [Evms-devel] XFS + evms + x86_64 + network hangs..., Jan De Landtsheer |
| Indexes: | [Date] [Thread] [Top] [All Lists] |