linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jens Benecke <jens@spamfreemail.de>
To: linux-raid@vger.kernel.org
Subject: Q: RAID-1 w/2x160GB, ReiserFS, Debian "woody", homebrew 2.4.25 kernel
Date: Wed, 04 Aug 2004 10:42:59 +0200	[thread overview]
Message-ID: <ceq7ij$vj7$1@sea.gmane.org> (raw)

Hi everybody,

I'm planning to set up a new RAID mirrored system with the above specs. Both
disks are master (hda and hdc). I'm currently trying to decide between LVM2
(is it in 2.4 already?), MD, and a "manual" nightly rsync onto the second
disk.

I'd like a few pointers (RTFwhatever welcome) to the following questions:


How about RAIDing the root partition? If one drive fails will the other be
able to boot via LILO? How about GRUB? Which do you prefer?

How about (/var)/tmp? I (suppose I'll) need it on both disks, does it make
sense to mirror it as well?

Can I mirror the whole disk? Or do I need to mirror each partition
seperately?

Does MD or LVM2 do hot sync, i.e. if one drive fails will I be able to stick
in a replacement, and stop worrying? Or do I need to repartition the new
disk exactly as the old one, before being able to sync?

How does LVM2/MD deal with failing harddisks, which is why I do the mirror
at all? I've heard about MD not detecting read errors because the "other"
disk was reading fine, and crashing completely when one disk was finally
replaced because the data on the other disk was also corrupt. Is that still
the current case?


The goal is to have as "stress free" a system as possible - i.e. with as
little manual configuration, and in event of emergencies, as little work to
do, as possible.


Thank you for your help!


-- 
Jens Benecke
http://www.hitchhikers.de - Europas kostenlose Mitfahrzentrale seit 1998
http://www.rb-hosting.de - Webhosting mit Extras - PHP ab €9 - SSH ab €19
http://www.spamfreemail.de - 100% saubere Postfächer, garantiert!

-
To unsubscribe from this list: send the line "unsubscribe linux-raid" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

             reply	other threads:[~2004-08-04  8:42 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-08-04  8:42 Jens Benecke [this message]
2004-08-04  9:00 ` Q: RAID-1 w/2x160GB, ReiserFS, Debian "woody", homebrew 2.4.25 kernel Mikael Abrahamsson
2004-08-04 11:10   ` Jens Benecke
2004-08-04 12:25     ` Mikael Abrahamsson
2004-08-04 12:32       ` Tim Small
2004-08-04 10:00 ` Q: RAID-1 w/2x160GB, ReiserFS, Debian 'woody', " Robin Bowes
2004-08-04 10:29   ` Mark Watts
2004-08-04 10:34     ` Tim Small
2004-08-04 10:37     ` Robin Bowes
2004-08-04 11:12     ` Alvin Oga
2004-08-04 23:51       ` Mark Hahn
2004-08-05  6:16   ` Jens Benecke
2004-08-05  7:26     ` Daniel Pittman
2004-08-05  9:20       ` Tim Small
2004-08-05 12:02         ` Jens Benecke
2004-08-05  9:57     ` robin-lists
2004-08-05 12:08       ` Jens Benecke
2004-08-05 12:38         ` Mark Watts
2004-08-05 12:49           ` Katarina WONG
2004-08-05 15:42         ` robin-lists
2004-08-04 10:28 ` Q: RAID-1 w/2x160GB, ReiserFS, Debian "woody", " Tim Small

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='ceq7ij$vj7$1@sea.gmane.org' \
    --to=jens@spamfreemail.de \
    --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).