The kernel maintains a cache to store were files, inodes and other stuff
reside. Don't know if e2fsck is able to flush it, but I guess so; otherwise
fsck'ing a read-only partition wqould also cause pain.
With read-write, you have to be sure all data was written (sync'ed) to disk
(easy) and the kernel is not trying to write something until e2fsck has
finished. Don't know, if e2fsck has ways to tell the kernel not to do it. I
guess, no.
-- Kurt Garloff <K.Garloff@ping.de> (Dortmund, FRG) PGP key on http://student.physik.uni-dortmund.de/homepages/garloff Unix IS user friendly - it's just selective about who its friends are!- 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.tux.org/lkml/