From: andy liebman <andyliebman@aol.com>
To: linux-raid@vger.kernel.org
Subject: Re: Imaging Mirrored OS Drives
Date: Wed, 16 Aug 2006 13:05:39 -0400 [thread overview]
Message-ID: <44E35063.3040706@aol.com> (raw)
For those who have been following my attempt to create IMAGES of a pair
of drives with mirrored OS partitions, and then restore the IMAGES to a
new set of drives...
This doesn't work directly. The imaging programs are FAST because they
do not perform block level copying. They replicated partition structure
and copy FILES from disk to image and then image to disk.
As I have just discovered, when I restore the images to NEW clean
drives, the partitions on the NEW drives do not have any RAID
information. No UUID for mdadm to use. No RAIDS to assemble. But the
file information is there.
So, my questions are...
1) Is it now possible to CREATE mirrored partitions with mdadm AND still
KEEP the existing data on the NEW set of drives. In other words, create
the mirrors AFTER the fact (given that the data on the drives is
identical).
2) Furthermore, if the above is possible, in creating the arrays on the
new drives is there a way to force mdadm to give the arrays specific
UUID numbers? It looks like I can do that with mdadm --update? Should I
create the arrays first using the normal "mdadm -C" procedure, and then
update the UUIDs?
I want to update the UUIDs so that they are the same as the UUIDs on the
partitions on the original set of drives.
Andy Liebman
next reply other threads:[~2006-08-16 17:05 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-16 17:05 andy liebman [this message]
2006-08-16 20:47 ` Imaging Mirrored OS Drives Luca Berra
-- strict thread matches above, loose matches on Subject: below --
2006-08-16 17:28 raid
2006-08-16 17:32 raid
2006-08-16 22:20 andy liebman
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=44E35063.3040706@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).