1LVMDUMP(8) System Manager's Manual LVMDUMP(8)
2
3
4
6 lvmdump — create lvm2 information dumps for diagnostic purposes
7
9 lvmdump [-a] [-c] [-d directory] [-h] [-l] [-m] [-p] [-s] [-u]
10
12 lvmdump is a tool to dump various information concerning LVM2. By
13 default, it creates a tarball suitable for submission along with a
14 problem report.
15
16 The content of the tarball is as follows:
17 - dmsetup info
18 - table of currently running processes
19 - recent entries from /var/log/messages (containing system messages)
20 - complete lvm configuration and cache (content of /etc/lvm)
21 - list of device nodes present under /dev
22 - list of files present /sys/block
23 - list of files present /sys/devices/virtual/block
24 - if enabled with -m, metadata dump will be also included
25 - if enabled with -a, debug output of vgscan, pvscan and list of all
26 available volume groups, physical volumes and logical volumes will be
27 included
28 - if enabled with -c, cluster status info
29 - if enabled with -l, lvmetad state if running
30 - if enabled with -p, lvmpolld state if running
31 - if enabled with -s, system info and context
32 - if enabled with -u, udev info and context
33
35 -a Advanced collection. WARNING: if lvm is already hung, then this
36 script may hang as well if -a is used.
37
38 -c If clvmd is running, gather cluster data as well.
39
40 -d directory
41 Dump into a directory instead of tarball By default, lvmdump
42 will produce a single compressed tarball containing all the
43 information. Using this option, it can be instructed to only
44 produce the raw dump tree, rooted in directory.
45
46 -h Print help message
47
48 -l Include lvmetad(8) daemon dump if it is running. The dump con‐
49 tains cached information that is currently stored in lvmetad: VG
50 metadata, PV metadata and various mappings in between these
51 metadata for quick access.
52
53 -m Gather LVM metadata from the PVs This option generates a 1:1
54 dump of the metadata area from all PVs visible to the system,
55 which can cause the dump to increase in size considerably. How‐
56 ever, the metadata dump may represent a valuable diagnostic
57 resource.
58
59 -p Include lvmpolld(8) daemon dump if it is running. The dump con‐
60 tains all in-progress operation currently monitored by the dae‐
61 mon and partial history for all yet uncollected results of
62 polling operations already finished including reason.
63
64 -s Gather system info and context. Currently, this encompasses sys‐
65 temd info and context only: overall state of systemd units
66 present in the system, more detailed status of units controlling
67 LVM functionality and the content of systemd journal for current
68 boot.
69
70 -u Gather udev info and context: /etc/udev/udev.conf file, udev
71 daemon version (output of 'udevadm info --version' command),
72 udev rules currently used in the system (content of
73 /lib/udev/rules.d and /etc/udev/rules.d directory), list of
74 files in /lib/udev directory and dump of current udev database
75 content (the output of 'udevadm info --export-db' command).
76
78 LVM_BINARY
79 The LVM2 binary to use. Defaults to "lvm". Sometimes you might
80 need to set this to "/sbin/lvm.static", for example.
81
82 DMSETUP_BINARY
83 The dmsetup binary to use. Defaults to "dmsetup".
84
86 lvm(8)
87
88
89
90Red Hat, Inc. LVM TOOLS 2.02.143(2)-RHEL6 (2016-12-13) LVMDUMP(8)