RFC Errata
RFC 5661, "Network File System (NFS) Version 4 Minor Version 1 Protocol", January 2010
Note: This RFC has been obsoleted by RFC 8881
Note: This RFC has been updated by RFC 8178, RFC 8434
Source of RFC: nfsv4 (wit)
Errata ID: 3065
Status: Held for Document Update
Type: Technical
Publication Format(s) : TEXT
Reported By: David Black
Date Reported: 2011-12-27
Held for Document Update by: Martin Stiemerling
Section 12.7.4 says:
If the metadata server's consistency checks on loca_layoutupdate succeed, then the metadata server MUST commit the data (as described by the loca_offset, loca_length, and loca_layoutupdate fields of the arguments) that was written to the storage device. If the metadata server's consistency checks on loca_layoutupdate fail, the metadata server rejects the LAYOUTCOMMIT operation and makes no changes to the file system. However, any time LAYOUTCOMMIT with loca_reclaim TRUE fails, the pNFS client has lost all the data in the range defined by <loca_offset, loca_length>.
It should say:
If the metadata server's consistency checks on loca_layoutupdate succeed, then the metadata server MUST commit the changed data that was written to the storage device within the scope of the LAYOUTCOMMIT operation. If the metadata server's consistency checks on loca_layoutupdate fail, the metadata server rejects the LAYOUTCOMMIT operation and makes no changes to the file system. However, any time LAYOUTCOMMIT with loca_reclaim TRUE fails, the pNFS client may have lost all uncommitted data within the scope of the failed LAYOUTCOMMIT operation.
Notes:
Errata 2 of 5 to deprecate loca_offset and loca_length arguments to LAYOUTCOMMIT.