From: "H. Peter Anvin" <hpa@zytor.com>
To: Alan Stern <stern@rowland.harvard.edu>
Cc: Oliver Neukum <oneukum@suse.de>,
James Bottomley <James.Bottomley@hansenpartnership.com>,
Ellwood Blues <elwood.blue@gmail.com>,
linux-efi@vger.kernel.org,
linux-scsi <linux-scsi@vger.kernel.org>,
USB Storage List <usb-storage@lists.one-eyed-alien.net>
Subject: Re: [usb-storage] Re: Fwd: 2TB USB hard drive for backing up
Date: Tue, 22 Jan 2013 11:05:26 -0600 [thread overview]
Message-ID: <50FEC6D6.3030708@zytor.com> (raw)
In-Reply-To: <Pine.LNX.4.44L0.1301221039350.1510-100000@iolanthe.rowland.org>
On 01/22/2013 09:43 AM, Alan Stern wrote:
> On Tue, 22 Jan 2013, Oliver Neukum wrote:
>
>> On Tuesday 22 January 2013 11:05:35 James Bottomley wrote:
>>>> May 3 18:19:06 relampago3 kernel: [ 3948.472796] sd 7:0:0:0: [sdf]
>>>> 1565565872 512-byte logical blocks: (801 GB/746 GiB)
>>>
>>> This looks like a wrap around of your actual size. This appears to
>>> indicate the device isn't replying correctly to READ CAPACITY. The
>>> conventional return from READ CAPACITY should be -1 which would trigger
>>> us to retry with READ CAPACITY(16).
>>
>> What can we do? The answer the device is giving is quite ordinary.
>> Do we need another quirk and an associated flag?
>
> The JMicron bridges are well known to be fairly buggy. Another quirk
> may indeed be the only solution. Oliver, would you like to write a
> patch for it?
>
Would it make more sense to try READ CAPACITY(16) first? Or does that
have other bad effects?
-hpa
next prev parent reply other threads:[~2013-01-22 17:05 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <jmunm9$90r$2@speranza.aioe.org>
[not found] ` <201204301814.21525.Martin@lichtvoll.de>
[not found] ` <CAGZeNoc82T0jS=Sg3d2umqi6PjAWjOKjqK2RbuK+QfAzN3Pmww@mail.gmail.com>
[not found] ` <201205010044.24643.Martin@lichtvoll.de>
[not found] ` <CAGZeNoeSEtTMK22+JcsG7xRRrbsQwgJV5iLgWenrX=rvLr-ZXQ@mail.gmail.com>
[not found] ` <CAGZeNof6NWiXhCDPpZiLu8QhQ_6Cmp-nhSOf=h=-jAjccWaa7g@mail.gmail.com>
[not found] ` <CAGZeNof6NWiXhCDPpZiLu8QhQ_6Cmp-nhSOf=h=-jAjccWaa7g-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2013-01-19 21:40 ` Fwd: 2TB USB hard drive for backing up Ellwood Blues
2013-01-21 21:21 ` H. Peter Anvin
2013-01-22 10:27 ` Ellwood Blues
[not found] ` <CAGZeNoeEoecpjvuP9uwphostOcrrAJNerxYGUtjyaMEBn04jxQ-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2013-01-22 11:05 ` James Bottomley
2013-01-22 11:49 ` Oliver Neukum
2013-01-22 11:58 ` James Bottomley
2013-01-22 15:43 ` [usb-storage] " Alan Stern
2013-01-22 17:05 ` H. Peter Anvin [this message]
2013-01-22 17:13 ` James Bottomley
[not found] ` <1358874830.2387.46.camel-sFMDBYUN5F8GjUHQrlYNx2Wm91YjaHnnhRte9Li2A+AAvxtiuMwx3w@public.gmane.org>
2013-01-22 19:17 ` H. Peter Anvin
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=50FEC6D6.3030708@zytor.com \
--to=hpa@zytor.com \
--cc=James.Bottomley@hansenpartnership.com \
--cc=elwood.blue@gmail.com \
--cc=linux-efi@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=oneukum@suse.de \
--cc=stern@rowland.harvard.edu \
--cc=usb-storage@lists.one-eyed-alien.net \
/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