I don't know how the count would be used. I have not ever looked at any of the file system code in the kernel or in the file system drivers. I am just speculating/assuming based on programming experience.
Some code somewhere in the file system driver or the kernel will be using that value for something. It would be bad programming practice to write a value of any kind to the disk unless some code somewhere needs to read it and act on it in some way. Otherwise, it is a waste of time to write it.
I was trying to point out that just not writing the value may have side effects and could break things where there is code dependent on the value written. All such side effects would have to be discovered and "hacked" around too.
Alan
-------Original Message-------
From: Rob Wultsch <
robert.wultsch@asu.edu>
Sent: 08/05/03 01:22 PM
To:
plug-discuss@lists.plug.phoenix.az.us
Subject: Re: Need help! Calling all Linux experts here.
>
> How would it use the mount count? I can understand ext3 doing so, as it
needs to fsck itself once in a while, but reiser does not do that, does
it?
Alan Dayley wrote:
> The code writes the mount count some other code somewhere can read it
and use it. It will be more complex than just eliminating the code that
writes it.
>
> OTOH, it shouldn't be that bad, assuming the code is structured well.
>
> Alan
>
(text/plain)