From owner-freebsd-scsi Sun Jan 25 00:06:02 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA22588 for freebsd-scsi-outgoing; Sun, 25 Jan 1998 00:06:02 -0800 (PST) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.19]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id AAA22566 for ; Sun, 25 Jan 1998 00:05:59 -0800 (PST) (envelope-from bde@godzilla.zeta.org.au) Received: (from bde@localhost) by godzilla.zeta.org.au (8.8.7/8.8.7) id TAA12845; Sun, 25 Jan 1998 19:04:13 +1100 Date: Sun, 25 Jan 1998 19:04:13 +1100 From: Bruce Evans Message-Id: <199801250804.TAA12845@godzilla.zeta.org.au> To: dburr@POBoxes.com, gibbs@narnia.plutotech.com Subject: Re: Minor annoyances with ZIP Plus Cc: scsi@FreeBSD.ORG Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org >>["normal" errors for zip disks] >This isn't the case. FreeBSD was being silly in asking for the optional, >rigid geometry page, which the IOMega guys chose not to implement. Since >FreeBSD stopped using physical geometry to "optimize" disk I/O (which >doesn't work on the ZBR drives of today), Actually, FreeBSD only stopped using the (possibly-non-physical) geometry in the disk label as a default for newfs. This changed about 3 years ago (before 2.0.5 was released). >asking for the rigid geometry >wasn't buying us anything and the code was recently changed to use the >information returned by the Read Capacity command instead. This hasn't actually changed (at least in the current sd driver). All that changed recently is that Read Capacity is now used to determine the sector size. Read Capacity has always been used to determine the disk size, and Mode Sense of the rigid geometry page has always been used to initialize default values for the geometry in the dummy label for the whole disk. If there is a valid DOS partition on the disk, as is normally(?) the case for new zip disks, then these default values are not used. In any case, the geometry in the dummy label for fdisk is only used by fdisk and sysinstall. Initialization of disk labels normally involves copying the geometry reported by fdisk to the labels, where it is normally not used because of the 3 year old hack to newfs. Summary: everything just works, but the lowest layer is too verbose and the highest layer (newfs) is too smart. Bruce