RFC 5663, "Parallel NFS (pNFS) Block/Volume Layout", January 2010Source of RFC: nfsv4 (tsv)
Errata ID: 4142
Status: Held for Document Update
Publication Format(s) : TEXT
Reported By: Christoph Hellwig
Date Reported: 2014-10-23
Held for Document Update by: Martin Stiemerling
Date Held: 2016-02-02
Section 2.8 says:
<section does not exist yet>
It should say:
2.8. Device-ID-to-device-address A pNFS block volume layout server MAY signal device-ID-to-device-address changes to the client using the CB_NOTIFY_DEVICEID callback operation. If the change is compatible and does not require outstanding layouts to be recalled the server can issue a notification of type NOTIFY_DEVICEID4_CHANGE. A device-ID-to-device-address mapping change signaled by NOTIFY_DEVICEID4_CHANGE must not change the storage system specific addressing of the volume, and can only add new storage to the existing device. In particular the following changes are allowed: o increasing the size of the underlying block device of a PNFS_BLOCK_VOLUME_SIMPLE volume. o increasing the size of a PNFS_BLOCK_VOLUME_SLICE volume if the underlying block device of the PNFS_BLOCK_VOLUME_SIMPLE volume it refers to is big enough to fit the new size. o increasing the size of each volume in a bsv_volumes of a PNFS_BLOCK_VOLUME_SLICE volume by the same amount. o increasing the size of the last volume in bcv_volumes of a PNFS_BLOCK_VOLUME_CONCAT volume. o adding new members to the end of bcv_volumes of a PNFS_BLOCK_VOLUME_CONCAT volume.
Specify what device configuration changes can be supported without recalling layouts.