From: Heinz Mauelshagen <heinzm@redhat.com>
To: LVM general discussion and development <linux-lvm@redhat.com>
Subject: [linux-lvm] Fwd: Re: Correct way to remove LVM Snapshot
Date: Wed, 26 Sep 2018 18:00:28 +0200 [thread overview]
Message-ID: <1bc84954-15e9-7e98-20c5-865d0381d639@redhat.com> (raw)
In-Reply-To: <f76497b5-d38f-b6c7-afe7-1615241c08c3@redhat.com>
[-- Attachment #1: Type: text/plain, Size: 1304 bytes --]
On 9/26/18 6:50 AM, Jaco van Niekerk wrote:
>
> Hi
>
> I will like to confirm the correct way to remove an LVM snapshot?
>
> Create my Logical Volume and snapshot:
> lvcreate --addtag pacemaker --name lv_iscsi_lun1 --size 100G vg_iscsi
> --config 'activation { volume_list = [ "@pacemaker" ]}'
> lvcreate --addtag pacemaker --name lv_iscsi_lun1_snap --snapshot
> --size 10G /dev/vg_iscsi/lv_iscsi_lun1 --config 'activation {
> volume_list = [ \"@pacemaker\" ]}'
>
> Do I have to Merge the Snapshot first before I can remove it?
> lvremove /dev/vg_iscsi/lv_iscsi_lun1_snap
Depends on your use case:
- if you need the data as of your snapshot and wnat to keep it in the
origin, you have to merge
- if you used the snapshot temorarily (e.g. for backup, fsck, ...), just
lvremove it.
>
> More Info:
> lv_iscsi_lun1 is a ISCSI target for a KVM virtual server.
>
> Trouble experienced:
> I lost my hole Volume Group after removing the Logical Volume Snapshot.
Can you provide any logs and "lvremove -vvvv ..." output (lvmdump
preferred)?
Heinz
> Regards
>
> --
>
> Jaco van Niekerk
>
>
>
> _______________________________________________
> linux-lvm mailing list
> linux-lvm@redhat.com
> https://www.redhat.com/mailman/listinfo/linux-lvm
> read the LVM HOW-TO athttp://tldp.org/HOWTO/LVM-HOWTO/
[-- Attachment #2: Type: text/html, Size: 3014 bytes --]
parent reply other threads:[~2018-09-26 16:00 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <f76497b5-d38f-b6c7-afe7-1615241c08c3@redhat.com>]
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=1bc84954-15e9-7e98-20c5-865d0381d639@redhat.com \
--to=heinzm@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).