linux-lvm.redhat.com archive mirror
 help / color / mirror / Atom feed
From: "Gang He" <ghe@suse.com>
To: linux-lvm@redhat.com
Subject: Re: [linux-lvm] [RELEASE] 2.02.178
Date: Fri, 25 May 2018 01:45:47 -0600	[thread overview]
Message-ID: <5B07BF2B020000F90001E5BB@prv1-mh.provo.novell.com> (raw)
In-Reply-To: <20180525070342.g247jatvm6dskehy@reti>

Hello Joe,

When will the formal LVM 2.02.178 be released?
In LVM2.02.178, online pvmove can work well under the cluster environment?

Thanks
Gang 

>>> Joe Thornber <thornber@redhat.com> 2018/5/25 15:03 >>>
ftp://sources.redhat.com/pub/lvm2/LVM2.2.02.178-rc1.tgz 


Version 2.02.178
================

There are going to be some large changes to the lvm2 codebase
over the next year or so.  Starting with this release.  These
changes should be internal rather than having a big effect on
the command line.  Inevitably these changes will increase the
chance of bugs, so please be on the alert.


Remove support for obsolete metadata formats
--------------------------------------------

Support for the GFS pool format, and format used by the
original 1990's version of LVM1 have been removed.

Use asynchronous IO
-------------------

Almost all IO uses libaio now.

Rewrite label scanning
----------------------

Dave Teigland has reworked the label scanning and metadata reading
logic to minimise the amount of IOs issued.  Combined with the aio changes 
this can greatly improve scanning speed for some systems.

./configure options
-------------------

We're going to try and remove as many options from ./configure as we
can.  Each option multiplies the number of possible configurations
that we should test (this testing is currently not occurring).

The first batch to be removed are:

  --enable-testing
  --with-snapshots
  --with-mirrors
  --with-raid
  --with-thin
  --with-cache

Stable targets that are in the upstream kernel will just be supported.

In future optional target flags will be given in two situations:

1) The target is experimental, or not upstream at all (eg, vdo).
2) The target is deprecated and support will be removed at some future date.

This decision could well be contentious, so could distro maintainers feel
free to comment.

_______________________________________________
linux-lvm mailing list
linux-lvm@redhat.com 
https://www.redhat.com/mailman/listinfo/linux-lvm 
read the LVM HOW-TO at http://tldp.org/HOWTO/LVM-HOWTO/ 

  reply	other threads:[~2018-05-25  7:46 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 [this message]
2018-05-30 10:42   ` Marian Csontos
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=5B07BF2B020000F90001E5BB@prv1-mh.provo.novell.com \
    --to=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).