| To: | Gorazd Golob <gorazd.golob@xxxxxxxxxxxx> |
|---|---|
| Subject: | Re: Error 990 |
| From: | Justin Piszcz <jpiszcz@xxxxxxxxxxxxxxx> |
| Date: | Tue, 11 Apr 2006 07:31:12 -0400 (EDT) |
| Cc: | Chris Wedgwood <cw@xxxxxxxx>, linux-xfs@xxxxxxxxxxx |
| In-reply-to: | <1144748564.10995.16.camel@xxxxxxxxxxxxxxxxxx> |
| References: | <1144744915.10995.14.camel@xxxxxxxxxxxxxxxxxx> <20060411091157.GB4359@xxxxxxxxxxxxxxxxxxxxx> <1144748564.10995.16.camel@xxxxxxxxxxxxxxxxxx> |
| Sender: | linux-xfs-bounce@xxxxxxxxxxx |
There is an option when you make the filesystem so it does not fill it
with NULL's when it fsck's the filesystem I believe...
On Tue, 11 Apr 2006, Gorazd Golob wrote: On Tue, 2006-04-11 at 02:11 -0700, Chris Wedgwood wrote:On Tue, Apr 11, 2006 at 10:41:55AM +0200, Gorazd Golob wrote:What can be wrong - filesystem is XFS on 2.6.15.6 - x86_64.990 is EFSCORRUPTED (nothing outside of XFS uses that error code hence the abiguity at times) try xfs_repairxfs_repair filled some of files with NULLs. Very uncool ;) |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: Error 990, Gorazd Golob |
|---|---|
| Next by Date: | Re: Error 990, Chris Wedgwood |
| Previous by Thread: | Re: Error 990, Gorazd Golob |
| Next by Thread: | Re: Error 990, Nathan Scott |
| Indexes: | [Date] [Thread] [Top] [All Lists] |