{"id":3157,"date":"2022-12-20T16:43:39","date_gmt":"2022-12-20T19:43:39","guid":{"rendered":"http:\/\/lode.uno\/linux-man\/index.php\/2022\/12\/20\/lvmdump-man8\/"},"modified":"2022-12-20T16:43:39","modified_gmt":"2022-12-20T19:43:39","slug":"lvmdump-man8","status":"publish","type":"post","link":"https:\/\/lode.uno\/linux-man\/2022\/12\/20\/lvmdump-man8\/","title":{"rendered":"LVMDUMP (man8)"},"content":{"rendered":"

LVMDUMP<\/h1>\n

NAME<\/a>
SYNOPSIS<\/a>
DESCRIPTION<\/a>
OPTIONS<\/a>
ENVIRONMENT VARIABLES<\/a>
SEE ALSO<\/a> <\/p>\n

\n

NAME <\/a> <\/h2>\n

lvmdump \u2014 create lvm2 information dumps for diagnostic purposes<\/p>\n

SYNOPSIS <\/a> <\/h2>\n

lvmdump<\/b> [\u2212a<\/b>] [\u2212c<\/b>] [\u2212d<\/b> directory<\/i>] [\u2212h<\/b>] [\u2212l<\/b>] [\u2212m<\/b>] [\u2212p<\/b>] [\u2212s<\/b>] [\u2212u<\/b>]<\/p>\n

DESCRIPTION <\/a> <\/h2>\n

lvmdump is a tool to dump various information concerning LVM2. By default, it creates a tarball suitable for submission along with a problem report.<\/p>\n

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 \u2212m, metadata dump will be also included
– if enabled with \u2212a, debug output of vgscan, pvscan and list of all available volume groups, physical volumes and logical volumes will be included
– if enabled with \u2212l, lvmetad state if running
– if enabled with \u2212p, lvmpolld state if running
– if enabled with \u2212s, system info and context
– if enabled with \u2212u, udev info and context<\/p>\n

OPTIONS <\/a> <\/h2>\n\n\n
<\/td>\n\n

\u2212a<\/b><\/p>\n<\/td>\n

<\/td>\n\n

Advanced collection. WARNING<\/b>: if lvm is already hung, then this script may hang as well if \u2212a<\/b> is used.<\/p>\n<\/td>\n<\/tr>\n<\/table>\n

\u2212d<\/b> directory<\/i><\/p>\n

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 directory<\/i>.<\/p>\n\n\n\n\n\n\n\n
<\/td>\n\n

\u2212h<\/b><\/p>\n<\/td>\n

<\/td>\n\n

Print help message<\/p>\n<\/td>\n<\/tr>\n

<\/td>\n\n

\u2212l<\/b><\/p>\n<\/td>\n

<\/td>\n\n

Include lvmetad<\/b>(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.<\/p>\n<\/td>\n<\/tr>\n

<\/td>\n\n

\u2212m<\/b><\/p>\n<\/td>\n

<\/td>\n\n

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.<\/p>\n<\/td>\n<\/tr>\n

<\/td>\n\n

\u2212p<\/b><\/p>\n<\/td>\n

<\/td>\n\n

Include lvmpolld<\/b>(8) daemon dump if it is running. The dump contains all in-progress operation currently monitored by the daemon and partial history for all yet uncollected results of polling operations already finished including reason.<\/p>\n<\/td>\n<\/tr>\n

<\/td>\n\n

\u2212s<\/b><\/p>\n<\/td>\n

<\/td>\n\n

Gather system info and context. Currently, this encompasses info gathered by calling 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.<\/p>\n<\/td>\n<\/tr>\n

<\/td>\n\n

\u2212u<\/b><\/p>\n<\/td>\n

<\/td>\n\n

Gather udev info and context: \/etc\/udev\/udev.conf file, udev daemon version (output of \u2019udevadm info \u2212\u2212version\u2019 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 \u2019udevadm info \u2212\u2212export\u2212db\u2019 command).<\/p>\n<\/td>\n<\/tr>\n<\/table>\n

ENVIRONMENT VARIABLES <\/a> <\/h2>\n

LVM_BINARY<\/b><\/p>\n

The LVM2 binary to use. Defaults to “lvm”. Sometimes you might need to set this to “\/sbin\/lvm.static”, for example.<\/p>\n

DMSETUP_BINARY<\/b><\/p>\n

The dmsetup binary to use. Defaults to “dmsetup”.<\/p>\n

SEE ALSO <\/a> <\/h2>\n

lvm<\/b>(8)<\/p>\n

\n","protected":false},"excerpt":{"rendered":"

lvmdump \u2014 create lvm2 information dumps for diagnostic purposes <\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[2],"tags":[5,52,300,4],"class_list":["post-3157","post","type-post","status-publish","format-standard","hentry","category-8-administracion-del-sistema","tag-5","tag-administracion","tag-lvmdump","tag-man8"],"gutentor_comment":0,"_links":{"self":[{"href":"https:\/\/lode.uno\/linux-man\/wp-json\/wp\/v2\/posts\/3157","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/lode.uno\/linux-man\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/lode.uno\/linux-man\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/lode.uno\/linux-man\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/lode.uno\/linux-man\/wp-json\/wp\/v2\/comments?post=3157"}],"version-history":[{"count":0,"href":"https:\/\/lode.uno\/linux-man\/wp-json\/wp\/v2\/posts\/3157\/revisions"}],"wp:attachment":[{"href":"https:\/\/lode.uno\/linux-man\/wp-json\/wp\/v2\/media?parent=3157"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/lode.uno\/linux-man\/wp-json\/wp\/v2\/categories?post=3157"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/lode.uno\/linux-man\/wp-json\/wp\/v2\/tags?post=3157"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}