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] | |
| details! | |
| (Linux system specific) | |
Explanation | n/a | |
Workaround | To solve this critical situation, proceed as follows: | |
| 1. | Check free space on the HSM file system. Invoke the following command: |
|
| df |
| 1. | Stop the FSE implementation: |
|
| fse |
| 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: |
|
| fse |
| 5. | To identify potential inconsistencies, run the following command on the FSE partition |
|
| containing the HSM file system which became full: |
fsecheck
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. |
HP StorageWorks File System Extender Software user guide 259