RFC 5663: Parallel NFS (pNFS) Block/Volume Layout
In plain English — editorial summary, not part of the RFC
Parallel NFS (pNFS) extends Network File Sharing version 4 (NFSv4) to allow clients to directly access file data on the storage used by the NFSv4 server. This ability to bypass the server for data access can increase both performance and parallelism, but requires additional client functionality for data access, some of which is dependent on the class of storage used. The main pNFS operations document specifies storage-class-independent extensions to NFS; this document specifies the additional extensions (primarily data structures) for use of pNFS with block- and volume-based storage. [STANDARDS-TRACK]
Document record
- Document ID
- RFC5663
- Published
- January 2010
- Authors
- D. Black; S. Fridella; J. Glasgow
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- wit
- Pages
- 28
- Also known as
- —
- Updated by:
- RFC 6688
Topics
Referenced by
One later RFC formally updates or obsoletes part of this document.
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 5662Network File System (NFS) Version 4 Minor Version 1 External Data Representation Standard (XDR) DescriptionCurrent
January 2010
- RFC 5532Network File System (NFS) Remote Direct Memory Access (RDMA) Problem StatementCurrent
May 2009
- RFC 7204Requirements for Labeled NFSCurrent
April 2014
- RFC 7569Registry Specification for Mandatory Access Control (MAC) Security Label FormatsCurrent
July 2015
- RFC 3530Network File System (NFS) version 4 ProtocolObsoleted
April 2003
- RFC 8154Parallel NFS (pNFS) Small Computer System Interface (SCSI) LayoutCurrent
May 2017
- RFC 8275Allowing Inheritable NFSv4 Access Control Entries to Override the UmaskCurrent
December 2017
- RFC 3010NFS version 4 ProtocolObsoleted
December 2000
Also filed under
About this page
The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.
Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.
Data sources · Editorial policy · Report a correction · What is an RFC?