public inbox for lvm2-cvs@sourceware.org
help / color / mirror / Atom feed
From: pcaulfield@sourceware.org
To: lvm2-cvs@sourceware.org
Subject: LVM2 ./WHATS_NEW daemons/clvmd/clvmd-cman.c
Date: Fri, 06 Oct 2006 10:06:00 -0000 [thread overview]
Message-ID: <20061006100611.23813.qmail@sourceware.org> (raw)
CVSROOT: /cvs/lvm2
Module name: LVM2
Changes by: pcaulfield@sourceware.org 2006-10-06 10:06:10
Modified files:
. : WHATS_NEW
daemons/clvmd : clvmd-cman.c
Log message:
Fix clvmd bug that could cause it to die when a node with a long name crashed.
Patches:
http://sourceware.org/cgi-bin/cvsweb.cgi/LVM2/WHATS_NEW.diff?cvsroot=lvm2&r1=1.455&r2=1.456
http://sourceware.org/cgi-bin/cvsweb.cgi/LVM2/daemons/clvmd/clvmd-cman.c.diff?cvsroot=lvm2&r1=1.14&r2=1.15
--- LVM2/WHATS_NEW 2006/10/05 22:02:52 1.455
+++ LVM2/WHATS_NEW 2006/10/06 10:06:10 1.456
@@ -1,5 +1,6 @@
Version 2.02.11 -
=====================================
+ Fix clvmd bug that could cause it to die when a node with a long name crashed.
Fix format_text mda_setup pv->size and pv_setup pe_count calculations.
Fix _for_each_pv() for mirror with core log.
Add lvm_dump.sh script to create a tarball of debugging info from a system.
--- LVM2/daemons/clvmd/clvmd-cman.c 2006/08/24 12:45:05 1.14
+++ LVM2/daemons/clvmd/clvmd-cman.c 2006/10/06 10:06:10 1.15
@@ -172,7 +172,7 @@
this currently just means that a node has stopped listening on our port */
static void event_callback(cman_handle_t handle, void *private, int reason, int arg)
{
- char namebuf[MAX_CLUSTER_NAME_LEN];
+ char namebuf[MAX_CLUSTER_MEMBER_NAME_LEN];
switch (reason) {
case CMAN_REASON_PORTCLOSED:
next reply other threads:[~2006-10-06 10:06 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-06 10:06 pcaulfield [this message]
-- strict thread matches above, loose matches on Subject: below --
2008-05-09 7:20 ccaulfield
2008-04-01 15:01 ccaulfield
2008-03-25 10:42 ccaulfield
2007-05-02 8:23 pcaulfield
2007-04-23 14:55 pcaulfield
2006-08-24 12:45 pcaulfield
2006-03-21 10:31 pcaulfield
2005-01-26 9:30 pcaulfield
2004-09-30 14:18 pcaulfield
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=20061006100611.23813.qmail@sourceware.org \
--to=pcaulfield@sourceware.org \
--cc=lvm2-cvs@sourceware.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 read-only IMAP folder(s) and NNTP newsgroup(s).