Hp StoreAll Storage User Manual Page 183

  • Download
  • Add to my manuals
  • Print
  • Page
    / 254
  • Table of contents
  • TROUBLESHOOTING
  • BOOKMARKS
  • Rated. / 5. Based on customer reviews
Page view 182
WriteableExampleDescriptionTypeSystem attribute (key)
that the last activity
on this file was a
system::lastActivityTime,
which is a combination
of the following values:
content modification,
which changes both
0x1:
nl
lastModifiedTime
(0x2) and
system::createTime
nl
lastChangedTime
(0x4) .
0x2:
nl
system::lastModifiedTime
nl
0x4:
nl
system::lastChangedTime
nl
0x8:
nl
system::deleteTime
nl
0x10:
nl
custom metadata
assignment time
(not queryable as
a system::
attribute)
This attribute is returned
in query results if the
request explicitly
includes
system::lastActivityReason
as an attribute to be
returned.
system::onDiskAtime
The atime inode field in IBRIX can be accessed as the system::onDiskAtime attribute from the
API. This field represents different concepts in the lifetime of a WORM/retained file, and it often
represents a concept other than the time of the file’s last access, which is why the field was named
onDiskAtime rather than (for example) lastAccessedTime. (See “Retention properties
assignment” (page 172) for a description of this life cycle).
Before a file is retained, whether WORM state or not, atime represents the last accessed time,
as long as the file system is mounted with the non-default atime option. If the file system is
mounted with the default noatime option, atime is the file’s creation time, and never changes
unless the file is retained (see the second bullet). See “Creating and mounting file systems”
(page 13) for more information about mount options.
While a file is in the retained state, atime represents the retention expiration time.
After retention expires, atime represents the time at which the file was first retained (even if
the file has been retained and expired more than once), and it never changes again, unless
the file is re-retained (see the second bullet).
If you have enabled the auditing of file read events, then reads are logged in the audit logs.
However, file reads do not update system::onDiskAtime even if the file reads are being
audited. All other file accesses modify the system::onDiskAtime with the current value of
atime. Therefore, before the file is retained (first bullet), if the file system is mounted with the
atime option, system::onDiskAtime represents the last accessed time before the last file
modification, not necessarily the current atime or the last accessed time. To list all read accesses
to a file, use the ibrix_audit_reports command as described in the CLI Reference Guide
StoreAll REST API 183
Page view 182
1 2 ... 178 179 180 181 182 183 184 185 186 187 188 ... 253 254

Comments to this Manuals

No comments