| To: | "'Russell Cattelan'" <cattelan@xxxxxxxxxxx> |
|---|---|
| Subject: | RE: Oops removing files on a full f/s |
| From: | "Juha Saarinen" <juha@xxxxxxxxxxxx> |
| Date: | Wed, 20 Jun 2001 17:41:51 +1200 |
| Cc: | "'Keith Owens'" <kaos@xxxxxxxxxxxxxxxxx>, "'Steve Lord'" <lord@xxxxxxx>, "'XFS Mailing List'" <linux-xfs@xxxxxxxxxxx> |
| Importance: | Normal |
| In-reply-to: | <3B2EE9A9.B1C4DBCC@thebarn.com> |
| Sender: | owner-linux-xfs@xxxxxxxxxxx |
Well, looks like you should scratch RH GCC 2.96-85 from the XFS compilers list... Those oopses appear to have been caused by file system corruption (in /var/log/ksymoops this time, according to xfs_repair). Once I fixed that, the oopses stopped. Then I recompiled the CVS code (from this morning NZ time) with kgcc, and the system's been rock-solid despite plenty of fsstress abuse. Am I reading it right, though, that XFS doesn't seem to handle corrupt file systems very well? Is there any way to test this, with the kgcc-compiled kernel? -- Juha |
| Previous by Date: | TAKE - libacl - acl_get_qualifier() change, Timothy Shimmin |
|---|---|
| Next by Date: | Re: nVidia driver incompatible, Sean Swallow |
| Previous by Thread: | Re: Oops removing files on a full f/s, Russell Cattelan |
| Next by Thread: | Re: Oops removing files on a full f/s, Christopher McCrory |
| Indexes: | [Date] [Thread] [Top] [All Lists] |