osyjm@caesar.cs.montana.edu (Jaye Mathisen) (04/23/91)
I've got a fresh install of 7.0.5 on a 9000/350SRX, and I'm noticing some
odd behavior.
The node hung the other day, and wouldn't respond to anything. So I power
it off, power it on, it starts to reboot, gets to the fsck part and starts
checking all the drives. My checklist file is something like:
/dev/dsk/src /src hfs rw 0 3
/dev/dsk/oct-5.0 /src/oct-5.0 hfs rw 0 4
It fsck's /dev/dsk/src, prints the message marking file system clean.
Then a few seconds later in the boot process, when it does the mount -a,
Mount gripes that /dev/dsk/src needs to be fsck'd before mounting. I run
fsck on it manually, and then it mounts fine. Any clue as to why the
first fsck doesn't really mark the disk clean? I've tried this twice by
just crashing the machine, and it's very consistent.
Second problem is that it appears that mount traverses the checklist
backwards (sometimes) . Given the above slice of /etc/checklist, a mount -a
typed manually (after the fsck) will say that /src/oct-5.0 doesn't exist, and
THEN it will mount /dev/dsk/src, and then a second mount -a will work.
However, it looks like during the bootup sequence, the order is the other way
around, ie, /dev/dsk/src has to be before /dev/dsk/oct-5.0. Isn't this
odd behavior? I suppose the simple solution is to have localrc() do about
20 mount -a's, just so I'm sure all the disks really do get mounted.
BTW this really wreaks havoc with my NFS stuff...
Please e-mail and I'll summarize and post if demand warrants.
--
Jaye Mathisen,sysmgr 410 Roberts Hall,Dept. of Computer Science
Montana State University,Bozeman MT 59717 PHONE: (406) 994-{4780,3931}