But... [I can't believe this problem can't die after years.. :)] there
are cases when the inodes cannot get cleaned up before a reboot... For
example, if libc.so is upgraded, and the old one is removed. When done
correctly, no harm is done, but programs, and especially init, if linked
dynamically (and keept running), will hold on to the inode until
infinity... In this case, if you don't let the remount succeed, the
current uneducated init scripts will reboot anyway, and let fsck sort
out what happened, which is a bit rude (i.e. e2fs knows what's going on,
but refuses to handle it). Resurrecting deleted, but irremovable inodes
into lost+found could solve this, but sounds a bit dodgy... I don't
know which is worse.
Maybe a dedicated 'hey-fsck-delete-these-inodes' special internal
(inaccessible from the filesystem) directory to keep them, and make it
easier for the kernel rather than create the possibly nonexistent
lost+found directory?
-- Janos - Don't worry, my address is real. I'm just bored of spam.- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.rutgers.edu Please read the FAQ at http://www.altern.org/andrebalsa/doc/lkml-faq.html