Fwd: [nfsv4] RFC 9737 on Reporting Errors in NFSv4.2 via LAYOUTRETURN

[Chuck Lever <chuck.lever@oracle.com>]

Hi -

Congratulations on getting this published!

I'm wondering if you have plans to implement the protocol elements
described in this RFC in the Linux NFS client and the server?


-------- Forwarded Message --------
Subject: [nfsv4] RFC 9737 on Reporting Errors in NFSv4.2 via LAYOUTRETURN
Date: Wed, 26 Feb 2025 15:46:27 -0800 (PST)
From: rfc-editor@rfc-editor.org
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
CC: rfc-editor@rfc-editor.org, drafts-update-ref@iana.org, nfsv4@ietf.org

A new Request for Comments is now available in online RFC libraries.

                RFC 9737

        Title:      Reporting Errors in NFSv4.2 via
LAYOUTRETURN         Author:     T. Haynes,
                    T. Myklebust
        Status:     Standards Track
        Stream:     IETF
        Date:       February 2025
        Mailbox:    loghyr@gmail.com,
                    trondmy@hammerspace.com
        Pages:      6
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-nfsv4-layrec-04.txt

        URL:        https://www.rfc-editor.org/info/rfc9737

        DOI:        10.17487/RFC9737

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.

This document is a product of the Network File System Version 4 Working
Group of the IETF.

This is now a Proposed Standard.

STANDARDS TRACK: This document specifies an Internet Standards Track
protocol for the Internet community, and requests discussion and suggestions
for improvements.  Please refer to the current edition of the Official
Internet Protocol Standards (https://www.rfc-editor.org/standards) for
the standardization state and status of this protocol.  Distribution of
this memo is unlimited.

This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see
  https://www.ietf.org/mailman/listinfo/ietf-announce
  https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist

For searching the RFC series, see https://www.rfc-editor.org/search
For downloading RFCs, see https://www.rfc-editor.org/retrieve/bulk

Requests for special distribution should be addressed to either the
author of the RFC in question, or to rfc-editor@rfc-editor.org.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.


The RFC Editor Team


_______________________________________________
nfsv4 mailing list -- nfsv4@ietf.org
To unsubscribe send an email to nfsv4-leave@ietf.org