From owner-freebsd-scsi Sun Mar 17 23:47:18 1996 Return-Path: owner-freebsd-scsi Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id XAA05442 for freebsd-scsi-outgoing; Sun, 17 Mar 1996 23:47:18 -0800 (PST) Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.19]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id XAA05435 for ; Sun, 17 Mar 1996 23:47:14 -0800 (PST) Received: (from bde@localhost) by godzilla.zeta.org.au (8.6.12/8.6.9) id SAA12737; Mon, 18 Mar 1996 18:42:33 +1100 Date: Mon, 18 Mar 1996 18:42:33 +1100 From: Bruce Evans Message-Id: <199603180742.SAA12737@godzilla.zeta.org.au> To: mmead@Glock.COM, scsi@freebsd.org Subject: Re: a little bit more information on the jaz drive situation... Sender: owner-freebsd-scsi@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > Ok, I've got some more information for ya, folks! Somewhere >in between 2.1.0R and -current, a bug must have crept in. Since >I've started running -current (cause it makes the Jaz drive >sleep/unsleep properly while it's mounted), I haven't used my >SyQuest EZ135 Drive. I tried it tonight. If I mount it, unmount >it, and then hit eject, it doesn't eject! It DID under 2.1.0R... >It seems like somehow the unmount code isn't telling the drives >they are no longer busy... any ideas? I'll keep playing... See PR 1087. Last-close has been broken since approx 1995/03/02 in -current. Bruce