Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!usc!wuarchive!zaphod.mps.ohio-state.edu!sample.eng.ohio-state.edu!purdue!haven.umd.edu!socrates.umd.edu!fletcher
From: fletcher@socrates.umd.edu (Charles Fletcher)
Newsgroups: comp.sys.next
Subject: Re: More on Device Busy
Message-ID: <1991May28.173536.20550@socrates.umd.edu>
Date: 28 May 91 17:35:36 GMT
References: <1991May25.004939.8691@eng.umd.edu> <1991May25.064738.18059@agate.berkeley.edu>
Organization: University of Maryland, University College
Lines: 31

In article <1991May25.064738.18059@agate.berkeley.edu> izumi@mindseye.berkeley.edu (Izumi Ohzawa) writes:
>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.
>>
>>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...
>
>We haven't experienced any problem during the past 1.5months
>with 040+2.1 on two cubes.
>
>In 2.0 days, it happened once to one of the users, and OD
>could be ejected when the person logged out.
>
>Just a data point.  Maybe my OD will get stuck tomorrow.
>
>Izumi Ohzawa             [ $@Bg_78^=;(J ]
>USMail: University of California, 360 Minor Hall, Berkeley, CA 94720
>Telephone: (415) 642-6440             Fax:  (415) 642-3323
>Internet: izumi@violet.berkeley.edu   NeXTmail: izumi@pinoko.berkeley.edu 

I had a disk do this a couple of weeks ago. When I tried to log out,
I *couldn't* due to the "device busy". I finally gave up and did the
ole Cmd-Cmd ~ ej routine. When I tried to fix the OD the next login,
it failed the fsck. I had to do alot of scrambling to recover the data
(a few blocks had been trashed.)

So the lesson of this data point is *be careful!* Also see my follow-up
comments to the related post.

-Charlie