I just ruined everything trying to increase OpenVZ space from 11G to 1T:
mv /iso //cassiniequinox/iso
mv /vz //cassiniequinox/vz
mv //cassiniequinox/iso & //cassiniequinox/vz //cassiniequinox/datastore0/storage/temp
cp //cassiniequinox/iso //cassiniequinox/vz/template
remove iso dir from storage via web interface
check iso inlocal dir via web interface
umount /iso
rmdir /iso
OR since it wont
delete "/dev/sdc1 /iso xfs defaults 0 1" line from /etc/fstab
echo "/dev/sdc1 /datastore1 defaults 0 1" >> /etc/fstab
mkdir /datastore1
mkdir /datastore1/vz
umount /dev/mapper/pve-data
del /vz symlink from /var/lib
reboot (will mount /datastore1 to /dev/sdc1 via fstab)
umount /dev/mapper/pve-data
rmdir /iso
rmdir /var/lib/vz
ln -s /datastore1/vz /var/lib/vz
cp contents of //cassiniequinox/vz/ to /var/lib/vz
mount /dev/mapper/pve-data /var/lib/vz
Problem was the missing xfs from echo "/dev/sdc1 /datastore1 defaults 0 1" >> /etc/fstab
When I copied everything back, it filled / & I couldn't do anything.
I tried rm /var/lib/vz/template/iso/biggestfile.iso with limited success since also I hadn't set the VMs to not start at boot. So they were running without a usable /dev/mapper/pve-data.
I was able to ssh via putty, but sftp wouldn't change dirs. At some point, I don't recall how, I was able to copy the contents /vz back to /datastore1/vz via dropping them onto /var/lib/vz, and after a reboot I had bad magic somethings in the xfs partition, so I tried reformatting that with a live CD & since then it's been unable to change dirs in sftp client.
I suspect it had something to do with /dev/mapper/pve-data being mounted to /var/lib/vz as ext3 & when it got redirected to the /datastore1/vz on xfs something went wrong there.
By now I've totally lost track of what happened & am set to re-install PVE to it's 25G partition.
I doubt I'll be able to recover the VM's that live on the LVM partition because it won't be visible to PVE unless I re-add via pvcreate & vgcreate prior to creating the LVM dir, which would overwrite it all.
This is BS that OVZ has to live on the same partition as the OS, making it all huge & all.
I don't know if I want to stick w/ PVE anymore. Maybe I'll feel differently tomorrow after some rest- this panic & loss is really draining.
---->> EDIT:
After re-installing PVE to it's little 25G partition, I see that lvdisplay shows the disks, I can re-add still-present LVMs to PVE's storage screen, & have been able to put symlinks for all the folders within /var/lib/vz into /var/lib/vz pointing to their counterparts in /datastore1, which is "mounted on" (I think that's the right term- occupying space from) /dev/sdc1.
I have the intended effect of having the iso's & OVZ parts in their own Tb space. The VM disks are still in their own TB space, too.
I've yet to figure out how to bring the machines back to the web interface, though.
Something I noticed while trying to make /var/lib/vz bigger was that if I first mounted /datastore1 on /dev/sdc1 and then mounted /dev/mapper/pve-data to either the vz symlink in /var/lib pointing to /datastore1/vz or to /datastore1/vz directly, the capacity of the local storage would immediateley drop from 900 to 11 G. So instead I let /dev/mapper/pve-data stay mounted to a real /var/lib/vz & just symlinked it's subdirs instead. Now as I'm adding several Gigs of iso, the local capacity stays at 11G.
How could I get that space meter on local to show actual space?
And how would one resurrect the VMs from their remains on the LV?
