New answers tagged openvz
Yes you can, but just don't rely on it (i.e. back up your data first!). The partitions should be adjacent, and for ease's sake you want to be expanding into a partition that comes AFTER the one you want to expand. Then just use parted on the device, delete both partitions (e.g. sdb1, sdb2), create a new one that spans the entire space, and use resize2fs ...
You can do it, but be careful. Use resize2fs to resize the partition, then you can adjust the partition to match using cfdisk. It's always easier to grow a partition than it is to shrink it, if you don't specify the final size then resize2fs will grow to fit.
I will allow others to answer who may have better ideas then me on this but after running e2fsck several times after umount, mount, start, repeat... I managed to bring all the containers back up finally. In fact, I think you can skip the umount process as one started right away and I forgot to umount it.
I found another solution to this problem! On the node I could not remove rmmod iptable_nat rmmod nf_nat rmmod nf_conntrack_ipv4 rmmod nf_conntrack in the Official Guide, I found: vzctl set VZID --netfilter full --save --setmode restart
For the first question the answer is yes. For the second it's NO. Since the introduction of namespaces some parameters differ. That's why we can have eth0 in host and container as well without name collision because network namespace is at work. sudo unshare -n -- ifconfig -a shows only lo. 'ip_forward' in container is quite possible because the ip stack in ...
Top 50 recent answers are included