[Search for users] [Overall Top Noters] [List of all Conferences] [Download this site]

Conference smurf::buildhelp

Title:USG buildhelp questions/answers
Moderator:SMURF::FILTER
Created:Mon Apr 26 1993
Last Modified:Mon Jan 20 1997
Last Successful Update:Fri Jun 06 1997
Number of topics:2763
Total number of notes:5802

2131.0. "odemount -all hangs" by AOSG::FILTER (Automatic Posting Software - mail to flume::puck) Wed Feb 28 1996 13:06

Date Of Receipt: 	28-FEB-1996 09:11:24.26
From: 	SMURF::ALPHA::"franzini@dxbldr.zk3.dec.com" "28-Feb-1996 0913"
To: 	odehelp@zk3.dec.com
CC: 	franzini@dxbldr.zk3.dec.com
Subj: 	odemount -all hangs

Hello.

An odemount -all on my workstation hangs.  It appears to be because node
obothr is not accessible.  Could the mount for that node be commented out
of ode_fstab until it becomes available or something?

Thanks,
John F.


T.RTitleUserPersonal
Name
DateLines
2131.1re: odemount -all hangsAOSG::FILTERAutomatic Posting Software - mail to flume::puckFri Mar 01 1996 16:1279
Date Of Receipt: 	 1-MAR-1996 12:49:10.27
From: 	SMURF::FLUME::jmf "Joshua M. Friedman OSF/UNIX SDE  01-Mar-1996 1246"
To: 	franzini@DEC:.zko.flume
CC: 	odehelp@DEC:.zko.flume
Subj: 	re: odemount -all hangs

John, if you make odemount run in the background, this will solve this.
There will always be odemount fstab entries which are not available; i.e.
some I believe are only exported to some systems. 

See the attached workaround...


------- Forwarded Message

--------
Subject: Re: ODE start up problem - odemount hanging?
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


- -- 

				-Grant



------- End of Forwarded Message