[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

2116.0. "odemount -bg bug ?" by AOSG::FILTER (Automatic Posting Software - mail to flume::puck) Tue Feb 20 1996 15:44

Date Of Receipt: 	20-FEB-1996 14:57:35.83
From: 	SMURF::FLUME::jmf "Joshua M. Friedman OSF/UNIX SDE  20-Feb-1996 1453"
To: 	decwet::ode
CC: 	odehelp@DEC:.zko.flume
Subj: 	odemount -bg "bug" ?

DECwest ODE Help,

Enough people have complained about this (this makes 3 since I put back
the supported odemount in place of our local odemount), that I'd say it's
a bug, or at least a very needed feature.  Either the -bg switch should
cause the mounts to use "&", or the ode install script run during bootup
should background the odemount command.

It may be that there's also a QAR against "mount" here.

Thanks...		-josh

------- Forwarded Message

Return-Path: [email protected] 
Delivery-Date: Tue, 20 Feb 96 14:17:14 -0500
Return-Path: [email protected]
Received: from alpha.zk3.dec.com by flume.zk3.dec.com; (5.65v3.2/1.1.8.2/16Jan95-0946AM)
	id AA28665; Tue, 20 Feb 1996 14:17:04 -0500
Received: from cardinal.zk3.dec.com by falpha.zk3.dec.com; (5.65v3.2/1.1.8.2/20May95-1022AM)
	id AA18601; Tue, 20 Feb 1996 14:16:34 -0500
Received: from localhost by cardinal.zk3.dec.com; (5.65v3.2/1.1.8.2/28Oct95-0926PM)
	id AA01277; Tue, 20 Feb 1996 14:16:33 -0500
Message-Id: <[email protected]>
X-Mailer: exmh version 1.6.5 12/11/95
To: [email protected]
Cc: [email protected], [email protected]
Subject: Re: odemount -bg -all hangs since inr disk upheaval... 
In-Reply-To: Your message of "Tue, 20 Feb 96 14:11:03 EST."
             <[email protected]> 
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Tue, 20 Feb 96 14:16:32 -0500
From: "Grant Van Dyck" <[email protected]>
X-Mts: smtp

Here's an earlier response to the same problem that may answer your question. 
This really has nothing to do with inr, but has to do with change to odemount. 
See the attached message.



Subject: re  DECode II hangs during boot

Subject: Re: ODE start up problem - odemount hanging?
In-Reply-To: Your message of "Tue, 06 Feb 96 13:08:39 EST."
             <[email protected]> 
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


T.RTitleUserPersonal
Name
DateLines