Introducing Network File System Version 4 on HP-UX 11i v3

4
Figure 2. COMPOUND RPC reply
Figure 2 displays the server’s reply to the COMPOUND RPC in Figure 1.
Unless an error occurs, each opcode has its own return status and its own return values. For example,
the result of the PUTROOTFH opcode (lines 9 and 10) is the return status “NFS4_OK”, indicating the
operation succeeded without error. The results of the GETATTR opcode include the status (NFS4_OK
on line 22) and the values of the different attributes requested by the GETATTR opcode.
If an error occurs in one of the opcodes, then execution of the remaining opcodes is terminated, and
the accumulated results are returned to the client.
Note the request and response for FATTR4_SUPPORTED_ATTRS in Figure 1, line 17 and in Figure 2,
lines 25 through 28. NFSv4 enhances the types of attributes supported by NFS. For example, there
are mandatory attributes that are required for NFSv4 compliance, recommended attributes that should
be supported for NFS interoperability, and named attributes that enable the server to maintain a
value/pair assignment. Named attributes are optional and not currently supported in the NFSv4
implementation on HP-UX 11i v3.
The GETATTR operation enables NFSv4 clients to query a server as to which NFSv4 attributes it
supports for a particular file. This functionality increases Windows and UNIX® interoperability by
allowing Windows client applications and NFSv4 implementations to query an NFSv4 server as to
which attributes it supports and include or exclude features accordingly.