| To: | jasonw@xxxxxxxxxxxxxxxxxxxxxxxx |
|---|---|
| Subject: | Re: Disappearing /, /home |
| From: | Jim Eshleman <jce0@xxxxxxxxxx> |
| Date: | Wed, 06 Feb 2002 09:13:50 -0500 |
| Cc: | linux-xfs@xxxxxxxxxxx |
| References: | <20020205220806.GA7060@xxxxxxxxxxxxxx> <1012949128.5437.16.camel@xxxxxxxxxxxxxxxxxxxxxx> <15456.34610.41991.980114@xxxxxxxxx> |
| Sender: | owner-linux-xfs@xxxxxxxxxxx |
| User-agent: | Mozilla/5.0 (X11; U; Linux i686; en-US; rv:0.9.7) Gecko/20011226 |
Jason White wrote: So, to summarize the current state of XFS, would I be correcting in saying the following? The data-corrupting bug (overwriting the first blocks of an XFS file system upon forced shutdown) has been fixed. There are still some problems with spurious forced shutdowns, however, that remain to be traced. I think there are still difficulties with kernel Oopses as well again without a clear cause? Beyond this, there are compatibility issues with LVM that are still being addressed.From reading the list, this at least is my impression of where theongoing issues lie. Of course it is probably also true that XFS is working reliably for most users. Well Jason, I'm quite happy with vanilla 2.4.17 + xfs-2.4.17-split, dated 22 Jan, I think. I've almost 300G now on top of LVM on top of hardware raid on a very busy 8-way 8.5G production mail server and haven't seen any funnies yet. Just a data point, and thanks to the XFS team. Jim |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Big file support, Alexey Tsiban |
|---|---|
| Next by Date: | Re: Big file support, Seth Mos |
| Previous by Thread: | Re: Disappearing /, /home, Jason White |
| Next by Thread: | Re: Disappearing /, /home, Marcin Zieba |
| Indexes: | [Date] [Thread] [Top] [All Lists] |