| To: | Dmitry Nikiforov <dniq@xxxxxxxxxxxxxxx> |
|---|---|
| Subject: | Re: file corruption |
| From: | Chris Wedgwood <cw@xxxxxxxx> |
| Date: | Fri, 2 Apr 2004 00:53:08 -0800 |
| Cc: | Christian Rice <xian@xxxxxxxxxxx>, Dmitry Nikiforov <dniq_kraft@xxxxxxxxxxxxxxx>, linux-xfs@xxxxxxxxxxx |
| In-reply-to: | <406D0AE4.2030203@xxxxxxxxxxxxxxx> |
| References: | <406AF7B6.6030405@xxxxxxxxxxxxxxx> <20040402001801.GA24900@xxxxxxxxxxxxxxxxxxxxxxx> <406CB95B.4040500@xxxxxxxxxxxxxxx> <20040402011618.GA25511@xxxxxxxxxxxxxxxxxxxxxxx> <406CC518.1090204@xxxxxxxxxxxxxxx> <20040402015022.GA25936@xxxxxxxxxxxxxxxxxxxxxxx> <406CCF08.9020309@xxxxxxxxxxx> <406CD88F.3070900@xxxxxxxxxxxxxxx> <20040402044712.GB27240@xxxxxxxxxxxxxxxxxxxxxxx> <406D0AE4.2030203@xxxxxxxxxxxxxxx> |
| Sender: | linux-xfs-bounce@xxxxxxxxxxx |
On Fri, Apr 02, 2004 at 12:40:36AM -0600, Dmitry Nikiforov wrote: > It appears that XFS does not guarantee the data consistency, and > even worse than that: it will never tell you that some files are > broken. I'd rather have a longer fsck which tells me which files are > broken, even if it can't fix them. ext2 sounds like a good solution then. > Thanks for clarification, though! :) At least now I know _why_ XFS > shouldn't be used on a production server :) You're most welcome. Best of luck with reiserfs. --cw |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: file corruption, Chris Wedgwood |
|---|---|
| Next by Date: | Re: file corruption, Ethan Benson |
| Previous by Thread: | Re: file corruption, Dmitry Nikiforov |
| Next by Thread: | Re: file corruption, Ethan Benson |
| Indexes: | [Date] [Thread] [Top] [All Lists] |