From: Zdenek Kabelac <zkabelac@redhat.com>
To: LVM general discussion and development <linux-lvm@redhat.com>
Subject: Re: [linux-lvm] Cancelling snapshot merge
Date: Tue, 11 Feb 2014 11:06:27 +0100 [thread overview]
Message-ID: <52F9F623.1090205@redhat.com> (raw)
In-Reply-To: <CA+VDVVVtkYVDNJP4f=oUiDTzhht60t-nDM3u5g5wezzv=tvzYg@mail.gmail.com>
Dne 10.2.2014 14:14, Alexander Meshcheryakov napsal(a):
> Hello,
>
> I had created snapshot of my /var logical volume a while ago and recently It
> occured to me that I don't need saved state anymore and I would like to
> reclaim disk space. But I have issued wrong lvconvert --merge command by
> mistake instead of proper lvremove.
>
> $ sudo lvconvert --merge VolGroup00/var_snap0
> Can't merge over open origin volume
> Merging of snapshot var_snap0 will start next activation.
>
> I have figured out at this point that I made mistake. Luckily merge is
> postponed as volume is used (mounted) now. But how do I prevent merge from
> running upon next reboot? Here is what I have tried:
>
> $ sudo lvremove VolGroup00/var_snap0
> Can't remove merging snapshot logical volume "var_snap0"
>
> $ sudo lvchange -an VolGroup00/var_snap0
> Change of snapshot var_snap0 will also change its origin LogVol01. Proceed?
> [y/n]: n
> Logical volume var_snap0 not changed.
>
>
> I even could not create snapshot of current state to roll back to it after merge
>
>
> $ sudo lvcreate --size 2G --snapshot -n var_snap1 /dev/mapper/VolGroup00-LogVol01
>
> Snapshots of an origin that has a merging snapshot is not supported
>
>
> Is there a way to cancel postponed snapshot merge?
vgcfgrestore - you could go via archive to the previous state of metadata.
There is no support for merge aborting - since it might have other 'side'
effects on metadata.
If you know what you are doing - vgcfgrestore is your rescue tool.
Zdenek
prev parent reply other threads:[~2014-02-11 10:06 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-10 13:14 [linux-lvm] Cancelling snapshot merge Alexander Meshcheryakov
2014-02-11 10:06 ` Zdenek Kabelac [this message]
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=52F9F623.1090205@redhat.com \
--to=zkabelac@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;
as well as URLs for NNTP newsgroup(s).