Re: [PATCH 2/2] i_version update - ext4 part

This patch adds 64-bit inode version support to ext4. The lower 32 bits are stored in the osd1.linux1.l_i_version field while the high 32 bits are stored in the i_version_hi field newly created in the ext4_inode. This field is incremented in case the ext4_inode is large enough. A i_version mount op

Re: [PATCH 1/2] i_version update - vfs part

Hi, This is an update of the previous patches on the ext4 git tree, the 2 coming patches applies at the end of the current ext4-patch-queue, and replaces the inode-version related patches: 64-bit-i_version.patch i_version_hi.patch ext4_i_version_hi_2.patch i_version_update_ext4.patch The first pa

[PATCH 2/2] i_version update - ext4 part

This patch update the i_version field of the inode and add a mount option to enable this feature. The other condition to enable this feature is that the inode size should be 256-bytes. Signed-off-by: Jean Noel Cordenner <[EMAIL PROTECTED]> --- fs/ext4/inode.c |4 +++- fs/ext4/super.c

[PATCH 1/2] i_version update - vfs part

Hi, This is an update of the i_version patch. The i_version field is a 64bit counter that is set on every inode creation and that is incremented every time the inode data is modified (similarly to the "ctime" time-stamp). The aim is to fulfill a NFSv4 requirement for rfc3530: "5.5. Mandator