| Date Of Receipt: 6-FEB-1996 15:54:00.29
From: SMURF::WASTED::bagley "Dick Bagley USG"
To: jmf@DEC:.zko.wasted
CC: bagley glidden odehelp
Subj: Re: ODE start up problem - odemount hanging?
Joshua -
Thank you very much for your suggestion. The odemount modification to
/sbin/init.d/ode3.0 got me over the problem.
On system reboot, nothing shows up in /var/adm/odemount.log, so there's no
further info there.
Anyways - I greatly appreciate your help !
- dick bagley
==============================================================================
From jmf Tue Feb 6 14:16:08 1996
Received: from flume.zk3.dec.com by fwasted.zk3.dec.com; (5.65v3.2/1.1.8.2/18Feb95-1123AM)
id AA24519; Tue, 6 Feb 1996 14:16:07 -0500
Received: from localhost by flume.zk3.dec.com; (5.65v3.2/1.1.8.2/16Jan95-0946AM)
id AA14378; Tue, 6 Feb 1996 14:16:04 -0500
Message-Id: <9602061916.AA14378@flume.zk3.dec.com>
To: bagley
Cc: odehelp, glidden
Subject: Re: ODE start up problem - odemount hanging?
In-Reply-To: Your message of "Tue, 06 Feb 96 13:08:39 EST."
<9602061808.AA09812@tlaser.zk3.dec.com>
Date: Tue, 06 Feb 96 14:16:03 -0500
From: "Joshua M. Friedman, OSF/UNIX SDE 381-1548" <jmf>
X-Mts: smtp
Dick,
Is your system setup as an ode client (it should be a client, not
a server). Is it setup to do odemounts at bootup? If you're doing
odemount -all, this mounts about 150 filesystems; you may want to
change this to only mount the trees you really use.
There was a change in odemount recently - when you reboot, if you're
setup to call odemount (grep ODEMOUNT /etc/rc.config), then this odemount
uses the -bg switch. It used to cause odemount to call mount as follows:
mount filesystem directory &
mount filesystem directory &
...
It now does
mount -o bg filesystem directory
mount -o bg filesystem directory
...
Where the 'bg' switch, from the 'man mount' reference page is defined as:
bg Retries in the background, if the first mount attempt fails.
If this is hanging your system (some nfs exports may be unavailable),
then this may be a bug in the version of UNIX you're running. You may
want to file a QAR against Digital UNIX (not ODE).
Try this as a workaround: modify the file /sbin/init.d/ode3.0 to call
odemount in the background, and to log its output.
I.e., at line 80 of this startup script, change the command from:
/usr/sde/${ODE_DEFAULT_DIR}/tools/common/odemount ${ODEMOUNT3_OPTS}
${ODE_ODEMOUNT_STRING} > /dev/null 2>&1
to:
/usr/sde/${ODE_DEFAULT_DIR}/tools/common/odemount ${ODEMOUNT3_OPTS}
${ODE_ODEMOUNT_STRING} > /var/adm/odemount.log 2>&1 &
^-changed to a file and ^-added the '&'
If this isn't at line 80 you may have an old startup that isn't calling
using the -bg switch. Rerun '/usr/sde/install/ode install' if this is
the case.
If anything useful shows up in the log file it may help diagnose the problem.
-josh
--------
To: odehelp@tlaser.zk3.dec.com
Cc: bagley@tlaser.zk3.dec.com
Subject: ODE start up problem
Date: Tue, 06 Feb 96 13:08:39 -0500
From: glidden@tlaser.zk3.dec.com
X-Mts: smtp
------- Forwarded Message
Date: Tue, 6 Feb 1996 10:27:29 -0500
From: Dick Bagley USG <bagley>
Message-Id: <9602061527.AA27322@fwasted.zk3.dec.com>
To: admin@falpha.zk3.dec.com
Subject: Unable to start ODE since yesterday...
Cc: bagley
Hi -
I have a Noritake in my office that I installed DECode II V3.0 on some
time ago. I've been using this system for my HW6 sandbox, backed to the
hw6os.nightly backing tree.
Yesterday, while re-booting the system to test out a new kernel with some
changes I need to check into HW6, the system hangs after invoking
/sbin/init.d/ode3.0 start. I get the message:
DECode II V3.0 Starting Tue Feb 6 10:23:12 EST 1996
Then nothing...After waiting quite awhile to see if I get an NFS error
message, if I type a control/c, the system will complete booting up to
the login prompt.
Any help with this ? I need this system ASAP so I can srequest/submit
some changes in before the end of the week.
Thanks,
- - dick bagley
UHS_IO
ZKO3-3/T23
------- End of Forwarded Message
|