From: "Stuart D. Gathman" <firstname.lastname@example.org>
To: LVM general discussion and development <email@example.com>
Subject: Re: [linux-lvm] Failed merge, still running?
Date: Wed, 22 Jan 2020 08:06:28 -0500 (EST) [thread overview]
Message-ID: <alpine.LRH.firstname.lastname@example.org> (raw)
On Wed, 22 Jan 2020, Mauricio Tavares wrote:
> 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
While not a guru, I think I can tell you the issue. It looks like
the snapshot was full (says 100.00). The snapshot is unusable at
that point. Maybe it wasn't before you started the merge, and the
merge sets it to 100.00 when it starts, I haven't noticed.
> Before I blow that lv up, what else should I be checking?
What was the snapshot percent used before you started the merge?
Stuart D. Gathman <email@example.com>
"Confutatis maledictis, flammis acribus addictis" - background song for
a Microsoft sponsored "Where do you want to go from here?" commercial.
next prev parent reply other threads:[~2020-01-22 13:50 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-22 10:58 [linux-lvm] Failed merge, still running? Mauricio Tavares
2020-01-22 13:06 ` Stuart D. Gathman [this message]
2020-01-22 13:56 ` Mauricio Tavares
2020-01-22 13:12 ` Zdenek Kabelac
2020-01-22 13:44 ` Mauricio Tavares
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).