Ken Hornstein <kenh@cmf.nrl.navy.mil> writes:
> >Sounds like the "clean bit" is the first thing set instead of the last.
> 
> Actually, as I recall, it wasn't quite that.  It was the case if you deleted
> an executable that never got properly killed before shutdown, _then_ it would
> get corrupted.  This was the case with init; since it never really exits (is
> that correct?), if you deleted the init executable (say, from doing a "make
> install" for world), you'd have a dirty filesystem.

So the only corruption actually caused is an incorrect access count on
the init inode?  If so, this is quite benign, merely failing to
reclaim the space used by the executable until the next fsck -f.

Of course once this is fixed it causes the summary info to become bad
as well...

	Mark
--------------------------------------------------------------------
Email: Mark_Weaver@brown.edu           | Brown University
PGP Key: finger mhw@cs.brown.edu       | Dept of Computer Science