From: Robin Hill <robin@robinhill.me.uk>
To: linux-raid@vger.kernel.org
Subject: Re: raid array with 3T disks and GPT partition
Date: Thu, 1 Sep 2011 17:58:40 +0100 [thread overview]
Message-ID: <20110901165840.GA22274@cthulhu.home.robinhill.me.uk> (raw)
In-Reply-To: <20110901163334.GA13347@apartia.fr>
[-- Attachment #1: Type: text/plain, Size: 2174 bytes --]
On Thu Sep 01, 2011 at 06:33:34PM +0200, Louis-David Mitterrand wrote:
> On Thu, Sep 01, 2011 at 04:59:13PM +0100, Robin Hill wrote:
> > On Thu Sep 01, 2011 at 05:47:59PM +0200, Louis-David Mitterrand wrote:
> > >
> > > I'm trying to create a raid6 array from 10x3T disks. Since disks > 2T
> > > must use the GPT partion table I used parted to created a single
> > > partition on each drive with the correct GPT partion type.
> > >
> > > Now how do I make sure that these partitions have the correct "raid
> > > autodetect" (fd) id? Is it even still needed? I didn't find any way to
> > > set that flag in (g)parted.
> > >
> > It's only needed for kernel auto-assembly (in which case you're also
> > limited to 0.90 metadata and 2TB drives), so no, there's no need to use
> > that. 0xDA seems to be the recommended partition type for RAID arrays
> > nowadays - that should prevent the OS from trying to read them directly.
>
> Auto-assembly and metadata are not related: I regularly use 1.2 metadata
> on non-boot partitions and they auto-assemble fine.
>
Kernel auto-assembly and metadata are related (see the description for
the --auto-detect option in the mdadm manual page). Most distributions
now use mdadm in an initrd for assembly, which will (of course) work
with any metadata version.
> However lilo won't boot on anything other than 0.9, this I found the
> hard way :)
>
LILO (and grub) should work with 0.9 or 1.0 metadata, as both of these
write the metadata at the end of the disk, leaving the start looking the
same as a normal disk (for RAID-1 anyway).
> Kernel auto-assembly seems quite useful and desirable to me, especially
> when using, say, initrd to unlock dm-crypt partitions (no need to
> configure madadm.conf in the initrd).
>
Kernel auto-assembly is not recommended by the main md developer.
> BTW, what is that 0xDA type?
>
0xDA is "non-FS data".
Cheers,
Robin
--
___
( ' } | Robin Hill <robin@robinhill.me.uk> |
/ / ) | Little Jim says .... |
// !! | "He fallen in de water !!" |
[-- Attachment #2: Type: application/pgp-signature, Size: 198 bytes --]
prev parent reply other threads:[~2011-09-01 16:58 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-01 15:47 raid array with 3T disks and GPT partition Louis-David Mitterrand
2011-09-01 15:53 ` Pim Zandbergen
2011-09-01 15:57 ` Louis-David Mitterrand
2011-09-01 16:01 ` Pim Zandbergen
2011-09-01 15:59 ` Robin Hill
2011-09-01 16:33 ` Louis-David Mitterrand
2011-09-01 16:55 ` Doug Ledford
2011-09-01 19:13 ` Rudy Zijlstra
2011-09-11 16:59 ` Bill Davidsen
2011-09-01 19:20 ` Louis-David Mitterrand
2011-09-01 20:10 ` Doug Ledford
2012-01-10 19:40 ` Phillip Susi
2012-01-25 11:15 ` Peter Grandi
2011-09-01 16:56 ` John Robinson
2011-09-01 16:58 ` Robin Hill [this message]
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=20110901165840.GA22274@cthulhu.home.robinhill.me.uk \
--to=robin@robinhill.me.uk \
--cc=linux-raid@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).