From: Tim Small <tim@seoss.co.uk>
To: "linux-raid@vger.kernel.org" <linux-raid@vger.kernel.org>
Cc: Jon@eHardcastle.com
Subject: Re: Is this likely to cause me problems?
Date: Wed, 22 Sep 2010 10:09:04 +0100 [thread overview]
Message-ID: <4C99C7B0.4090807@seoss.co.uk> (raw)
In-Reply-To: <94202.62107.qm@web51304.mail.re2.yahoo.com>
On 21/09/10 22:07, Jon Hardcastle wrote:
> Are you sure this is the issue?
Pretty sure.
> the number of blocks is different in both measurements see below..
>
Yes - differing CHS-compatible geometry will do this, because
CHS-compatible partitions will start/end on the fake "cylinder"
boundaries. So you have different amounts of unnecessary wastage at
both the start and the end when using different number of pretend
cylinders, heads, and sectors per track...
If there's nothing on the disk yet, then surely you haven't got anything
to lose by telling fdisk to use different CHS layouts (using the command
line switches) anyway, or just ignoring CHS entirely and using the whole
disk - and like I said it's highly unlikely anything on your system ever
does anything with CHS block addressing anyway - Linux uses LBA
addressing exclusively, and so do its bootloaders.
Tim.
--
South East Open Source Solutions Limited
Registered in England and Wales with company number 06134732.
Registered Office: 2 Powell Gardens, Redhill, Surrey, RH1 1TQ
VAT number: 900 6633 53 http://seoss.co.uk/ +44-(0)1273-808309
next parent reply other threads:[~2010-09-22 9:09 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <94202.62107.qm@web51304.mail.re2.yahoo.com>
2010-09-22 9:09 ` Tim Small [this message]
2010-09-21 20:33 Is this likely to cause me problems? Jon Hardcastle
2010-09-21 21:15 ` John Robinson
2010-09-21 21:18 ` Jon Hardcastle
2010-09-21 22:34 ` John Robinson
2010-09-22 6:42 ` Jon Hardcastle
2010-09-22 11:25 ` John Robinson
2010-09-22 14:38 ` Jon Hardcastle
2010-09-23 13:14 ` John Robinson
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=4C99C7B0.4090807@seoss.co.uk \
--to=tim@seoss.co.uk \
--cc=Jon@eHardcastle.com \
--cc=linux-raid@vger.kernel.org \
/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).