File system problems with 386/ix

Conor P. Cahill cpcahil at virtech.UUCP
Mon Oct 16 10:23:24 AEST 1989

In article <652 at npiatl.UUCP>, dkelly at npiatl.UUCP (Dwight Kelly) writes:
> Under 2.0.?, Interactive's fast file system marks almost all inodes as free
> and keeps a true map of allocated inodes in memory.  This way a panic or
> powerdown will force fschk to rebuild the ENTIRE inode list, giving the
> very large amount of incorrectly free blocks. 

The FFS does not mark inodes as free.  What does happen is that the (block)
free list is purposely damaged so that it appears empty. The messages that
appeared in the original posters fsck output were probably due to his running
the fsck on a mounted file system (or else the file system was really damaged).

| Conor P. Cahill     uunet!virtech!cpcahil      	703-430-9247	!
| Virtual Technologies Inc.,    P. O. Box 876,   Sterling, VA 22170     |

More information about the Comp.unix.i386 mailing list