Last updated on JULY 05, 2017
Applies to:Sun QFS and Storage Archive Manager (SAM) - Version 5.2 and later
Information in this document applies to any platform.
After a reboot of a shared QFS client, it fails to mount the shared QFS filesystem[s] automatically after a reboot.
However, it can manually be mounted, after the system comes up, without a problem. The issue is again encountered if/when the system is rebooted again and an automatic mount is attempted.
The following errors are logged in /var/adm/messages on the client:
Oct 7 11:43:57 client-hostname last message repeated 2 times
Oct 7 11:43:57 client-hostname svc.startd: [ID 748625 daemon.error] system/sam-fsd:default failed: transitioned to maintenance (see 'svcs -xv' for details)
The following service status commands confirm that the sam-fsd service is in a 'maintenance' state:
# svcs -x sam-fsd
svc:/system/sam-fsd:default (Sun QFS Daemon service)
State: maintenance since Fri Oct 07 13:32:10 2011
Reason: Start method failed repeatedly, last exited with status 98.
Impact: 1 dependent service is not running. (Use -v for list.)
# svcs -v sam-fsd
STATE NSTATE STIME CTID FMRI
maintenance - Oct_07 - svc:/system/sam-fsd:default
The default state of sam-fsd SMF start-up service was incorrectly set to 'enabled' after boot.
For SAM-QFS the default value is 'disabled' and SAM-QFS will take care of enabling it, as part of the mount process.
If it's 'enabled', by default, then when the sam-fsd daemon gets started by SMF at boot time, it's often too early for all the devices to be initiated and/or the config to be ready to load. Once sam-fsd fails, SMF marks it as in 'maintenance' mode because it assumes the admin needs to hand start the daemon.
One way this incorrect setting can occur, is by issuing the following command:
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
Million Knowledge Articles and hundreds of Community platforms