--=_courier-10021-1049415511-0001-2
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable
On Fri, 04/04/03 at 02:02:28 +0200, Andries Brouwer wrote:
> On Thu, Apr 03, 2003 at 11:11:48AM -0600, Brandon Low wrote:
>=20
> > http://bugs.gentoo.org/show_bug.cgi?id=3D18612
> >=20
> > This bug appears to be caused by using cfdisk's default allocation
> > on the last partition on a drive. From the looks of it on the user's
> > LBA mapped drive, cfdisk allocated a bunch of non-existant sectors
> > when the user allowed it to pick the default size for that last partiti=
on.
>=20
> (please break lines)
Heh, sorry about that.
>=20
> (in case something is wrong with cfdisk, tell the cfdisk maintainer,
> not the kernel list)
>=20
> (what kernel version is this? - I see, 2.4.20)
>=20
It is indeed 2.4.20 in the report.
> According to WD, this disk has 78,165,360 sectors.
> So, in case it was partitioned with such a size maybe nothing was wrong.
>=20
> The boot messages shown say:
> kenny kernel: hda: setmax LBA 78165360, native 78125000
> How come setmax has the right value and native has not?
> Did other software clip the disk?
> What is the identify data for this drive?
Interesting, I wonder why stock 2.4.20 would report it differently than the
new IDE stuff that is in our kernel, as that seems to be the problem.
>=20
> Was the partitioning done with a kernel that had CONFIG_IDEDISK_STROKE
> enabled?
Haven't heard of that option, I'll check with the bug reporter.
>=20
>=20
> Andries
>=20
Thanks a lot for the reply, it has at least helped us much to narrow things
down.
--Brandon
--=_courier-10021-1049415511-0001-2
Content-Type: application/pgp-signature
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.1 (GNU/Linux)
iD8DBQE+jM4/HCCPbR8BLcYRAtDmAJwM+Dlg2PlUym+GksY1iPVxJt1rygCeJG3z
fegBVxIOG5mCE1m2tM+WLFw=
=Pfgg
-----END PGP SIGNATURE-----
--=_courier-10021-1049415511-0001-2--