Comment 7 for bug 230192

On Tue, May 20, 2008 at 04:57:09AM -0000, Kenan Begovic wrote:
> #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

> 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 understood from what you meantioned that a logical volume can map to
several physical volumes, is that correct ?

> 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...
---end quoted text---

Yes, that's what I was planning to do. The problem is that if /boot is
on an LV, I need to detect which physical volume does it exist on,
especially that you mentioned that a logical volume could map to several
physical volumes.

Anyways, it seems that in your case, /boot is not on a LV, so I still
can't figure the reason of your problem, please run the attached script
(test.sh), and send me its output.

--
 أحمد المحمودي (Ahmed El-Mahmoudy)
  Digital design engineer
  SySDSoft, Inc.
 GPG KeyID: 0x9DCA0B27 (@ subkeys.pgp.net)
 GPG Fingerprint: 087D 3767 8CAC 65B1 8F6C 156E D325 C3C8 9DCA 0B27