public inbox for linux-scsi@vger.kernel.org
 help / color / mirror / Atom feed
From: Boaz Harrosh <boaz@plexistor.com>
To: James Bottomley <James.Bottomley@HansenPartnership.com>
Cc: Christoph Hellwig <hch@infradead.org>,
	Alan Stern <stern@rowland.harvard.edu>,
	"Dale R. Worley" <worley@alum.mit.edu>,
	linux-scsi@vger.kernel.org, linux-usb@vger.kernel.org
Subject: Re: Large disk drives
Date: Thu, 06 Nov 2014 18:34:28 +0200	[thread overview]
Message-ID: <545BA314.4050109@plexistor.com> (raw)
In-Reply-To: <1415289258.10617.4.camel@jarvis.quadriga.com>

On 11/06/2014 05:54 PM, James Bottomley wrote:
> 
> We don't have a failure.  This is the problem.  Determining that a
> problem exists 
> 

OK Sorry. I assumed the bridge is smart enough to do nothing,

ie READ_CAPACITY_10 is passed as is via sata to the device that
actually supports READ_CAPACITY_16, as I understand then the 
actual good drive is not suppose to send size-modulue-2G in
response to READ_CAPACITY_10. Should it ?

Then the bridge just sends that back to me, now if I send
READ_CAPACITY_16 the bridge will return NOT-SUPPORTED because
it is unexpected.

But what are you saying that the bridge was smart enough to
do READ_CAPACITY_16 get a 64bit value from the drive and then
return the lower 32bit to me ? Really ? I would not imagine
in the life of me someone so dumb. And surly it is against
any spec.

Are you sure ? I think you are wrong I think the guy reported
that he can only see 2T out of his 3T drive which means the
bridge returned 0xffffffff, exactly 2T

> James
> 
> 

But hey, I guess stupidity is limitless, this one here pushing
real far.

Cheers
Boaz


  reply	other threads:[~2014-11-06 16:34 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-11-03 21:06 Large disk drives Dale R. Worley
2014-11-04  7:52 ` James Bottomley
     [not found]   ` <1415087562.2351.3.camel-7O4RPy5TklLPRNG96csxHf8+0UxHXcjY@public.gmane.org>
2014-11-04 16:14     ` Alan Stern
     [not found]       ` <Pine.LNX.4.44L0.1411041112010.966-100000-IYeN2dnnYyZXsRXLowluHWD2FQJk+8+b@public.gmane.org>
2014-11-05 15:51         ` Dale R. Worley
2014-11-05 16:07       ` James Bottomley
2014-11-05 16:34         ` Alan Stern
     [not found]           ` <Pine.LNX.4.44L0.1411051130470.1531-100000-IYeN2dnnYyZXsRXLowluHWD2FQJk+8+b@public.gmane.org>
2014-11-05 18:53             ` Boaz Harrosh
2014-11-05 19:30           ` Christoph Hellwig
     [not found]             ` <20141105193045.GA13265-wEGCiKHe2LqWVfeAwA7xHQ@public.gmane.org>
2014-11-06 10:30               ` James Bottomley
2014-11-06 14:33                 ` Boaz Harrosh
     [not found]                   ` <545B86AC.3080704-/8YdC2HfS5554TAoqtyWWQ@public.gmane.org>
2014-11-06 15:53                     ` Alan Stern
2014-11-06 16:43                       ` Boaz Harrosh
     [not found]                         ` <545BA52F.6050205-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2014-11-06 17:08                           ` David Laight
2014-11-06 17:18                             ` James Bottomley
2014-11-06 15:54                   ` James Bottomley
2014-11-06 16:34                     ` Boaz Harrosh [this message]
2014-11-06 16:59                       ` Alan Stern
2014-11-06 19:23                 ` Dale R. Worley
2014-11-06 20:16                   ` Alan Stern
2014-11-05 19:15         ` Theodore Ts'o
     [not found]           ` <20141105191505.GF27083-AKGzg7BKzIDYtjvyW6yDsg@public.gmane.org>
2014-11-06 19:17             ` Dale R. Worley
2014-11-05 23:30       ` Dale R. Worley
2014-11-06 17:47         ` Alan Stern
  -- strict thread matches above, loose matches on Subject: below --
2014-11-07  4:53 Norman Diamond
     [not found] ` <533357.25557.qm-303aDswoEIZ5hgrKqgaBcEyFvBl6snHEEwWAM/ix52Y@public.gmane.org>
2014-11-07 10:03   ` David Laight
2014-11-08  0:35     ` Norman Diamond

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=545BA314.4050109@plexistor.com \
    --to=boaz@plexistor.com \
    --cc=James.Bottomley@HansenPartnership.com \
    --cc=hch@infradead.org \
    --cc=linux-scsi@vger.kernel.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=stern@rowland.harvard.edu \
    --cc=worley@alum.mit.edu \
    /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