On Wed, Nov 12, 2014 at 09:27:10AM +1100, Dave Chinner wrote:
> To clarify what Christoph wrote, XFS updates i_version is updated
> once per transaction that modifies the inode. So if a VFS level
> operation results in multiple transactions then each transaction
> will but the version.
>
> It was implemented that way because nobody could tell me what the
> actual granularity requirement for change detection was. Hence what
> I implemented was "be able to detect any persistent change that is
> made" to cover all bases.
Honestly the XFS implementation seems most sensible, and easiest to
verify for me. I don't really understand the rationale behind the
fairly convoluted NFS4_CHANGE_TYPE_IS_VERSION_COUNTER semantics, and
I doubt you could actually implemet them on any Unix-like semantics.
Trond, given that the language in the standard is from you:
1) how do you expect to use NFS4_CHANGE_TYPE_IS_VERSION_COUNTER
semantics in the client
2) what server do you have in mind that could actually implement them?
--
To unsubscribe from this list: send the line "unsubscribe linux-nfs" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
