From: NeilBrown <neilb@suse.de>
To: Chris Murphy <lists@colorremedies.com>
Cc: Linux RAID <linux-raid@vger.kernel.org>
Subject: Re: GPT Table broken on a Raid1
Date: Sun, 23 Sep 2012 07:58:43 +1000 [thread overview]
Message-ID: <20120923075843.42ec8efb@notabene.brown> (raw)
In-Reply-To: <F7E53090-1143-4811-86B9-E71923B98AA2@colorremedies.com>
[-- Attachment #1: Type: text/plain, Size: 1349 bytes --]
On Sat, 22 Sep 2012 12:45:39 -0600 Chris Murphy <lists@colorremedies.com>
wrote:
>
> On Sep 22, 2012, at 9:31 AM, John Robinson wrote:
>
> >
> > I don't think there's anything wrong here.
> >
> > The kernel sees the whole discs, sda and sdb, and complains that the GPT partition table looks wrong becase the second copy isn't at the end of the discs. That's correct, at the end of the raw discs is the IMSM metadata.
>
> OK so sda and sdb shouldn't have been partitioned in the first place, is what that tells me.
>
>
> > Don't try to change the partition tables on /dev/sda and sdb or you will damage the IMSM metadata.
>
> Sounds like either imsm metadata is either not well designed for GPT, or it was intended to be placed on an unpartitioned disk in the first place.
IMSM metadata is definitely intended to be placed on an un-partitioned disk.
The only real point of IMSM is to provide interoperability with other
implementations, whether the one for Windows (allowing dual-boot) or the one
in the bios (allowing boot-from-RAID5 etc).
Those other implementations use IMSM on the whole device, so it would be
pointless using mdadm/IMSM on partitions.
Note that I haven't really been following this thread, so I might have missed
the point. I'm really just responding to that last sentence.
NeilBrown
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 828 bytes --]
next prev parent reply other threads:[~2012-09-22 21:58 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-19 11:03 GPT Table broken on a Raid1 Günther J. Niederwimmer
2012-09-20 2:39 ` Chris Murphy
2012-09-20 11:05 ` Günther J. Niederwimmer
2012-09-20 17:34 ` Chris Murphy
2012-09-21 11:42 ` Günther J. Niederwimmer
2012-09-21 19:35 ` Chris Murphy
2012-09-21 22:43 ` Chris Murphy
2012-09-22 8:37 ` Günther J. Niederwimmer
2012-09-22 18:30 ` Chris Murphy
2012-09-23 6:47 ` Hello,Re: " Günther J. Niederwimmer
2012-09-23 7:17 ` Chris Murphy
2012-09-24 7:28 ` Günther J. Niederwimmer
2012-09-24 17:21 ` Chris Murphy
2012-09-24 19:06 ` Günther J. Niederwimmer
2012-09-24 20:18 ` Chris Murphy
2012-09-24 21:06 ` Günther J. Niederwimmer
2012-09-24 21:12 ` Chris Murphy
2012-09-25 8:27 ` Günther J. Niederwimmer
2012-09-25 9:28 ` John Robinson
2012-09-25 16:55 ` Chris Murphy
2012-09-26 12:17 ` Günther J. Niederwimmer
2012-09-26 19:33 ` Chris Murphy
2012-09-27 2:43 ` NeilBrown
2012-09-22 15:31 ` John Robinson
2012-09-22 18:45 ` Chris Murphy
2012-09-22 21:58 ` NeilBrown [this message]
2012-09-22 22:07 ` John Robinson
2012-09-22 22:30 ` Chris Murphy
2012-09-23 12:00 ` John Robinson
2012-09-23 17:44 ` Chris Murphy
2012-09-23 18:53 ` Chris Murphy
2012-09-24 9:37 ` John Robinson
2012-09-24 17:35 ` Chris Murphy
2012-09-24 18:17 ` Roberto Spadim
[not found] ` <CABYL=ToFtzXv95At54=jSCaD0QVSB+bdxbssda1AMw5gNBqvhg@mail.gmail.com>
2012-09-24 18:55 ` Chris Murphy
2012-09-25 7:33 ` Miquel van Smoorenburg
2012-09-21 21:30 ` Chris Murphy
2012-09-21 21:49 ` Chris Murphy
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=20120923075843.42ec8efb@notabene.brown \
--to=neilb@suse.de \
--cc=linux-raid@vger.kernel.org \
--cc=lists@colorremedies.com \
/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).