Reporting Errors in NFSv4.2 via LAYOUTRETURN
RFC 9737, “Reporting Errors in NFSv4.2 via LAYOUTRETURN”, is a Proposed Standard document published in February 2025 by T. Haynes, T. Myklebust. The canonical text is published by the RFC Editor.
Abstract
The Parallel Network File System (pNFS) allows for a file's metadata and data to be on different servers (i.e., the metadata server (MDS) and the data server (DS)). When the MDS is restarted, the client can still modify the data file component. During the recovery phase of startup, the MDS and the DSs work together to recover state. If the client has not encountered errors with the data files, then the state can be recovered and the resilvering of the data files can be avoided. With any errors, there is no means by which the client can report errors to the MDS. As such, the MDS has to assume that a file needs resilvering. This document presents an extension to RFC 8435 to allow the client to update the metadata via LAYOUTRETURN and avoid the resilvering.
What “Proposed Standard” means
An entry-level standards-track specification: stable, peer-reviewed and a solid basis for implementation, though it may still evolve before becoming an Internet Standard.
The canonical text of RFC 9737 is hosted at rfc-editor.org. Available in HTML,TXT,PDF,XML.
- RFC 9736 The BGP Monitoring Protocol Peer Up Message Namespace
- RFC 9738 IMAP MESSAGELIMIT Extension
- RFC 9735 Locator/ID Separation Protocol Distinguished Name Encoding
- RFC 9739 Protocol Independent Multicast Light
- RFC 9734 X.509 Certificate Extended Key Usage for Instant Messaging URIs
- RFC 9740 New IPFIX Information Elements for TCP Options and IPv6 Extension Headers
- RFC 9733 BRSKI with Alternative Enrollment
- RFC 9741 Concise Data Definition Language : Additional Control Operators for the Conversion and Processing of Text