From: tariq wali <ganaiwali@gmail.com>
To: LVM general discussion and development <linux-lvm@redhat.com>
Subject: Re: [linux-lvm] Fun and games with mirroring
Date: Wed, 23 May 2012 00:09:23 +0530 [thread overview]
Message-ID: <CAGQjrKYeeG4Bwifh3yno46P3BDe9grbz8Um6mZqpcst5Eh7JaA@mail.gmail.com> (raw)
In-Reply-To: <4FBBD376.7070001@bmsi.com>
[-- Attachment #1: Type: text/plain, Size: 1934 bytes --]
if I may ask an elementary question please :) I normally take a snapshot on
lvm partition offcourse that contains MySQL data say /data and then mount
it as ro and then use the ancient tar/scp to copy it elsewhere . Could
anyone please correct me if there is a better way to do it ? like can i
take a snapshot of /data and transfer the entire volume to another system
( i mean duplicate/mirror it ) ?
Also
sometime /data contains data that I really don't need to be in the snapshot
but the way i take snapshot it pretty much creates a mirror .. I have
always wondered how snapshot thing works because when i take snapshot I
continue to use my original /data and continue to do IO on it while
snapshot is mounted :)
On Tue, May 22, 2012 at 11:27 PM, Stuart D Gathman <stuart@bmsi.com> wrote:
> Long ago, Nostradamus foresaw that on 05/22/2012 10:50 AM, Vic would write:
>
>> p.s. The reason I want to do this with LVM mirrors rather than MD RAID is
>> that this is potentially a very useful way of grabbing a backup snapshot
>> of a machine prior to some risky operation - it allows me to "fork" a
>> machine onto two sets of media. But if it leaves the result unbootable,
>> that's something of a problem...
>>
>> LVM RAID is mainly used for pvmove at the moment. LVM has a ways to go
> to match ZFS or AIX in LVM mirroring features. MD RAID takes a snapshot
> just fine. Add the mirror with mdadm, sync it, and "fail" the mirror and
> remove it before physically removing the drive. I can see the issue with
> multiple PVs, however. There is no atomic way to fail multiple mirrors at
> once.
>
>
>
> ______________________________**_________________
> linux-lvm mailing list
> linux-lvm@redhat.com
> https://www.redhat.com/**mailman/listinfo/linux-lvm<https://www.redhat.com/mailman/listinfo/linux-lvm>
> read the LVM HOW-TO at http://tldp.org/HOWTO/LVM-**HOWTO/<http://tldp.org/HOWTO/LVM-HOWTO/>
>
--
*Tariq Wali.*
[-- Attachment #2: Type: text/html, Size: 2842 bytes --]
next prev parent reply other threads:[~2012-05-22 18:39 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-22 14:50 [linux-lvm] Fun and games with mirroring Vic
2012-05-22 15:27 ` Les Mikesell
2012-05-22 15:29 ` Vic
2012-05-22 16:00 ` Bryn M. Reeves
2012-05-22 16:40 ` Vic
2012-05-22 19:24 ` Brassow Jonathan
2012-05-22 19:59 ` Vic
2012-05-23 8:52 ` Bryn M. Reeves
2012-05-23 10:02 ` Zdenek Kabelac
2012-05-23 15:16 ` Brassow Jonathan
2012-05-23 8:54 ` Bryn M. Reeves
2012-05-23 15:21 ` Les Mikesell
2012-05-23 15:36 ` Bryn M. Reeves
2012-05-23 17:03 ` Les Mikesell
2012-05-23 17:24 ` Bryn M. Reeves
2012-05-23 18:00 ` Les Mikesell
2012-05-23 18:32 ` Stuart D Gathman
2012-05-23 19:07 ` Les Mikesell
2012-05-23 22:39 ` Stuart D Gathman
2012-05-22 17:57 ` Stuart D Gathman
2012-05-22 18:39 ` tariq wali [this message]
2012-05-23 22:44 ` 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=CAGQjrKYeeG4Bwifh3yno46P3BDe9grbz8Um6mZqpcst5Eh7JaA@mail.gmail.com \
--to=ganaiwali@gmail.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;
as well as URLs for NNTP newsgroup(s).