1 .TH LVMDUMP 8 "LVM TOOLS #VERSION#" "Red Hat, Inc."
3 lvmdump - create lvm2 information dumps for diagnostic purposes
5 \fBlvmdump\fP [options] [-d directory]
7 \fBlvmdump\fP is a tool to dump various information concerning LVM2. By default, it creates a tarball suitable for submission along with a problem report.
9 The content of the tarball is as follows:
13 - table of currently running processes
15 - recent entries from /var/log/messages (containing system messages)
17 - complete lvm configuration and cache (content of /etc/lvm)
19 - list of device nodes present under /dev
21 - list of files present /sys/block
23 - list of files present /sys/devices/virtual/block
25 - if enabled with -m, metadata dump will be also included
27 - if enabled with -a, debug output of vgscan, pvscan and list of all available volume groups, physical volumes and logical volumes will be included
29 - if enabled with -c, cluster status info
32 \fB\-h\fR \(em print help message
34 \fB\-a\fR \(em advanced collection
35 \fBWARNING\fR: if lvm is already hung, then this script may hang as well if \fB\-a\fR is used
37 \fB\-m\fR \(em gather LVM metadata from the PVs
38 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.
40 \fB\-d\fR directory \(em dump into a directory instead of tarball
41 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 \fBdirectory\fP.
43 \fB\-c\fR \(em if clvmd is running, gather cluster data as well
44 .SH ENVIRONMENT VARIABLES
47 The LVM2 binary to use.
49 Sometimes you might need to set this to "/sbin/lvm.static", for example.
52 The dmsetup binary to use.
53 Defaults to "dmsetup".