This is the mail archive of the
cluster-cvs@sourceware.org
mailing list for the cluster.
Cluster Project tag, cmirror_1_1_16, created. cmirror_1_1_15-63-g6bb8188
- From: cfeist at sourceware dot org
- To: cluster-cvs at sources dot redhat dot com, cluster-devel at redhat dot com
- Date: 14 May 2008 20:54:24 -0000
- Subject: Cluster Project tag, cmirror_1_1_16, created. cmirror_1_1_15-63-g6bb8188
This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project "Cluster Project".
http://sources.redhat.com/git/gitweb.cgi?p=cluster.git;a=commitdiff;h=6bb8188b10227bb97a0fb1cbca88e5fc9a236f2a
The tag, cmirror_1_1_16 has been created
at 6bb8188b10227bb97a0fb1cbca88e5fc9a236f2a (commit)
- Log -----------------------------------------------------------------
commit 6bb8188b10227bb97a0fb1cbca88e5fc9a236f2a
Author: Jonathan Brassow <jbrassow@redhat.com>
Date: Wed May 7 14:55:48 2008 -0500
clogd: Remove scary print statements that show up on --resync
When LVM creates mirrors, it is kind enough to initialize the
log. However, when a 'lvchange --resync' is issued to resync
a mirror, it simply wipes the log instead of reinitializing it.
The log server was responding to this by issuing a warning that
it couldn't read a valid log header. This is not a problem,
because it simply reinitializes it on its own... so the messages
served no purpose.
LVM should probably be consistent and initialize the log when
a --resync is issued though.
-----------------------------------------------------------------------
hooks/post-receive
--
Cluster Project