xfs
[Top] [All Lists]

Re: Error 990

To: Justin Piszcz <jpiszcz@xxxxxxxxxxxxxxx>
Subject: Re: Error 990
From: Nathan Scott <nathans@xxxxxxx>
Date: Wed, 12 Apr 2006 08:46:47 +1000
Cc: Gorazd Golob <gorazd.golob@xxxxxxxxxxxx>, Chris Wedgwood <cw@xxxxxxxx>, linux-xfs@xxxxxxxxxxx
In-reply-to: <Pine.LNX.4.64.0604110730530.7449@p34>; from jpiszcz@xxxxxxxxxxxxxxx on Tue, Apr 11, 2006 at 07:31:12AM -0400
References: <1144744915.10995.14.camel@xxxxxxxxxxxxxxxxxx> <20060411091157.GB4359@xxxxxxxxxxxxxxxxxxxxx> <1144748564.10995.16.camel@xxxxxxxxxxxxxxxxxx> <Pine.LNX.4.64.0604110730530.7449@p34>
Sender: linux-xfs-bounce@xxxxxxxxxxx
User-agent: Mutt/1.2.5i
On Tue, Apr 11, 2006 at 07:31:12AM -0400, Justin Piszcz wrote:
> 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...

Theres so many errors in that statement I don't even know where
to start correcting it!

> > 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_repair
> >>
> > xfs_repair filled some of files with NULLs. Very uncool ;)

Thats not correct either.

Pretty sure theres a FAQ entry on the notorious "NULL files" issue.
It has nothing to do with xfs_repair or unwritten extents FWIW.

cheers.

-- 
Nathan


<Prev in Thread] Current Thread [Next in Thread>