From: DervishD <lkml@dervishd.net>
To: Petr Vandrovec <vandrove@vc.cvut.cz>
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 09:14:07 +0200 [thread overview]
Message-ID: <20050524071407.GA60@DervishD> (raw)
In-Reply-To: <42925760.9010603@vc.cvut.cz>
Hi Petr :)
Thanks for your answer :)
* Petr Vandrovec <vandrove@vc.cvut.cz> dixit:
> >>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...
I'm surprised :??? Does 2.6 'stroking' by default? I supposed
that maybe Debian people had activated stroking...
> > 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.
I would prefer to do it. Otherwise I have to calculate where the
partition must end in order to not disturb the kernel. Moreover, in
that space will go the swap partition, probably...
> (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.
I'll try right now... YES, it works!. I don't understand, my BIOS
is AMI, not Awards, and I assumed that the stroke option was used
only for Awards BIOS'es. I've looked at the code in the kernel and it
doesn't seem to be particular for Award :?? It should be specified in
the documentation.
Thanks a lot for your suggestion and for solving my problem :)
Raúl Núñez de Arenas Coronado
--
Linux Registered User 88736 | http://www.dervishd.net
http://www.pleyades.net & http://www.gotesdelluna.net
It's my PC and I'll cry if I want to...
prev parent reply other threads:[~2005-05-24 7:13 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
2005-05-24 7:14 ` DervishD [this message]
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=20050524071407.GA60@DervishD \
--to=lkml@dervishd.net \
--cc=jgarzik@pobox.com \
--cc=linux-kernel@vger.kernel.org \
--cc=vandrove@vc.cvut.cz \
/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