From owner-freebsd-scsi Tue Nov 19 04:26:14 1996 Return-Path: owner-freebsd-scsi Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id EAA01377 for freebsd-scsi-outgoing; Tue, 19 Nov 1996 04:26:14 -0800 (PST) Received: from bnr.ca (x400gate.nortel.ca [192.58.194.73]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id EAA01372 for ; Tue, 19 Nov 1996 04:26:12 -0800 (PST) Message-Id: <199611191226.EAA01372@freefall.freebsd.org> Received: from bcarsfba by bnr.ca id <19961119122413-1@bnr.ca>; Tue, 19 Nov 1996 07:24:14 -0500 Received: from bnr.ca by bcarsfba.bnr.ca id <16396-0@bcarsfba.bnr.ca>; Tue, 19 Nov 1996 07:19:51 -0500 Date: 19 Nov 1996 07:18 EST To: joerg_wunsch@uriah.heep.sax.de Cc: freebsd-scsi@freebsd.org, peter@taronga.com From: "barry (b.a.) scott" Subject: Re: Drive with 1024 byte logical blocks Sender: owner-freebsd-scsi@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > > Our UFS is not yet up to the task. I've seen references to 1024-byte > sectoring inside #ifdef PC98 though i'm afraid that they've simply > special-cased this one as opposed to walking through every function > and removing the implicit assumption that all the world's a DEV_BSIZE > world. > > MO drives (which are hard-sectored) also suffer from this. > John Gumb and My self are about to submit a patch against 2.2 that supports 512, 1024 and 2048 byte sectors for MO. (The algorithms scale able 2048 trivially) The changes for sd.c to support 1024 byte sectors would be simple to create as well, modelled on the od.c changes we made. Specifically we have msdosfs and ufs fully working on 2048 byte MO media. We installed the 1006 snap from 2048 byte MO media. The code changes are small. There are small changes to fdisk to read and write the mbr in real section size chunks. #ifdef'ed as tahoe in newfs.c and mkfs.c is the place to apply sector size scaleing. The kernal ufs code is untouched. In the driver we did not fight the DEV_BSIZE assumption. All we do is scale block number by the ratio of the real sector size over DEV_BSIZE. We are still testing the changes to make sure that we have not missed something. BArry