nfs-storage · shipping · also Network File System, NFSv3, NFSv4

NFS

Network File System is a family of protocols for accessing files and directories on a remote server over a network.

Related Observatory article: Read on hesela.com

Persistence and recovery depend on protocol version and implementation. In NFSv3, WRITE requests UNSTABLE, DATA_SYNC or FILE_SYNC and returns the achieved level in committed; the server may return a stronger level than requested. COMMIT persists buffered file-range writes and metadata, with write-verifier comparison needed to detect lost uncommitted state. Do not infer durable server storage from an application write return or generalize the complete v3 recovery procedure to v4. The Linux server's async export option explicitly weakens protocol persistence guarantees.

Cache visibility is a separate concern: close-to-open checks support sequential sharing, and NFSv4 delegations can change when validation and writeback occur. See the related cache records for version-specific boundaries. Open-file lifetime is separate from write stability: Linux can use silly rename, while NFSv4.1 defines an advertised preservation capability. [7]

NFSv4.1 maintains open and locking state under a client lease. After server state loss, grace and reclaim coordinate restoration of prior state; these mechanisms do not certify file-data persistence. See the lease, stateid and state-reclaim records for the version-specific recovery boundary. [8]

Parallel NFS separates metadata coordination from direct data access through type-specific layouts; see pNFS and pNFS layout. [9]

Relations

related
NAS, File storage, NFS COMMIT, NFS write verifier, fsync, Write-back cache, Close-to-open consistency, NFS attribute cache, NFSv4 file delegation, NFS lookup cache, NFS silly rename, NFS open-file preservation, NFS write gathering, NFSv4 lease, NFSv4 grace period, NFSv4 stateid, NFSv4 state reclaim, Duplicate request cache, Parallel NFS (pNFS), pNFS layout

Advantages

  • Provides a network file interface while separating client access from server storage implementation. [1]

Limitations

  • Client buffering, server export policy and storage-cache behavior are distinct durability boundaries. [1, 2, 3]

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-utils exports(5), Debian trixie manual: async and sync export options. (accessed 2026-10-12)
  3. NFS stable writes: what COMMIT, flush and FUA actually promise (accessed 2026-10-12)
  4. RFC 8881 (NFSv4.1), sections 8.3-8.5, lease renewal and crash recovery. (accessed 2026-10-18)
  5. RFC 8434: Requirements for Parallel NFS Layout Types, sections 1-3; roles, layout-specific protocols and control requirements. (accessed 2026-11-09)

Further reading

  1. nfs-utils nfs(5), Debian trixie: data and metadata coherence and version-specific cto/nocto options. (accessed 2026-10-14)
  2. Haynes and Noveck (editors). NFS Version 4 Protocol. RFC 7530, sections 10.3, 10.4 and 10.6 (NFSv4.0). (accessed 2026-10-14)
  3. Noveck and Lever (editors). NFS Version 4 Minor Version 1 Protocol. RFC 8881, sections 10.3-10.6 (NFSv4.1). (accessed 2026-10-14)

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

Published by Hesela team · Updated

Report a correction · Editorial standards · Reuse guidance

Cite this page
Hesela team. NFS. Hesela. 2026-11-09. https://hesela.dev/terms/nfs-storage/