On Wed, Jul 05, 2006 at 08:24:29AM -0400, Bill Davidsen wrote:There are versions in both VMS and the ISO filesystem. I have a sneaking suspicion that those of us who ever use them are few and far between. The other issue is that unless the field is time, programs like make can't really use it, at least without becoming Linux specific.
Theodore Tso wrote:
Some of the ideas which have been tossed about include:The 2nd one is probably more urgent than the first. I can see a general benefit from timestamp in ms, beyond that seems to be a specialty requirement best provided at the application level rather than the bits of a trillion inodes which need no such thing.
* nanosecond timestamps, and support for time beyond the 2038
What's urgently needed for NFS (and I suspect for most other
applications demanding higher timestamps) isn't really nanosecond
precision so much as something that's guaranteed to increase whenever
the file changes.
Of course, just adding space in the inodes for nanoseconds isn't
sufficient. XFS, for example, has nanosecond timestamps, but it's still
easy to modify a file twice without seeing the ctime or mtime change.
So either we need a timesource guaranteed to tick faster than the kernel
can process IO, or we have to be willing to, say, add 1 to the
nanoseconds field whenever the time doesn't change between operations.
Or we could add an entirely separate attribute that's guaranteed to
increase whenever the ctime is updated, and that doesn't necessarily
have any connection with time--call it a version number or something.