Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!swrinde!mips!spool.mu.edu!agate!mindseye!izumi
From: izumi@mindseye.berkeley.edu (Izumi Ohzawa)
Newsgroups: comp.sys.next
Subject: Re: More on Device Busy
Message-ID: <1991May25.064738.18059@agate.berkeley.edu>
Date: 25 May 91 06:47:38 GMT
References: <1991May25.004939.8691@eng.umd.edu>
Sender: root@agate.berkeley.edu (Charlie Root)
Organization: /etc/organization
Lines: 19

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