From: "Linda A. Walsh" <lvm@tlinx.org>
To: LVM general discussion and development <linux-lvm@redhat.com>
Subject: Re: [linux-lvm] more vg problems or oddities...not using dmsetup remove seems to be bad?
Date: Sun, 11 Sep 2011 21:08:03 -0700 [thread overview]
Message-ID: <4E6D85A3.50404@tlinx.org> (raw)
In-Reply-To: <alpine.LRH.2.00.1109112310400.5744@bmsred.bmsi.com>
Here's a sadistic (or masochistic, maybe both, if I do it to myself)...
question...
If I start a snapshot today... (or if one is already running)...
And the merge happens, will the snapshot take today have the
data to undo the merge?
Stuart D. Gathman wrote:
> On Sun, 11 Sep 2011, Stuart D. Gathman wrote:
>
>> On Sun, 11 Sep 2011, Linda A. Walsh wrote:
>>
>>> tried -- merging it...
>>
>> Ooops. You likely did not want that. That reverts the origin volume
>> to the snapshot by copying the original data for updated sectors from
>> the snapshot. This is an extremely useful feature, but *not* when
>> you invoke it accidentally!
>
>>> I'm wondering if I really want this 'merge' it wants to do...and if
>>> not, how do I abort it?
>>
>> If it is really delayed until boot (or close), then you have a chance
>> to abort
>> it, but I don't know how. I hope an expert answers. Meanwhile, I'll
>> peruse the man page to see if it talks about delayed merge.
>
> The man page says:
>
> If both the origin and snapshot volume are not open the merge will
> start
> immediately. Otherwise, the merge will start the first time
> either the
> origin or snap??? shot are activated and both are closed. Merging a
> snapshot
> into an origin that cannot be closed, for example a root
> filesystem, is
> deferred until the next time the origin volume is activated. When
> merging
> starts, the resulting logical volume will have the origin's name, minor
> number and UUID. While the merge is in progress, reads or
> writes to
> the origin appear as they were directed to the snapshot being
> merged. When
> the merge finishes, the merged snapshot is removed. Multiple
> snapshots may
> be specified on the commandline or a @tag may be used to specify
> multi??? ple
> snapshots be merged to their respective origin.
>
> If you have space, I would copy your origin LV while you can. There is
> nothing about cancelling the merge. I suspect you could restore the
> metadata
> backup from before your merge. But make backups first!
>
> --
> Stuart D. Gathman <stuart@bmsi.com>
> Business Management Systems Inc. Phone: 703 591-0911 Fax: 703
> 591-6154
> "Confutatis maledictis, flammis acribus addictis" - background song for
> a Microsoft sponsored "Where do you want to go from here?" commercial.
>
> _______________________________________________
> linux-lvm mailing list
> linux-lvm@redhat.com
> https://www.redhat.com/mailman/listinfo/linux-lvm
> read the LVM HOW-TO at http://tldp.org/HOWTO/LVM-HOWTO/
next prev parent reply other threads:[~2011-09-12 4:08 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-12 0:44 [linux-lvm] more vg problems or oddities...not using dmsetup remove seems to be bad? Linda A. Walsh
2011-09-12 3:04 ` Stuart D. Gathman
2011-09-12 3:14 ` Stuart D. Gathman
2011-09-12 4:05 ` Linda A. Walsh
2011-09-12 4:08 ` Linda A. Walsh [this message]
2011-09-12 7:33 ` Ray Morris
2011-09-12 13:57 ` Stuart D. Gathman
2011-09-12 17:27 ` [linux-lvm] How to stop MERGE? (was Re: more vg problems or oddities...not using dmsetup remove seems to be bad?) Linda A. Walsh
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=4E6D85A3.50404@tlinx.org \
--to=lvm@tlinx.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.