Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!seismo!mimsy!chris
From: chris@mimsy.UUCP (Chris Torek)
Newsgroups: comp.unix.questions
Subject: Re: unmounting file systems
Message-ID: <6898@mimsy.UUCP>
Date: Wed, 3-Jun-87 08:56:12 EDT
Article-I.D.: mimsy.6898
Posted: Wed Jun  3 08:56:12 1987
Date-Received: Sat, 6-Jun-87 20:43:12 EDT
References: <1734@drivax.UUCP>
Organization: U of Maryland, Dept. of Computer Science, Coll. Pk., MD 20742
Lines: 29

In article <1734@drivax.UUCP> braun@drivax.UUCP (Kral) writes:
>... I am running 4.2BSD on an 11/780 with a TU78, RM03, and an RP07.
>... a problem with automatically unmounting all partitions reliably.
>The main culprit seems to be the line printer spooler.  If there is
>anything spooled (say a printer is out of paper and one or more jobs
>are waiting) then /usr won't unmount.

Since shutdown is supposed to kill everything, the spooler should
die too.  (If you are getting the infamous

	WARNING: something is hung (wont die); ps axl advised

message, your kernel probably has a device driver bug.)

>... when the system reboots and mounts the other file systems,
>things get confused when a mount of an already mounted file system
>is attempted.

If you are in fact rebooting, no file systems save `/' are mounted.
I guess that you are simply returning to multi-user mode.  You
can either leave the file systems mounted throughout---the shutdown
guarantees that nothing is running, so once synced, the file systems
are stable---or you can use `mount -f -a' to force mount to ignore
any errors.  The latter will pretend to mount such things as file
systems with corrupted superblocks.  It may also not exist in stock
4.2BSD (which crashes when you mount bad superblocks anyway).
-- 
In-Real-Life: Chris Torek, Univ of MD Comp Sci Dept (+1 301 454 7690)
Domain:	chris@mimsy.umd.edu	Path:	seismo!mimsy!chris