On Wed, 2006-12-13 at 20:52 -0500, J. Bruce Fields wrote:
What kind of requirements does NFSv4 place on the version? Monotonic is
probably a good bet.
The only requirement is that it be unique (assuming a file is never
modified 2^64 times). Clients can't compare them except for equality.
On Wed, Sep 13, 2006 at 01:31:30PM -0600, Andreas Dilger wrote:
On Sep 13, 2006 18:42 +0200, Alexandre Ratchov wrote:
the change attribute is a simple counter that is reset to zero on
inode creation and that is incremented every time the inode data is
modified (similarly to the ctime
On Sep 14, 2006 15:21 +0200, Alexandre Ratchov wrote:
IMHO, the natural place to do this stuff is the VFS, because it can be
common to all file-systems supporting this feature. Currently it's the same
with ctime, mtime and atime. These are in the VFS even if there are
file-systems that don't
hello,
here is a small patch that adds the change attribute for ext3
file-systems;
the change attribute is a simple counter that is reset to zero on
inode creation and that is incremented every time the inode data is
modified (similarly to the ctime time-stamp).
Its purpose is to make possible
On Sep 13, 2006 18:42 +0200, Alexandre Ratchov wrote:
the change attribute is a simple counter that is reset to zero on
inode creation and that is incremented every time the inode data is
modified (similarly to the ctime time-stamp).
To start, I'm supportive of this concept, my comments are
