Re: Kernel 2.6.6: Removing the last large file does not reset filesystem properties

[Andrew Morton <akpm@osdl.org>]

John McGowan <jmcgowan@inch.com> wrote:
>
>  1: For the first week, at least, after installing a new kernel, I set the
>      system to force fsck on boot (Fedora Core1, rc.local script to "touch"
>      "/forcefsck").
> 
>   2: Home system, single user. Turn off at night. Turn off when I go to eat
>      lunch. Etc. (reboot at least once each day - silly, but it is a single
>      user system and I don't want to waste electricity and it gives better
>      protection against storms and line spikes).
>      
>   3: Was using Gimp 2.0 and used a tool. Got a 6 Gig swap file in /tmp/gimp2
>      (there must be a problem with that tool). Closed gimp, got rid of the
>      swap file. Upon the next boot I got:
>        FAILED!!
>        Dropping to root command line for system maintenance
>      (such fun ... entering the root password got more error messages about
>      missing programmes such as "id" and "test" - well, I have "/usr" on
>      another partition and it was not mounted).

I think this is really an e2fsck/initscript problem.

fsck saw that there were no large files on the fs, then fixed up the
superblock to say that then returned an exit code which says "I modified
the fs".

The initscripts see that exit code and have a heart attack.

What should happen is that fsck returns an exit code which says "I modified
the fs, but everythig is OK".  And the initscripts should say "oh, cool"
and keep booting.

I don't know whether the problem lies with fsck or initscripts.