6.3.3 HP StoreAll OS Release Notes (AW549-96082, January 2014)

Data retention and validation
• In a retention-enabled file system, if the absolute pathname (/FSNAME/<filename>) of the file
is greater than 1023 characters, the checksum is not generated and the validation scan fails.
• When using the ibrix_datavalidation –s –f FSNAME [-d PATH] command, be aware
that if the PATH is a StoreAll Archiving Infrastructure directory, the files within the path will not
be validated.
• The ibrix_vs_snap command cannot delete a block snapshot file system that is enabled for
data retention. Instead, use the ibrix_fs command with the -R option. For example:
ibrix_fs -d -f block_snap_ifs2_1 -R
• Directories are not supported in the path list for the ibrix_reten_adm command. However,
the command does not display the correct error message when the path list includes a directory.
• PDF reports do not display on Internet Explorer with Adobe Reader 10.1.2 installed. Reports
display properly with earlier versions of Adobe Reader or with other supported browsers.
• The ibrix_reten_adm -e command fails for WORM files that are not retained. If a WORM
file is not retained (either it has never been retained, or it was retained but its retention period
has expired), use the touch command to set its last accessed time (atime) forward to the desired
expiration time. The file will then be retained until that time.
• PDF reports cannot be generated from the GUI when using Windows Internet Explorer 8. To
display the PDF, use one of these options:
◦ On the browser, right-click in the white border surrounding the grey area, and select View
Source. Locate the src= line in the source. For example:
src="/fusion/reporting/retention/retention_ifs1.pdf#scrollbar=0"
width='100%' height='100%'/>
Prepend https://<hostname> to the path specified in the source and enter that URL in
the browser. Using the previous example, you would enter:
https://<hostname>/fusion/reporting/retention/retention_ifs1.pdf
◦ Log into the node specified as the hostname in the URL and go to the directory /usr/local/
ibrix/reports/output/retention, which contains the report.
Express Query Database
• If you use hard links, be aware that there could be some inconsistencies in the metadata stored
in the Express Query database. If you perform any file system operations on a hard link that
changes the system metadata, metadata stored in the file system is updated, and it is visible to a
stat call to any of the links to that file. For example, if hardlinkA and hardlinkB point to the same
file, and hardlinkA is updated, then the stat hardlinkA command produces the same (updated)
size as the stat hardlinkB command, since the stat command shows metadata from the
file system.
In contrast, Express Query treats hard links to the same file as if they are separate files. As a
result, only the hard link you modified has its metadata updated in Express Query. The Express
Query metadata for all other hard links to the same file are not updated. Express Query requests
for system::size for hardlinkA show the larger size, but requests for hardlinkB’s system::size
still report the old (smaller) size.
To find all hard linked files in a directory tree, enter the following command:
find <path> -links +1 -xtype f
Express Query treats soft links as “normal” paths. System metadata for the soft link is maintained
independently of the system metadata of the target. Custom metadata is also independent. You
Workarounds 19