Actually, I think I got the answer on this one. Having come from HP-UX where LVM is native - and there are no partitions, I forgot something: on PC-based systems, LVM considers a partition to be a "physical device", not the entire disk as is natural in HP-UX LVM.
Thus, when the "disk" was expanded from 30Gb to 60Gb, the partition table tool (parted) saw it - and repaired the "damage" nicely.
However, the "physical disk" that LVM used never changed as the partition never changed size. The proper way to expand the filesystem involved was to:
- Expand the volume group (using
vgextend) to include the new partition.
- Expand the logical volume (using
lvextend) to encompass the rest of the
space in the new volume group.
- Expand the filesystem (in this case, by using
resize2fs) to match the new space in
the logical volume.
That did it for me.