linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: tmp <skrald@amossen.dk>
To: linux-raid@vger.kernel.org
Subject: Questions about software RAID
Date: Mon, 18 Apr 2005 21:50:24 +0200	[thread overview]
Message-ID: <1113853825.1483.34.camel@debian> (raw)

I read the software RAID-HOWTO, but the below 6 questions is still
unclear. I have asked around on IRC-channels and it seems that I am not
the only one being confused. Maybe the HOWTO could be updated to
clearify the below items?


1) I have a RAID-1 setup with one spare disk. A disk crashes and the
spare disk takes over. Now, when the crashed disk is replaced with a new
one, what is then happening with the role of the spare disk? Is it
reverting to its old role as spare disk?

If it is NOT reverting to it's old role, then the raidtab file will
suddenly be out-of-sync with reality. Is that correct?

Does the answer given here differ in e.g. RAID-5 setups?


2) The new disk has to be manually partitioned before beeing used in the
array. What happens if the new partitions are larger than other
partitions used in the array? What happens if they are smaller?


3) Must all partition types be 0xFD? What happens if they are not?


4) I guess the partitions itself doesn't have to be formated as the
filesystem is on the RAID-level. Is that correct?


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?
Aren't there some more hotswap-friendly setup?


6) I know that the kernel does stripping automatically if more
partitions are given as swap partitions in /etc/fstab. But can it also
handle if one disk crashes? I.e. do I have to let my swap disk be a
RAID-setup too if I wan't it to continue upon disk crash?


Thanks!


             reply	other threads:[~2005-04-18 19:50 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-04-18 19:50 tmp [this message]
2005-04-18 20:12 ` Questions about software RAID 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
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=1113853825.1483.34.camel@debian \
    --to=skrald@amossen.dk \
    --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).