The SAM-FS/QFS daemons do not start and the file systems are unmountable if you performed either of the following operations:
You upgraded to Solaris 9 4/04 Release.
You applied the Solaris 9 Recommended Patch Cluster (Solaris 9 patch ID 112233-11).
The error occurs because system call 181 that the daemons normally use is being used by a different module. The module was introduced by the patch that you had just applied. The following error messages are recorded in /var/adm/messages:
/var/adm/messages Jan 5 13:28:46 host genunix: [ID 147998 kern.warning] WARNING: system call entry 181 is already in use Jan 5 13:28:46 host samfs: [ID 798779 kern.warning] WARNING: SAM-FS: modload(samsys) failed. |
In addition, the following error messages are also recorded in /var/adm/sam-log:
/var/adm/sam-log Jan 5 13:30:08 host sam-fsd[355]: [ID 617651 local4.alert] Fatal error - samsys module not loaded Jan 5 13:30:08 host sam-fsd[355]: [ID 765074 local4.alert] Correct problem and 'kill -HUP 355' |
Perform the following steps:
Become superuser.
Issue a grep of 181 from the modinfo output to determine if 181 is in use by another module:
# modinfo | grep 181 8 1181aa0 38c4 1 1 TS (time sharing sched class) 15 11b1092 181a 12 1 sad (STREAMS Administrative Driver ') 43 1295cd8 ce9 181 1 ssc050 (SSC050 i2c device driver: v1.4) 158 7813a87f 181c 95 1 cpc (cpc sampling driver v1.10) 158 7813a87f 181c 179 1 cpc (cpc sampling system call) 158 7813a87f 181c 179 1 cpc (32-bit cpc sampling system call) |
Because system call 181 is used by another module, configure samsys to use another unused system call value.
Edit /etc/name_to_sysnum by changing samsys to use 182 or some other unused value from 0-255.
samsys 182 |
Boot the system to reconfigure samsys.
# shutdown -y -g0 -i0
OK> boot -r
Verify that the error messages no longer appear in /var/adm/messages and that all SAM-FS file systems can mount.