All of lore.kernel.org
 help / color / mirror / Atom feed
From: Alan Stern <stern@rowland.harvard.edu>
To: James Bottomley <James.Bottomley@HansenPartnership.com>
Cc: "Dale R. Worley" <worley@alum.mit.edu>,
	linux-scsi@vger.kernel.org, linux-usb@vger.kernel.org
Subject: Re: Large disk drives
Date: Wed, 5 Nov 2014 11:34:11 -0500 (EST)	[thread overview]
Message-ID: <Pine.LNX.4.44L0.1411051130470.1531-100000@iolanthe.rowland.org> (raw)
In-Reply-To: <1415203668.13212.2.camel@jarvis>

On Wed, 5 Nov 2014, James Bottomley wrote:

> On Tue, 2014-11-04 at 11:14 -0500, Alan Stern wrote:
> > On Tue, 4 Nov 2014, James Bottomley wrote:
> > 
> > > 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.
> > 
> > I posted a patch to allow the user to override the reported capacity:
> > 
> > 	http://marc.info/?l=linux-scsi&m=140993840113445&w=2
> > 
> > Nobody responded to it.
> 
> Sorry, meant to.  In principle I'm OK with this as the lever for the
> hack (largely because it means we don't need to do anything) but will
> the distributions support it?

While I can't speak for the distributions, it's reasonable to assume 
that if something becomes part of the upstream kernel then they will 
include it.

> OK, but I still don't understand how windows gets the partition table on
> there in the first place ... that must surely be some sort of guess the
> disk size hack.

It's simpler than that: The drive is attached directly to the computer
(i.e., via SATA rather than USB) when the partition table is created.  
With no USB-SATA bridge chip to mess things up, there's no problem
determining the correct capacity.

Alan Stern


  reply	other threads:[~2014-11-05 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 [this message]
     [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
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=Pine.LNX.4.44L0.1411051130470.1531-100000@iolanthe.rowland.org \
    --to=stern@rowland.harvard.edu \
    --cc=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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.