From: David Greaves <david@dgreaves.com>
To: linux-raid@vger.kernel.org
Subject: Re: Questions about software RAID
Date: Tue, 19 Apr 2005 09:08:40 +0100 [thread overview]
Message-ID: <4264BC88.4050209@dgreaves.com> (raw)
In-Reply-To: <20050419071514.GB29247@percy.comedia.it>
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
>
>
>>> >4) I guess the partitions itself doesn't have to be formated as the
>>> >filesystem is on the RAID-level. Is that correct?
>>> compulsory!
>>
>>
>> I meant, the /dev/mdX has to be formatted, not the individual
>> partitions. Still right?
>
> compulsory! if you do anything on the individual components you'll
> damage data.
>
>>> >5) Removing a disk requires that I do a "mdadm -r" on all the
>>> partitions
>>> >that is involved in a RAID array. I attempt to by a hot-swap capable
>>> >controler, so what happens if I just pull out the disk without this
>>> >manual removal command?
>>> as far as md is concerned the disk disappeared.
>>> I _think_ this is just like mdadm -r.
>>
> i think it will be marked faulty, not removed.
yep - you're right, I remember now.
You have to mdadm -r remove it and re-add it once you restore the disk.
>
>> So I could actually just pull out the disk, insert a new one and do a
>> "mdadm -a /dev/mdX /dev/sdY"?
>> The RAID system won't detect the newly inserted disk itself?
>
> no, think of it as flexibility. if you want you can build something
> using the "hotplug" subsystem.
or:
no, it would be mighty strange if the raid subsystem just grabbed every
new disk it saw...
Think of what would happen when I insert my camera's compact flash card
and it suddenly gets used as a hot spare <grin>
I'll leave Luca's last word - although it's also worth re-reading Peter's
first words!!
David
> one last word:
> never trust howtos (they should be called howidid), they have the
> tendency to apply to the author configuration, not yours.
> general documentation is far more accurate.
next prev parent reply other threads:[~2005-04-19 8:08 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 [this message]
2005-04-19 12:18 ` Michael Tokarev
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=4264BC88.4050209@dgreaves.com \
--to=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).