2008-10-08 16:50:13 +04:00
.TH LVMDUMP 8 "LVM TOOLS #VERSION#" "Red Hat, Inc."
2006-11-16 19:44:48 +03:00
.SH NAME
lvmdump - create lvm2 information dumps for diagnostic purposes
.SH SYNOPSIS
2012-04-11 16:42:10 +04:00
.B lvmdump
.RB [ \- a ]
.RB [ \- c ]
.RB [ \- d
.IR directory ]
.RB [ \- h ]
2013-08-29 16:20:57 +04:00
.RB [ \- l ]
2012-04-11 16:42:10 +04:00
.RB [ \- m ]
2013-08-29 16:20:57 +04:00
.RB [ \- u ]
2006-11-16 19:44:48 +03:00
.SH DESCRIPTION
2012-04-11 16:42:10 +04:00
lvmdump is a tool to dump various information concerning LVM2.
By default, it creates a tarball suitable for submission along
with a problem report.
2006-11-16 19:44:48 +03:00
.PP
The content of the tarball is as follows:
.br
- dmsetup info
.br
- table of currently running processes
.br
- recent entries from /var/log/messages (containing system messages)
.br
2010-06-24 12:18:54 +04:00
- complete lvm configuration and cache (content of /etc/lvm)
2006-11-16 19:44:48 +03:00
.br
- list of device nodes present under /dev
.br
2010-06-24 12:18:54 +04:00
- list of files present /sys/block
.br
- list of files present /sys/devices/virtual/block
.br
2012-04-11 16:42:10 +04:00
- if enabled with \- m, metadata dump will be also included
2006-11-16 19:44:48 +03:00
.br
2012-04-11 16:42:10 +04:00
- if enabled with \- a, debug output of vgscan, pvscan and list of all available volume groups, physical volumes and logical volumes will be included
2006-11-16 19:44:48 +03:00
.br
2012-04-11 16:42:10 +04:00
- if enabled with \- c, cluster status info
2013-08-28 16:57:34 +04:00
.br
- if enabled with \- l, lvmetad state if running
.br
- if enabled with \- u, udev info and context
2006-11-16 19:44:48 +03:00
.SH OPTIONS
.TP
2012-04-11 16:42:10 +04:00
.B \- a
Advanced collection.
\fB WARNING\fR : if lvm is already hung, then this script may hang as well
if \fB \- a\fR is used.
2006-11-16 19:44:48 +03:00
.TP
2012-04-11 16:42:10 +04:00
.B \- c
If clvmd is running, gather cluster data as well.
2006-11-16 19:44:48 +03:00
.TP
2012-04-11 16:42:10 +04:00
.B \- d \fI directory
Dump into a directory instead of tarball
By default, lvmdump will produce a single compressed tarball containing
all the information. Using this option, it can be instructed to only
produce the raw dump tree, rooted in \fI directory\fP .
2006-11-16 19:44:48 +03:00
.TP
2012-04-11 16:42:10 +04:00
.B \- h
Print help message
2006-11-16 19:44:48 +03:00
.TP
2013-08-28 16:57:34 +04:00
.B \- l
Include \fB lvmetad\fP (8) daemon dump if it is running. The dump contains
cached information that is currently stored in lvmetad: VG metadata,
PV metadata and various mappings in between these metadata for quick
access.
.TP
2012-04-11 16:42:10 +04:00
.B \- m
Gather LVM metadata from the PVs
This option generates a 1:1 dump of the metadata area from all PVs visible
to the system, which can cause the dump to increase in size considerably.
However, the metadata dump may represent a valuable diagnostic resource.
2013-08-28 16:57:34 +04:00
.TP
.B \- u
Gather udev info and context: /etc/udev/udev.conf file, udev daemon version
(output of 'udevadm info --version' command), udev rules currently used in the system
(content of /lib/udev/rules.d and /etc/udev/rules.d directory),
list of files in /lib/udev directory and dump of current udev
database content (the output of 'udevadm info --export-db' command).
2006-11-23 20:44:15 +03:00
.SH ENVIRONMENT VARIABLES
.TP
2012-04-11 16:42:10 +04:00
\fB LVM_BINARY\fP
2006-11-23 20:44:15 +03:00
The LVM2 binary to use.
Defaults to "lvm".
Sometimes you might need to set this to "/sbin/lvm.static", for example.
.TP
2012-04-11 16:42:10 +04:00
\fB DMSETUP_BINARY\fP
2006-11-23 20:44:15 +03:00
The dmsetup binary to use.
Defaults to "dmsetup".
2006-11-16 19:44:48 +03:00
.PP
2012-04-11 16:42:10 +04:00
.SH SEE ALSO
.BR lvm (8)