Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!sdd.hp.com!wuarchive!udel!haven.umd.edu!socrates.umd.edu!fletcher
From: fletcher@socrates.umd.edu (Charles Fletcher)
Newsgroups: comp.sys.next
Subject: Re: More on Device Busy
Summary: Device busy on umount
Keywords: OD, device busy, umount
Message-ID: <1991May28.172822.20355@socrates.umd.edu>
Date: 28 May 91 17:28:22 GMT
References: <1991May25.004939.8691@eng.umd.edu>
Organization: University of Maryland, University College
Lines: 25

In article <1991May25.004939.8691@eng.umd.edu> cyliao@eng.umd.edu (Chun-Yao Liao) writes:
>I've got a few responses, but most of them had same problem.
>It seems to me that the problem occurs with 040+2.1.
>
>Now, it happens always everytime when I mount an OD. I quit ALL
>processes except workspace manager... didn't help.
>I even used ofiles, an utility ported by Vic Abell, to show all
>possible processes left on OD directories... no luck, none of the 
>process has anything to do with OD, but the OD just desn't umount...
>
>any other with OD experienced the same prob? The only way I can
>correct the prob is power down and up... which is not very nice...
>

This weekend I was setting up an external HD. After formatting
and doing a BuildDisk, I mounted the drive. When I 'umount'ed
the drive I got-you guessed it-"device busy". No further explaination.
(I was still in a directory in terminal.) Since an OD is a mounted
device, I think there are two problems. One in the NeXT (a bug?)
at makes the 'umount' fail. And two, the lack of information provided
by Unix (Mach?) to correct the situation. We'll be "traveling in the
dark" for a long time due to two. Any gurus know of any diagonstics
connected to umount?

Charlie