HSM Will Not Start Due to Bad Disk Volume Database
(Doc ID 2759468.1)
Last updated on APRIL 19, 2022
Applies to:
Oracle Hierarchical Storage Manager (HSM) and StorageTek QFS Software - Version 6.1.5 and laterInformation in this document applies to any platform.
Symptoms
Customer added a filesystem to their configuration while there appeared to be low memory space warnings which caused a problem resulting in the disk volume database getting corrupted.
The error messages indicate a problem with the disk volume database.
More specifically, the following message found in the /var/opt/SUNWsamfs/trace/sam-fsd file is indicative of a corrupted disk volume database.
Changes
Customer was performing HSM configuration changes (adding an additional HSM filesystem) and performing re-configuration attempts to get the configuration update completed.
Cause
To view full details, sign in with your My Oracle Support account. |
|
Don't have a My Oracle Support account? Click to get started! |
In this Document
Symptoms |
Changes |
Cause |
Solution |
References |