POSIX metadata

Content Platform Tenant Management Help

Version
9.7.x
File Size
4269 KB
Audience
anonymous
Part Number
MK-95HCPH002-19

To support the NFS protocol, HCP maintains POSIX metadata for objects, directories, and symbolic links. The protocol you’re using to access the namespace determines what actions you can perform on POSIX metadata:

  • With HTTP, you can view some POSIX metadata on objects, but you cannot change it.
  • With WebDAV, you can view all POSIX metadata on objects, directories, and symbolic links, but you cannot change it.
  • With CIFS and NFS, you can view all POSIX metadata on objects, directories, and symbolic links, and you can change some of it.

    A request to change POSIX metadata on a symbolic link changes the metadata on the object that’s the target of the link. Such a request does not change the metadata on the link itself.

The POSIX metadata that HCP maintains for items in a namespace (that is, objects, directories, and symbolic links) depends on the protocol through which the item was added:

  • For items added through NFS, HCP maintains these attributes for each item:
    • A user ID and group ID.
    • A POSIX permissions value.
  • For all items, HCP maintains atime, ctime, and mtime attributes.
Note: Metafiles also have POSIX metadata. With the WebDAV, CIFS, and NFS protocols, you can view the POSIX metadata for metafiles but you cannot explicitly change it.

For example, if you specify an mtime value for an object in a WebDAV command, the mtime values of the corresponding metadirectories equal the specified value. However, the mtime values for the metafiles in these directories reflect the time the request executed. (The atime values of the metafiles equal any specified atime value.)