From: "Randy.Dunlap" <rdunlap@xenotime.net>
To: Dale Blount <linux-kernel@dale.us>
Cc: linux-kernel@vger.kernel.org
Subject: Re: scsi disk size reporting in dmesg
Date: Wed, 19 Oct 2005 22:09:20 -0700 [thread overview]
Message-ID: <20051019220920.7c91b922.rdunlap@xenotime.net> (raw)
In-Reply-To: <1129577044.17327.11.camel@dale.velocity.net>
On Mon, 17 Oct 2005 15:24:04 -0400 Dale Blount wrote:
> Hello,
>
> I just added 2 external 1TB+ scsi devices to my i686 linux server
> running 2.6.13.4 connected to external LSI MPT card. fdisk and df both
> show the sizes correctly (see below), but I'm worried that dmesg reports
> them incorrectly.
>
> SCSI device sda: 2460934144 512-byte hdwr sectors (160487 MB)
> SCSI device sdb: 3790438400 512-byte hdwr sectors (841193 MB)
>
> I don't think it's as simple as a variable overflow because both
> sdkp->capacity and mb look to be cast as unsigned long longs. I know a
> workaround is to present less data per LUN, but I'd like to use it as
> it's setup currently if possible. Is this just printing incorrectly or
> will I run into trouble when the device gets more full?
The casts to (unsigned long long) just fix the printk() args to match
the format strings (and eliminate warnings).
Looks to me like sdkp->capacity is correct. The <mb> value looks
way off. Since it's just printed here for user info, I don't see
how it can be a problem later on.
I don't see the error just yet. Are there any other SCSI device-
related messages near these? And just to confirm, but you must
have CONFIG_LBD (Large Block Device) enabled, right?
> Thanks,
>
> Dale
>
>
>
>
> # df -h
> /dev/sda1 1.2T 129M 1.1T 1% /mnt/sda1
> /dev/sdb1 1.8T 129M 1.7T 1% /mnt/sdb1
> # df
> /dev/sda1 1211159084 131228 1149504532 1% /mnt/sda1
> /dev/sdb1 1865473692 131228 1770581860 1% /mnt/sdb1
>
>
> # fdisk -l /dev/sda
> Disk /dev/sda: 1259.9 GB, 1259998281728 bytes
> 255 heads, 63 sectors/track, 153186 cylinders
> Units = cylinders of 16065 * 512 = 8225280 bytes
>
> Device Boot Start End Blocks Id System
> /dev/sda1 1 153186 1230466513+ 83 Linux
>
> # fdisk -l /dev/sdb
>
> Disk /dev/sdb: 1940.7 GB, 1940704460800 bytes
> 255 heads, 63 sectors/track, 235943 cylinders
> Units = cylinders of 16065 * 512 = 8225280 bytes
>
> Device Boot Start End Blocks Id System
> /dev/sdb1 1 235943 1895212116 83 Linux
---
~Randy
next prev parent reply other threads:[~2005-10-20 5:09 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-17 19:24 Dale Blount
2005-10-20 5:09 ` Randy.Dunlap [this message]
2005-10-20 12:17 ` Dale Blount
2005-10-20 19:26 ` Randy.Dunlap
2005-10-20 23:04 ` Bill Davidsen
2005-10-21 2:04 ` Randy.Dunlap
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=20051019220920.7c91b922.rdunlap@xenotime.net \
--to=rdunlap@xenotime.net \
--cc=linux-kernel@dale.us \
--cc=linux-kernel@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
all inboxes | Powered by JetHome®