On Sep 13, 2006 14:11 -0400, Trond Myklebust wrote: > On Wed, 2006-09-13 at 18:42 +0200, Alexandre Ratchov wrote: > > 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. Trond, can you please elaborate on the need for a 64-bit version counter for NFSv4? We have been looking at something similar, but ctime+nsec is not really sufficient as it is possible that the inode ctime can go backward if the clock is reset. What kind of requirements does NFSv4 place on the version? Monotonic is probably a good bet. Does it need to be global for the filesystem, or is a per-inode version sufficient? What functionality of NFSv4 needs the version? Cheers, Andreas -- Andreas Dilger Principal Software Engineer Cluster File Systems, Inc. - 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
