archive mirror
 help / color / mirror / Atom feed
From: Mauricio Tavares <>
To: LVM general discussion and development <>
Subject: [linux-lvm] Failed merge, still running?
Date: Wed, 22 Jan 2020 05:58:21 -0500	[thread overview]
Message-ID: <> (raw)

So after a botched package update I decided to revert to the snapshot
I took just before doing the update. After shutting guest down, I

lvconvert --merge vmhost_vg0/desktop_snap_20200121

and instead of seeing the usual percentage of how far it has
completed, I got nothing. lvs -a -o +devices shows

  LV                      VG         Attr       LSize  Pool Origin
Data%  Meta%  Move Log Cpy%Sync Convert Devices
  desktop                 vmhost_vg0 Owi-a-s--- 20.00g
  [desktop_snap_20200121] vmhost_vg0 Swi-a-s--- 10.00g      desktop 100.00

I see nothing when I do lsof against both the lv (lsof
/dev/vmhost_vg0/desktop) and its snapshot. dmsetup tells me:

[root@vmhost ~]# dmsetup info /dev/vmhost_vg0/desktop
Name:              vmhost_vg0-desktop
State:             ACTIVE
Read Ahead:        256
Tables present:    LIVE
Open count:        0
Event number:      0
Major, minor:      253, 5
Number of targets: 1
UUID: LVM-qa4WnlE7w8V7pasHwdNH6bnpz2ajYY1F2ZXwTWzpUE2r6eE2DftMGLHdeATE8XAq

[root@vmhost ~]# dmsetup info /dev/vmhost_vg0/desktop_snap_20200121
Name:              vmhost_vg0-desktop_snap_20200121
State:             ACTIVE
Read Ahead:        256
Tables present:    LIVE
Open count:        0
Event number:      0
Major, minor:      253, 15
Number of targets: 1
UUID: LVM-qa4WnlE7w8V7pasHwdNH6bnpz2ajYY1FkyXcvv8ai1Sc0q5zlsXeenYOqCPUXs3M

[root@vmhost ~]#

Before I blow that lv up, what else should I be checking?

             reply	other threads:[~2020-01-22 10:58 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-01-22 10:58 Mauricio Tavares [this message]
2020-01-22 13:06 ` [linux-lvm] Failed merge, still running? Stuart D. Gathman
2020-01-22 13:56   ` Mauricio Tavares
2020-01-22 13:12 ` Zdenek Kabelac
2020-01-22 13:44   ` Mauricio Tavares

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \

* 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).