Mike_MT wrote:1) We are...not always, but somewhat frequently adding/removing services like Moodle and the amount of required storage space may grow quickly.
2) We are looking to virtualize pretty much all the servers we can and it doesn't make sense to allocate all the space a physical server has allocated when it's only using a fraction of it.
3) For virtual machines, I allocate the system resources they need today, not what they might need some day. Resizing storage has been easy and fast for other OSes so when I need more it's an easy task.
I'll look into gvirstor.
Mike_MT wrote:As far as using gparted, growing the fs is by far the easiest thing for me. I just shutdown the vm, extend the disk using vmkfstools, boot the server using gparted and extend it - done.
I'm getting a clearer picture now of what the best solution probably is - a single disk zpool.
...also, it seems like a pretty straight forward task when I need more space (please correct me if I'm wrong) - just create a new, larger size 'disk' (vmdk file) and replace the existing 'disk' in the zpool.
fdisk -I da0
bsdlabel -wB da0s1
bsdlabel -e da0s1
(... edit the disk label: You need ~512m for the a: partition, and if you need swap, make a b: partition ...)
zpool create pool da1
zfs set mountpoint=legacy pool
mount -t zfs pool /mnt
mount /dev/da0s1a /mnt/.bootfs
ln -s .bootfs/boot /mnt/boot
(... now install the system to /mnt, setup fstab and loader.conf ...)
vmkfstools -X new_size vmfs_name:disk_name
And if I need to reclaim space, I'll have to create a new pool with a smaller disk, migrate the data, then destroy the first pool.
Users browsing this forum: ralphbsz and 2 guests