From: Michael Tokarev <mjt@tls.msk.ru>
To: David Greaves <david@dgreaves.com>
Cc: linux-raid@vger.kernel.org
Subject: Re: Questions about software RAID
Date: Tue, 19 Apr 2005 16:18:34 +0400 [thread overview]
Message-ID: <4264F71A.9070103@tls.msk.ru> (raw)
In-Reply-To: <4264BC88.4050209@dgreaves.com>
David Greaves wrote:
> Luca Berra wrote:
>
>> many people find it easier to understand if raid partitions are set to
>> 0XFD. kernel autodetection is broken and should not be relied upon.
>
> Could you clarify what is broken?
> I understood that it was simplistic (ie if you have a raid0 built over a
> raid5
> or something exotic then it may have problems) but essentially worked.
> Could it be :
> * broken for complex raid on raid
> * broken for root devices
> * fine for 'simple', non-root devices
It works when everything works. If something does not work (your disk
died, you moved disks, or esp. you added another disk from another
machine wich was also a part of (another) raid array), every bad
thing can happen, from just inability to assemble the array at all,
to using the wrong disks/partitions, and to assembling the wrong
array (the one from another machine). If it's your root device
you're trying to assemble, recovery involves booting from a rescue
CD and cleaning stuff up, which can be problematic at times.
/mjt
next prev parent reply other threads:[~2005-04-19 12:18 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-18 19:50 Questions about software RAID tmp
2005-04-18 20:12 ` David Greaves
2005-04-18 23:12 ` tmp
2005-04-19 6:36 ` Peter T. Breuer
2005-04-19 7:15 ` Luca Berra
2005-04-19 8:08 ` David Greaves
2005-04-19 12:18 ` Michael Tokarev [this message]
2005-04-19 12:08 ` Don't use whole disks for raid arrays [was: Questions about software RAID] Michael Tokarev
2005-04-18 20:15 ` Questions about software RAID Peter T. Breuer
2005-04-18 20:50 ` Frank Wittig
-- strict thread matches above, loose matches on Subject: below --
2005-04-19 11:00 bernd
2005-04-19 14:40 ` Hervé Eychenne
2005-04-19 15:27 ` David Greaves
2005-04-19 15:54 ` Hervé Eychenne
2005-04-19 16:53 ` Frank Wittig
2005-04-19 17:54 ` Hervé Eychenne
2005-04-19 19:46 ` Frank Wittig
2005-04-20 4:15 ` Guy
2005-04-20 7:59 ` David Greaves
2005-04-20 9:26 ` Molle Bestefich
2005-04-20 9:32 ` Hervé Eychenne
2005-04-20 17:36 ` Molle Bestefich
2005-04-20 11:16 ` Peter T. Breuer
2005-04-20 12:34 ` Lars Marowsky-Bree
2005-04-20 15:49 ` Martin K. Petersen
2005-04-21 1:21 ` Guy
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=4264F71A.9070103@tls.msk.ru \
--to=mjt@tls.msk.ru \
--cc=david@dgreaves.com \
--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).