linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Tim Small <tim@buttersideup.com>
To: Jens Benecke <jens@spamfreemail.de>
Cc: linux-raid@vger.kernel.org
Subject: Re: Q: RAID-1 w/2x160GB, ReiserFS, Debian "woody", homebrew 2.4.25 kernel
Date: Wed, 04 Aug 2004 11:28:53 +0100	[thread overview]
Message-ID: <4110BA65.60801@buttersideup.com> (raw)
In-Reply-To: <ceq7ij$vj7$1@sea.gmane.org>

I'll just deal with the MD solution, since it's a while since I played 
with LVM...

Jens Benecke wrote:

>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?
>
>  
>
Yes you can do this - see last post, I prefer Grub, see the thread with 
the subject "GRUB + RAID howto" in the page linked below - I suggest 
trying both methods stated there, and testing which one works for you...

http://www.linuxsa.org.au/mailing-list/2003-07/thread.html

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

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

>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?
>
>  
>
You will need to partition it, and use mdadm to add the new partitions 
to the array.  But you can simply do something like this:

dd if=/dev/hda of=/dev/hdc ; echo w | fdisk /dev/hdc

>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?
>  
>
You need to arrange to read check the drive (you probably want to do 
this on single drive systems as well) I would advise using 
smartmontools, (e.g. from Sarge), with these lines like these in 
/etc/smartd.conf (also comment out the DEVICESCAN line):

/dev/hda -a -s L/../../6/01 -m root
/dev/hdc -a -s L/../../6/02 -m root

This way you stand a better chance of catching blocks which are going 
bad before they become unreadable - it will ask the drives to carry out 
an extended self test (e.g. surface scan etc.) at 1am/2am on Saturday.  
Note that this will work with SCSI disks, PATA disks, and SATA disks 
which use the old IDE driver, but not yet with SATA disks using libata 
(you could make do with a "dd if=/dev/sda of=/dev/null" in a cron job 
instead).

>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.
>
>  
>
On Debian, you should install the raidtools2 package, this will install 
a cron job which will email you on degraded array events (the smartd 
lines will email root on SMART errors as well) - but you should also 
install mdadm to use the new "mdadm" management tools.  I would advise 
using Sarge, instead of Woody, unless you have a good reason not too...

Tim.


      parent reply	other threads:[~2004-08-04 10:28 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-08-04  8:42 Q: RAID-1 w/2x160GB, ReiserFS, Debian "woody", homebrew 2.4.25 kernel Jens Benecke
2004-08-04  9:00 ` 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 ` Tim Small [this message]

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=4110BA65.60801@buttersideup.com \
    --to=tim@buttersideup.com \
    --cc=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).