public inbox for linux-scsi@vger.kernel.org
 help / color / mirror / Atom feed
From: James Bottomley <James.Bottomley@HansenPartnership.com>
To: "Dale R. Worley" <worley@alum.mit.edu>
Cc: linux-scsi@vger.kernel.org, linux-usb@vger.kernel.org
Subject: Re: Large disk drives
Date: Tue, 04 Nov 2014 08:52:42 +0100	[thread overview]
Message-ID: <1415087562.2351.3.camel@jarvis.mobile.lan> (raw)
In-Reply-To: <201411032106.sA3L6MqU026397@hobgoblin.ariadne.com>

On Mon, 2014-11-03 at 16:06 -0500, Dale R. Worley wrote:
> Was there any resolution as to how large disk drives would be handled
> if their interface did not support the "capacity" request that would
> tell how large they were?

Realistically no ... unless someone comes up with a reliable heuristic
to give us the size.

> Or as an alternative, is there any way to avoid buying USB-SCSI
> interfaces that do not support the large-capacity request?
> Unfortunately, such devices work OK with Windows (since Windows trusts
> what the partition table says), you can't just say to the salesperson
> "It has to work on drives over 3 TB."

This is a stopgap: your 3TB drive can be guessed as the 16 bit capacity
plus 2TB, but the same won't happen for a 5TB device.  Believing the
partition table gives us a chicken and egg problem because something
still has to get the partition table on to the device.

I don't think "don't buy something that doesn't work" is a hugely
unreasonable response to this.

James

> Dale
> --
> To unsubscribe from this list: send the line "unsubscribe linux-scsi" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> 



  reply	other threads:[~2014-11-04  7:52 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 [this message]
     [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
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=1415087562.2351.3.camel@jarvis.mobile.lan \
    --to=james.bottomley@hansenpartnership.com \
    --cc=linux-scsi@vger.kernel.org \
    --cc=linux-usb@vger.kernel.org \
    --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