I've got a single server running debian 6.0. We mainly use this server as a production fileserver for my company but we're running out of space on the share that is available to us for storage. Unfortunately, my outsourced IT either can't fix the problem or won't and I get no resolution despite repeated requests to take care of this and it's been a month.
So here I come, poking around in my server to see if I can help out my remote admin. I see there is proxmox installed. I email him this and some info on resizing disks and hear nothing for two weeks. The share/Openvz container size is 256GB and the drive size is 1.6TB so there is space available.
I decide to look into this myself tonight and see several articles that say the container can be resized on the fly. Great. I edit the resource in proxmox from 256 to 512GB and I get this error:
command 'vzctl --skiplock set 100 --diskspace 512G:590558003 --diskinodes 102400000:112640000 --save' failed: exit code 139 (500) Ok. Great. That failed because it seems the root partition has no space left on it so it could not save the open vz configuration file. The results of df -h are:
Filesystem Size Used Avail Use% Mounted on /dev/md1 16G 16G 0 100% / tmpfs 7.9G 0 7.9G 0% /lib/init/rw udev 7.9G 264K 7.9G 1% /dev tmpfs 7.9G 16M 7.8G 1% /dev/shm /dev/mapper/data-lvol0 1.6T 255G 1.4T 16% /var/lib/vz overflow 1.0M 0 1.0M 0% /tmp /dev/fuse 30M 16K 30M 1% /etc/pve However, in windows, the drive size has been increased to 512GB. Does this mean the container was resized to 512GB but this was not saved to the config file so upon a restart of the server, it would revert back to 256GB? (i.e. I'm screwed?)
I tried deleting a file in the / directory structure but that didn't give me any space on the /dev/md1 drive. This file was in /root and was 22k in size. What can I do now?
[link][2 comments]