#lvsidplay -m

  --- Logical volume ---
  LV Name                /dev/VolGroup00/LogVol00
  VG Name                VolGroup00
  LV UUID                k225JE-0V0O-xjp1-BUQ7-dJJj-2i2t-MFCsHH
  LV Write Access        read/write
  LV Status              available
  # open                 1
  LV Size                52.03 GB
  Current LE             1665
  Segments               1
  Allocation             inherit
  Read ahead sectors     0
  Block device           254:0
   
  --- Segments ---
  Logical extent 0 to 1664:
    Type                linear
    Physical volume     /dev/sda2
    Physical extents    0 to 1664
   
   
  --- Logical volume ---
  LV Name                /dev/VolGroup00/LogVol02
  VG Name                VolGroup00
  LV UUID                YVTQWL-3Dfc-BBkU-LXbv-0Qco-8RMf-vGgl5C
  LV Write Access        read/write
  LV Status              available
  # open                 1
  LV Size                39.06 GB
  Current LE             1250
  Segments               1
  Allocation             inherit
  Read ahead sectors     0
  Block device           254:1
   
  --- Segments ---
  Logical extent 0 to 1249:
    Type                linear
    Physical volume     /dev/sda2
    Physical extents    1665 to 2914
   
   
  --- Logical volume ---
  LV Name                /dev/VolGroup00/LogVol01
  VG Name                VolGroup00
  LV UUID                7IL2wb-H7M1-y4vt-Ux7N-My62-0nwU-pohXKs
  LV Write Access        read/write
  LV Status              available
  # open                 2
  LV Size                1.94 GB
  Current LE             62
  Segments               1
  Allocation             inherit
  Read ahead sectors     0
  Block device           254:2
   
  --- Segments ---
  Logical extent 0 to 61:
    Type                linear
    Physical volume     /dev/sda2
    Physical extents    2915 to 2976


Output of "lvdisplay -m /dev/mapper/VolGroup00-LogVol00" is no different than 
first portion of "lvdisplay -m" output.

As for, how to determine which physical volume is mapped to which logical 
volume, you must be aware that logical extents (LE) from one logical volume can 
be mapped to physical extents (PE) from multiple physical volumes within same 
volume group. 
I believe that you are interested in device that mounts to /boot in this case. 
Most normal people do not set /boot on LV. So you can edit postinst script to 
detect if LVs are used and confirm that /boot is not on LV (as the script is 
already checking if /boot is on separate partition). I am just shooting here in 
dark, maybe it will help...

-- 
ubuntu-artwork package reports error while installing
https://bugs.launchpad.net/bugs/230192
You received this bug notification because you are a member of Ubuntu
Muslim Edition Team, which is subscribed to Ubuntu Muslim Edition
Artwork.

Status in Ubuntu Muslim Edition Artwork: New

Bug description:
Following error reported by dpkg

sed: -e expression #1, char 47: unknown option to `s'  
dpkg: error processing ubuntume-artwork (--configure):  

menu.lst and device.map attached

_______________________________________________
Mailing list: https://launchpad.net/~ubuntume.team
Post to     : [email protected]
Unsubscribe : https://launchpad.net/people/+me/+editemails
More help   : https://help.launchpad.net/ListHelp

رد على