linux-lvm.redhat.com archive mirror
 help / color / mirror / Atom feed
From: Marian Csontos <mcsontos@redhat.com>
To: LVM general discussion and development <linux-lvm@redhat.com>,
	Gang He <ghe@suse.com>
Subject: Re: [linux-lvm] [RELEASE] 2.02.178
Date: Wed, 30 May 2018 12:42:47 +0200	[thread overview]
Message-ID: <80318f1a-2b2e-9d0f-ae16-3b1eb0af2740@redhat.com> (raw)
In-Reply-To: <5B07BF2B020000F90001E5BB@prv1-mh.provo.novell.com>

On 05/25/2018 09:45 AM, Gang He wrote:
> Hello Joe,
> 
> When will the formal LVM 2.02.178 be released?

Within two weeks. I have pushed the RC1 to rawhide, and unless problems 
are reported, we will be releasing shortly.

> In LVM2.02.178, online pvmove can work well under the cluster environment?

Yes, the clustered pvmove issues are fixed in 2.02.178.

You need either:
- exclusive activation,
- wait for 2.02.178,
- or patch .177

-- Marian

  reply	other threads:[~2018-05-30 10:42 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-05-25  7:03 [linux-lvm] [RELEASE] 2.02.178 Joe Thornber
2018-05-25  7:45 ` Gang He
2018-05-30 10:42   ` Marian Csontos [this message]
2018-05-31  1:38     ` Gang He

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=80318f1a-2b2e-9d0f-ae16-3b1eb0af2740@redhat.com \
    --to=mcsontos@redhat.com \
    --cc=ghe@suse.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).