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: [ANNOUNCE] multipath-tools-0.4.5
Date: Fri, 02 Sep 2005 21:16:05 +0000 [thread overview]
Message-ID: <1125695765.6217.10.camel@zezette> (raw)
Hello,
here goes multipath-tools-0.4.5
This release was long due.
Full of new shiny features.
Worth noting :
* multipathd keeps Device Mapper path status in sync with path
checker status : proactive fail_path and reinstate_path
* proactive path group re-enable, as soon as one path goes up
* multipathd is now fully event driven :
o NetLink? uevents for kernels/distro that enables the feature
o Hotplug
o Unix socket messages
* a Command Line Interface to drive and inspect the daemon
* remove the multipath(8) cache file logic in favour of a
multipathd<->multipath unix socket request/reply design
* split multipath(8) listing option into
o short-list (-l) : don't fetch wwid, path checker status,
priorities ... fast
o detailed-list (-ll) : refetch all info
* the daemon asynchronous logger is now solid and avoid sending
critical messages
* daemon CLI command to reload the config file
* path checking interval gets longer when the path is reliably up,
resets to short as soon as a problem occur
* daemon implements 3 path group failback methods :
o manual
o immediate : failback as soon as an (enabled && !active) PG
gets the highest priority
o defered : failback to the highest priority
(enabled && !active) PG n seconds after the last PG priority
order change
* remove over-complicated and thread-confusing daemon initial
clone() w/ private namespace
* prioritizers official prefix is now mpath_prio_
* multipath(8) displays PG priorities when available
* new hp_sw checker. It's a tri-state UP/DOWN/GHOST
* new directio checker. Useful with DASD devices. May suplant
readsector0 in the long run ?
* stricter default blacklist regexps
* new '-f' multipath(8) flag to selectively suppress a multipath
map, and its device-mapped partitions
* alua prioritizer update, should work on x86
* support for >2TB multipaths
* claimed device detection : no more warning/error messages with
paths pinned by mounted FS
* option to use priorities as weights in the round-robin scheduler :
for people who can't wait for a qlen-based scheduler
As usual, doc and download at :
http://christophe.varoqui.free.fr/
Archive mirror at ftp://sources.redhat.com/pub/dm/multipath-tools/
Regards,
--
christophe varoqui <christophe.varoqui@free.fr>
-------------------------------------------------------
SF.Net email is Sponsored by the Better Software Conference & EXPO
September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices
Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA
Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf
_______________________________________________
Linux-hotplug-devel mailing list http://linux-hotplug.sourceforge.net
Linux-hotplug-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel
reply other threads:[~2005-09-02 21:16 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=1125695765.6217.10.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