{"id":3952,"date":"2022-12-20T17:28:29","date_gmt":"2022-12-20T20:28:29","guid":{"rendered":"http:\/\/lode.uno\/linux-man\/index.php\/2022\/12\/20\/lvmreport-man7\/"},"modified":"2022-12-20T17:28:29","modified_gmt":"2022-12-20T20:28:29","slug":"lvmreport-man7","status":"publish","type":"post","link":"https:\/\/lode.uno\/linux-man\/2022\/12\/20\/lvmreport-man7\/","title":{"rendered":"LVMREPORT (man7)"},"content":{"rendered":"

LVMREPORT<\/h1>\n

NAME<\/a>
DESCRIPTION<\/a>
Categorization based on reporting facility<\/a>
Terms<\/a>
Common report configuration settings and command line options<\/a>
Main report specifics<\/a>
Log report specifics<\/a>
Selection<\/a>
EXAMPLES<\/a>
SEE ALSO<\/a> <\/p>\n

\n

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

lvmreport \u2014 LVM reporting and related features<\/p>\n

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

LVM uses single reporting infrastructure that sets standard on LVM command\u2019s output and it provides wide range of configuration settings and command line options to customize report and filter the report\u2019s output.<\/p>\n

Categorization based on reporting facility <\/a> <\/h2>\n

Based on functionality, commands which make use of the reporting infrastructure are divided in two groups:
Report-oriented<\/b><\/p>\n

These commands inform about current LVM state and their primary role is to display this information in compendious way. To make a distinction, we will name this report as main report<\/b>. The set of report-only commands include: pvs, vgs, lvs, pvdisplay, vgdisplay, lvdisplay, lvm devtypes, lvm fullreport. For further information about main report, see main report specifics<\/b>.<\/p>\n

Processing-oriented<\/b><\/p>\n

These commands are responsible for changing LVM state and they do not contain any main report as identified for report-oriented commands, they only perform some kind of processing. The set of processing-oriented commands includes: pvcreate, vgcreate, lvcreate, pvchange, vgchange, lvchange, pvremove, vgremove, lvremove, pvresize, vgextend, vgreduce, lvextend, lvreduce, lvresize, lvrename, pvscan, vgscan, lvscan, pvmove, vgcfgbackup, vgck, vgconvert, vgexport, vgimport, vgmknodes.<\/p>\n

If enabled, so called log report<\/b> is either displayed solely (for processing-oriented commands) or in addition to main report (for report-oriented commands). The log report contains a log of operations, messages and per-object status with complete object identification collected during LVM command execution. See log report specifics<\/b> for more information about this report type.<\/p>\n

Terms <\/a> <\/h2>\n

When describing reporting functionality and features in this text, we will use terms row<\/b> and column<\/b>. By row we mean series of values reported for single entity (for example single PV, VG or LV). Each value from the row then belongs to a column of certain type. The columns have column headings<\/b> which are short descriptions for the columns. The columns are referenced by column names<\/b>. Please note that this text is also using term field<\/b> interchangeably with the term column<\/b>. Most of the time the term columns is abbreviated as col<\/b> in configuration.<\/p>\n

Common report configuration settings and command line options <\/a> <\/h2>\n

There are common configuration settings and command line options which apply to both main report<\/b> and log report<\/b>. Following lists contain all of them, separated into groups based on their use.<\/p>\n

Common configuration settings:<\/b><\/p>\n\n\n
<\/td>\n\n

\u2022<\/p>\n<\/td>\n

<\/td>\n\n

Changing report output format, composition and other output modifiers:<\/p>\n<\/td>\n<\/tr>\n<\/table>\n

\u2212<\/p>\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
<\/td>\n<\/td>\n<\/td>\n\n

global\/units<\/p>\n<\/td>\n

 <\/td>\n<\/tr>\n
<\/td>\n\n

\u2212<\/p>\n<\/td>\n

<\/td>\n\n

global\/suffix<\/p>\n<\/td>\n

 <\/td>\n<\/tr>\n
<\/td>\n\n

\u2212<\/p>\n<\/td>\n

<\/td>\n\n

report\/output_format<\/p>\n<\/td>\n

 <\/td>\n<\/tr>\n
<\/td>\n\n

\u2212<\/p>\n<\/td>\n

<\/td>\n\n

report\/compact_output<\/p>\n<\/td>\n

 <\/td>\n<\/tr>\n
<\/td>\n\n

\u2212<\/p>\n<\/td>\n

<\/td>\n\n

report\/compact_output_cols<\/p>\n<\/td>\n

 <\/td>\n<\/tr>\n
<\/td>\n\n

\u2212<\/p>\n<\/td>\n

<\/td>\n\n

report\/aligned<\/p>\n<\/td>\n

 <\/td>\n<\/tr>\n
<\/td>\n\n

\u2212<\/p>\n<\/td>\n

<\/td>\n\n

report\/headings<\/p>\n<\/td>\n

 <\/td>\n<\/tr>\n
<\/td>\n\n

\u2212<\/p>\n<\/td>\n

<\/td>\n\n

report\/separator<\/p>\n<\/td>\n

 <\/td>\n<\/tr>\n
<\/td>\n\n

\u2212<\/p>\n<\/td>\n

<\/td>\n\n

report\/list_item_separator<\/p>\n<\/td>\n

 <\/td>\n<\/tr>\n
<\/td>\n\n

\u2212<\/p>\n<\/td>\n

<\/td>\n\n

report\/prefixes<\/p>\n<\/td>\n

 <\/td>\n<\/tr>\n
<\/td>\n\n

\u2212<\/p>\n<\/td>\n

<\/td>\n\n

report\/quoted<\/p>\n<\/td>\n

 <\/td>\n<\/tr>\n
<\/td>\n\n

\u2212<\/p>\n<\/td>\n

<\/td>\n\n

report\/columns_as_rows<\/p>\n<\/td>\n

 <\/td>\n<\/tr>\n
<\/td>\n\n

\u2212<\/p>\n<\/td>\n

<\/td>\n\n

report\/binary_values_as_numeric<\/p>\n<\/td>\n

 <\/td>\n<\/tr>\n
<\/td>\n\n

\u2212<\/p>\n<\/td>\n

<\/td>\n\n

report\/time_format<\/p>\n<\/td>\n

 <\/td>\n<\/tr>\n
<\/td>\n\n

\u2212<\/p>\n<\/td>\n

<\/td>\n\n

report\/mark_hidden_devices<\/p>\n<\/td>\n

 <\/td>\n<\/tr>\n
<\/td>\n\n

\u2212<\/p>\n<\/td>\n

<\/td>\n\n

report\/two_word_unknown_device<\/p>\n<\/td>\n

 <\/td>\n<\/tr>\n
<\/td>\n\n

\u2022<\/p>\n<\/td>\n

<\/td>\n<\/td>\n <\/td>\n<\/tr>\n<\/table>\n

Special settings<\/p>\n\n\n
<\/td>\n\n

\u2212<\/p>\n<\/td>\n

<\/td>\n\n

report\/buffered<\/p>\n<\/td>\n

 <\/td>\n<\/tr>\n<\/table>\n

This document does not describe these settings in more detail \u2212 if you need detailed information, including values which are accepted for the settings, please run lvmconfig \u2212\u2212type default \u2212\u2212withcomments <\/b>. There are more configuration settings in addition to the common set listed above, but they are specific to either main report<\/b> or log report<\/b>, see main report specifics<\/b> and log report specifics<\/b> for these settings. Besides configuring reports globally by using configuration settings, there are also command line options you can use to extend, override or further specify the report configuration.<\/p>\n

Common command line options:<\/b><\/p>\n\n\n
<\/td>\n\n

\u2022<\/p>\n<\/td>\n

<\/td>\n\n

Definition of the set set of fields to use<\/p>\n<\/td>\n<\/tr>\n<\/table>\n

\u2212<\/p>\n\n\n
<\/td>\n\n

-\u2212options|\u2212o FieldSet<\/p>\n<\/td>\n

 <\/td>\n<\/tr>\n<\/table>\n

Field set to use. See main report specifics<\/b> and log report specifics<\/b> for information about field sets configured with global configuratin settings that this option overrides.<\/p>\n\n\n
<\/td>\n\n

\u2212<\/p>\n<\/td>\n

<\/td>\n\n

-\u2212options|\u2212o+ FieldSet<\/p>\n<\/td>\n

 <\/td>\n<\/tr>\n<\/table>\n

Fields to include to current field set. See main report specifics\u00a0<\/b>and log report specifics<\/b> for information about field sets configured with global configuration settings that this option extends.<\/p>\n\n\n
<\/td>\n\n

\u2212<\/p>\n<\/td>\n

<\/td>\n\n

-\u2212options|\u2212o- FieldSet<\/p>\n<\/td>\n

 <\/td>\n<\/tr>\n<\/table>\n

Fields to exclude from current field set. See main report specifics<\/b> and log report specifics<\/b> for information about field sets configured with global configuration settings that this option reduces.<\/p>\n\n\n
<\/td>\n\n

\u2212<\/p>\n<\/td>\n

<\/td>\n\n

-\u2212options|\u2212o# FieldSet<\/p>\n<\/td>\n

 <\/td>\n<\/tr>\n<\/table>\n

Compaction of unused fields. Overrides report\/compact_output_cols configuration setting.<\/p>\n\n\n
<\/td>\n\n

\u2022<\/p>\n<\/td>\n

<\/td>\n\n

Sorting<\/p>\n<\/td>\n

 <\/td>\n<\/tr>\n<\/table>\n

\u2212<\/p>\n\n\n
<\/td>\n\n

-\u2212sort|\u2212O+ FieldSet<\/p>\n<\/td>\n

 <\/td>\n<\/tr>\n<\/table>\n

Fields to sort by in ascending order. See main report specifics<\/b> and log report specifics<\/b> for information about field sets configured with global configuration settings that this option overrides.<\/p>\n\n\n
<\/td>\n\n

\u2212<\/p>\n<\/td>\n

<\/td>\n\n

-\u2212sort|\u2212O- FieldSet<\/p>\n<\/td>\n

 <\/td>\n<\/tr>\n<\/table>\n

Fields to sort by in descending order. See main report specifics<\/b> and log report specifics<\/b> for information about fields sets configured with global configuration settings that this options overrides.<\/p>\n\n\n
<\/td>\n\n

\u2022<\/p>\n<\/td>\n

<\/td>\n\n

Selection<\/p>\n<\/td>\n

 <\/td>\n<\/tr>\n<\/table>\n

\u2212<\/p>\n\n\n
<\/td>\n\n

-\u2212select|\u2212S Selection<\/p>\n<\/td>\n

 <\/td>\n<\/tr>\n<\/table>\n

Define selection criteria for report output. For log report<\/b>, this also overrides log\/command_log_selection configuration setting, see also log report specifics<\/b>.<\/p>\n\n\n
<\/td>\n\n

\u2022<\/p>\n<\/td>\n

<\/td>\n\n

Changing output format and composition<\/p>\n<\/td>\n

 <\/td>\n<\/tr>\n<\/table>\n

\u2212<\/p>\n\n\n
<\/td>\n\n

-\u2212reportformat<\/p>\n<\/td>\n

 <\/td>\n<\/tr>\n<\/table>\n

Overrides report\/output_format configuration setting.<\/p>\n\n\n
<\/td>\n\n

\u2212<\/p>\n<\/td>\n

<\/td>\n\n

-\u2212aligned<\/p>\n<\/td>\n

 <\/td>\n<\/tr>\n<\/table>\n

Overrides report\/aligned configuration setting.<\/p>\n\n\n
<\/td>\n\n

\u2212<\/p>\n<\/td>\n

<\/td>\n\n

-\u2212binary<\/p>\n<\/td>\n

 <\/td>\n<\/tr>\n<\/table>\n

Overrides report\/binary_values_as_numeric configuration setting.<\/p>\n\n\n
<\/td>\n\n

\u2212<\/p>\n<\/td>\n

<\/td>\n\n

-\u2212nameprefixes<\/p>\n<\/td>\n

 <\/td>\n<\/tr>\n<\/table>\n

Overrides report\/prefixes configuration setting.<\/p>\n\n\n
<\/td>\n\n

\u2212<\/p>\n<\/td>\n

<\/td>\n\n

-\u2212noheadings<\/p>\n<\/td>\n

 <\/td>\n<\/tr>\n<\/table>\n

Overrides report\/noheadings configuration setting.<\/p>\n\n\n
<\/td>\n\n

\u2212<\/p>\n<\/td>\n

<\/td>\n\n

-\u2212nosuffix<\/p>\n<\/td>\n

 <\/td>\n<\/tr>\n<\/table>\n

Overrides global\/suffix configuration setting.<\/p>\n\n\n
<\/td>\n\n

\u2212<\/p>\n<\/td>\n

<\/td>\n\n

-\u2212rows<\/p>\n<\/td>\n

 <\/td>\n<\/tr>\n<\/table>\n

Overrides report\/columns_as_rows configuration setting.<\/p>\n\n\n
<\/td>\n\n

\u2212<\/p>\n<\/td>\n

<\/td>\n\n

-\u2212separator<\/p>\n<\/td>\n

 <\/td>\n<\/tr>\n<\/table>\n

Overrides report\/separator configuration setting.<\/p>\n\n\n
<\/td>\n\n

\u2212<\/p>\n<\/td>\n

<\/td>\n\n

-\u2212units<\/p>\n<\/td>\n

 <\/td>\n<\/tr>\n<\/table>\n

Overrides global\/units configuration setting.<\/p>\n\n\n
<\/td>\n\n

\u2212<\/p>\n<\/td>\n

<\/td>\n\n

-\u2212unquoted<\/p>\n<\/td>\n

 <\/td>\n<\/tr>\n<\/table>\n

Overrides report\/quoted configuration setting.<\/p>\n\n\n
<\/td>\n\n

\u2022<\/p>\n<\/td>\n

<\/td>\n\n

Special options<\/p>\n<\/td>\n

 <\/td>\n<\/tr>\n<\/table>\n

\u2212<\/p>\n\n\n
<\/td>\n\n

-\u2212configreport ReportName<\/b><\/p>\n<\/td>\n

 <\/td>\n<\/tr>\n<\/table>\n

This defines the ReportName<\/b> for which any subsequent \u2212o\u2212\u2212columns, -O\u2212\u2212sort or \u2212S\u2212\u2212select applies to. See also main report specifics<\/b> and log report specifics<\/b> for possible ReportName<\/b> values.<\/p>\n\n\n
<\/td>\n\n

\u2212<\/p>\n<\/td>\n

<\/td>\n\n

-\u2212logonly<\/p>\n<\/td>\n

 <\/td>\n<\/tr>\n<\/table>\n

When an LVM command contains both main report<\/b> and log report<\/b>, this option suppresses the main report<\/b> output and it causes the log report<\/b> output to be displayed only.<\/p>\n\n\n
<\/td>\n\n

\u2212<\/p>\n<\/td>\n

<\/td>\n\n

-\u2212unbuffered<\/p>\n<\/td>\n

 <\/td>\n<\/tr>\n<\/table>\n

Overrides report\/bufffered configuration setting.<\/p>\n

The FieldSet<\/b> mentioned in the lists above is a set of field names where each field name is delimited by “,” character. Field set definition, sorting and selection may be repeated on command line (\u2212o+\/\u2212o- includes\/excludes fields to\/from current list, for all the other repeatable options, the last value typed for the option on the command line is used). The Selection<\/b> is a string with selection criteria<\/b>, see also Selection<\/b> paragraph below for more information about constructing these criteria.<\/p>\n

Main report specifics <\/a> <\/h2>\n

The main report<\/b> currently encompasses these distinct subtypes, referenced by their name – ReportName<\/b> as listed below. The command in parenthesis is representative command that uses the main report subtype by default. Each subtype has its own configuration setting for global field set definition as well as sort field definition (listed below each individual ReportName<\/b>):<\/p>\n\n\n
<\/td>\n\n

\u2022<\/p>\n<\/td>\n

<\/td>\n\n

pv<\/b> representing report about Physical Volumes (pvs<\/b>)<\/p>\n<\/td>\n<\/tr>\n<\/table>\n

\u2212<\/p>\n\n\n\n\n
<\/td>\n<\/td>\n<\/td>\n\n

report\/pvs_cols<\/p>\n<\/td>\n

 <\/td>\n<\/tr>\n
<\/td>\n\n

\u2212<\/p>\n<\/td>\n

<\/td>\n\n

report\/pvs_sort<\/p>\n<\/td>\n

 <\/td>\n<\/tr>\n
<\/td>\n\n

\u2022<\/p>\n<\/td>\n

<\/td>\n<\/td>\n <\/td>\n<\/tr>\n<\/table>\n

pvseg<\/b> representing report about Physical Volume Segments (pvs \u2212\u2212segments<\/b>)<\/p>\n\n\n\n\n
<\/td>\n\n

\u2212<\/p>\n<\/td>\n

<\/td>\n\n

report\/pvseg_cols<\/p>\n<\/td>\n

 <\/td>\n<\/tr>\n
<\/td>\n\n

\u2212<\/p>\n<\/td>\n

<\/td>\n\n

report\/pvseg_sort<\/p>\n<\/td>\n

 <\/td>\n<\/tr>\n
<\/td>\n\n

\u2022<\/p>\n<\/td>\n

<\/td>\n<\/td>\n <\/td>\n<\/tr>\n<\/table>\n

vg<\/b> representing report about Volume Groups (vgs<\/b>)<\/p>\n\n\n\n\n
<\/td>\n\n

\u2212<\/p>\n<\/td>\n

<\/td>\n\n

report\/vgs_cols<\/p>\n<\/td>\n

 <\/td>\n<\/tr>\n
<\/td>\n\n

\u2212<\/p>\n<\/td>\n

<\/td>\n\n

report\/vgs_sort<\/p>\n<\/td>\n

 <\/td>\n<\/tr>\n
<\/td>\n\n

\u2022<\/p>\n<\/td>\n

<\/td>\n<\/td>\n <\/td>\n<\/tr>\n<\/table>\n

lv<\/b> representing report about Logical Volumes (lvs<\/b>)<\/p>\n\n\n\n\n
<\/td>\n\n

\u2212<\/p>\n<\/td>\n

<\/td>\n\n

report\/lvs_cols<\/p>\n<\/td>\n

 <\/td>\n<\/tr>\n
<\/td>\n\n

\u2212<\/p>\n<\/td>\n

<\/td>\n\n

report\/lvs_sort<\/p>\n<\/td>\n

 <\/td>\n<\/tr>\n
<\/td>\n\n

\u2022<\/p>\n<\/td>\n

<\/td>\n<\/td>\n <\/td>\n<\/tr>\n<\/table>\n

seg<\/b> representing report about Logical Volume Segments (lvs \u2212\u2212segments<\/b>)<\/p>\n\n\n\n\n
<\/td>\n\n

\u2212<\/p>\n<\/td>\n

<\/td>\n\n

report\/segs_cols<\/p>\n<\/td>\n

 <\/td>\n<\/tr>\n
<\/td>\n\n

\u2212<\/p>\n<\/td>\n

<\/td>\n\n

report\/segs_sort<\/p>\n<\/td>\n

 <\/td>\n<\/tr>\n
<\/td>\n\n

\u2022<\/p>\n<\/td>\n

<\/td>\n<\/td>\n <\/td>\n<\/tr>\n<\/table>\n

full<\/b> representing report combining all of the above as a whole (lvm fullreport<\/b>)<\/p>\n\n\n\n\n\n\n\n\n\n\n\n\n
<\/td>\n\n

\u2212<\/p>\n<\/td>\n

<\/td>\n\n

report\/pvs_cols_full<\/p>\n<\/td>\n

 <\/td>\n<\/tr>\n
<\/td>\n\n

\u2212<\/p>\n<\/td>\n

<\/td>\n\n

report\/pvs_sort_full<\/p>\n<\/td>\n

 <\/td>\n<\/tr>\n
<\/td>\n\n

\u2212<\/p>\n<\/td>\n

<\/td>\n\n

report\/pvsegs_cols_full<\/p>\n<\/td>\n

 <\/td>\n<\/tr>\n
<\/td>\n\n

\u2212<\/p>\n<\/td>\n

<\/td>\n\n

report\/pvseg_sort_full<\/p>\n<\/td>\n

 <\/td>\n<\/tr>\n
<\/td>\n\n

\u2212<\/p>\n<\/td>\n

<\/td>\n\n

report\/vgs_cols_full<\/p>\n<\/td>\n

 <\/td>\n<\/tr>\n
<\/td>\n\n

\u2212<\/p>\n<\/td>\n

<\/td>\n\n

report\/vgs_sort_full<\/p>\n<\/td>\n

 <\/td>\n<\/tr>\n
<\/td>\n\n

\u2212<\/p>\n<\/td>\n

<\/td>\n\n

report\/lvs_cols_full<\/p>\n<\/td>\n

 <\/td>\n<\/tr>\n
<\/td>\n\n

\u2212<\/p>\n<\/td>\n

<\/td>\n\n

report\/lvs_sort_full<\/p>\n<\/td>\n

 <\/td>\n<\/tr>\n
<\/td>\n\n

\u2212<\/p>\n<\/td>\n

<\/td>\n\n

report\/segs_cols_full<\/p>\n<\/td>\n

 <\/td>\n<\/tr>\n
<\/td>\n\n

\u2212<\/p>\n<\/td>\n

<\/td>\n\n

report\/segs_sort_full<\/p>\n<\/td>\n

 <\/td>\n<\/tr>\n
<\/td>\n\n

\u2022<\/p>\n<\/td>\n

<\/td>\n<\/td>\n <\/td>\n<\/tr>\n<\/table>\n

devtype<\/b> representing report about device types (lvm devtypes<\/b>)<\/p>\n\n\n\n
<\/td>\n\n

\u2212<\/p>\n<\/td>\n

<\/td>\n\n

report\/devtypes_cols<\/p>\n<\/td>\n

 <\/td>\n<\/tr>\n
<\/td>\n\n

\u2212<\/p>\n<\/td>\n

<\/td>\n\n

report\/devtypes_sort<\/p>\n<\/td>\n

 <\/td>\n<\/tr>\n<\/table>\n

Use pvs, vgs, lvs \u2212o help<\/b> or lvm devtypes \u2212o help<\/b> to get complete list of fields that you can use for main report. The list of fields in the help output is separated in groups based on which report type they belong to. Note that LVM can change final report type used if fields from different groups are combined together. Some of these combinations are not allowed in which case LVM will issue an error.<\/p>\n

For all main report subtypes except full<\/b>, it\u2019s not necessary to use \u2212\u2212configreport ReportName<\/b> to denote which report any subsequent \u2212o, \u2212O or \u2212S<\/b> option applies to as they always apply to the single main report type. Currently, lvm fullreport<\/b> is the only command that includes more than one main report<\/b> subtype. Therefore, the \u2212\u2212configreport is particularly suitable for the full report if you need to configure each of its subreports in a different way.<\/p>\n

Log report specifics <\/a> <\/h2>\n

You can enable log report with log\/report_command_log<\/b> configuration setting \u2212 this functionality is disabled by default. The log report<\/b> contains a log collected during LVM command execution and then the log is displayed just like any other report known from main report. There is only one log report subtype as shown below together with related configuration settings for fields, sorting and selection:<\/p>\n\n\n
<\/td>\n\n

\u2022<\/p>\n<\/td>\n

<\/td>\n\n

log<\/b> representing log report<\/p>\n<\/td>\n

 <\/td>\n<\/tr>\n<\/table>\n

\u2212<\/p>\n\n\n\n\n
<\/td>\n<\/td>\n<\/td>\n\n

log\/command_log_cols<\/p>\n<\/td>\n

 <\/td>\n<\/tr>\n
<\/td>\n\n

\u2212<\/p>\n<\/td>\n

<\/td>\n\n

log\/command_log_sort<\/p>\n<\/td>\n

 <\/td>\n<\/tr>\n
<\/td>\n\n

\u2212<\/p>\n<\/td>\n

<\/td>\n\n

log\/command_log_selection<\/p>\n<\/td>\n

 <\/td>\n<\/tr>\n<\/table>\n

You always need to use \u2212\u2212configreport log<\/b> together with \u2212o\u2212\u2212options, -O\u2212\u2212sort or \u2212S\u2212\u2212selection<\/b> to override configuration settings directly on command line for log report<\/b>. When compared to main report<\/b>, in addition to usual configuration settings for report fields and sorting, the log report<\/b> has also configuration option for selection – report\/command_log_selection<\/b>. This configuration setting is provided for convenience so it\u2019s not necessary to use \u2212S\u2212\u2212select<\/b> on command line each time an LVM command is executed and we need the same selection criteria to be applied for log report<\/b>. Default selection criteria used for log report<\/b> are log\/command_log_selection=”!(log_type=status && message=success)”<\/b>. This means that, by default, log report<\/b> doesn\u2019t display status messages about successful operation and it displays only rows with error, warning, print-type messages and messages about failure states (for more information, see log report content<\/b> below).<\/p>\n

Log report coverage<\/b>
Currently, when running LVM commands directly (not in LVM shell), the log report covers command\u2019s processing stage<\/b> which is the moment when LVM entities are iterated and processed one by one. It does not cover any command initialization nor command finalization stage. If there is any message issued out of log report\u2019s coverage range, such message goes directly to output, bypassing the log report<\/b>. By default, that is standard error output<\/b> for error and warning messages and standard output<\/b> for common print-like messages.<\/p>\n

When running LVM commands in LVM shell<\/b>, the log report covers the whole LVM command\u2019s execution, including command\u2019s processing<\/b> as well as initialization<\/b> and finalization stage<\/b>. So from this point of view, the log report coverage is complete for executed LVM commands. Note that there are still a few moments when LVM shell needs to initialize itself before it even enters the main loop in which it executes LVM commands. Also, there is a moment when LVM shell<\/b> needs to prepare log report<\/b> properly for next command executed in the shell and then, after the command\u2019s run, the shell needs to display the log report for that recently executed command. If there is a failure or any other message issued during this time, the LVM will bypass log report<\/b> and display messages on output directly.<\/p>\n

For these reasons and for completeness, it\u2019s not possible to rely fully on log report<\/b> as the only indicator of LVM command\u2019s status and the only place where all messages issued during LVM command execution are collected. You always need to check whether the command has not failed out of log report\u2019s range by checking the non-report output too.<\/p>\n

To help with this, LVM can separate output which you can then redirect to any custom file descriptor<\/b> that you prepare before running an LVM command or LVM shell and then you make LVM to use these file descriptors for different kinds of output by defining environment variables with file descriptor numbers. See also LVM_OUT_FD<\/b>, LVM_ERR_FD<\/b> and LVM_REPORT_FD<\/b> environment variable description in lvm<\/b>(8) man page.<\/p>\n

Also note that, by default, reports use the same file descriptor as common print-like messages, which is standard output<\/b>. If you plan to use log report<\/b> in your scripts or any external tool, you should use LVM_OUT_FD<\/b>, LVM_ERR_FD<\/b> and LVM_REPORT_FD<\/b> to separate all output types to different file descriptors. For example, with bash, that would be:<\/p>\n

LVM_OUT_FD=3 LVM_ERR_FD=4 LVM_REPORT_FD=5 3>out_file 4>err_file 5>report_file<\/p>\n

Where the is either direct LVM command or LVM shell. You can collect all three types of output in particular files then.<\/p>\n

Log report content<\/b>
Each item in the log report consists of these set of fields providing various information:<\/p>\n\n\n
<\/td>\n\n

\u2022<\/p>\n<\/td>\n

<\/td>\n\n

Basic information (mandatory):<\/p>\n<\/td>\n

 <\/td>\n<\/tr>\n<\/table>\n

\u2212<\/p>\n\n\n
<\/td>\n\n

log_seq_num<\/p>\n<\/td>\n

 <\/td>\n<\/tr>\n<\/table>\n

Item sequence number. The sequence number is unique for each log item and it increases in the order of the log items as they appeared during LVM command execution.<\/p>\n\n\n
<\/td>\n\n

\u2212<\/p>\n<\/td>\n

<\/td>\n\n

log_type<\/p>\n<\/td>\n

 <\/td>\n<\/tr>\n<\/table>\n

Type of log for the item. Currently, these types are used:<\/p>\n

status<\/b> for any status information that is logged<\/p>\n

print<\/b> for any common message printed while the log is collected<\/p>\n

error<\/b> for any error message printed while the log is collected<\/p>\n

warn<\/b> for any warning message printed while the log is collected<\/p>\n\n\n
<\/td>\n\n

\u2212<\/p>\n<\/td>\n

<\/td>\n\n

log_context<\/p>\n<\/td>\n

 <\/td>\n<\/tr>\n<\/table>\n

Context of the log for the item. Currently, two contexts are identified:<\/p>\n

shell<\/b> for the log collected in the outermost code before and after executing concrete LVM commands<\/p>\n

processing<\/b> for the log collected while processing LVM entities during LVM command execution<\/p>\n\n\n
<\/td>\n\n

\u2022<\/p>\n<\/td>\n

<\/td>\n\n

Message (mandatory):<\/p>\n<\/td>\n

 <\/td>\n<\/tr>\n<\/table>\n

\u2212<\/p>\n\n\n
<\/td>\n\n

log_message<\/p>\n<\/td>\n

 <\/td>\n<\/tr>\n<\/table>\n

Any message associated with current item. For status<\/b> log type, the message contains either success<\/b> or failure<\/b> denoting current state. For print<\/b>, error<\/b> and warn<\/b> log types, the message contains the exact message of that type that got issued.<\/p>\n\n\n
<\/td>\n\n

\u2022<\/p>\n<\/td>\n

<\/td>\n\n

Object information (used only if applicable):<\/p>\n<\/td>\n

 <\/td>\n<\/tr>\n<\/table>\n

\u2212<\/p>\n\n\n
<\/td>\n\n

log_object_type field<\/p>\n<\/td>\n

 <\/td>\n<\/tr>\n<\/table>\n

Type of the object processed. Currently, these object types are recognized:<\/p>\n

cmd<\/b> for command as a whole<\/p>\n

orphan<\/b> for processing group of PVs not in any VG yet<\/p>\n

pv<\/b> for PV processing<\/p>\n

label<\/b> for direct PV label processing (without VG metadata)<\/p>\n

vg<\/b> for VG processing<\/p>\n

lv<\/b> for LV processing<\/p>\n\n\n
<\/td>\n\n

\u2212<\/p>\n<\/td>\n

<\/td>\n\n

log_object_name<\/p>\n<\/td>\n

 <\/td>\n<\/tr>\n<\/table>\n

Name of the object processed.<\/p>\n\n\n
<\/td>\n\n

\u2212<\/p>\n<\/td>\n

<\/td>\n\n

log_object_id<\/p>\n<\/td>\n

 <\/td>\n<\/tr>\n<\/table>\n

ID of the object processed.<\/p>\n\n\n
<\/td>\n\n

\u2212<\/p>\n<\/td>\n

<\/td>\n\n

log_object_group<\/p>\n<\/td>\n

 <\/td>\n<\/tr>\n<\/table>\n

A group where the processed object belongs to.<\/p>\n\n\n
<\/td>\n\n

\u2212<\/p>\n<\/td>\n

<\/td>\n\n

log_object_group_id<\/p>\n<\/td>\n

 <\/td>\n<\/tr>\n<\/table>\n

An ID of a group where the processed object belongs to.<\/p>\n\n\n
<\/td>\n\n

\u2022<\/p>\n<\/td>\n

<\/td>\n\n

Numeric status (used only if applicable)<\/p>\n<\/td>\n

 <\/td>\n<\/tr>\n<\/table>\n

\u2212<\/p>\n\n\n
<\/td>\n\n

log_errno<\/p>\n<\/td>\n

 <\/td>\n<\/tr>\n<\/table>\n

Error number associated with current item.<\/p>\n\n\n
<\/td>\n\n

\u2212<\/p>\n<\/td>\n

<\/td>\n\n

log_ret_code<\/p>\n<\/td>\n

 <\/td>\n<\/tr>\n<\/table>\n

Rreturn code associated with current item.<\/p>\n

You can also run \u2212\u2212configreport log \u2212o help<\/b> to to display complete list of fields that you may use for the log report<\/b>.<\/p>\n

Selection <\/a> <\/h2>\n

Selection is used for a report to display only rows that match selection criteria<\/b>. All rows are displayed with the additional selected<\/b> field (\u2212o selected<\/b>) displaying 1 if the row matches the Selection<\/i> and 0 otherwise. The selection criteria<\/b> are a set of statements<\/b> combined by logical and grouping operators<\/b>. The statement<\/b> consists of a field<\/b> name for which a set of valid values<\/b> is defined using comparison operators<\/b>. For complete list of fields names that you can use in selection, see the output of \u2212S help<\/b>. The help output also contains type of values that each field displays enclosed in brackets.<\/p>\n

List of operators recognized in selection criteria<\/b><\/p>\n\n\n
<\/td>\n\n

\u2022<\/p>\n<\/td>\n

<\/td>\n\n

Comparison operators (cmp_op)<\/p>\n<\/td>\n

 <\/td>\n<\/tr>\n<\/table>\n

=~<\/b> matching regular expression.<\/p>\n

!~<\/b> not matching regular expression.<\/p>\n

=<\/b> equal to.<\/p>\n

!=<\/b> not equal to.<\/p>\n

>=<\/b> greater than or equal to.<\/p>\n

><\/b> greater than<\/p>\n

<=<\/b> less than or equal to.<\/p>\n

<<\/b> less than.<\/p>\n\n\n
<\/td>\n\n

\u2022<\/p>\n<\/td>\n

<\/td>\n\n

Binary logical operators (cmp_log)<\/p>\n<\/td>\n

 <\/td>\n<\/tr>\n<\/table>\n

&&<\/b> all fields must match<\/p>\n

,<\/b> all fields must match<\/p>\n

||<\/b> at least one field must match<\/p>\n

#<\/b> at least one field must match<\/p>\n\n\n
<\/td>\n\n

\u2022<\/p>\n<\/td>\n

<\/td>\n\n

Unary logical operators<\/p>\n<\/td>\n

 <\/td>\n<\/tr>\n<\/table>\n

!<\/b> logical negation<\/p>\n\n\n
<\/td>\n\n

\u2022<\/p>\n<\/td>\n

<\/td>\n\n

Grouping operators<\/p>\n<\/td>\n

 <\/td>\n<\/tr>\n<\/table>\n

(<\/b> left parenthesis<\/p>\n

)<\/b> right parenthesis<\/p>\n

[<\/b> list start<\/p>\n

]<\/b> list end<\/p>\n

{<\/b> list subset start<\/p>\n

}<\/b> list subset end<\/p>\n

Field types and selection operands<\/b>
Field type restricts the set of operators and values that you may use with the field when defining selection criteria. You can see field type for each field if you run \u2212S help<\/b> where you can find the type name enclosed in square brackets. Currently, LVM recognizes these field types in reports:<\/p>\n\n\n\n\n\n\n\n
<\/td>\n\n

\u2022<\/p>\n<\/td>\n

<\/td>\n\n

string<\/b> for set of characters (for each string field type, you can use either string or regular expression \u2212 regex for the value used in selection criteria)<\/p>\n<\/td>\n<\/tr>\n

<\/td>\n\n

\u2022<\/p>\n<\/td>\n

<\/td>\n\n

string list<\/b> for set of strings<\/p>\n<\/td>\n<\/tr>\n

<\/td>\n\n

\u2022<\/p>\n<\/td>\n

<\/td>\n\n

number<\/b> for integer value<\/p>\n<\/td>\n<\/tr>\n

<\/td>\n\n

\u2022<\/p>\n<\/td>\n

<\/td>\n\n

size<\/b> for integer or floating point number with size unit suffix (see also lvcreate<\/b>(8) man page and description for “\u2212L\u2212\u2212size” option for the list of recognized suffixes)<\/p>\n<\/td>\n<\/tr>\n

<\/td>\n\n

\u2022<\/p>\n<\/td>\n

<\/td>\n\n

percent<\/b> for floating point number with or without “%” suffix (e.g. 50 or 50%)<\/p>\n<\/td>\n<\/tr>\n

<\/td>\n\n

\u2022<\/p>\n<\/td>\n

<\/td>\n\n

time<\/b> for time values<\/p>\n<\/td>\n<\/tr>\n<\/table>\n

When using string list<\/b> in selection criteria, there are several ways how LVM can match string list fields from report, depending on what list grouping operator is used and what item separator is used within that set of items. Also, note that order of items does not matter here.<\/p>\n\n\n\n\n
<\/td>\n\n

\u2022<\/p>\n<\/td>\n

<\/td>\n\n

matching the set strictly<\/b> where all items must match \u2212 use [ ], e.g. [“a”,”b”,”c”]<\/p>\n<\/td>\n<\/tr>\n

<\/td>\n\n

\u2022<\/p>\n<\/td>\n

<\/td>\n\n

matching a subset of the set<\/b> \u2212 use { } with “,” or “&&” as item delimiter, e.g. {“a”,”b”,”c”}<\/p>\n<\/td>\n<\/tr>\n

<\/td>\n\n

\u2022<\/p>\n<\/td>\n

<\/td>\n\n

matching an intersection with the set<\/b> \u2212 use { } with “#” or “||” as item delimiter, e.g. {“a” || “b” || “c”}<\/p>\n<\/td>\n<\/tr>\n<\/table>\n

When using time<\/b> in your selection criteria, LVM can recognize various time formats using standard, absolute or freeform expressions. For examples demonstrating time expressions in selection criteria, see EXAMPLES<\/b> section.<\/p>\n\n\n
<\/td>\n\n

\u2022<\/p>\n<\/td>\n

<\/td>\n\n

Standard time format<\/b><\/p>\n<\/td>\n

 <\/td>\n<\/tr>\n<\/table>\n

\u2212<\/p>\n\n\n
<\/td>\n\n

date<\/p>\n<\/td>\n

 <\/td>\n<\/tr>\n<\/table>\n

YYYY-MM\u2212DD<\/p>\n

YYYY-MM, auto DD=1<\/p>\n

YYYY, auto MM=01 and DD=01<\/p>\n\n\n
<\/td>\n\n

\u2212<\/p>\n<\/td>\n

<\/td>\n\n

time<\/p>\n<\/td>\n

 <\/td>\n<\/tr>\n<\/table>\n

hh:mm:ss<\/p>\n

hh:mm, auto ss=0<\/p>\n

hh, auto mm=0, auto ss=0<\/p>\n\n\n
<\/td>\n\n

\u2212<\/p>\n<\/td>\n

<\/td>\n\n

timezone<\/p>\n<\/td>\n

 <\/td>\n<\/tr>\n<\/table>\n

+hh:mm or \u2212hh:mm<\/p>\n

+hh or \u2212hh<\/p>\n

The full date\/time specification is YYYY-MM\u2212DD hh:mm:ss. Users are able to leave date\/time parts from right to left. Whenever these parts are left out, a range is assumed automatically with second granularity. For example:<\/p>\n

“2015-07-07 9:51” means range of “2015-07-07 9:51:00” – “2015-07-07 9:51:59”.<\/p>\n

“2015\u221207” means range of “2015-07-01 0:00:00” – “2015-07-31 23:59:59”<\/p>\n

“2015” means range of “2015-01-01 0:00:00” – “2015-12-31 23:59:59”<\/p>\n\n\n
<\/td>\n\n

\u2022<\/p>\n<\/td>\n

<\/td>\n\n

Absolute time format<\/b><\/p>\n<\/td>\n

 <\/td>\n<\/tr>\n<\/table>\n

Absolute time is defined as number of seconds since the Epoch (1970:01:01 00:00 +00:00).<\/p>\n\n\n\n
<\/td>\n\n

\u2212<\/p>\n<\/td>\n

<\/td>\n\n

@seconds<\/p>\n<\/td>\n

 <\/td>\n<\/tr>\n
<\/td>\n\n

\u2022<\/p>\n<\/td>\n

<\/td>\n<\/td>\n <\/td>\n<\/tr>\n<\/table>\n

Freeform time format<\/b><\/p>\n\n\n\n\n\n
<\/td>\n\n

\u2212<\/p>\n<\/td>\n

<\/td>\n\n

weekday names (“Sunday” – “Saturday” or abbreviated as “Sun” – “Sat”)<\/p>\n<\/td>\n<\/tr>\n

<\/td>\n\n

\u2212<\/p>\n<\/td>\n

<\/td>\n\n

labels for points in time (“noon”, “midnight”)<\/p>\n<\/td>\n<\/tr>\n

<\/td>\n\n

\u2212<\/p>\n<\/td>\n

<\/td>\n\n

labels for a day relative to current day (“today”, “yesterday”)<\/p>\n<\/td>\n<\/tr>\n

<\/td>\n\n

\u2212<\/p>\n<\/td>\n

<\/td>\n\n

points back in time with relative offset from today (N is a number)<\/p>\n<\/td>\n<\/tr>\n<\/table>\n

“N” “seconds” \/ “minutes” \/ “hours” \/ “days” \/ “weeks” \/ “years” “ago”<\/p>\n

“N” “secs” \/ “mins” \/ “hrs” … “ago”<\/p>\n

“N” “s” \/ “m” \/ “h” … “ago”<\/p>\n\n\n\n
<\/td>\n\n

\u2212<\/p>\n<\/td>\n

<\/td>\n\n

time specification either in hh:mm:ss format or with AM\/PM suffixes<\/p>\n<\/td>\n<\/tr>\n

<\/td>\n\n

\u2212<\/p>\n<\/td>\n

<\/td>\n\n

month names (“January” – “December” or abbreviated as “Jan” – “Dec”)<\/p>\n<\/td>\n<\/tr>\n<\/table>\n

Informal grammar specification<\/b><\/p>\n

STATEMENT<\/b> = column<\/b> cmp_op VALUE<\/b> | STATEMENT<\/b> log_op STATEMENT<\/b> | (STATEMENT)<\/b> | !(STATEMENT)<\/b><\/p>\n

VALUE<\/b> = [VALUE<\/b> log_op VALUE]<\/b>
For list-based types: string list. Matches strictly. The log_op must always be of one type within the whole list value.<\/p>\n

VALUE<\/b> = {VALUE<\/b> log_op VALUE}<\/b>
For list-based types: string list. Matches a subset. The log_op must always be of one type within the whole list value.<\/p>\n

VALUE<\/b> = value<\/b>
For scalar types: number, size, percent, string (or string regex).<\/p>\n

EXAMPLES <\/a> <\/h2>\n

Basic usage<\/b>
We start our examples with default configuration – lvmconfig<\/b>(8) is helpful command to display configuration settings which are currently used, including all configuration related to reporting. We will use it throughout examples below to display current configuration.<\/p>\n

# lvmconfig \u2212\u2212type full global\/units global\/suffix
report\/output_format report\/compact_output
report\/compact_output_cols report\/aligned
report\/headings report\/separator
report\/list_item_separator report\/prefixes
report\/quoted report\/columns_as_rows
report\/binary_values_as_numeric report\/time_format
report\/mark_hidden_devices report\/two_word_unknown_device
report\/buffered
units=”h”
suffix=1
output_format=”basic”
compact_output=0
compact_output_cols=””
aligned=1
headings=1
separator=” ”
list_item_separator=”,”
prefixes=0
quoted=1
columns_as_rows=0
binary_values_as_numeric=0
time_format=”%Y-%m-%d %T %z”
mark_hidden_devices=1
two_word_unknown_device=0
buffered=1<\/p>\n

Also, we start with simple LVM layout with two PVs (\/dev\/sda, \/dev\/sdb), VG (vg) and two LVs (lvol0 and lvol1) in the VG. We display all possible reports as single commands here, see also pvs<\/b>(8), vgs<\/b>(8), lvs<\/b>(8) man pages for more information. The field set for each report type is configured with configuration settings as we already mentioned in main report specifics<\/b> section in this man page.<\/p>\n

# lvmconfig \u2212\u2212type full report\/pvs_cols report\/pvs_sort
report\/pvsegs_cols report\/pvsegs_sort report\/vgs_cols
report\/vgs_sort report\/lvs_cols report\/lvs_sort
report\/segs_cols report\/segs_sort
pvs_cols=”pv_name,vg_name,pv_fmt,pv_attr,pv_size,pv_free”
pvs_sort=”pv_name”
pvsegs_cols=”pv_name,vg_name,pv_fmt,pv_attr,pv_size,pv_free,
pvseg_start,pvseg_size”
pvsegs_sort=”pv_name,pvseg_start”
vgs_cols=”vg_name,pv_count,lv_count,snap_count,vg_attr,vg_size,vg_free”
vgs_sort=”vg_name”
lvs_cols=”lv_name,vg_name,lv_attr,lv_size,pool_lv,origin,move_pv,
mirror_log,copy_percent,convert_lv”
lvs_sort=”vg_name,lv_name”
segs_cols=”lv_name,vg_name,lv_attr,stripes,segtype,seg_size”
segs_sort=”vg_name,lv_name,seg_start”<\/p>\n

# pvs
PV VG Fmt Attr PSize PFree
\/dev\/sda vg lvm2 a\u2212\u2212 100.00m 88.00m
\/dev\/sdb vg lvm2 a\u2212\u2212 100.00m 92.00m<\/p>\n

# pvs \u2212\u2212segments
PV VG Fmt Attr PSize PFree Start SSize
\/dev\/sda vg lvm2 a\u2212\u2212 100.00m 88.00m 0 1
\/dev\/sda vg lvm2 a\u2212\u2212 100.00m 88.00m 1 1
\/dev\/sda vg lvm2 a\u2212\u2212 100.00m 88.00m 2 1
\/dev\/sda vg lvm2 a\u2212\u2212 100.00m 88.00m 3 22
\/dev\/sdb vg lvm2 a\u2212\u2212 100.00m 92.00m 0 1
\/dev\/sdb vg lvm2 a\u2212\u2212 100.00m 92.00m 1 1
\/dev\/sdb vg lvm2 a\u2212\u2212 100.00m 92.00m 2 23<\/p>\n

# vgs
VG #PV #LV #SN Attr VSize VFree
vg 2 2 0 wz\u2212\u2212n- 200.00m 180.00m<\/p>\n

# lvs
LV VG Attr LSize Pool Origin Move Log Cpy%Sync Convert
lvol0 vg \u2212wi\u2212a\u2212\u2212\u2212\u2212\u2212 4.00m
lvol1 vg rwi\u2212a-r\u2212\u2212\u2212 4.00m 100.00<\/p>\n

# lvs \u2212\u2212segments
LV VG Attr #Str Type SSize
lvol0 vg \u2212wi\u2212a\u2212\u2212\u2212\u2212\u2212 1 linear 4.00m
lvol1 vg rwi\u2212a-r\u2212\u2212\u2212 2 raid1 4.00m<\/p>\n

We will use report\/lvs_cols<\/b> and report\/lvs_sort<\/b> configuration settings to define our own list of fields to use and to sort by that is different from defaults. You can do this for other reports in same manner with report\/{pvs,pvseg,vgs,seg}_{cols,sort}<\/b> configuration settings. Also note that in the example below, we don\u2019t display the “lv_time” field even though we\u2019re using it for sorting \u2212 this is allowed.<\/p>\n

# lvmconfig \u2212\u2212type full report\/lvs_cols report\/lvs_sort
lvs_cols=”lv_name,lv_size,origin,pool_lv,copy_percent”
lvs_sort=”\u2212lv_time”<\/p>\n

# lvs
LV LSize Origin Pool Cpy%Sync
lvol1 4.00m 100.00
lvol0 4.00m<\/p>\n

You can use \u2212o\u2212\u2212options<\/b> command line option to override current configuration directly on command line.<\/p>\n

# lvs \u2212o lv_name,lv_size
LV LSize
lvol1 4.00m
lvol0 4.00m<\/p>\n

# lvs \u2212o+lv_layout
LV LSize Origin Pool Cpy%Sync Layout
lvol1 4.00m 100.00 raid,raid1
lvol0 4.00m linear<\/p>\n

# lvs \u2212o-origin
LV LSize Pool Cpy%Sync
lvol1 4.00m 100.00
lvol0 4.00m<\/p>\n

# lvs \u2212o lv_name,lv_size,origin \u2212o+lv_layout \u2212o-origin \u2212O lv_name
LV LSize Layout
lvol0 4.00m linear
lvol1 4.00m raid,raid1<\/p>\n

You can obtain the same information with single command where all the information about PVs, PV segments, LVs and LV segments are obtained per VG under a single VG lock for consistency, see also lvm-fullreport<\/b>(8) man page for more information. The fullreport has its own configuration settings to define field sets to use, similar to individual reports as displayed above, but configuration settings have “_full” suffix now. This way, it\u2019s possible to configure different sets of fields to display and to sort by for individual reports as well as the full report.<\/p>\n

# lvmconfig \u2212\u2212type full report\/pvs_cols_full
report\/pvs_sort_full report\/pvsegs_cols_full
report\/pvsegs_sort_full report\/vgs_cols_full
report\/vgs_sort_full report\/lvs_cols_full
report\/lvs_sort_full report\/segs_cols_full
report\/segs_sort_full
pvs_cols_full=”pv_name,vg_name”
pvs_sort_full=”pv_name”
pvsegs_cols_full=”pv_name,pvseg_start,pvseg_size”
pvsegs_sort_full=”pv_uuid,pvseg_start”
vgs_cols_full=”vg_name”
vgs_sort_full=”vg_name”
lvs_cols_full=”lv_name,vg_name”
lvs_sort_full=”vg_name,lv_name”
segs_cols_full=”lv_name,seg_start,seg_size”
segs_sort_full=”lv_uuid,seg_start”<\/p>\n

# lvm fullreport
VG
vg
PV VG
\/dev\/sda vg
\/dev\/sdb vg
LV VG
lvol0 vg
lvol1 vg
PV Start SSize
\/dev\/sda 0 1
\/dev\/sda 1 1
\/dev\/sda 2 1
\/dev\/sda 3 22
\/dev\/sdb 0 1
\/dev\/sdb 1 1
\/dev\/sdb 2 23
LV Start SSize
lvol0 0 4.00m
lvol1 0 4.00m<\/p>\n

Automatic output compaction<\/b>
If you look at the lvs output above, you can see that the report also contains fields for which there is no information to display (e.g. the columns under “Origin” and “Pool” heading \u2212 the “origin” and “pool_lv” fields). LVM can automatically compact report output so such fields are not included in final output. To enable this feature and to compact all fields, use report\/compact_output=1<\/b> in your configuration.<\/p>\n

# lvmconfig \u2212\u2212type full report\/compact_output
compact_output=1<\/p>\n

# lvs
LV LSize Cpy%Sync
lvol1 4.00m 100.00
lvol0 4.00m<\/p>\n

# lvs vg\/lvol0
LV LSize
lvol0 4.00m<\/p>\n

Alternatively, you can define which fields should be compacted by configuring report\/compact_output_cols<\/b> configuration setting (or \u2212o\u2212\u2212options #<\/b> command line option).<\/p>\n

# lvmconfig \u2212\u2212type full report\/compact_output report\/compact_output_cols
compact_output=0
compact_output_cols=”origin”<\/p>\n

# lvs
LV LSize Pool Cpy%Sync
lvol1 4.00m 100.00
lvol0 4.00m<\/p>\n

# lvs vg\/lvol0
LV LSize Pool
lvol0 4.00m<\/p>\n

# lvs \u2212o#pool_lv
LV LSize Origin Cpy%Sync
lvol1 4.00m 100.00
lvol0 4.00m<\/p>\n

We will use report\/compact_output=1<\/b> for subsequent examples.<\/p>\n

Further formatting options<\/b>
By default, LVM displays sizes in reports in human-readable form which means that the most suitable unit is used so it\u2019s easy to read. You can use report\/units<\/b> configuration setting (or \u2212\u2212units<\/b> option directly on command line) and report\/suffix<\/b> configuration setting (or \u2212\u2212nosuffix<\/b> command line option) to change this.<\/p>\n

# lvs \u2212\u2212units b \u2212\u2212nosuffix
LV LSize Cpy%Sync
lvol1 4194304 100.00
lvol0 4194304<\/p>\n

If you want to configure whether report headings are displayed or not, use report\/headings<\/b> configuration settings (or \u2212\u2212noheadings<\/b> command line option).<\/p>\n

# lvs \u2212\u2212noheadings
lvol1 4.00m 100.00
lvol0 4.00m<\/p>\n

In some cases, it may be useful to display report content as key=value pairs where key here is actually the field name. Use report\/prefixes<\/b> configuration setting (or \u2212\u2212nameprefixes<\/b> command line option) to switch between standard output and the key=value output. The key=value pair is the output that is suitable for use in scripts and for other tools to parse easily. Usually, you also don\u2019t want to display headings with the output that has these key=value pairs.<\/p>\n

# lvs \u2212\u2212noheadings \u2212\u2212nameprefixes
LVM2_LV_NAME=\u2019lvol1\u2019 LVM2_LV_SIZE=\u20194.00m\u2019 LVM2_COPY_PERCENT=\u2019100.00\u2019
LVM2_LV_NAME=\u2019lvol0\u2019 LVM2_LV_SIZE=\u20194.00m\u2019 LVM2_COPY_PERCENT=\u2019\u2019<\/p>\n

To define whether quotation marks in key=value pairs should be used or not, use report\/quoted<\/b> configuration setting (or \u2212\u2212unquoted<\/b> command line option).<\/p>\n

# lvs \u2212\u2212noheadings \u2212\u2212nameprefixes \u2212\u2212unquoted
LVM2_LV_NAME=lvol1 LVM2_LV_SIZE=4.00m LVM2_COPY_PERCENT=100.00
LVM2_LV_NAME=lvol0 LVM2_LV_SIZE=4.00m LVM2_COPY_PERCENT=<\/p>\n

For easier parsing, you can even transpose the report so each column now becomes a row in the output. This is done with report\/output_as_rows<\/b> configuration setting (or \u2212\u2212rows<\/b> command line option).<\/p>\n

# lvs \u2212\u2212noheadings \u2212\u2212nameprefixes \u2212\u2212unquoted \u2212\u2212rows
LVM2_LV_NAME=lvol1 LVM2_LV_NAME=lvol0
LVM2_LV_SIZE=4.00m LVM2_LV_SIZE=4.00m
LVM2_COPY_PERCENT=100.00 LVM2_COPY_PERCENT=<\/p>\n

Use report\/separator<\/b> configuration setting (or \u2212\u2212separator<\/b> command line option) to define your own field separator to use.<\/p>\n

# lvs \u2212\u2212noheadings \u2212\u2212nameprefixes \u2212\u2212unquoted \u2212\u2212separator ” | ”
LVM2_LV_NAME=lvol1 | LVM2_LV_SIZE=4.00m | LVM2_COPY_PERCENT=100.00
LVM2_LV_NAME=lvol0 | LVM2_LV_SIZE=4.00m | LVM2_COPY_PERCENT=<\/p>\n

If you are using your own separator, the columns in the output are not aligned by default. Use report\/aligned<\/b> configuration setting (or \u2212\u2212aligned<\/b> command line option) for LVM to add extra spaces in report to align the output properly.<\/p>\n

# lvs \u2212\u2212separator ” | ”
LV | LSize | Cpy%Sync
lvol1 | 4.00m | 100.00
lvol0 | 4.00m |<\/p>\n

# lvs \u2212\u2212separator ” | ” \u2212\u2212aligned
LV | LSize | Cpy%Sync
lvol1 | 4.00m | 100.00
lvol0 | 4.00m |<\/p>\n

Let\u2019s display one one more field in addition (“lv_tags” in this example) for the lvs report output.<\/p>\n

# lvs \u2212o+lv_tags
LV LSize Cpy%Sync LV Tags
lvol1 4.00m 100.00
lvol0 4.00m tagA,tagB<\/p>\n

The “LV Tags” column in the example above displays two list values, separated by “,” character for LV lvol0. If you need different list item separator, use report\/list_item_separator<\/b> configuration setting its definition.<\/p>\n

# lvmconfig \u2212\u2212type full report\/list_item_separator
list_item_separator=”;”<\/p>\n

# lvs \u2212o+tags
LV LSize Cpy%Sync LV Tags
lvol1 4.00m 100.00
lvol0 4.00m tagA;tagB<\/p>\n

But let\u2019s still use the original “,” character for list_item_separator for subsequent examples.<\/p>\n

Format for any of time values displayed in reports can be configured with report\/time_format<\/b> configuretion setting. By default complete date and time is displayed, including timezone.<\/p>\n

# lvmconfig \u2212\u2212type full report\/time_format
time_format=”%Y-%m-%d %T %z”<\/p>\n

# lvs \u2212o+time
LV LSize Cpy%Sync CTime
lvol1 4.00m 100.00 2016-08-29 12:53:36 +0200
lvol0 4.00m 2016-08-29 10:15:17 +0200<\/p>\n

We can change time format in similar way as we do when using date<\/b>(1) command or strftime<\/b>(3) function (lvmconfig \u2212\u2212type default \u2212\u2212withcomments report\/time_format<\/b> will give you complete list of available formatting options). In the example below, we decided to use %s for number of seconds since Epoch (1970-01-01 UTC).<\/p>\n

# lvmconfig \u2212\u2212type full report\/time_format
time_format=”%s”<\/p>\n

# lvs
LV Attr LSize Cpy%Sync LV Tags CTime
lvol1 rwi\u2212a-r\u2212\u2212\u2212 4.00m 100.00 1472468016
lvol0 \u2212wi\u2212a\u2212\u2212\u2212\u2212\u2212 4.00m tagA,tagB 1472458517<\/p>\n

The lvs<\/b> does not display hidden LVs by default \u2212 to include these LVs in the output, you need to use \u2212a\u2212\u2212all<\/b> command line option. Names for these hidden LVs are displayed within square brackets.<\/p>\n

# lvs \u2212a
LV LSize Cpy%Sync
lvol1 4.00m 100.00
[lvol1_rimage_0] 4.00m
[lvol1_rmeta_0] 4.00m
[lvol1_rimage_1] 4.00m
[lvol1_rmeta_1] 4.00m
lvol0 4.00m<\/p>\n

You can configure LVM to display the square brackets for hidden LVs or not with report\/mark_hidden_devices<\/b> configuration setting.<\/p>\n

# lvmconfig \u2212\u2212type full report\/mark_hidden_devices
mark_hidden_devices=0<\/p>\n

# lvs \u2212a
LV LSize Cpy%Sync
lvol1 4.00m 100.00
lvol1_rimage_0 4.00m
lvol1_rmeta_0 4.00m
lvol1_rimage_1 4.00m
lvol1_rmeta_1 4.00m
lvol0 4.00m<\/p>\n

It\u2019s not recommended to use LV marks for hidden devices to decide whether the LV is the one to use by end users or not. Please, use “lv_role” field instead which can report whether the LV is “public” or “private”. The private LVs are used by LVM only and they should not be accessed directly by end users.<\/p>\n

# lvs \u2212a \u2212o+lv_role
LV LSize Cpy%Sync Role
lvol1 4.00m 100.00 public
lvol1_rimage_0 4.00m private,raid,image
lvol1_rmeta_0 4.00m private,raid,metadata
lvol1_rimage_1 4.00m private,raid,image
lvol1_rmeta_1 4.00m private,raid,metadata
lvol0 4.00m public<\/p>\n

Some of the reporting fields that LVM reports are of binary nature. For such fields, it\u2019s either possible to display word representation of the value (this is used by default) or numeric value (0\/1 or \u22121 in case the value is undefined).<\/p>\n

# lvs \u2212o+lv_active_locally
LV LSize Cpy%Sync ActLocal
lvol1 4.00m 100.00 active locally
lvol0 4.00m active locally<\/p>\n

We can change the way how these binary values are displayed with report\/binary_values_as_numeric<\/b> configuration setting.<\/p>\n

# lvmconfig \u2212\u2212type full report\/binary_values_as_numeric
binary_values_as_numeric=1<\/p>\n

# lvs \u2212o+lv_active_locally
LV LSize Cpy%Sync ActLocal
lvol1 4.00m 100.00 1
lvol0 4.00m 1<\/p>\n

Changing output format<\/b>
LVM can output reports in different formats \u2212 use report\/output_format<\/b> configuration setting (or \u2212\u2212reportformat<\/b> command line option) to swith the report output format. Currently, LVM supports “basic”<\/b> (all the examples we used above used this format) and “JSON”<\/b> output format.<\/p>\n

# lvs \u2212o lv_name,lv_size \u2212\u2212reportformat json
{
“report”: [
{
“lv”: [
{“lv_name”:”lvol1″, “lv_size”:”4.00m”},
{“lv_name”:”lvol0″, “lv_size”:”4.00m”}
]
}
]
}<\/p>\n

Note that some configuration settings and command line options have no effect with certain report formats. For example, with JSON<\/b> output, it doesn\u2019t have any meaning to use report\/aligned<\/b> (\u2212\u2212aligned<\/b>), report\/noheadings<\/b> (\u2212\u2212noheadings<\/b>), report\/columns_as_rows<\/b> (\u2212\u2212rows<\/b>) or report\/buffered<\/b> (\u2212\u2212unbuffered<\/b>). All these configuration settings and command line options are ignored if using the JSON<\/b> report output format.<\/p>\n

Selection<\/b>
If you need to select only specific rows from report, you can use LVM\u2019s report selection feature. If you call \u2212S help<\/b>, you\u2019ll get quick help on selection. The help contains list of all fields that LVM can use in reports together with its type enclosed in square brackets. The example below contains a line from lvs \u2212S help.<\/p>\n

# lvs \u2212S help
…
lv_size – Size of LV in current units. [size]
…<\/p>\n

This line tells you you that the “lv_size” field is of “size” type. If you look at the bottom of the help output, you can see section about “Selection operators” and its “Comparison operators”.<\/p>\n

# lvs \u2212S help
…
Selection operators
\u2212\u2212—————–
Comparison operators:
=~ – Matching regular expression. [regex]
!~ – Not matching regular expression. [regex]
= – Equal to. [number, size, percent, string, string list, time]
!= – Not equal to. [number, size, percent, string, string_list, time]
>= – Greater than or equal to. [number, size, percent, time]
> – Greater than. [number, size, percent, time]
<= - Less than or equal to. [number, size, percent, time]
< - Less than. [number, size, percent, time]
since – Since specified time (same as \u2019>=\u2019). [time]
after – After specified time (same as \u2019>\u2019). [time]
until – Until specified time (same as \u2019<=\u2019). [time]
before – Before specified time (same as \u2019<\u2019). [time]
…<\/p>\n

Here you can match comparison operators that you may use with the “lv_size” field which is of type “size” – it\u2019s =, !=, >=, >, <= and <. You can find applicable comparison operators for other fields and other field types the same way.<\/p>\n

To demostrate selection functionality in LVM, we will create more LVs in addition to lvol0 and lvol1 we used in our previous examples.<\/p>\n

# lvs \u2212o name,size,origin,snap_percent,tags,time
LV LSize Origin Snap% LV Tags CTime
lvol4 4.00m lvol2 24.61 2016-09-09 16:57:44 +0200
lvol3 4.00m lvol2 5.08 2016-09-09 16:56:48 +0200
lvol2 8.00m tagA,tagC,tagD 2016-09-09 16:55:12 +0200
lvol1 4.00m 2016-08-29 12:53:36 +0200
lvol0 4.00m tagA,tagB 2016-08-29 10:15:17 +0200<\/p>\n

When selecting size and percent fields, we don\u2019t need to use units. For sizes, default “m” (for MiB) is used \u2212 this is the same behaviour as already used for LVM commands when specifying sizes (e.g. lvcreate \u2212L). For percent fields, “%” is assumed automatically if it\u2019s not specified. The example below also demonstrates how several criteria can be combined together.<\/p>\n

# lvs \u2212o name,size,snap_percent \u2212S \u2019size=8m\u2019
LV LSize
lvol2 8.00m<\/p>\n

# lvs \u2212o name,size,snap_percent \u2212S \u2019size=8\u2019
LV LSize
lvol2 8.00m<\/p>\n

# lvs \u2212o name,size,snap_percent \u2212S \u2019size < 5000k\u2019
LV LSize Snap%
lvol4 4.00m 24.61
lvol3 4.00m 5.08
lvol1 4.00m
lvol0 4.00m<\/p>\n

# lvs \u2212o name,size,snap_percent \u2212S \u2019size < 5000k && snap_percent > 20\u2019
LV LSize Snap%
lvol4 4.00m 24.61<\/p>\n

# lvs \u2212o name,size,snap_percent
\u2212S \u2019(size < 5000k && snap_percent > 20%) || name=lvol2\u2019
LV LSize Snap%
lvol4 4.00m 24.61
lvol2 8.00m<\/p>\n

You can also use selection together with processing-oriented commands.<\/p>\n

# lvchange \u2212\u2212addtag test \u2212S \u2019size < 5000k\u2019
Logical volume vg\/lvol1 changed.
Logical volume vg\/lvol0 changed.
Logical volume vg\/lvol3 changed.
Logical volume vg\/lvol4 changed.<\/p>\n

# lvchange \u2212\u2212deltag test \u2212S \u2019tags = test\u2019
Logical volume vg\/lvol1 changed.
Logical volume vg\/lvol0 changed.
Logical volume vg\/lvol3 changed.
Logical volume vg\/lvol4 changed.<\/p>\n

LVM can recognize more complex values used in selection criteria for string list and time field types. For string lists, you can match whole list strictly, its subset or intersection. Let\u2019s take “lv_tags” field as an example \u2212 we select only rows which contain “tagA” within tags field. We\u2019re using { } to denote that we\u2019re interested in subset that matches. If the subset has only one item, we can leave out { }.<\/p>\n

# lvs \u2212o name,tags \u2212S \u2019tags={tagA}\u2019
LV LV Tags
lvol2 tagA,tagC,tagD
lvol0 tagA,tagB<\/p>\n

# lvs \u2212o name,tags \u2212S \u2019tags=tagA\u2019
LV LV Tags
lvol2 tagA,tagC,tagD
lvol0 tagA,tagB<\/p>\n

Depending on whether we use “&&” (or “,”) or “||” ( or “#”) as delimiter for items in the set we define in selection criterion for string list, we either match subset (“&&” or “,”) or even intersection (“||” or “#”).<\/p>\n

# lvs \u2212o name,tags \u2212S \u2019tags={tagA,tagC,tagD}\u2019
LV LV Tags
lvol2 tagA,tagC,tagD<\/p>\n

# lvs \u2212o name,tags \u2212S \u2019tags={tagA || tagC || tagD}\u2019
LV LV Tags
lvol2 tagA,tagC,tagD
lvol0 tagA,tagB<\/p>\n

To match the complete set, use [ ] with “&&” (or “,”) as delimiter for items. Also note that the order in which we define items in the set is not relevant.<\/p>\n

# lvs \u2212o name,tags \u2212S \u2019tags=[tagA]\u2019<\/p>\n

# lvs \u2212o name,tags \u2212S \u2019tags=[tagB,tagA]\u2019
LV LV Tags
lvol0 tagA,tagB<\/p>\n

If you use [ ] with “||” (or “#”), this is exactly the same as using { }.<\/p>\n

# lvs \u2212o name,tags \u2212S \u2019tags=[tagA || tagC || tagD]\u2019
LV LV Tags
lvol2 tagA,tagC,tagD
lvol0 tagA,tagB<\/p>\n

To match a set with no items, use “” to denote this (note that we have output compaction enabled so the “LV Tags” column is not displayed in the example below because it\u2019s blank and so it gets compacted).<\/p>\n

# lvs \u2212o name,tags \u2212S \u2019tags=””\u2019
LV
lvol4
lvol3
lvol1<\/p>\n

# lvs \u2212o name,tags \u2212S \u2019tags!=””\u2019
LV LV Tags
lvol2 tagA,tagC,tagD
lvol0 tagA,tagB<\/p>\n

When doing selection based on time fields, we can use either standard, absolute or freeform time expressions in selection criteria. Examples below are using standard forms.<\/p>\n

# lvs \u2212o name,time
LV CTime
lvol4 2016-09-09 16:57:44 +0200
lvol3 2016-09-09 16:56:48 +0200
lvol2 2016-09-09 16:55:12 +0200
lvol1 2016-08-29 12:53:36 +0200
lvol0 2016-08-29 10:15:17 +0200<\/p>\n

# lvs \u2212o name,time \u2212S \u2019time since “2016-09-01″\u2019
LV CTime
lvol4 2016-09-09 16:57:44 +0200
lvol3 2016-09-09 16:56:48 +0200
lvol2 2016-09-09 16:55:12 +0200<\/p>\n

# lvs \u2212o name,time \u2212S \u2019time since “2016-09-09 16:56″\u2019
LV CTime
lvol4 2016-09-09 16:57:44 +0200
lvol3 2016-09-09 16:56:48 +0200<\/p>\n

# lvs \u2212o name,time \u2212S \u2019time since “2016-09-09 16:57:30″\u2019
LV CTime
lvol4 2016-09-09 16:57:44 +0200<\/p>\n

# lvs \u2212o name,time
\u2212S \u2019time since “2016-08-29” && time until “2016-09-09 16:55:12″\u2019
LV CTime
lvol2 2016-09-09 16:55:12 +0200
lvol1 2016-08-29 12:53:36 +0200
lvol0 2016-08-29 10:15:17 +0200<\/p>\n

# lvs \u2212o name,time
\u2212S \u2019time since “2016-08-29” && time before “2016-09-09 16:55:12″\u2019
LV CTime
lvol1 2016-08-29 12:53:36 +0200
lvol0 2016-08-29 10:15:17 +0200<\/p>\n

Time operators have synonyms: “>=” for since, “<=\" for until, \">” for “after” and “<\" for \"before\".<\/p>\n

# lvs \u2212o name,time
\u2212S \u2019time >= “2016-08-29” && time <= \"2016-09-09 16:55:30\"\u2019
LV CTime
lvol2 2016-09-09 16:55:12 +0200
lvol1 2016-08-29 12:53:36 +0200
lvol0 2016-08-29 10:15:17 +0200<\/p>\n

# lvs \u2212o name,time
\u2212S \u2019time since “2016-08-29” && time < \"2016-09-09 16:55:12\"\u2019
LV CTime
lvol1 2016-08-29 12:53:36 +0200
lvol0 2016-08-29 10:15:17 +0200<\/p>\n

Example below demonstrates using absolute time expression.<\/p>\n

# lvs \u2212o name,time \u2212\u2212config report\/time_format=”%s”
LV CTime
lvol4 1473433064
lvol3 1473433008
lvol2 1473432912
lvol1 1472468016
lvol0 1472458517<\/p>\n

# lvs \u2212o name,time \u2212S \u2019time since @1473433008\u2019
LV CTime
lvol4 2016-09-09 16:57:44 +0200
lvol3 2016-09-09 16:56:48 +0200<\/p>\n

Examples below demonstrates using freeform time expressions.<\/p>\n

# lvs \u2212o name,time \u2212S \u2019time since “2 weeks ago”\u2019
LV CTime
lvol4 2016-09-09 16:57:44 +0200
lvol3 2016-09-09 16:56:48 +0200
lvol2 2016-09-09 16:55:12 +0200
lvol1 2016-08-29 12:53:36 +0200
lvol0 2016-08-29 10:15:17 +0200<\/p>\n

# lvs \u2212o name,time \u2212S \u2019time since “1 week ago”\u2019
LV CTime
lvol4 2016-09-09 16:57:44 +0200
lvol3 2016-09-09 16:56:48 +0200
lvol2 2016-09-09 16:55:12 +0200<\/p>\n

# lvs \u2212o name,time \u2212S \u2019time since “2 weeks ago”\u2019
LV CTime
lvol1 2016-08-29 12:53:36 +0200
lvol0 2016-08-29 10:15:17 +0200<\/p>\n

# lvs \u2212o name,time \u2212S \u2019time before “1 week ago”\u2019
LV CTime
lvol1 2016-08-29 12:53:36 +0200
lvol0 2016-08-29 10:15:17 +0200<\/p>\n

# lvs \u2212o name,time \u2212S \u2019time since “68 hours ago”\u2019
LV CTime
lvol4 2016-09-09 16:57:44 +0200
lvol3 2016-09-09 16:56:48 +0200
lvol2 2016-09-09 16:55:12 +0200<\/p>\n

# lvs \u2212o name,time \u2212S \u2019time since “1 year 3 months ago”\u2019
LV CTime
lvol4 2016-09-09 16:57:44 +0200
lvol3 2016-09-09 16:56:48 +0200
lvol2 2016-09-09 16:55:12 +0200
lvol1 2016-08-29 12:53:36 +0200
lvol0 2016-08-29 10:15:17 +0200<\/p>\n

Command log reporting<\/b>
As described in categorization based on reporting facility<\/b> section at the beginning of this document, both report-oriented<\/b> and processing-oriented<\/b> LVM commands can report the command log if this is enabled with log\/report_command_log<\/b> configuration setting. Just like any other report, we can set the set of fields to display (log\/command_log_cols<\/b>) and to sort by (log\/command_log_sort<\/b>) for this report.<\/p>\n

# lvmconfig \u2212\u2212type full log\/report_command_log log\/command_log_cols
log\/command_log_sort log\/command_log_selection
report_command_log=1
command_log_cols=”log_seq_num,log_type,log_context,log_object_type,
log_object_name,log_object_group,log_message,
log_errno,log_ret_code”
command_log_sort=”log_seq_num”
command_log_selection=”!(log_type=status && message=success)”<\/p>\n

# lvs
Logical Volume
==============
LV LSize Cpy%Sync
lvol1 4.00m 100.00
lvol0 4.00m<\/p>\n

Command Log
===========
Seq LogType Context ObjType ObjName ObjGrp Msg Errno RetCode<\/p>\n

As you can see, the command log is empty (it contains only field names). By default, LVM uses selection on the command log report and this case no row matched the selection criteria, see also log report specifics<\/b> section in this document for more information. We\u2019re displaying complete log report in the example below where we can see that both LVs lvol0 and lvol1 were successfully processed as well as the VG vg they are part of.<\/p>\n

# lvmconfig \u2212\u2212type full log\/command_log_selection
command_log_selection=”all”<\/p>\n

# lvs
Logical Volume
==============
LV LSize Cpy%Sync
lvol1 4.00m 100.00
lvol0 4.00m<\/p>\n

Command Log
===========
Seq LogType Context ObjType ObjName ObjGrp Msg Errno RetCode
1 status processing lv lvol0 vg success 0 1
2 status processing lv lvol1 vg success 0 1
3 status processing vg vg success 0 1<\/p>\n

# lvchange \u2212an vg\/lvol1
Command Log
===========
Seq LogType Context ObjType ObjName ObjGrp Msg Errno RetCode
1 status processing lv lvol1 vg success 0 1
2 status processing vg vg success 0 1<\/p>\n

Handling multiple reports per single command<\/b>
To configure the log report directly on command line, we need to use \u2212\u2212configreport<\/b> option before we start any \u2212o\u2212\u2212options<\/b>, \u2212O\u2212\u2212sort<\/b> or \u2212S\u2212\u2212select<\/b> that is targeted for log report.<\/p>\n

# lvs \u2212o lv_name,lv_size \u2212\u2212configreport log \u2212o log_object_type,
log_object_name,log_message,log_ret_code
Logical Volume
==============
LV LSize
lvol1 4.00m
lvol0 4.00m<\/p>\n

Command Log
===========
ObjType ObjName Msg RetCode
lv lvol0 success 1
lv lvol1 success 1
vg vg success 1<\/p>\n

The lvm fullreport<\/b>, with or without log report, consists of several reports \u2212 the \u2212\u2212configreport<\/b> is also used to target particular subreport here.<\/p>\n

Below is an extended example with lvm fullreport<\/b> to illustrate combination of various options. The report output is in JSON format. Also, we configure “vg”, “pvseg”, “seg” and “log” subreport to contain only specified fields. For the “pvseg” subreport, we\u2019re intested only in PV names having “sda” in their name. For the “log” subreport we\u2019re intested only in log lines related to either “lvol0” object or object having “sda” in its name. Also, for the log subreport we define ordering to be based on “log_object_type” field.<\/p>\n

# lvm fullreport \u2212\u2212reportformat json
\u2212\u2212configreport vg \u2212o vg_name,vg_size
\u2212\u2212configreport pvseg \u2212o pv_name,pvseg_start
\u2212S \u2019pv_name=~sda\u2019
\u2212\u2212configreport seg \u2212o lv_name,seg_start
\u2212\u2212configreport log \u2212o log_object_type,log_object_name
\u2212O log_object_type
\u2212S \u2019log_object_name=lvol0 ||
log_object_name=~sda\u2019
{
“report”: [
{
“vg”: [
{“vg_name”:”vg”, “vg_size”:”200.00m”}
]
,
“pv”: [
{“pv_name”:”\/dev\/sda”, “vg_name”:”vg”},
{“pv_name”:”\/dev\/sdb”, “vg_name”:”vg”}
]
,
“lv”: [
{“lv_name”:”lvol0″, “vg_name”:”vg”},
{“lv_name”:”lvol1″, “vg_name”:”vg”}
]
,
“pvseg”: [
{“pv_name”:”\/dev\/sda”, “pvseg_start”:”0″},
{“pv_name”:”\/dev\/sda”, “pvseg_start”:”1″},
{“pv_name”:”\/dev\/sda”, “pvseg_start”:”2″},
{“pv_name”:”\/dev\/sda”, “pvseg_start”:”3″}
]
,
“seg”: [
{“lv_name”:”lvol0″, “seg_start”:”0 “},
{“lv_name”:”lvol1″, “seg_start”:”0 “}
]
}
]
,
“log”: [
{“log_object_type”:”lv”, “log_object_name”:”lvol0″},
{“log_object_type”:”lv”, “log_object_name”:”lvol0″},
{“log_object_type”:”pv”, “log_object_name”:”\/dev\/sda”},
{“log_object_type”:”pv”, “log_object_name”:”\/dev\/sda”},
]
}<\/p>\n

Report extensions for LVM shell<\/b>
As already stated in log report coverage<\/b> paragraph under log report specifics<\/b> in this documentation, when using LVM shell<\/b> the log report<\/b> coverage is wider. There\u2019s also special command designed to query last command\u2019s log report in the LVM shell<\/b> – the lastlog<\/b> command.<\/p>\n

The example below illustrates a situation where we called lvs command. After that, we inspected the log report with the lastlog<\/b>, without any selection so all the log report is displayed on output. Then we called lastlog<\/b> further, giving various selection criteria. Then we ran unknown LVM command “abc” for which the log report displays appropriate failure state.<\/p>\n

# lvm
lvm> lvs
Logical Volume
==============
LV LSize Cpy%Sync
lvol1 4.00m 100.00
lvol0 4.00m<\/p>\n

Command Log
===========
Seq LogType Context ObjType ObjName ObjGrp Msg Errno RetCode
1 status processing lv lvol0 vg success 0 1
2 status processing lv lvol1 vg success 0 1
3 status processing vg vg success 0 1
4 status shell cmd lvs success 0 1<\/p>\n

lvm> lastlog
Command Log
===========
Seq LogType Context ObjType ObjName ObjGrp Msg Errno RetCode
1 status processing lv lvol0 vg success 0 1
2 status processing lv lvol1 vg success 0 1
3 status processing vg vg success 0 1
4 status shell cmd lvs success 0 1<\/p>\n

lvm> lastlog \u2212S log_object_type=lv
Command Log
===========
Seq LogType Context ObjType ObjName ObjGrp Msg Errno RetCode
1 status processing lv lvol0 vg success 0 1
2 status processing lv lvol1 vg success 0 1<\/p>\n

lvm> lastlog \u2212S log_context=shell
Command Log
===========
Seq LogType Context ObjType ObjName ObjGrp Msg Errno RetCode
4 status shell cmd lvs success 0 1<\/p>\n

lvm> abc
Command Log
===========
Seq LogType Context ObjType ObjName ObjGrp Msg Errno RetCode
1 error shell cmd abc No such command \u2019abc\u2019. Try \u2019help\u2019. \u22121 0
2 status shell cmd abc failure \u22121 2<\/p>\n

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

lvm<\/b> (8), lvmconfig<\/b> (8), lvm fullreport<\/b> (8)<\/p>\n

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

lvmreport \u2014 LVM reporting and related features <\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[971],"tags":[973,1044,972],"class_list":["post-3952","post","type-post","status-publish","format-standard","hentry","category-7-miscelanea","tag-973","tag-lvmreport","tag-man7"],"gutentor_comment":0,"_links":{"self":[{"href":"https:\/\/lode.uno\/linux-man\/wp-json\/wp\/v2\/posts\/3952","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=3952"}],"version-history":[{"count":0,"href":"https:\/\/lode.uno\/linux-man\/wp-json\/wp\/v2\/posts\/3952\/revisions"}],"wp:attachment":[{"href":"https:\/\/lode.uno\/linux-man\/wp-json\/wp\/v2\/media?parent=3952"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/lode.uno\/linux-man\/wp-json\/wp\/v2\/categories?post=3952"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/lode.uno\/linux-man\/wp-json\/wp\/v2\/tags?post=3952"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}