From: ben <benscott@nwlink.com>
To: linux-lvm@redhat.com
Subject: [linux-lvm] lvconvert --merge bug
Date: Sat, 16 Jul 2011 22:29:33 -0700 [thread overview]
Message-ID: <201107162229.33740.benscott@nwlink.com> (raw)
I was playing with snapshot merging a discovered a problem. If a snap starts
out as invalid the merge command starts merging and then quits. That leaves
the snap in a strange condition. It is listed as merging even though the merge
failed. It also becomes tricky to delete the invalid snap. It would seem
better if the merge command checked the validity first.
I also have a question. The error message from lvconvert suggests that the
snap might become invalid <during> the merge. If that happens does the origin
get scrambled?
Thank you.
next reply other threads:[~2011-07-17 5:29 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-17 5:29 ben [this message]
2011-07-17 12:23 ` [linux-lvm] lvconvert --merge bug Mike Snitzer
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=201107162229.33740.benscott@nwlink.com \
--to=benscott@nwlink.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 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.