From: Kevin Corry <corryk@us.ibm.com>
To: evms-devel@lists.sourceforge.net, evms-announce@lists.sourceforge.net
Cc: linux-kernel@vger.kernel.org
Subject: [ANNOUNCE] Enterprise Volume Management System (EVMS) Release 0.2.2
Date: Sun, 4 Nov 2001 12:10:57 -0600 [thread overview]
Message-ID: <01110412105700.30243@boiler> (raw)
Release 0.2.2 of EVMS is now available for download at the project web site:
http://www.sf.net/projects/evms
Highlights for version 0.2.2
v0.2.2 - 11/04/01
- Support for Devfs
- If devfs is enabled in the kernel, all necessary device files for
discovered volumes will appear at boot time in /dev/evms.
- Updated code in engine for creating device files in the case when devfs
is not enabled.
- Dual on-disk copies of EVMS-native metadata (system data and
feature headers)
- Kernel and engine common code responsible for recognizing and reconciling
the redundant copies of system data and feature headers
- Individual plugins responsible for maintaining multiple copies of
their private metadata.
- LVM plugin
- Creating snapshot LVs and contiguous LVs, and deleting snapshot LVs.
- All metadata is now read/written in endian-neutral format
- Improved option handling and information displays.
- Default Segment Manager plugin
- Fixed a bug with removing the last segment from a disk.
- When assigning the segment manager to a new disk, it now adds OS/2 boot
sector code to the MBR.
- Drivelinking and BBR engine plugins now commit using the new
dual-metadata format.
- BBR discovery works, but there is a known I/O bug when running mkfs on
a BBR volume.
- OS/2 Region Manager
- Kernel and engine discovery of OS/2 compatibility volumes
- Kernel discovery of OS/2 LVM volumes
- Fixed kernel-side volume quiesce/rediscover bug
- Modifed kernel patching process
- EVMS package now comes with several small patches specific to particular
2.4 kernel versions for patching the common files modified by EVMS.
- See the EVMS-HOWTO for more details.
Kevin Corry
corryk@us.ibm.com
Enterprise Volume Management System
http://www.sf.net/projects/evms
reply other threads:[~2001-11-04 18:12 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=01110412105700.30243@boiler \
--to=corryk@us.ibm.com \
--cc=evms-announce@lists.sourceforge.net \
--cc=evms-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.