From: Phillip Susi <psusi@cfl.rr.com>
To: "linux-os (Dick Johnson)" <linux-os@analogic.com>
Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>,
Seewer Philippe <philippe.seewer@bfh.ch>,
Bartlomiej Zolnierkiewicz <bzolnier@gmail.com>,
linux-kernel@vger.kernel.org
Subject: Re: RFC: disk geometry via sysfs
Date: Thu, 16 Feb 2006 10:26:32 -0500 [thread overview]
Message-ID: <43F499A8.4080204@cfl.rr.com> (raw)
In-Reply-To: <Pine.LNX.4.61.0602160728100.20319@chaos.analogic.com>
linux-os (Dick Johnson) wrote:
>> I'm talking about the geometry of the disk. If the disk has 16 sectors
>> and 8 heads, then the maximum value allowed for any valid address is 16
>> in the sector field and 7 in the heads field. This influences the
>> translation to/from LBA. A sector with LBA of 1234 would have a CHS
>> address using this geometry of 9/5/3. If the disk reports a geometry of
>> x/8/16 but the bios is using a geometry of x/255/63, then when you pass
>> 9/5/3 to int 13 it will fetch LBA 144902 which is clearly not going to
>> give you what you wanted.
>>
>
> Wrong! The disk gets an OFFSET! It doesn't care how that OFFSET
> is obtained. That OFFSET is the sum of some variables. Some start
> at 0 and some start at 1. The BIOS takes these PHONY things, without
> checking to see if they "fit" in some pre-conceived notion of
> "geometery" and sums them all up to make an OFFSET. The C/H/S
> stuff started and ENDED with the ST-506 interface. PERIOD.
>
Please reread my explanation above. The bios has to compute the
absolute offset based on the geometry and the values you pass it. It
does so by multiplying the track number you pass by the number of
sectors per track, multiplies the cylinder number by the number of
sectors per track and the number of tracks, and adds those two values to
the sector number you pass to arrive at the LBA to read. If it performs
the CHS->LBA translation using a different geometry than you used to go
from LBA->CHS, then it will get the wrong sector.
next prev parent reply other threads:[~2006-02-16 15:27 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-10 13:06 RFC: disk geometry via sysfs Seewer Philippe
2006-02-13 9:56 ` Bartlomiej Zolnierkiewicz
2006-02-15 7:57 ` Seewer Philippe
2006-02-13 16:32 ` Phillip Susi
2006-02-13 19:02 ` Seewer Philippe
2006-02-13 19:22 ` linux-os (Dick Johnson)
2006-02-13 19:36 ` Phillip Susi
2006-02-14 16:35 ` Seewer Philippe
2006-02-13 19:34 ` Phillip Susi
[not found] ` <43F206E7.70601@bfh.ch>
2006-02-14 18:19 ` Phillip Susi
2006-02-15 8:39 ` Seewer Philippe
2006-02-15 8:51 ` Bartlomiej Zolnierkiewicz
2006-02-15 9:01 ` Seewer Philippe
2006-02-15 14:06 ` Alan Cox
2006-02-15 14:11 ` Seewer Philippe
2006-02-15 15:15 ` Alan Cox
2006-02-15 15:29 ` Phillip Susi
2006-02-16 8:12 ` Seewer Philippe
2006-02-16 15:36 ` Phillip Susi
2006-02-16 15:41 ` Seewer Philippe
2006-02-16 16:15 ` Phillip Susi
2006-02-15 15:20 ` Phillip Susi
2006-02-15 16:06 ` Alan Cox
2006-02-15 16:20 ` Phillip Susi
2006-02-15 17:32 ` Alan Cox
2006-02-15 18:43 ` Phillip Susi
2006-02-15 19:23 ` linux-os (Dick Johnson)
2006-02-15 20:54 ` Phillip Susi
2006-02-15 21:41 ` linux-os (Dick Johnson)
2006-02-15 22:43 ` Phillip Susi
2006-02-16 12:33 ` linux-os (Dick Johnson)
2006-02-16 15:26 ` Phillip Susi [this message]
2006-02-16 16:15 ` Seewer Philippe
2006-02-16 17:01 ` Phillip Susi
2006-02-16 16:39 ` linux-os (Dick Johnson)
2006-02-16 17:09 ` Phillip Susi
2006-02-16 19:01 ` linux-os (Dick Johnson)
2006-02-16 19:55 ` Phillip Susi
2006-02-16 8:18 ` Seewer Philippe
2006-02-16 18:14 ` Matt Domsch
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=43F499A8.4080204@cfl.rr.com \
--to=psusi@cfl.rr.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=bzolnier@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-os@analogic.com \
--cc=philippe.seewer@bfh.ch \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox