public inbox for
help / color / mirror / Atom feed
Subject: LVM2 ./WHATS_NEW man/clvmd.8
Date: Mon, 11 Dec 2006 14:06:00 -0000	[thread overview]
Message-ID: <> (raw)

CVSROOT:	/cvs/lvm2
Module name:	LVM2
Changes by:	2006-12-11 14:06:26

Modified files:
	.              : WHATS_NEW 
	man            : clvmd.8 

Log message:
	Add manpage reference for clvmd -T that got missed out when I
	checked the code in (sorry).


--- LVM2/WHATS_NEW	2006/12/11 14:00:26	1.517
+++ LVM2/WHATS_NEW	2006/12/11 14:06:25	1.518
@@ -1,5 +1,6 @@
 Version 2.02.17 -
+  Add manpage entry for clvmd -T
   Fix gulm operation of clvmd, including a hang when doing lvchange -aey
   Fix hang in clvmd if a pre-command failed.
--- LVM2/man/clvmd.8	2006/10/04 08:28:17	1.3
+++ LVM2/man/clvmd.8	2006/12/11 14:06:25	1.4
@@ -6,6 +6,7 @@
 [\-d] [\-h]
 [\-t <timeout>]
+[\-T <start timeout>]
 clvmd is the daemon that distributes LVM metadata updates around a cluster.
@@ -23,6 +24,23 @@
 may need to increase this on systems with very large disk farms. 
 The default is 30 seconds.
+.I \-T <start timeout>
+Specifies the timeout for clvmd daemon startup. If the daemon does not report 
+that it has started up within this time then the parent command will exit with 
+status of 5. This does NOT mean that clvmd has not started! What it means is 
+that the startup of clvmd has been delayed for some reason; the most likely 
+cause of this is an inquorate cluster though it could be due to locking 
+latencies on a cluster with large numbers of logical volumes. If you get the 
+return code of 5 it is usually not necessary to restart clvmd - it will start
+as soon as that blockage has cleared. This flag is to allow startup scripts
+to exit in a timely fashion even if the cluster is stalled for some reason.
+The default is 0 (no timeout) and the value is in seconds. Don't set this too
+small or you will experience spurious errors. 10 or 20 seconds might be
+This timeout will be ignored if you start clvmd with the -d switch.
 .I \-R
 Tells all the running clvmd in the cluster to reload their device cache and
 re-read the lvm configuration file. This command should be run whenever the

             reply	other threads:[~2006-12-11 14:06 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-12-11 14:06 pcaulfield [this message]
  -- strict thread matches above, loose matches on Subject: below --
2004-09-02 14:16 agk

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \

* 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).