From: Theodore Ts'o <tytso-3s7WtUTddSA@public.gmane.org>
To: James Bottomley
<James.Bottomley-d9PhHud1JfjCXq6kfMZ53/egYHeGw8Jk@public.gmane.org>
Cc: Alan Stern
<stern-nwvwT67g6+6dFdvTe/nMLpVzexx5G7lz@public.gmane.org>,
"Dale R. Worley" <worley-FrUbXkNCsVf2fBVCVOL8/A@public.gmane.org>,
linux-scsi-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
linux-usb-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: Large disk drives
Date: Wed, 5 Nov 2014 14:15:05 -0500 [thread overview]
Message-ID: <20141105191505.GF27083@thunk.org> (raw)
In-Reply-To: <1415203668.13212.2.camel@jarvis>
On Wed, Nov 05, 2014 at 05:07:48PM +0100, James Bottomley wrote:
>
> 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.
99% of the time the partition table was provided by the drive
manufacturer; I would assume they have a way of doing that as a part
of their manufacturing processes that don't require an OS individually
running the equivalent of fdisk or gdisk on said drive.
- Ted
--
To unsubscribe from this list: send the line "unsubscribe linux-usb" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2014-11-05 19:15 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
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 [this message]
[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=20141105191505.GF27083@thunk.org \
--to=tytso-3s7wtutddsa@public.gmane.org \
--cc=James.Bottomley-d9PhHud1JfjCXq6kfMZ53/egYHeGw8Jk@public.gmane.org \
--cc=linux-scsi-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-usb-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=stern-nwvwT67g6+6dFdvTe/nMLpVzexx5G7lz@public.gmane.org \
--cc=worley-FrUbXkNCsVf2fBVCVOL8/A@public.gmane.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