From owner-freebsd-current Sun Mar 17 22:28:49 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id WAA02486 for current-outgoing; Sun, 17 Mar 1996 22:28:49 -0800 (PST) Received: from neon.Glock.COM (root@neon.glock.com [198.82.228.159]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id WAA02480 Sun, 17 Mar 1996 22:28:47 -0800 (PST) Received: (from mmead@localhost) by neon.Glock.COM (8.7.4/8.7.3) id BAA00389; Mon, 18 Mar 1996 01:28:45 -0500 (EST) From: "matthew c. mead" Message-Id: <199603180628.BAA00389@neon.Glock.COM> Subject: a little more jaz drive info To: scsi@freebsd.org Date: Mon, 18 Mar 1996 01:28:45 -0500 (EST) Cc: current@freebsd.org 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-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Ok, I booted under a 2.1.0R kernel, and found that both my SyQuest EZ135 Drive and my JAZ drive now are able to be mounted, unmounted, ejected, and inserted multiple times. It's pretty clear now that there's some sort of subtle problem with telling removeable scsi devices they're no longer being used once they're umounted under -current. This is probably something we want to fix for the snapshot coming this week, so if someone could help me out with what files to start looking through in the /sys/scsi directory, I'll see if I can turn anything up. Thanks for listening to all this spam! -matt PS - I've CC'd this to current@freebsd.org because I believe it to be important to the development issues being discussed there. If repliers want to remove the CC feel free. -- Matthew C. Mead mmead@Glock.COM http://www.Glock.COM/~mmead/