* Seremeth, Stephen (SSeremeth@xxxxxxxxxxx) wrote:
> > Unfortunately, I only have one test system, but when installing this
> > particular system, I created three partitions. One was
> > /boot, the other
> > two I designated as LVM PVs. These were numbered pv.8 and
> > pv.10. After
> > searching through /proc and all the LVM commands I can think
> > of, I can't
> > seem to correlate pv.8 and pv.10 to anything (in fact, I can find no
> > mention of those "names" outside kickstart at all).
>
> I believe you're looking for:
>
> lvdisplay -m
Thanks for the reply Stephen. lvdisplay -m on my system throws an error.
I guess I neglected to mention, this is on RHEL 3, which I guess uses
LVM1. My RHEL4 systems have LVM2 and that command works fine.
Let me clarify my question a bit. Are the pv numbers arbitrary? Say my
kickstart file created during installation contains the following:
part /boot --fstype "ext3" --onpart hda1
part pv.8 --noformat --onpart hda2
part pv.10 --noformat --onpart hda3
volgroup vg00 --pesize=4096 pv.8 pv.10
If I wanted to write a new, but equivalent kickstart file, could I use
the following:
part /boot --fstype "ext3" --onpart hda1
part pv.1 --noformat --onpart hda2
part pv.2 --noformat --onpart hda3
volgroup vg00 --pesize=4096 pv.1 pv.2
Or do the pv.#s actually correspond to a partition? If so, how do I
derive that relationship from an existing installation?
Thanks,
drew
--
Don't break your shin on a stool that is not in your way.
- Irish Proverb
