From owner-freebsd-current Wed Mar 15 23:39:02 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id XAA02237 for current-outgoing; Wed, 15 Mar 1995 23:39:02 -0800 Received: from ref.tfs.com (ref.tfs.com [140.145.254.251]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id XAA02231 for ; Wed, 15 Mar 1995 23:39:01 -0800 Received: (from phk@localhost) by ref.tfs.com (8.6.8/8.6.6) id XAA10444; Wed, 15 Mar 1995 23:38:26 -0800 From: Poul-Henning Kamp Message-Id: <199503160738.XAA10444@ref.tfs.com> Subject: Re: newfs: sectors per cylinder (4096) disagrees with disk label (36) To: bde@zeta.org.au (Bruce Evans) Date: Wed, 15 Mar 1995 23:38:25 -0800 (PST) Cc: terry@cs.weber.edu, current@FreeBSD.org, rgrimes@gndrsh.aac.dev.com In-Reply-To: <199503160703.RAA19633@godzilla.zeta.org.au> from "Bruce Evans" at Mar 16, 95 05:03:29 pm Content-Type: text Content-Length: 994 Sender: current-owner@FreeBSD.org Precedence: bulk > >1) The device-driver may use a geometry(A) to access the disk. > > >2) The UFS may be created with a geometry(B) != geometry(A) > > >3) The device driver may need to read the geometry(A) from the disklabel, > > because the BIOS lies and the drive is too dumb to answer the question. > > The disklabel is the only place this can come from. > > Only on old devices that are currently unsupported because they also > require bad144 support. > > Anyway, for sliced devices, geometry(A) is stored in the label for the > whole disk and is not necessarily related to the geometries(B) stored > in the BSD labeled slices on the disk. You can put a 4096 * 1 geometry > in the slices is that is good for file systems. Uhm, is "label for the whole disk" the MBR ? If so, how do we handle the >1023 stuff ? -- Poul-Henning Kamp -- TRW Financial Systems, Inc. 'All relevant people are pertinent' && 'All rude people are impertinent' => 'no rude people are relevant'