linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: andy liebman <andyliebman@aol.com>
To: linux-raid@vger.kernel.org
Subject: Can you IMAGE Mirrored OS Drives?
Date: Tue, 15 Aug 2006 18:55:09 -0400	[thread overview]
Message-ID: <44E250CD.5040308@aol.com> (raw)

Okay, I figured out how to take my existing OS installation from a 
single SATA drive and put it on a set of mirrored partitions on two 
different SATA drives. I looked at ALL of the "recipies" I could find on 
the Web -- none of them were quite right for MY situtation.

I will post my recipe here tomorrow for others to see -- maybe it will 
help somebody else. I just want to edit a few things to clarify before I 
post it. Some of the gotchas were were amusing -- like I couldn't run 
LILO on degraded raid1 arrays, and running "mkinitrd" from within 
Mandriva 2006 produces gzipped initrd files, but running "mkinitrd" by 
chrooting in from a LIVE CD produces initrd files that needs cpio to 
decompress and read it.

So, now that I have a running mirrored OS, I have a few more questions.

-- If I were to create disk images of EACH drive (i.e., /dev/sda and 
/dev/sdb), could I restore each of those images to NEW drives -- with 
all of their respective partitions -- and have a working RAIDED OS?  I 
ask because my ultimate goal is to put a RAIDED OS on many systems, and 
once I get ONE working, it would be nice to clone them the way I already 
clone SINGLE OS drives. Can you clone RAIDS? It would mean, of course, 
that the UUIDs would be the same on each system. Is that bad? Is there 
any risk here?

-- I know there was a lot of discussion on the list a while back about 
whether or not to mirror SWAP space. Was there ever any conclusion? It 
seems to me that mirroring will ensure that if one drive fails, you 
don't lose information in virtual memory. My applications rarely if 
every use virtual memory anyway so I'm not worried about speed. I want 
the ultimate in stabilty for the OS drive. Otherwise, I guess I would 
designate swap space on just one drive (but prepare identical partitions 
on each for swap). If the first drive failed (/dev/sda -- with the swap 
space), /dev/sdb would become the new /dev/sda anyway. And so fstab 
would be correct in pointing to /dev/sda.

Sound opinions welcome.

Thanks,
Andy Liebman

             reply	other threads:[~2006-08-15 22:55 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-08-15 22:55 andy liebman [this message]
2006-08-16  2:24 ` Can you IMAGE Mirrored OS Drives? Guy
2006-08-16  7:03 ` Gordon Henderson
2006-08-16 10:06   ` andy liebman
2006-08-16 11:02     ` Gordon Henderson
2006-08-19  1:18     ` Gabor Gombas
2006-09-04 18:18     ` Bill Davidsen
2006-08-16  7:38 ` Luca Berra
2006-08-19  1:13   ` Gabor Gombas
2006-08-19  7:05     ` Luca Berra
2006-08-22 17:30       ` Gabor Gombas

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=44E250CD.5040308@aol.com \
    --to=andyliebman@aol.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).