NAS
Network-attached storage (NAS) provides file access over a network through protocols such as NFS or SMB.
NAS exposes files and directories while the server manages the backing storage. A server can use directly attached disks and export files through NFS or SMB: local disk attachment and network file service describe different layers. NAS does not require DAS backing storage. [4] [6]
NFS recovery is version-specific. NFSv3 retries can encounter duplicate-request-cache loss or eviction and execute again, so statelessness does not make every retry safe. NFSv4.1 adds sessions for request tracking, with persistence negotiated separately. [3] [2]
SMB3 supports features including encryption and leases for client caching. A protocol's available features do not establish which dialect or options a particular connection negotiated. [5]
File visibility, write persistence and protection from permanent storage failure are separate requirements. A network file interface alone does not provide a backup or a multi-file application transaction. [3]
Relations
- related
- File storage, SMB file sharing, NFS, SAN, Block storage, Duplicate request cache, Direct-attached storage, Unified storage, NAS gateway
Advantages
- Clients can share a namespace without directly managing the server's block devices. [4]
Limitations
- Legacy CIFS dialects have weaker security properties than modern SMB3. [5]
Citations
- RFC 8881: NFSv4.1, sessions and reply-cache persistence (sections 2.10 and 18.36).
- RFC 1813: NFSv3, duplicate request cache and stable storage (sections 4.5 and 4.8).
- SNIA: What is NAS (Network Attached Storage) and why is NAS Important?
- Introduction, SMB3/CIFS client (The Linux Kernel documentation, admin guide)
- Red Hat Enterprise Linux 10: Overview of available file systems, local and network file systems