Date: Fri, 10 Dec 2010 08:58:28 +0000 From: Bruce Cran <bruce@cran.org.uk> To: Bruce Evans <brde@optusnet.com.au> Cc: src-committers@freebsd.org, svn-src-all@freebsd.org, Andriy Gapon <avg@freebsd.org>, Bruce Cran <brucec@freebsd.org>, svn-src-head@freebsd.org, Matthew Jacob <mj@feral.com> Subject: Re: svn commit: r216269 - head/sys/geom/part Message-ID: <20101210085828.780e2d45@core.draftnet> In-Reply-To: <20101210092805.M8539@besplex.bde.org> References: <201012072046.oB7KkB4L079555@svn.freebsd.org> <4CFEAD09.30904@freebsd.org> <4CFEAFA6.4020103@feral.com> <4CFEB1AD.70906@freebsd.org> <20101208153857.H1428@besplex.bde.org> <20101208225235.501ced0e@core.draftnet> <20101209191657.B1400@besplex.bde.org> <20101209221458.42448075@core.draftnet> <20101210092805.M8539@besplex.bde.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Fri, 10 Dec 2010 10:12:34 +1100 (EST) Bruce Evans <brde@optusnet.com.au> wrote: > The BIOS has little control over the mode. It can't enforce LBA if > the drive supports CHS. It can't force any particular CHS mode since > the driver may set any CHS mode. ata used to reset the drive in the > probe and in reinit. I think this is a hard reset which restores the > default CHS. I can't see where ata resets now. It is nicely > obfuscated using function pointers. I think it does less resetting. > It also has a soft reset for at least sata, but sata won't be using > CHS. Removing of resets would explain why it now has to use the > current CHS (since it doesn't change the CHS back to the default). The BIOS does seem to have complete control over the geometry that FreeBSD detects. Yes we'll use LBA mode if it's available, but what I'm talking about is the geometry that gets used for creating disklabels and the MBR. Since I saw the change in the BIOS reflected in what FreeBSD detected, it appears the BIOS has control over those values except when it decides to initially use LBA mode. > The driver always ignores CHS (except to report it) and uses LBA if > possible. If a manufacturer stops supporting CHS, then the driver > shouldn't notice, but the manufacturer's non-support should include > setting the obsolete fields to 0 (or possibly other specified magic > numbers). It is then up to utilities whether to report these fields > as simply there value or to decrypt their magic values into a CHS- > unsupported flag (I don't know of any actual flag for this). Then > there is the "firmware geometry" reported to GEOM. You could try > changing this to 0/0/0 and see what breaks. CAM for SCSI drives still > invents a geometry to avoid seeing evil here, since SCSI drives have > only had no geometry for about 30 years now. But the problem is that we _do_ use CHS: we use it to create the MBR and disklabel. Linux invents a geometry if it can't create one from the on-disk data; we don't. -- Bruce Cran
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20101210085828.780e2d45>