From: Andries Brouwer <aebr@win.tue.nl>
To: Jeff Garzik <jgarzik@pobox.com>
Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>,
Walt H <waltabbyh@comcast.net>,
arjanv@redhat.com,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
davzaffiro@tasking.nl
Subject: Re: [PATCH] pdcraid and weird IDE geometry
Date: Thu, 17 Jul 2003 18:03:28 +0200 [thread overview]
Message-ID: <20030717180328.A2467@pclin040.win.tue.nl> (raw)
In-Reply-To: <3F16C1F3.40206@pobox.com>; from jgarzik@pobox.com on Thu, Jul 17, 2003 at 11:34:11AM -0400
On Thu, Jul 17, 2003 at 11:34:11AM -0400, Jeff Garzik wrote:
> Can't you fix the geometry from fdisk expert mode?
>
> I've done that several times before, when otherwise like-sized disks
> appeared with vastly different geometry.
It is easiest to think that it is meaningless what you say
(in this case). A disk does not have a geometry, and
moreover you cannot change it with fdisk.
However, under some circumstances, some kernels will guess
a (translated) geometry from a DOS-type partition table,
so it is true that under some kernel versions you can use
fdisk to change the kernel's ideas about disk geometry.
A very fragile activity.
[Moreover, there are several kinds of geometry, and the present
authors of ide-disk.c conveniently confused them all.
Concerning pdcraid, I don't know for which of the possible
ideas of geometry it is true that one needs the first sector
of the last cylinder.]
Andries
next prev parent reply other threads:[~2003-07-17 15:50 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-17 2:26 [PATCH] pdcraid and weird IDE geometry Walt H
2003-07-17 8:49 ` Arjan van de Ven
2003-07-17 14:37 ` Walt H
2003-07-17 14:58 ` Alan Cox
2003-07-17 15:34 ` Jeff Garzik
2003-07-17 16:03 ` Andries Brouwer [this message]
2003-07-17 15:34 ` Andries Brouwer
2003-07-18 2:33 ` Walt H
2003-07-18 8:58 ` Andries Brouwer
2003-07-18 13:56 ` Walt H
2003-07-17 12:19 ` David Zaffiro
2003-07-18 14:51 Walt H
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=20030717180328.A2467@pclin040.win.tue.nl \
--to=aebr@win.tue.nl \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=arjanv@redhat.com \
--cc=davzaffiro@tasking.nl \
--cc=jgarzik@pobox.com \
--cc=linux-kernel@vger.kernel.org \
--cc=waltabbyh@comcast.net \
/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;
as well as URLs for NNTP newsgroup(s).