3.3.1 Procedure 1: GETATTR - Get file attributes

Quality Cables & Networking Supplies	Search by Cable Connectors	SHIPPING ADDRESS: 4170 B Place NW, Auburn, WA 98001 USA View Map	MAILING ADDRESS: P.O. Box 8026, Bonney Lake, WA 98391 USA
EMAIL: Sales, Customer Service or Webmaster		PHONE: 800-931-3133 or 253-373-0800 \| FAX: 253-373-0100
Hours: 9:00am - 5:00pm PST Monday - Friday

You are here: PacificCable.com 3.3.1 Procedure 1: GETATTR - Get file attributes

Connected: An Internet Encyclopedia
3.3.1 Procedure 1: GETATTR - Get file attributes

Up: Connected: An Internet Encyclopedia
Up: Requests For Comments
Up: RFC 1813
Up: 3. Server Procedures
Up: 3.3. Procedure Descriptions
Prev: 3.3.0 Procedure 0: NULL - Do nothing
Next: 3.3.2 Procedure 2: SETATTR - Set file attributes

3.3.1 Procedure 1: GETATTR - Get file attributes

SYNOPSIS

      GETATTR3res NFSPROC3_GETATTR(GETATTR3args) = 1;

      struct GETATTR3args {
         nfs_fh3  object;
      };

      struct GETATTR3resok {
         fattr3   obj_attributes;
      };

      union GETATTR3res switch (nfsstat3 status) {
      case NFS3_OK:
         GETATTR3resok  resok;
      default:
         void;
      };

DESCRIPTION

Procedure GETATTR retrieves the attributes for a specified file system object. The object is identified by the file handle that the server returned as part of the response from a LOOKUP, CREATE, MKDIR, SYMLINK, MKNOD, or READDIRPLUS procedure (or from the MOUNT service, described elsewhere). On entry, the arguments in GETATTR3args are:

object: The file handle of an object whose attributes are to be retrieved.

On successful return, GETATTR3res.status is NFS3_OK and GETATTR3res.resok contains:

obj_attributes: The attributes for the object.

Otherwise, GETATTR3res.status contains the error on failure and no other results are returned.

IMPLEMENTATION

The attributes of file system objects is a point of major disagreement between different operating systems. Servers should make a best attempt to support all of the attributes in the fattr3 structure so that clients can count on this as a common ground. Some mapping may be required to map local attributes to those in the fattr3 structure.

Today, most client NFS version 3 protocol implementations implement a time-bounded attribute caching scheme to reduce over-the-wire attribute checks.

ERRORS

NFS3ERR_IO NFS3ERR_STALE NFS3ERR_BADHANDLE NFS3ERR_SERVERFAULT