User's Manual

hp StorageWorks File System Extender User Guide 209
Description Free space on an HSM file system runs out and the following error is written to the kernel ring
buffer (displayed by the dmesg command):
[CRITICAL] FSE-HSM not listening for FS events! Unmount FS and
check FSE logs for more details!
(Linux system-specific)
Explanation n/a
Workaround To solve this critical situation, proceed as follows:
1. Stop the FSE implementation using the fse --stop command.
2. Extend the size of the volume that stores the HSM file system. Use the lvextend command
for this purpose.
3. Reconfigure the corresponding FSE partition with modified values for the
CriticalWatermark, HighWaterMark, and ReleaseInterval variables to prevent
the HSM file system from becoming full.
4. Start the FSE implementation using the fse --start command.
5. To identify potential inconsistencies, run the fsecheck --fsc-hsmfs command on the
FSE partition containing the HSM file system which became full.
Description On a heavy loaded FSE client, after mounting an HSM file system that has reached the critical
watermark, many migration jobs are triggered and the FSE implementation becomes
unresponsive (Windows system-specific).
Explanation In the above circumstances, a race condition between the HSM file system filter and NTFS
occurs. This leads to a deadlock that blocks the system.
Workaround Proceed as follows:
1. Reconfigure the affected FSE partition with the ReleaseInterval variable set to some
large value, for example 24h.
2. Restart the FSE client system.
3. Start the FSE implementation on the FSE client.
4. If the FSE partition has not been mounted automatically, mount it using the fse --mount
command.
5. Prevent any change of data on the FSE partition and wait for pending migration jobs on the
partition to complete.
6. Unmount the FSE partition using the fse --umount command.
7. Reconfigure the FSE partition with the ReleaseInterval variable reset to its original
value.
8. Mount the FSE partition and resume with normal FSE implementation operation.
Description If the I/O traffic on an HSM file system is very high, the Hierarchical Storage Manager (HSM)
process may stop reading file system events and completely block access to the HSM file system
(Linux system-specific).
Explanation n/a
Workaround Terminate all user applications that are currently trying to access the HSM file system, including
NFS and Samba daemons.