file-storage · shipping · also file-level storage, network file sharing

File storage

File storage presents data as named files, commonly organized in directories, through a file-system interface.

File access does not require a network or multiple clients. A local file system can provide it on an attached disk or on a SAN volume assigned to one host; NAS provides file access over a network. The existing alias 'network file sharing' describes that network case, not the full meaning of file storage [7] [8].

The file interface and the underlying storage interface are different layers. Linux's Virtual File System presents a common interface to user programs across different file-system implementations. Applications use names and file operations while the implementation manages the underlying representation [9].

For network access, NFS and SMB supply their own sharing contracts. NFSv4 integrates locking with lease-based state; NFSv4.1 adds optional pNFS layouts that separate metadata handling from data access. SMB transport and dialect support also vary. Select the deployed protocol and implementation before making assumptions about caching, locking or recovery [2] [3] [6].

Sharing a file service is different from mounting one block volume on several hosts. A shared-disk file system coordinates those hosts' metadata and cached state; ordinary local file systems do not acquire that capability merely because their block device is reachable from more than one machine [8].

Relations

related
NAS, Object storage, Block storage, NFS, SMB file sharing, Shared-disk file system, NumPy NPY format, Filesystem

Advantages

  • File names and directory operations give applications an interface distinct from the underlying storage layout, whether the file system is local or network-backed. [7, 9]
  • NFSv4.1 adds optional parallel access (pNFS) so clients can read file data directly from the storage devices, which the RFC says can significantly improve performance when data is on multiple or faster devices. [3]
  • SMB 2 and 3 can run over Direct TCP, RDMA (3.0 and later) and QUIC (3.1.1), so the same file-sharing model works over different transports. [6]

Limitations

  • Protocol versions differ in behaviour: NFSv3 assumes a stateless server and a 64-byte maximum file handle, while NFSv4 keeps lease-based lock state at the server, so features and failure behaviour depend on the version in use. [4, 2]
  • Security is optional to deploy: RPCSEC_GSS must be implemented in NFSv4 but its deployment is optional, and pNFS is an optional feature of NFSv4.1. [2, 3]
  • A file interface alone does not specify concurrency or recovery behavior; network file services and shared-disk file systems coordinate access at different layers. [8]

Citations

  1. IETF RFC 7530: Network File System (NFS) Version 4 Protocol (March 2015) (accessed 2026-10-16)
  2. IETF RFC 8881: Network File System (NFS) Version 4 Minor Version 1 Protocol (August 2020) (accessed 2026-10-16)
  3. IETF RFC 1813: NFS Version 3 Protocol Specification (June 1995) (accessed 2026-10-16)
  4. [MS-SMB2] Transport section (vendor-published protocol specification) (accessed 2026-10-16)
  5. SNIA Dictionary: file storage (terminology) (accessed 2026-10-19)
  6. Red Hat Enterprise Linux 8: Overview of available file systems, local, network and shared-storage categories (accessed 2026-10-19)
  7. Linux kernel documentation: Overview of the Linux Virtual File System (accessed 2026-10-19)

Further reading

  1. File storage (accessed 2026-03-26)
  2. [MS-SMB2] Server Message Block (SMB) Protocol Versions 2 and 3 (vendor-published protocol specification, revision list) (accessed 2026-10-16)

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

Published by Hesela team · Updated

Report a correction · Editorial standards · Reuse guidance

Cite this page
Hesela team. File storage. Hesela. 2026-11-15. https://hesela.dev/terms/file-storage/