From: Jeff Garzik <jeff@garzik.org>
To: Romain Kubany <rkubany@ikoula.com>
Cc: Mikael Pettersson <mikpe@it.uu.se>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-ide@vger.kernel.org" <linux-ide@vger.kernel.org>
Subject: Re: Possible regression of LBA48 support for piix
Date: Thu, 17 Dec 2009 07:22:22 -0500 [thread overview]
Message-ID: <4B2A227E.2010106@garzik.org> (raw)
In-Reply-To: <A9C151C7BD19EC47976D4AA14CF277A8BC64DFB31D@HMCEXMBX01CLUS.hmcikoula.com>
On 12/17/2009 07:07 AM, Romain Kubany wrote:
> Here it is under the 2.6.28 :
>
> # hdparm -I /dev/sda
>
> /dev/sda:
>
> ATA device, with non-removable media
> Model Number: Virtual HD
> Serial Number:
> Firmware Revision: 1.1.0
> Standards:
> Likely used: 2
> Configuration:
> Logical max current
> cylinders 16383 65535
> heads 16 16
> sectors/track 63 255
> --
> bytes/track: 65024 bytes/sector: 512
> CHS current addressable sectors: 267382800
> LBA user addressable sectors: 267382800
> device size with M = 1024*1024: 130558 MBytes
> device size with M = 1000*1000: 136899 MBytes (136 GB)
Yeah, that info is straight from the virtual disk, without any sort of
massaging. The disk is reporting 136GB max, so I would poke around
Windows to see if a setting changed somewhere... maybe there is an "old
IDE compatible" setting that got turned on, for the virtual hd?
Jeff
next prev parent reply other threads:[~2009-12-17 12:22 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <A9C151C7BD19EC47976D4AA14CF277A8BC64DFB2AF@HMCEXMBX01CLUS.hmcikoula.com>
[not found] ` <19241.63911.160765.909812@pilspetsen.it.uu.se>
2009-12-17 10:04 ` Possible regression of LBA48 support for piix Romain Kubany
2009-12-17 11:03 ` Jeff Garzik
2009-12-17 11:34 ` Romain Kubany
2009-12-17 12:02 ` Jeff Garzik
2009-12-17 12:05 ` Jeff Garzik
2009-12-17 12:07 ` Romain Kubany
2009-12-17 12:22 ` Jeff Garzik [this message]
2009-12-17 13:33 ` Bartlomiej Zolnierkiewicz
2009-12-18 13:36 ` Romain Kubany
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=4B2A227E.2010106@garzik.org \
--to=jeff@garzik.org \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mikpe@it.uu.se \
--cc=rkubany@ikoula.com \
/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).