From: Alasdair G Kergon <agk@redhat.com>
To: linux-lvm@redhat.com
Subject: [linux-lvm] LVM2 development release 2.02.31
Date: Mon, 21 Jan 2008 13:31:07 +0000 [thread overview]
Message-ID: <20080121133107.GZ24157@agk.fab.redhat.com> (raw)
We've just made a new development release of LVM2 with a few new features we'd
like people to test.
ftp://sources.redhat.com/pub/lvm2/LVM2.2.02.31.tgz
(Current stable release is 2.02.28)
ftp://sources.redhat.com/pub/dm/device-mapper.1.02.24.tgz
(considered stable in its default configuration)
1. Setting readahead is now supported.
Use --readahead with lvchange or lvcreate.
-r, --readahead ReadAheadSectors|auto|none
Set read ahead sector count of this logical volume. For volume
groups with metadata in lvm1 format, this must be a value
between 2 and 120 sectors. The default value is "auto" which
allows the kernel to choose a suitable value automatically.
"None" is equivalent to specifying zero.
We're particularly interested in comparisons between 'auto' and 'none' with
different configurations.
2. vgsplit now lets you split off PVs into a new VG, and accepts vgcreate
command line options to set properties of that VG.
[a few known bugs in the validation still to fix here]
3. If you enable dmeventd (configure '--enable-dmeventd' on both packages)
it can now monitor snapshots and report to syslog if they are getting full.
[further enhancements to this are planned]
4. The --resizefs argument to lvresize/lvextend/lvreduce now calls out
to a new script, fsadm, which attempts to resize the filesystem in
conjunction with the LV.
[further enhancements to this are planned - only some cases supported
so far, and we want fsadm to become a new commandline entry point too,
like e2fsadm used to be in LVM1 - it isn't yet]
5. pvs --segments will now also display LV segment fields so you can
see what is layered on each PV segment.
6. lvconvert now supports additional mirror reconfigurations (similar to the
way pvmove works). E.g. convert from -m1 to -m2.
Alasdair
--
agk@redhat.com
reply other threads:[~2008-01-21 13:31 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20080121133107.GZ24157@agk.fab.redhat.com \
--to=agk@redhat.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).