From: "Bryn M. Reeves" <bmr@redhat.com>
To: LVM general discussion and development <linux-lvm@redhat.com>
Subject: Re: [linux-lvm] Using LVM Mirroring to obtain a usable backup
Date: Thu, 17 Sep 2009 11:05:56 +0100 [thread overview]
Message-ID: <1253181956.30299.25.camel@breeves.fab.redhat.com> (raw)
In-Reply-To: <1253127828.3243.1.camel@delo.gdit>
On Wed, 2009-09-16 at 21:03 +0200, Ambrogio De Lorenzo wrote:
> Il giorno mer, 16/09/2009 alle 11.19 -0700, malahal@us.ibm.com ha
> scritto:
> > Ambrogio De Lorenzo [ambrogio.de.lorenzo@alice.it] wrote:
> > > Hi all.
> > > I'm doing a big upgrade on my computer and I tryed to use lv mirroring
> > > to obtain a copy of my data before to do it.
> > >
> > > As I do with LVM on other OS i thought that after mirroring one could
> > > chose to split the mirrored lv.
> > >
> > > I can't find how to do it with LVM2 on Linux.
> >
> > snapshot may be a good fit in this case, but if you insist you can use
> > lvconvert to convert your linear volume to a mirrored volume. Once the
> > sync is complete, you can use the same lvconvert to convert the mirror
> > volume to a linear one.
> But with this I loose the secondary copy.
> It's not a good idea.
> Backup and destroy backup :-)
Well, the data is still there following the split but you are correct
that there is not currently a direct way to "split" the mirrored LV into
a pair of independent LVs.
Using a snapshot will not actually duplicate the data for you which
seems to be what you want to do.
If you don't want to muck about making manual changes you might be
better off creating a new LV and mirroring the data with dd or some
other block-level tool.
Regards,
Bryn.
next prev parent reply other threads:[~2009-09-17 9:57 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-16 13:59 [linux-lvm] Using LVM Mirroring to obtain a usable backup Ambrogio De Lorenzo
2009-09-16 15:05 ` André Gillibert
2009-09-16 16:47 ` Ambrogio De Lorenzo
2009-09-16 16:58 ` Brian J. Murrell
2009-09-16 19:15 ` Ambrogio De Lorenzo
2009-09-16 19:49 ` Brian J. Murrell
2009-09-16 20:03 ` André Gillibert
2009-09-16 20:22 ` Ambrogio De Lorenzo
2009-09-16 22:03 ` Kai Stian Olstad
2009-09-16 18:19 ` malahal
2009-09-16 19:03 ` Ambrogio De Lorenzo
2009-09-16 20:33 ` malahal
2009-09-17 10:05 ` Bryn M. Reeves [this message]
2009-09-17 15:06 ` Stuart D. Gathman
2009-09-17 15:34 ` Brian J. Murrell
2009-09-17 22:49 ` Stuart D. Gathman
2009-09-17 23:26 ` Les Mikesell
2009-09-18 0:58 ` Stuart D. Gathman
2009-09-18 1:51 ` Sven Eschenberg
2009-09-18 16:05 ` Mark H. Wood
2009-09-18 19:12 ` Stuart D. Gathman
2009-09-17 23:48 ` Brian J. Murrell
2009-09-18 1:55 ` Stuart D. Gathman
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=1253181956.30299.25.camel@breeves.fab.redhat.com \
--to=bmr@redhat.com \
--cc=linux-lvm@redhat.com \
/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