nfs-commit · shipping · also NFSv3 COMMIT

NFS COMMIT

NFSv3 COMMIT requests stable storage of previously buffered writes and associated metadata for a specified file range.

RFC 1813 section 3.3.21 defines the operation; count zero means from offset to end of file. The client compares the returned verifier with those associated with its outstanding writes, retransmitting uncommitted buffers if the verifier changes. A successful status alone is insufficient evidence that earlier volatile data survived a server restart. This is a file-range persistence operation, not a transaction across several files; NFSv4 recovery is outside this record's scope.

Relations

related

nfs-storage, nfs-write-verifier, cache-flush, fsync

Advantages

• Allows clients to batch unstable writes before requesting their persistence. [1]

Limitations

• Cannot recover a lost client copy of data that never reached stable server storage. [1]

Citations

1. B. Callaghan, B. Pawlowski and P. Staubach. NFS Version 3 Protocol Specification. RFC 1813, June 1995, sections 3.3.7, 3.3.21 and 4.8. (accessed 2026-10-12)
2. NFS stable writes: what COMMIT, flush and FUA actually promise (accessed 2026-10-12)

JSON: /data/terms/nfs-commit.json