Theres so many errors in that statement I don't even know where
to start correcting it!
Must have been thinking of something else...
On Wed, 12 Apr 2006, Nathan Scott wrote:
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
|