Simple definition
NFS exposes files on another server through a local mount point. An application uses a filesystem path while the data remains on remote storage. Unlike a one-off file transfer, the client continues to depend on the server and network while the shared directory is in use. A mounted path is therefore part of the application’s availability chain.
Technical definition
The server publishes an export and the client mounts it using compatible versions and options. NFSv4 generally uses TCP 2049 and integrates functions separated in earlier versions. NFSv3 may require additional RPC services and ports. Firewall rules must match the deployed version rather than assuming that one port describes every installation.
Access depends on the identity mechanism, export rules and filesystem permissions. In a traditional UID/GID-based setup, inconsistent numeric identifiers can produce unexpected access results. A matching displayed username alone does not establish that both systems recognize the same effective identity. Check how the particular client and server map users.
What is it used for?
NFS supports shared server directories, some virtualization datastores and common application storage. Latency, bandwidth and storage availability become application dependencies. Before choosing mount options, understand the consequences of losing the network or server. A filesystem path that looks local can still block or fail because a remote component is unavailable.
Practical example
A Proxmox host accesses an NFS export on a NAS for a configured storage purpose. Troubleshooting separates export access, permissions, capacity and network stability. A NAS can respond to ping while denying the export or delivering poor storage performance. Compare the failing operation with another authorized client before changing shared settings.
Key points
| Element | Role |
|---|---|
| Export | Directory made accessible by the server |
| Mount | Access point used by the client |
| UID/GID or negotiated identity | Contributes to effective permissions |
| Version and options | Determine compatibility and failure behavior |
Common problems
- Access denied: check the exported path, permitted client, protocol version and effective permissions.
- Stale file handle: investigate file or export changes before unmounting an active share.
- Stalls or slow access: correlate network errors, storage latency, server load and mount options.
Operational checks and limitations
A mount is neither a backup nor a high-availability guarantee. Restrict exports and choose suitable authentication and encryption mechanisms; NFS does not automatically encrypt every deployment. Test connectivity loss and file recovery against the application’s requirements, and document which systems depend on each export before performing maintenance.