From: David Greaves <david@dgreaves.com>
To: Peter Rabbitson <rabbit+list@rabbit.us>
Cc: linux-raid@vger.kernel.org
Subject: Re: Proper partition type for components with V1.x superblocks?
Date: Wed, 11 Jun 2008 12:24:21 +0100 [thread overview]
Message-ID: <484FB5E5.8000207@dgreaves.com> (raw)
In-Reply-To: <484F9A3E.7020709@rabbit.us>
Peter Rabbitson wrote:
> Hello,
>
> The subject pretty much says it all - it obviously is not 0xFD, since
> there is nothing to autodetect. Is there some best
> practice/semi-standard way of marking a raid component partition as
> such? After reading the specs 0xDA (non-fs data) comes to mind, but I
> figured I'll ask here.
I recently wondered if there should be a new partition type.
Partitioning tools look for (and sometimes find!) filesystems on 0x83 partitions
so 0x83 is out (anyone splitting a mirror should be happy changing the type back)
I'd rather that rescue disk didn't think 'oh, I'll use that swap partition', so
0x82 is out.
I don't want md trying to autodetect and complaining so, as you say, 0xfd is out.
I think it would be nice to mark them as 0xFC
David
next prev parent reply other threads:[~2008-06-11 11:24 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-11 9:26 Proper partition type for components with V1.x superblocks? Peter Rabbitson
2008-06-11 11:23 ` Andre Noll
2008-06-11 12:12 ` Peter Rabbitson
2008-06-11 21:06 ` Andre Noll
2008-06-11 11:24 ` David Greaves [this message]
2008-06-11 11:35 ` Peter Rabbitson
2008-06-11 23:52 ` Neil Brown
2008-07-02 22:02 ` H. Peter Anvin
2008-07-03 5:17 ` Doug Ledford
2008-07-07 3:17 ` Neil Brown
2008-07-07 14:02 ` Doug Ledford
2008-07-07 17:33 ` H. Peter Anvin
2008-07-07 17:32 ` H. Peter Anvin
2008-07-07 23:10 ` David Greaves
2008-07-07 23:47 ` H. Peter Anvin
2008-07-07 17:38 ` H. Peter Anvin
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=484FB5E5.8000207@dgreaves.com \
--to=david@dgreaves.com \
--cc=linux-raid@vger.kernel.org \
--cc=rabbit+list@rabbit.us \
/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.