From: Damon Wang <damon.devops@gmail.com>
To: David Teigland <teigland@redhat.com>
Cc: linux-lvm@redhat.com
Subject: Re: [linux-lvm] [lvmlockd] Refresh lvmlockd leases after sanlock changes
Date: Wed, 7 Mar 2018 15:11:18 +0800 [thread overview]
Message-ID: <CABZYMH74+CjXCZk6GdHsCc0wG7p1yiFQ0hA4bEyO087=4+gckQ@mail.gmail.com> (raw)
In-Reply-To: <CABZYMH5UEDWhO30KiZ1xVe1z+S0pA4DR_yJ8TQ1sCYK48+0d9g@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 223 bytes --]
Besides, during migrating, libvirt will make sure only one host is using
(read/write) the lv,
and I'm trying to find a way to deactivate lv after migrating, so that
there's always
only one host has I/O on a thin lv.
Damon
[-- Attachment #2: Type: text/html, Size: 412 bytes --]
next prev parent reply other threads:[~2018-03-07 7:11 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-05 8:37 [linux-lvm] [lvmlockd] Refresh lvmlockd leases after sanlock changes Damon Wang
2018-03-05 16:59 ` David Teigland
2018-03-07 5:50 ` Damon Wang
2018-03-07 7:11 ` Damon Wang [this message]
2018-03-07 8:14 ` Damon Wang
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='CABZYMH74+CjXCZk6GdHsCc0wG7p1yiFQ0hA4bEyO087=4+gckQ@mail.gmail.com' \
--to=damon.devops@gmail.com \
--cc=linux-lvm@redhat.com \
--cc=teigland@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).