Found 1 record.

Status: Reported (1)

RFC 9754, "Extensions for Opening and Delegating Files in NFSv4.2", March 2025

Errata ID: 8595
Status: Reported
Type: Technical
Publication Format(s) : HTML
Reported By: Chuck Lever
Date Reported: 2025-10-08

Section 2 says:

If the client is not aware that the file is offline, it might
inadvertently open the file to determine what type of file it is
accessing.  By interrogating the new attribute fattr4_offline, a
client can predetermine the availability of the file, avoiding the
need to open it at all.  Being offline might also involve situations
in which the file is archived in the cloud, i.e., there can be an
expense in both retrieving the file to bring it online and in sending
the file back to offline status.

It should say:

If the client is not aware that the file is offline, it might
inadvertently open the file to determine what type of file it is
accessing.  By interrogating the new attribute fattr4_offline, a
client can predetermine the availability of the file, avoiding the
need to open it at all.  Being offline might also involve situations
in which the file is archived in the cloud, i.e., there can be an
expense in both retrieving the file to bring it online and in sending
the file back to offline status.

When a client reads file content, the file's OFFLINE attribute may
change from "offline" to "online". The NFSv4 protocol does not
provide a mechanism to change the attribute value from "online" to
"offline".

Notes:

Section 2 is missing a clear indication that, via the NFSv4 protocol, the OFFLINE attribute is read-only. A table, similar to Table 4 in RFC 8881, should be added to the document.

Report New Errata