On Thu, Sep 14, 2006 at 09:46:03AM -0400, Peter Staubach wrote:
> Trond Myklebust wrote:
> >On Wed, 2006-09-13 at 18:42 +0200, Alexandre Ratchov wrote:
> >
> >>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).
> >>
> >
> >I would really have preferred a full-blown 64-bit counter as per
> >RFC3530, but I suppose we could always combine this change attribute
> >with the high word from ctime in order to make up the NFSv4 change
> >attribute. That should keep us safe until someone develops a ramdisk
> >with < 1 nsecond access time.
>
> Wouldn't the generation count work better than ctime to differentiate
> between
> instances of files using the same inode number? That way, there wouldn't be
> a clock resolution issue.
Yes, and afaik it's already used for that purpose by NFSv{2,3}.
Note that the change attribute is for counting changes of the same instance
of a file using a given inode (as opposed to the generation counter that's
used to count the number of files that have used a given inode).
-- Alexandre
-
To unsubscribe from this list: send the line "unsubscribe linux-ext4" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
