HSM - Shared Clients' File System Status in 'samu g' Show "4000821" After MDS Failover
Last updated on SEPTEMBER 11, 2017
Applies to:Oracle Hierarchical Storage Manager (HSM) and StorageTek QFS Software - Version 6.0 to 6.1 [Release 6.0]
Information in this document applies to any platform.
MDS switched to secondary (from server2x to server1x). The status of 12 clients showed "4000821" for days on the "samu -g" display.
The status values were correctly updated only after the MDS was switched back to the other server.
The 'samu - g' image showing status "4000821" for all 12 clients:
There was no problem with the filesystems and the client servers' operations at the time the clients' status were showing "4000821". The customer found out that they can clear the status by rebooting the client server or by doing another MDS failover. Both of these options are disruptive.
Voluntary MDS failover occurred.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms