[nfsv4] I-D Action: draft-ietf-nfsv4-layrec-02.txt
internet-drafts@ietf.org Tue, 15 October 2024 16:55 UTC
Return-Path: <internet-drafts@ietf.org>
X-Original-To: nfsv4@ietf.org
Delivered-To: nfsv4@ietfa.amsl.com
Received: from [10.244.8.251] (unknown [104.131.183.230]) by ietfa.amsl.com (Postfix) with ESMTP id 85BABC1D4CCD; Tue, 15 Oct 2024 09:55:32 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: internet-drafts@ietf.org
To: i-d-announce@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 12.25.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <172901133219.1095498.8406788055644926435@dt-datatracker-78dc5ccf94-w8wgc>
Date: Tue, 15 Oct 2024 09:55:32 -0700
Message-ID-Hash: WO6TE33RHOEECYZDIJ3VVKF2L2IJ5BNR
X-Message-ID-Hash: WO6TE33RHOEECYZDIJ3VVKF2L2IJ5BNR
X-MailFrom: internet-drafts@ietf.org
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; header-match-nfsv4.ietf.org-0; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header
CC: nfsv4@ietf.org
X-Mailman-Version: 3.3.9rc6
Reply-To: nfsv4@ietf.org
Subject: [nfsv4] I-D Action: draft-ietf-nfsv4-layrec-02.txt
List-Id: NFSv4 Working Group <nfsv4.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/nfsv4/5llg_6FPr6WNTt50Gi9MTLSilAg>
List-Archive: <https://mailarchive.ietf.org/arch/browse/nfsv4>
List-Help: <mailto:nfsv4-request@ietf.org?subject=help>
List-Owner: <mailto:nfsv4-owner@ietf.org>
List-Post: <mailto:nfsv4@ietf.org>
List-Subscribe: <mailto:nfsv4-join@ietf.org>
List-Unsubscribe: <mailto:nfsv4-leave@ietf.org>
Internet-Draft draft-ietf-nfsv4-layrec-02.txt is now available. It is a work item of the Network File System Version 4 (NFSV4) WG of the IETF. Title: Reporting of Errors via LAYOUTRETURN in NFSv4.2 Authors: Thomas Haynes Trond Myklebust Name: draft-ietf-nfsv4-layrec-02.txt Pages: 7 Dates: 2024-10-15 Abstract: The Parallel Network File System (pNFS) allows for a file'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. The IETF datatracker status page for this Internet-Draft is: https://datatracker.ietf.org/doc/draft-ietf-nfsv4-layrec/ There is also an HTML version available at: https://www.ietf.org/archive/id/draft-ietf-nfsv4-layrec-02.html A diff from the previous version is available at: https://author-tools.ietf.org/iddiff?url2=draft-ietf-nfsv4-layrec-02 Internet-Drafts are also available by rsync at: rsync.ietf.org::internet-drafts
- [nfsv4] I-D Action: draft-ietf-nfsv4-layrec-02.txt internet-drafts