# LVMDUMP - create lvm2 information dumps for diagnostic purposes - man(8) - [phpMan]

[_LVMDUMP_(8)](https://www.chedong.com/phpMan.php/man/LVMDUMP/8/markdown)                             System Manager's Manual                            [_LVMDUMP_(8)](https://www.chedong.com/phpMan.php/man/LVMDUMP/8/markdown)

## NAME
       lvmdump — create lvm2 information dumps for diagnostic purposes

## SYNOPSIS
       **lvmdump **[**-a**] [**-c**] [**-d _**directory_] [**-h**] [**-l**] [**-m**] [**-p**] [**-s**] [**-u**]

## DESCRIPTION
       lvmdump is a tool to dump various information concerning LVM2.  By default, it creates a tar‐
       ball suitable for submission along with a problem report.

       The content of the tarball is as follows:
       • dmsetup info
       • table of currently running processes
       • recent entries from _/var/log/messages_ (containing system messages)
       • complete lvm configuration and cache (content of _/etc/lvm_)
       • list of device nodes present under _/dev_
       • list of files present _/sys/block_
       • list of files present _/sys/devices/virtual/block_
       • if enabled with -m, metadata dump will be also included
       • if enabled with -a, debug output of vgscan, pvscan and list of all available volume groups,
         physical volumes and logical volumes will be included
       • if enabled with -l, lvmetad state if running
       • if enabled with -p, lvmpolld state if running
       • if enabled with -s, system info and context
       • if enabled with -u, udev info and context

## OPTIONS
### -a     
              well if **-a **is used.

### -d _
              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 in‐
              structed to only produce the raw dump tree, rooted in _directory_.

### -h     

### -l     
              that  is currently stored in lvmetad: VG metadata, PV metadata and various mappings in
              between these metadata for quick access.

### -m     
              from all PVs visible to the system, which can cause the dump to increase in size  con‐
              siderably.  However, the metadata dump may represent a valuable diagnostic resource.

### -p     
              operation currently monitored by the daemon and partial history  for  all  yet  uncol‐
              lected results of polling operations already finished including reason.

### -s     
              lsblk command and various systemd info and context: overall  state  of  systemd  units
              present in the system, more detailed status of units controlling LVM functionality and
              the content of systemd journal for current boot.

### -u     
              '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 direc‐
              tory and dump of current udev database content (the  output  of  'udevadm  info  --ex‐
              port-db' command).

## ENVIRONMENT VARIABLES
       **LVM_BINARY**
              The  LVM2  binary to use.  Defaults to "**lvm**".  Sometimes you might need to set this to
              "_/usr/bin/lvm.static_", for example.

       **DMSETUP_BINARY**
              The dmsetup binary to use.  Defaults to "**dmsetup**".

## SEE ALSO
       [**lvm**(8)](https://www.chedong.com/phpMan.php/man/lvm/8/markdown), [**lvmpolld**(8)](https://www.chedong.com/phpMan.php/man/lvmpolld/8/markdown),

       [**udev**(8)](https://www.chedong.com/phpMan.php/man/udev/8/markdown), [**udevadm**(8)](https://www.chedong.com/phpMan.php/man/udevadm/8/markdown)

Red Hat, Inc.                     LVM TOOLS [2.03.16(2)](https://www.chedong.com/phpMan.php/man/2.03.16/2/markdown) (2022-05-18)                       [_LVMDUMP_(8)](https://www.chedong.com/phpMan.php/man/LVMDUMP/8/markdown)