From owner-freebsd-scsi Tue Mar 19 05:45:51 1996 Return-Path: owner-freebsd-scsi Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id FAA28576 for freebsd-scsi-outgoing; Tue, 19 Mar 1996 05:45:51 -0800 (PST) Received: from who.cdrom.com (who.cdrom.com [204.216.27.3]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id FAA28547 for ; Tue, 19 Mar 1996 05:45:10 -0800 (PST) Received: from neon.Glock.COM (root@neon.glock.com [198.82.228.159]) by who.cdrom.com (8.6.12/8.6.11) with ESMTP id FAA26907 for ; Tue, 19 Mar 1996 05:45:04 -0800 Received: (from mmead@localhost) by neon.Glock.COM (8.7.4/8.7.3) id IAA04250; Tue, 19 Mar 1996 08:41:45 -0500 (EST) From: "matthew c. mead" Message-Id: <199603191341.IAA04250@neon.Glock.COM> Subject: Re: a little bit more information on the jaz drive situation... To: bde@zeta.org.au (Bruce Evans) Date: Tue, 19 Mar 1996 08:41:45 -0500 (EST) Cc: bde@zeta.org.au, scsi@freebsd.org In-Reply-To: <199603190654.RAA06722@godzilla.zeta.org.au> from "Bruce Evans" at Mar 19, 96 05:54:14 pm X-Mailer: ELM [version 2.4 PL24 ME8a] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-scsi@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Bruce Evans writes: > > The suggestion you made about ffs_unmount() and > >vn_close() halfway worked. I reversed the order of the calls, > >and the drives are now able to eject once they've been unmounted. > >Unfortunately, however, something is still wrong because if you > >try to reinsert the cartridge and mount it again, it ends up > >complaining that the device is busy. I'm guessing here, but does > >this have something to do with some other counter not being > >decremented properly so that the kernel thinks the device is > >still being used? > Try the fix in -current. I'll sup it and try it out tonight. For temporary use I've got the "> 2" patch installed so I can back things up normally, but I'd like to have a real fix... > The bug affects my zip drive too. It worked a week or two ago, but > not today for ufs mounted file systems. It still works for ext2fs > mounted file systems because there is no vmio stuff for ext2fs. I haven't played with ext2fs at all - might be a reason to play with caldera at some point. The bug affected my JAZ and my EZ135 drives... -matt -- Matthew C. Mead mmead@Glock.COM http://www.Glock.COM/~mmead/