I-D list for Network File System Version 4 RSS FeedDocument changesurn:uuid:b3d571ad-abff-53bb-b3df-bf56703eacb22024-03-28T10:33:24-0700Recursively Setting Directories and Subitems9833292024-03-26T17:59:21-07002024-03-26T17:59:21-0700Dongyu GengNew version available: <b>draft-mzhang-nfsv4-recursively-setting-02.txt</b>new_revisionnoneactiveidexists In recent years, the concept of near-data computing has been widely
recognized in storage architectures. The core idea is to process
data nearby, reduce the overhead of network transmission, and utilize
the computing capability of smart devices (such as intelligent NICs,
smart SSDs, and DPUs). This reduces CPU and memory usage of clients
(computing nodes) and improves data processing efficiency. This
design idea is applied in NFSv4.2 or future NFS verions, such as
Server-Side Copy, in which client sends the control command and the
storage server copies data without passing through the data between
the client and storage server. Compared with traditional copy
operations, data is read from the source storage server and then
written to the target storage server after two network transmissions.
Data transmission on the network is reduced, and bandwidth resources
are greatly released. In addition, the client changes from an
original data copy executor to a data copy controller, and a specific
execution action is executed by the storage server. Therefore, a
large amount of computing resources and memory resources are saved on
the client side.
02Recursively Setting Directories and Subitems9833282024-03-26T17:59:21-07002024-03-26T17:59:21-0700Dongyu GengNew version accepted (logged-in submitter: Dongyu Geng)new_submissionnoneactiveidexistsRecursively Setting Directories and Subitems9833272024-03-26T17:59:20-07002024-03-26T17:59:20-0700Dongyu GengUploaded new revisionnew_submissionnoneactiveidexistsRecursively Setting Directories and Subitems9832442024-03-25T20:41:44-07002024-03-25T20:41:44-0700Dongyu GengNew version available: <b>draft-mzhang-nfsv4-recursively-setting-01.txt</b>new_revisionnoneactiveidexists In recent years, the concept of near-data computing has been widely
recognized in storage architectures. The core idea is to process
data nearby, reduce the overhead of network transmission, and utilize
the computing capability of smart devices (such as intelligent NICs,
smart SSDs, and DPUs). This reduces CPU and memory usage of clients
(computing nodes) and improves data processing efficiency. This
design idea is applied in NFSv4.2 or future NFS verions, such as
Server-Side Copy, in which client sends the control command and the
storage server copies data without passing through the data between
the client and storage server. Compared with traditional copy
operations, data is read from the source storage server and then
written to the target storage server after two network transmissions.
Data transmission on the network is reduced, and bandwidth resources
are greatly released. In addition, the client changes from an
original data copy executor to a data copy controller, and a specific
execution action is executed by the storage server. Therefore, a
large amount of computing resources and memory resources are saved on
the client side.
02Recursively Setting Directories and Subitems9832432024-03-25T20:41:44-07002024-03-25T20:41:44-0700Dongyu GengNew version accepted (logged-in submitter: Dongyu Geng)new_submissionnoneactiveidexistsRecursively Setting Directories and Subitems9832422024-03-25T20:41:44-07002024-03-25T20:41:44-0700Dongyu GengUploaded new revisionnew_submissionnoneactiveidexistsReporting of Errors via LAYOUTRETURN in NFSv4.29824392024-03-20T17:36:54-07002024-03-20T17:36:54-0700Thomas HaynesNew version available: <b>draft-ietf-nfsv4-layrec-01.txt</b>new_revisionietfnfsv4activeidexistswg-doc 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.
01Reporting of Errors via LAYOUTRETURN in NFSv4.29824382024-03-20T17:36:54-07002024-03-20T17:36:54-0700(System)New version approvednew_submissionietfnfsv4activeidexistswg-docReporting of Errors via LAYOUTRETURN in NFSv4.29824372024-03-20T17:36:10-07002024-03-20T17:36:10-0700(System)Request for posting confirmation emailed to previous authors: Thomas Haynes <loghyr@hammerspace.com>, Trond Myklebust <trondmy@hammerspace.com>new_submissionietfnfsv4activeidexistswg-docReporting of Errors via LAYOUTRETURN in NFSv4.29824362024-03-20T17:36:10-07002024-03-20T17:36:10-0700Thomas HaynesUploaded new revisionnew_submissionietfnfsv4activeidexistswg-docUsing the Parallel NFS (pNFS) SCSI Layout to access NVMe storage devices9819022024-03-19T20:07:19-07002024-03-19T20:07:19-0700(System)RFC Editor state changed to <a href="https://www.rfc-editor.org/auth48/rfc9561"><b>AUTH48-DONE</b></a> from AUTH48changed_stateietfnfsv4Christopher InacioZaheduzzaman Sarkeractivenoicok-noactrfcqueueauth48-donesub-pubAdd CB_LAYOUTRECLL_DEVICE to NFSv4.29813232024-03-18T21:53:38-07002024-03-18T21:53:38-0700Thomas HaynesNew version available: <b>draft-haynes-nfsv4-recalldevice-00.txt</b>new_revisionnoneactiveidexists The Parallel Network File System (pNFS) allows for the metadata
server to use CB_LAYOUTRECALL to recall a layout from a client by
file id or file system id or all. It also allows the server to use
CB_NOTIFY_DEVICEID to delete a devicid. It does not provide a
mechanism for the metadata server to recall all layouts that have a
data file on a specific deviceid. This document presents an
extension to RFC8881 to allow the server recall layouts from clients
based on deviceid.
00Add CB_LAYOUTRECLL_DEVICE to NFSv4.29813222024-03-18T21:53:38-07002024-03-18T21:53:38-0700(System)New version approvednew_submissionnoneactiveidexistsAdd CB_LAYOUTRECLL_DEVICE to NFSv4.29813212024-03-18T21:53:17-07002024-03-18T21:53:17-0700Thomas HaynesRequest for posting confirmation emailed to submitter and authors: Thomas Haynes <loghyr@hammerspace.com>new_submissionnoneactiveidexistsAdd CB_LAYOUTRECLL_DEVICE to NFSv4.29813202024-03-18T21:52:50-07002024-03-18T21:52:50-0700Thomas HaynesUploaded new revisionnew_submissionnoneactiveidexistsExtending the Opening of Files in NFSv4.29810982024-03-18T17:33:12-07002024-03-18T17:33:12-0700Thomas HaynesNew version available: <b>draft-ietf-nfsv4-delstid-04.txt</b>new_revisionietfnfsv4Christopher InacioZaheduzzaman Sarkeractivedeadsub-pub The Network File System v4 (NFSv4) allows a client to both open a
file and be granted a delegation of that file. This delegation
provides the client the right to authoritatively cache metadata on
the file locally. This document presents several extensions for both
the opening and delegating of the file to the client. This document
extends both RFC8881 and RFC7863.
04Extending the Opening of Files in NFSv4.29810972024-03-18T17:33:12-07002024-03-18T17:33:12-0700(System)New version approvednew_submissionietfnfsv4Christopher InacioZaheduzzaman Sarkeractivedeadsub-pubExtending the Opening of Files in NFSv4.29810962024-03-18T17:32:44-07002024-03-18T17:32:44-0700(System)Request for posting confirmation emailed to previous authors: Thomas Haynes <loghyr@hammerspace.com>, Trond Myklebust <trondmy@hammerspace.com>new_submissionietfnfsv4Christopher InacioZaheduzzaman Sarkeractivedeadsub-pubExtending the Opening of Files in NFSv4.29810952024-03-18T17:32:44-07002024-03-18T17:32:44-0700Thomas HaynesUploaded new revisionnew_submissionietfnfsv4Christopher InacioZaheduzzaman Sarkeractivedeadsub-pub