Visit Our UNIX and Linux User Community

Linux and UNIX Man Pages

Linux & Unix Commands - Search Man Pages

lvmetad(8) [centos man page]

LVMETAD(8)						      System Manager's Manual							LVMETAD(8)

NAME
lvmetad - LVM metadata cache daemon SYNOPSIS
lvmetad [-l {all|wire|debug}] [-p pidfile_path] [-s socket_path] [-f] [-h] [-V] [-?] DESCRIPTION
lvmetad is a metadata caching daemon for LVM. The daemon receives notifications from udev rules (which must be installed for LVM to work correctly when lvmetad is in use). Through these notifications, lvmetad has an up-to-date and consistent image of the volume groups avail- able in the system. By default, lvmetad, even if running, is not used by LVM. See lvm.conf(5). OPTIONS
To run the daemon in a test environment both the pidfile_path and the socket_path should be changed from the defaults. -f Don't fork, but run in the foreground. -h, -? Show help information. -l {all|wire|debug} Select the type of log messages to generate. Messages are logged by syslog. Additionally, when -f is given they are also sent to standard error. Since release 2.02.98, there are two classes of messages: wire and debug. Selecting 'all' supplies both and is equivalent to a comma-separated list -l wire,debug. Prior to release 2.02.98, repeating -d from 1 to 3 times, viz. -d, -dd, -ddd, increased the detail of messages. -p pidfile_path Path to the pidfile. This overrides both the built-in default (#DEFAULT_PID_DIR#/lvmetad.pid) and the environment variable LVM_LVMETAD_PIDFILE. This file is used to prevent more than one instance of the daemon running simultaneously. -s socket_path Path to the socket file. This overrides both the built-in default (/run/lvm/lvmetad.socket) and the environment variable LVM_LVMETAD_SOCKET. To communicate successfully with lvmetad, all LVM2 processes should use the same socket path. -V Display the version of lvmetad daemon. ENVIRONMENT VARIABLES
LVM_LVMETAD_PIDFILE Path for the pid file. LVM_LVMETAD_SOCKET Path for the socket file. SEE ALSO
lvm(8), lvm.conf(5) Red Hat Inc LVM TOOLS 2.02.105(2)-RHEL7 (2014-03-26) LVMETAD(8)

Check Out this Related Man Page

CLVMD(8)						      System Manager's Manual							  CLVMD(8)

NAME
clvmd - cluster LVM daemon SYNOPSIS
clvmd [-d[<value>]] [-C] [-h] [-E <lock uuid>] [-R] [-S] [-t <timeout>] [-T <start timeout>] [-V] DESCRIPTION
clvmd is the daemon that distributes LVM metadata updates around a cluster. It must be running on all nodes in the cluster and will give an error if a node in the cluster does not have this daemon running. OPTIONS
-d[<value>] Enable debug logging. Value can be 0, 1 or 2. 0 disables debug logging 1 sends debug logs to stderr (implies -f option) 2 sends debug logs to syslog If -d is specified without a value then 1 is assumed. -C Only valid if -d is also specified. Tells all clvmds in a cluster to enable/disable debug logging. Without this switch, only the local clvmd will change its debug level to that given with -d. This does not work correctly if specified on the command-line that starts clvmd. If you want to start clvmd and enable cluster-wide logging then the command needs to be issued twice, eg: clvmd clvmd -d2 -t <timeout> Specifies the timeout for commands to run around the cluster. This should not be so small that commands with many disk updates to do will fail, so you may need to increase this on systems with very large disk farms. The default is 30 seconds. -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 par- ent 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 sensible. This timeout will be ignored if you start clvmd with the -d switch. -E <lock uuid> Pass lock uuid to be reacquired exclusively when clvmd is restarted. -R Tells all the running clvmds in the cluster to reload their device cache and re-read the lvm configuration file. This command should be run whenever the devices on a cluster system are changed. -S Tells the running clvmd to exit and reexecute itself, for example at the end of a package upgrade. The new instance is instructed to reacquire any locks in the same state as they were previously held. (Alternative methods of restarting the daemon have the side effect of changing exclusive LV locks into shared locks.) -I Selects the cluster manager to use for locking and internal communications, the available managers will be listed as part of the 'clvmd -h' output. clvmd will use the first cluster manager that succeeds, and it checks them in the order cman,corosync,openais. As it is quite possible to have (eg) corosync and cman available on the same system you might have to manually specify this option to override the search. -V Display the version of the cluster LVM daemon. ENVIRONMENT VARIABLES
LVM_CLVMD_BINARY The CLVMD binary to use when clmvd restart is requested. Defaults to /usr/sbin/clvmd. LVM_BINARY The LVM2 binary to use. Defaults to /sbin/lvm. SEE ALSO
lvm(8) Red Hat Inc LVM TOOLS 2.02.95(2) (2012-03-06) CLVMD(8)

Featured Tech Videos