Re: Filesystem still has errors

[Eric Sandeen <sandeen@redhat.com>]

Raimund andersen wrote:
> Hi,
> 
> I'm using ext4 as a root fs on my 2.6.28-gentoo-r1 (x86_64), and after a few
> locks due to X misconfiguration, which forced me to hard-reset, I sometimes get
> the 'no space left on device' error message when trying to create new files. But
> that's not true:
> 
> #>df
> Filesystem           1K-blocks      Used Available Use% Mounted on
> rootfs               201585632  16234952 175110680   9% /
> /dev/root            201585632  16234952 175110680   9% /
> (...)
> 
> #>df -i
> Filesystem            Inodes   IUsed   IFree IUse% Mounted on
> rootfs               12804096  520672 12283424    5% /
> /dev/root            12804096  520672 12283424    5% /
> (...)
> 

snip ...

> The same is true with putting a '/forcefsck'; the filesystem is checked and no
> error message appears.
> But when invoking fsck manually after full bootup, fs is still corrupted. 
> 
> So what should I do?

You should expect that checking a live filesystem will produce errors,
actually.  So don't worry about that.  The filesystem is not quiesced,
and it's not consistent.  That is to be expected, and it's why you see
the different behavior w/ forcefsck vs. e2fsck -n on the live fs.

As for the spurious ENOSPC, I'm not certain.  Do you still get the error?

> Any help is greatly apreciated.
> 
> Raimund