From: "Tomas Dalebjörk" <tomas.dalebjork@gmail.com>
To: linux-lvm@redhat.com
Subject: [linux-lvm] what will happen with lvconvert merge after reboot?
Date: Mon, 10 Aug 2020 01:19:00 +0200 [thread overview]
Message-ID: <A71F734D-C071-4CC7-A381-6FC11171B94C@gmail.com> (raw)
hi
If a user starts a
# lvconvert --merge -b snaplv
and reboots the server before the convert/merge has completed
will the merge/converting process continue after reboot?
or will the volume be stale?
if the merge/convert is restarted, can it resume where it was?
regards Tomas
Sent from my iPhone
next reply other threads:[~2020-08-09 23:19 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-09 23:19 Tomas Dalebjörk [this message]
2020-08-10 9:36 ` [linux-lvm] how often does lvm team update source code in ftp site heming.zhao
2020-08-10 10:22 ` Marian Csontos
[not found] ` <20200810115232.GB1049@redhat.com>
2020-08-10 15:26 ` heming.zhao
2020-08-10 15:44 ` Frank Ch. Eigler
2020-08-10 15:24 ` [linux-lvm] what will happen with lvconvert merge after reboot? Zdenek Kabelac
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=A71F734D-C071-4CC7-A381-6FC11171B94C@gmail.com \
--to=tomas.dalebjork@gmail.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).