Table of Contents
Advertisement
Chapter 6.
LVM Troubleshooting
This chapter provide instructions for troubleshooting a variety of LVM issues.
1. Troubleshooting Diagnostics
If a command is not working as expected, you can gather diagnostics in the following ways:
• Use the
,
,
-v
-vv
-vvv
output.
• If the problem is related to the logical volume activation, set 'activation = 1' in the 'log' section
of the configuration file and run the command with the
finished examining this output be sure to reset this parameter to 0, to avoid possible problems
with the machine locking during low memory situations.
• Run the
command, which provides an information dump for diagnostic purposes. For
lvmdump
information, see the
• Execute the
lvs -v
information.
• Examine the last backup of the metadata in the
in the
/etc/lvm/archive
• Check the current configuration information by running the
• Check the
file in the
.cache
volumes on them.
2. Displaying Information on Failed Devices
You can use the
argument of the
-P
volume that would otherwise not appear in the output. This argument permits some operations
even though the metatdata is not completely consistent internally. For example, if one of the
devices that made up the volume group
output.
[root@link-07 tmp]# vgs -o +devices
Volume group "vg" not found
If you specify the
argument of the
-P
can see more information about the failed device.
[root@link-07 tmp]# vgs -P -o +devices
, or
argument of any command for increasingly verbose levels of
-vvvv
(8) man page.
lvmdump
,
or
pvs -a
dmsetup info -c
file.
directory for a record of which devices have physical
/etc/lvm
or
lvs
vgs
failed, the
vg
command, the volume group is still unusable but you
vgs
argument. After you have
-vvvv
command for additional system
file and archived versions
/etc/lvm/backup
lvm dumpconfig
command to display information about a failed
command might show the following
vgs
command.
69
Advertisement
Table of Contents
