From: Robert Hancock <hancockr@shaw.ca>
To: Arkadiusz Miskiewicz <arekm@maven.pl>
Cc: linux-kernel@vger.kernel.org
Subject: Re: very big device. try to use READ CAPACITY(16)
Date: Wed, 25 Jul 2007 17:12:55 -0600 [thread overview]
Message-ID: <46A7D8F7.7030002@shaw.ca> (raw)
In-Reply-To: <fa.zVvXcMRLRvR5DEG+ZLYeulb/+oA@ifi.uio.no>
Arkadiusz Miskiewicz wrote:
> Hello,
>
> What does "very big device. try to use READ CAPACITY(16)" mean for user? Is
> this advice for driver developer or for user (if for user then what does it
> mean exactly) ?
It isn't really advice at all, just indicates that the sd driver needed
to use the bigger version of READ CAPACITY for that device. It looks
like that message has now been reworded to "trying to use" instead of
"try to use", so it doesn't sound like it's saying the user has to do
something.
>
>
> sdc : very big device. try to use READ CAPACITY(16).
> SCSI device sdc: 4823210240 512-byte hdwr sectors (2469484 MB)
> sdc: Write Protect is off
> sdc: Mode Sense: 00 12 00 00
> SCSI device sdc: write cache: enabled, read cache: enabled, doesn't support
> DPO or FUA
> sdc : very big device. try to use READ CAPACITY(16).
> SCSI device sdc: 4823210240 512-byte hdwr sectors (2469484 MB)
> sdc: Write Protect is off
> sdc: Mode Sense: 00 12 00 00
> SCSI device sdc: write cache: enabled, read cache: enabled, doesn't support
> DPO or FUA
> sdc: unknown partition table
> sd 0:2:0:0: Attached scsi disk sdc
>
> 2.6.21.6, stex driver
>
--
Robert Hancock Saskatoon, SK, Canada
To email, remove "nospam" from hancockr@nospamshaw.ca
Home Page: http://www.roberthancock.com/
next parent reply other threads:[~2007-07-25 23:12 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <fa.zVvXcMRLRvR5DEG+ZLYeulb/+oA@ifi.uio.no>
2007-07-25 23:12 ` Robert Hancock [this message]
2007-07-25 23:00 very big device. try to use READ CAPACITY(16) Arkadiusz Miskiewicz
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=46A7D8F7.7030002@shaw.ca \
--to=hancockr@shaw.ca \
--cc=arekm@maven.pl \
--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