From: christophe varoqui <christophe.varoqui@free.fr>
To: device-mapper development <dm-devel@redhat.com>
Cc: "linux-raid@vger.kernel.org" <linux-raid@vger.kernel.org>,
"linux-hotplug-devel@lists.sourceforge.net"
<linux-hotplug-devel@lists.sourceforge.net>,
"linux-scsi@vger.kernel.org" <linux-scsi@vger.kernel.org>
Subject: multipath-tools-0.3.2
Date: Sun, 17 Oct 2004 16:03:07 +0200 [thread overview]
Message-ID: <1098021787.5433.8.camel@zezette> (raw)
In-Reply-To: <1097495416.416a73787e0ae@imp1-q.free.fr>
Hello,
here goes multipath-tools-0.3.2
This one will need you to upgrade to latest -udm patchset to support the
new path reinstate feature.
Lots of bugfixes from Suse review.
Full ChangeLog for the release :
* [multipath] add path reinstate logic :
* if a path is given as multipath arg
* if the map containing that path already exists
* if this map is the same as the that would be
created by this multipath run
* THEN reinstate the path
multipathd is is thus unchanged, while now supporting
reinstate
* audit and ensafe all sprintf usage
* [multipath] fix the annoying \n after each dev_t in
params string reporting
* [multipath] print out devmaps in "-v2 -d" mode
* [kpartx] bump up the params string size (lmb at suse)
* [kpartx] replace sprintf by snprintf (lmb at suse)
* [kpartx] initialize some more vars (lmb at suse)
* [multipath] mp->pg == NULL safety net before calling
assemble_map() (for Andy who happen to hit the bug)
* [multipath] last rampant bug in map CREATE or UPDATE switch
logic due to the device alias feature
* [kpartx] zeroe "struct slice all" (lmb at suse)
As usual, doc and download at :
http://christophe.varoqui.free.fr/
regards,
--
christophe varoqui <christophe.varoqui@free.fr>
next prev parent reply other threads:[~2004-10-17 14:03 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-25 0:24 [ANNOUNCE] multipath-tools-0.2.9 christophe varoqui
2004-10-06 9:22 ` [ANNOUNCE] multipath-tools-0.3.0 christophe.varoqui
2004-10-06 9:50 ` [dm-devel] " Lars Marowsky-Bree
2004-10-06 10:18 ` christophe.varoqui
2004-10-11 12:00 ` Lars Marowsky-Bree
2004-10-11 12:31 ` christophe.varoqui
2004-10-07 20:01 ` Dave Olien
2004-10-08 12:49 ` christophe.varoqui
2004-10-11 11:50 ` [ANNOUNCE] multipath-tools-0.3.1 christophe.varoqui
2004-10-12 18:35 ` Dave Olien
2004-10-17 14:03 ` christophe varoqui [this message]
2004-10-20 10:46 ` [ANNOUNCE] multipath-tools-0.3.3 christophe.varoqui
2004-10-24 22:14 ` [ANNOUNCE] multipath-tools-0.3.4 christophe varoqui
2004-10-25 8:22 ` Arjan van de Ven
2004-10-25 9:38 ` christophe.varoqui
2004-10-25 10:39 ` Douglas Gilbert
2004-10-25 21:03 ` [dm-devel] " Lars Marowsky-Bree
2004-10-26 17:52 ` Mike Christie
2004-10-26 10:06 ` [ANNOUNCE] multipath-tools-0.3.5 christophe.varoqui
2004-11-01 17:08 ` [ANNOUNCE] multipath-tools-0.3.6 christophe varoqui
2004-11-11 23:10 ` [ANNOUNCE] multipath-tools-0.3.7 christophe varoqui
2004-11-25 14:55 ` [ANNOUNCE] multipath-tools-0.3.8 christophe varoqui
2004-12-05 15:43 ` [ANNOUNCE] multipath-tools-0.3.9 christophe varoqui
2004-12-12 17:20 ` [ANNOUNCE] multipath-tools-0.4.0 christophe varoqui
2004-12-20 16:01 ` [ANNOUNCE] multipath-tools-0.4.1 christophe varoqui
2005-01-23 23:03 ` [ANNOUNCE] multipath-tools-0.4.2 christophe varoqui
2005-03-19 14:27 ` [ANNOUNCE] multipath-tools-0.4.3 christophe varoqui
2005-04-24 22:26 ` [ANNOUNCE] multipath-tools-0.4.4 christophe varoqui
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=1098021787.5433.8.camel@zezette \
--to=christophe.varoqui@free.fr \
--cc=dm-devel@redhat.com \
--cc=linux-hotplug-devel@lists.sourceforge.net \
--cc=linux-raid@vger.kernel.org \
--cc=linux-scsi@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 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).