From owner-freebsd-hackers Sun Jan 12 12:51:35 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id MAA20556 for hackers-outgoing; Sun, 12 Jan 1997 12:51:35 -0800 (PST) Received: from sax.sax.de (sax.sax.de [193.175.26.33]) by freefall.freebsd.org (8.8.4/8.8.4) with SMTP id MAA20547 for ; Sun, 12 Jan 1997 12:51:31 -0800 (PST) Received: (from uucp@localhost) by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id VAA25020 for freebsd-hackers@freebsd.org; Sun, 12 Jan 1997 21:51:27 +0100 Received: (from j@localhost) by uriah.heep.sax.de (8.8.4/8.6.9) id VAA13526; Sun, 12 Jan 1997 21:47:16 +0100 (MET) Message-ID: Date: Sun, 12 Jan 1997 21:47:15 +0100 From: j@uriah.heep.sax.de (J Wunsch) To: freebsd-hackers@freebsd.org Subject: Re: mount -o async on a news servre References: <199701121917.LAA25941@root.com> <199701121947.MAA26105@phaeton.artisoft.com> X-Mailer: Mutt 0.55-PL10 Mime-Version: 1.0 X-Phone: +49-351-2012 669 X-PGP-Fingerprint: DC 47 E6 E4 FF A6 E9 8F 93 21 E0 7D F9 12 D6 4E Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: <199701121947.MAA26105@phaeton.artisoft.com>; from Terry Lambert on Jan 12, 1997 12:47:36 -0700 Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk As Terry Lambert wrote: > I realize FreeBSD has problems handling JAZ drives that the other > BSD's do not, like getting the media size right for a drive without ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ > meduia inserted instead of throwing an error into dmesg: ^^^^^^^^^^^^^^^ You simply can't do this. Either, the drive reports a medium size, or it doesn't. If it doesn't, you're at wits end: the drive could support differently sized media as well, so you can't even guess which one Terry will insert next. ;-) > > (ncr0:1:0): "iomega jaz 1GB G.60" type 0 removable SCSI 2 > sd1(ncr0:1:0): Direct-Access > sd1(ncr0:1:0): FAST SCSI-2 100ns (10 Mb/sec) offset 8. > > sd1(ncr0:1:0): ILLEGAL REQUEST asc:24,0 Invalid field in CDB This one might be a FreeBSD driver problem. You can compile your kernel with SCSIDEBUG enabled, to learn which SCSI command triggered that problem. > sd1 could not mode sense (4). Using ficticious geometry > > sd1(ncr0:1:0): NOT READY asc:3a,0 Medium not present > sd1: could not get size > 0MB (0 512 byte sectors) > > However, I doubt if this is JAZ specific; it seems more related to it > being removable than anything else. > > (yes, the drive was spun up at the time, so you can't blame that). The drive was not read. It claimed the medium being not present. How should the driver know that there really was a medium in the drive, if it claims wrong? (FreeBSD had a problem with devices saying ``Device is in the process of becoming ready'', but i fixed this recently.) > The eject was manual. Which eject? > Truly, when I press the eject button, an "umount -f" operation should > occur on behalf of the FS's mounted on the drive... oh well. I'm afraid you gotta wait for SCSI-4 for this to happen. AFAIK, the drive doesn't start a transaction on the bus if you press the eject button, saying ``Terry wishes to eject my cartridge right now''. :-) So the system couldn't know, even at best willingness. (It doesn't even announce the arrival of a new medium unless you ask for it, sadly.) -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-)