Alpha 3000/600 _at_ OSF v3.2
root, usr, and a data filesystem are ADVfs
We had a power failure last Fri. evening and Sat. morning while all were
out of the office. Later Sat., one of the Alphas wouldn't complete a
boot. After having completed ADVfs mounts, it fails initing to
multiuser at script /rc2.d/K09snmpd, wherein the failure is at the
execution of /usr/sbin/rcmgr to get COMMON_AGENT_CONF. Well, further
testing reveiled this:
1. boot to single user and mount advfs filesets with "# bcheckrc".
2. /sbin/find on root and the data filesystems work fine
3. /sbin/find on usr filesystem fails and goes to reboot of system but I
can't get the error mssgs before screen is refreshed for reboot.
4. from singleuser, /sbin/bcheckrc mount ADVfs filesets; do a man on
/usr/sbin/rcmgr, can get following:
ADVFS error: alloc_mcell: mcell (2.1394) not really free
ADVFS cont: alloc_mcell: vol=1, page=1394
ADVFS cont: alloc_mcell: tag=0x00003f33.8066,setTag=0x00000001.8001
ADVFS EXCEPTION
Module-3, Line=2648
panic (cpu0)
syncing disks .. 1 1 1 1 1 1 1
What does this mean?
a. Does this have anything to do with a hard disk failure on the usr
partition? (same disk as root)
b. Or is this related to an ADVfs problem requireing a patch, say Patch
ID: OSF360-350163, mentioned by Drew Ibbotson <wwibbd_at_itwhy.bhp.com.au>
last August (I can't seem to locate the patch so as to read the README)
Thanks in advance.
PS, where in the documentation is there help on ADVfs errors and
troubleshooting? I really don't like to hear those black-box-like
statements about ADVfs problems. They always seem to be, paraphrasing,
"If ADVfs can't fix itself, you'll just have to write off that disk".
-Neil
--
Neil R. Smith, Res. Assoc./Sys. Admin. neils_at_csrp.tamu.edu
Dept. Meteorology, Texas A&M Univ. 409/862-4342
Received on Thu Mar 06 1997 - 00:45:14 NZDT