Red Hat Bugzilla – Bug 127367
lvscan -v fails to report mapping of logical to physical extents
Last modified: 2010-04-27 09:37:25 EDT
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.6) Gecko/20040510
Description of problem:
Entire output of lvdisplay -v is
# /usr/sbin/lvdisplay -v /dev/vgob01/lv_var
Using logical volume(s) on command line
--- Logical volume ---
LV Name /dev/vgob01/lv_var
VG Name vgob01
LV UUID iQiNiG-1HO8-aRqg-I0e0-R531-Urpn-jARgIi
LV Write Access read/write
LV Status available
# open 1
LV Size 1.46 GB
Current LE 375
Allocation next free (default)
Read ahead sectors 0
Block device 253:6
According to the man page, this command should report mapping of
logical to physical extents (and did so in LVM 1). Adding extra "-v"
options does not help.
lvdisplay --help reveals some options not documented in the man page
(nor in the man page for lvm), including --maps, which gives some of
the desired information.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. pick a logical volume.
2. run lvdisplay -v against it.
Actual Results: No mapping information (-v adds only one line to the
Expected Results: Mapping of logical to physical extents should be
--maps is the way to do this now; or lvs --segments; will be improved
(e.g. to include reverse mapping from pv->lv) in future
Man page example needs fixing.
Suggest also lvs -o +devices
Fedora Core 2 is now maintained by the Fedora Legacy project for
security updates only. If this problem is a security issue, please
reopen and reassign to the Fedora Legacy product. If it is not a
security issue and hasn't been resolved in the current FC3 updates or
in the FC4 test release, reopen and change the version to match.
PV to LV mappings are available using something like:
pvs --segments -o+lv_name,seg_start_pe,segtype
Mentioning this on man page and closing - lvdisplay is unlikely to receive further enhancement.