jack@mudshark.org said:
> On Fri, Sep 15, 2000 at 07:48:48AM -0400, Jamey Hicks wrote:
> > That would be much better. The superblock still gets modified when
> > you unmount the filesystem unless it was mounted read-only, even if no
> > files or atimes were modified. Is there any way to avoid that?
> Not easily, ext2 wants to keep track of things like mount counts.
It's not so difficult. ext2 only _really_ needs to keep track of the mount
count when the filesystem has been written to.
AIUI, the superblock is rewritten upon mounting, and the EXT2_VALID_FS flag
is cleared. This flag is later set upon successful unmounting.
It ought to be possible to delay the clearing of that flag until the
filesystem is first actually modified. That way, if the filesystem isn't
modified at all, the superblock isn't ever changed.
It would also be nice to be able to flush all buffers and reset the
filesystem to this state after a period of inactivity. That way, filesystems
which are mounted RW but are generally idle for long periods of time would
be far less likely to need a fsck after a crash.
-- dwmw2Received on Mon Sep 18 05:27:52 2000
This archive was generated by hypermail 2.1.8 : Tue May 04 2004 - 09:43:42 EDT