<?xml version="1.0" encoding="UTF-8"?>
<reference anchor="I-D.ietf-nfsv4-layrec" target="https://datatracker.ietf.org/doc/html/draft-ietf-nfsv4-layrec-04">
   <front>
      <title>Reporting of Errors via LAYOUTRETURN in NFSv4.2</title>
      <author initials="T." surname="Haynes" fullname="Thomas Haynes">
         <organization>Hammerspace</organization>
      </author>
      <author initials="T." surname="Myklebust" fullname="Trond Myklebust">
         <organization>Hammerspace</organization>
      </author>
      <date month="November" day="21" year="2024" />
      <abstract>
	 <t>   The Parallel Network File System (pNFS) allows for a file&#x27;s metadata
   (MDS) and data (DS) to be on different servers.  When the metadata
   server is restarted, the client can still modify the data file
   component.  During the recovery phase of startup, the metadata server
   and the data servers work together to recover state (which files are
   open, last modification time, size, etc.).  If the client has not
   encountered errors with the data files, then the state can be
   recovered, avoiding resilvering of the data files.  With any errors,
   there is no means by which the client can report errors to the
   metadata server.  As such, the metadata server has to assume that
   file needs resilvering.  This document presents an extension to
   RFC8435 to allow the client to update the metadata and avoid the
   resilvering.

	 </t>
      </abstract>
   </front>
   <seriesInfo name="Internet-Draft" value="draft-ietf-nfsv4-layrec-04" />
   
</reference>
