| Re: vzdump snapshot problem and workaround for it [message #12016 is a reply to message #11958] |
Sat, 14 April 2007 20:14   |
jarcher
Messages: 91
Registered: August 2006
Location: Smithfield, Rhode Island
|
Member |
|
|
Thanks very much!
I’ll set the /dev// issue aside for right now and write about the PE allocation in the volume group. As you thought, my VG has no more capacity:
prod03:~# vgdisplay
--- Volume group ---
VG Name prod03-vg001
System ID
Format lvm2
Metadata Areas 2
Metadata Sequence No 4
VG Access read/write
VG Status resizable
MAX LV 0
Cur LV 1
Open LV 1
Max PV 0
Cur PV 2
Act PV 2
VG Size 195.24 GB
PE Size 4.00 MB
Total PE 49982
Alloc PE / Size 49982 / 195.24 GB
Free PE / Size 0 / 0
VG UUID r9QqPU-rRQr-jIzr-U0Pa-bBle-2DYJ-fHcifB
If I understand correctly from investigating this, I can run:
# pvchange –s 8m
And this will increase the size of each extent, adding capacity, but not actual storage space, to the VG. To get more storage space I would actually have to add an additional PV to the VG, correct?
There does not seem to be a command to increase the number of extents, just the size of each extent. Is that correct?
If I don’t add another PV, will I be able to create another LV in the VG? If so, where would the data live?
|
|
|
|
OpenVZ Forum
Members
Search
Help
Register
Login
Home
