From: Petr Vandrovec <vandrove@vc.cvut.cz>
To: DervishD <lkml@dervishd.net>
Cc: Jeff Garzik <jgarzik@pobox.com>,
Linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: [RESEND] Hard disk LBA sector count is not always the same
Date: Tue, 24 May 2005 00:21:20 +0200 [thread overview]
Message-ID: <42925760.9010603@vc.cvut.cz> (raw)
In-Reply-To: <20050523200221.GE57@DervishD>
DervishD wrote:
>>DervishD wrote:
>>
>>> current capacity is 156299375
>>> native capacity is 156301488
>>
>>Hard drives have a feature that can reserve a certain amount of space
>>away from the user.
>
>
> Yes, I know, but the problem is that 2.4 kernels *does* reserve
> that space but 2.6 certainly not, and if I boot into 2.6 and then
> reboot into 2.4, then 2.4 *does NOT* reserve that space.
Yes. It is normal...
> See the paragraph above: if I partition the disk under 2.6 the
> partition will have a bigger address than the one that will be
> available under 2.4, and that can give errors while accessing that
> extra sectors. What can I do? For technical limitations in my box, I
> have to use 2.6 for repartitioning that disk (and I will be doing
> that in less than a month) and this will lead to unaccesible sectors
> when I boot back into my usual 2.4 kernel :(
(1) You do not have to create partition over full disk.
(2) If you'll build your 2.4.x kernel with CONFIG_IDEDISK_STROKE=y
('Auto-Geometry Resizing support'), I bet that your problems with 2.4.x
kernels disappear.
Petr
next prev parent reply other threads:[~2005-05-23 22:21 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-23 12:14 [RESEND] Hard disk LBA sector count is not always the same DervishD
2005-05-23 18:31 ` Jeff Garzik
2005-05-23 20:02 ` DervishD
2005-05-23 22:21 ` Petr Vandrovec [this message]
2005-05-24 7:14 ` DervishD
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=42925760.9010603@vc.cvut.cz \
--to=vandrove@vc.cvut.cz \
--cc=jgarzik@pobox.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lkml@dervishd.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.