On Thursday 19 March 2009 18:02:26 Frank Cox wrote:
...
> LV Name /dev/VolGroup00/LogVol00
> VG Name VolGroup00
> LV UUID yFemKc-s2bo-zZC0-cc7q-50By-4jQM-G1MsQr
...
> Block device 253:0
>
> --- Segments ---
> Logical extent 0 to 8872:
> Type linear
> Physical volume /dev/sdb2
> Physical extents 0 to 8872
...
> LV Name /dev/VolGroup00/LogVol01
> VG Name VolGroup00
> LV UUID 6UuO4G-X2dI-LirG-HvVF-zLfz-hrYW-NYZEdN
...
> Block device 253:1
>
> --- Segments ---
> Logical extent 0 to 61:
> Type linear
> Physical volume /dev/sdb2
> Physical extents 8873 to 8934
Here's the useful information about what's currently active (the "Block device"
should correspond to numbers you'll see in the output from "ls -l /dev/mapper")
and below we can match these details against the physical devices:
> PV Name /dev/sdb2
...
> Allocated PE 8935
> PV UUID SW3Qdy-7qcu-0Th1-Rb2Z-ui24-14ab-qRpMoq
>
> --- Physical Segments ---
> Physical extent 0 to 8872:
> Logical volume /dev/VolGroup00/LogVol00
> Logical extents 0 to 8872
This matches up with your LogVol00 above ...
> Physical extent 8873 to 8934:
> Logical volume /dev/VolGroup00/LogVol01
> Logical extents 0 to 61
... and this with your LogVol01 above.
And the rest:
> PV Name /dev/sda2
> VG Name VolGroup00
...
> PV UUID 1dl8EY-s2Qe-W50Y-wU8V-nCRJ-5Upz-SEkJgp
...
> Physical extent 0 to 14834:
> Logical volume /dev/VolGroup00/LogVol00
> Logical extents 0 to 14834
> Physical extent 14835 to 14896:
> Logical volume /dev/VolGroup00/LogVol01
> Logical extents 0 to 61
This is your "duplicate" volume group, which has likewise two logical volumes,
but looks like one of them is considerably larger.
You should probably be able to get some sense out of this by doing:
# vgrename 1dl8EY-s2Qe-W50Y-wU8V-nCRJ-5Upz-SEkJgp vg_sda2
Give it a try, hopefully that VG is "inactive" and will let you rename it.
--
fedora-list mailing list
fedora-list@xxxxxxxxxx
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
