From: Peter Rabbitson <rabbit+list@rabbit.us>
To: Andre Noll <maan@systemlinux.org>
Cc: linux-raid@vger.kernel.org
Subject: Re: Proper partition type for components with V1.x superblocks?
Date: Wed, 11 Jun 2008 14:12:50 +0200 [thread overview]
Message-ID: <484FC142.9030600@rabbit.us> (raw)
In-Reply-To: <20080611112319.GB4981@skl-net.de>
Andre Noll wrote:
> On 11:26, Peter Rabbitson wrote:
>
>> 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?
>
> Nobody really cares about the partition type these days. I usually
> stick to the default 83 (Linux) for software raid partitions and
> never encountered any problems.
This is a very flawed assumption. You will be surprised how many
utilities/live CDs are there in existence, which will selently attempt to
mount/fsck a partition based solely on its type. The implications of a
commenced mount/fsck on a raid component are not to be uttered here :)
next prev parent reply other threads:[~2008-06-11 12:12 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 [this message]
2008-06-11 21:06 ` Andre Noll
2008-06-11 11:24 ` David Greaves
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=484FC142.9030600@rabbit.us \
--to=rabbit+list@rabbit.us \
--cc=linux-raid@vger.kernel.org \
--cc=maan@systemlinux.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).