6.0 HP X9000 File Serving Software File System User Guide (TA768-96043, October 2011)

Meta hash: 80f68a53bb4a49d0ca19af1dec18e2ff0cf965da
Data hash: d64492d19786dddf50b5a7c3bebd3fc8930fc493
The showvms command displays the hash sums stored for the file. For example:
# /usr/local/ibrix/sbin/showvms rhnplugin.py
VMSQuery returned 0
Path hash: f4b82f4da9026ba4aa030288185344db46ffda7b
Meta hash: 80f68a53bb4a49d0ca19af1dec18e2ff0cf965da
Data hash: d64492d19786dddf50b5a7c3bebd3fc8930fc493
last attempt: Wed Dec 31 17:00:00 1969
last success: Wed Dec 31 17:00:00 1969
changed: 0
In this example, the hash sums match and there are no inconsistencies. The 1969 dates appearing
in the showvms output mean than the file had not yet been validated.
Handling validation scan errors
When a validation scan detects files having hash values inconsistent with their original values, it
displays an alert in the events section of the GUI. However, the alert lists only the first inconsistent
file detected. It is important to check the validation summary report to identify all inconsistent files
that were flagged during the scan.
To replace an inconsistent file, follow these steps:
1. Obtain a good version of the file from a backup or a remote replication.
2. If the file is retained, remove the retention period for the file, using the GUI or the
ibrix_reten_adm -c command.
3. Delete the file administratively using the GUI or the ibrix_reten_adm -d command.
4. Copy the good version of the file to the data-retained file system or directory. If you recover
the file using an NDMP backup application, the proper retention expiration period is applied
from the backup copy of the file. If you copy the file another way, you will need to set the
atime and read-only status.
Using hard links with WORM files
You can use the Linux ln command without the -s option to create a hard link to a normal
(non-WORM) file on an retention-enabled file system. If you later make the file a WORM file, the
following restrictions apply until the file is deleted:
• You cannot make any new hard links to the file. Doing this would increment the metadata of
the link count in the file's inode, which is not allowed under WORM rules.
• You can delete hard links (the original file system entry or a hard-link entry) without deleting
the other file system entries or the file itself. WORM rules allow the link count to be
decremented.
Using remote replication
When using remote replication for file systems enabled for retention, the following requirements
must be met:
• The source and target file systems must use the same retention mode (Enterprise or Relaxed).
• The default, maximum, and minimum retention periods must be the same on the source and
target file systems.
• A clock synchronization tool such as ntpd must be used on the source and target clusters. If
the clock times are not in sync, file retention periods might not be handled correctly.
124 Managing data retention and validation