From: andy liebman <andyliebman@aol.com>
To: linux-raid@vger.kernel.org
Subject: Re: Imaging Mirrored OS Drive
Date: Wed, 16 Aug 2006 15:02:42 -0400 [thread overview]
Message-ID: <44E36BD2.20707@aol.com> (raw)
>
> Sorry, I EOF'd too soon..
> As to creating mirrored partitions over top of existing data, mdadm will write a \
> superblock at the beginning of each mirrored component, which will blow up the first \
> several bytes of the partition (probably the FS descriptor). I believe there is an \
> option to create a raid1 pair without a superblock, but I don't think I would want to \
> use it.
>
Well, I created new mirrors on top of the existing partition pairs, and
specified the UUID for each device(so that they were the same as the old
mirrored partition pairs) and the system booted up fine. I'm going to
run e2fsck on the md devices (booting again in a Live CD) to see if
there's any corruption.
I'm actually kind of surprised the system booted up.
Can anybody suggest other tests to run to see if things really ARE okay?
Should one be able to do what I just did?
Andy
reply other threads:[~2006-08-16 19:02 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=44E36BD2.20707@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).