Date: Sun, 12 Jan 1997 14:38:08 -0700 (MST) From: Terry Lambert <terry@lambert.org> To: joerg_wunsch@uriah.heep.sax.de Cc: freebsd-hackers@freebsd.org Subject: Re: mount -o async on a news servre Message-ID: <199701122138.OAA26359@phaeton.artisoft.com> In-Reply-To: <Mutt.19970112214715.j@uriah.heep.sax.de> from "J Wunsch" at Jan 12, 97 09:47:15 pm
next in thread | previous in thread | raw e-mail | index | archive | help
> > 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. ;-) Oh? So then why is the OS even looking until it gets an insertion event? If the media isn't present, it has no business making observations about geometry in the first place. > > (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. Mode sense on a drive it knows to (1) be removable and (2) to not have media inserted. > > 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.) You are confusing the error on boot without media inserted with me explaining that the delay on umount was not the driver waiting for the drive to spin up. The parenthetical comment is logically seperate. > > The eject was manual. > > Which eject? The eject of the media following the umount which I've been complaining takes too long. > > 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. <grumble....> Maybe it could if it were hooked to a PCMCIA card. 8-). > (It doesn't even announce the arrival of a new medium unless you ask > for it, sadly.) I think you can have a request outstanding with a long timeout, which will be satisfied by insertion... I really, *really* hate the "click... click... click..." media presence checking that Win95 does on CDROMs... 8-(. Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199701122138.OAA26359>