Hi,
I'm testing debian compiled kernel 2.6.32-openvz-042stab082.6-amd64 2.6.32-openvz-042stab082.6-amd64 libploop1:amd64 1.9-2 poop 1.9-2 vzctl 4.5-5wt1 vzquota 3.1-1 vzstats 0.5.2-1 Once I created a CT in ploop layout mode with --diskspace <=1026m , then I can't resize de ploop image to size greater than initial size of 1026. Otherwise, if I create it with diskspace greater than 1026 then It works perfectly. Is It a bug? See above: ---------------------------------------------------------------------------- -------- debian~$ sudo vzctl create 601 --layout ploop --diskspace 1026m Creating image: /data/vz/private/601.tmp/root.hdd/root.hdd size=1050624K Creating delta /data/vz/private/601.tmp/root.hdd/root.hdd bs=2048 size=2101248 sectors v1 Storing /data/vz/private/601.tmp/root.hdd/DiskDescriptor.xml Opening delta /data/vz/private/601.tmp/root.hdd/root.hdd Adding delta dev=/dev/ploop20444 img=/data/vz/private/601.tmp/root.hdd/root.hdd (rw) mke2fs 1.42.5 (29-Jul-2012) Discarding device blocks: done Filesystem label= OS type: Linux Block size=4096 (log=2) Fragment size=4096 (log=2) Stride=0 blocks, Stripe width=0 blocks 65536 inodes, 262139 blocks 13106 blocks (5.00%) reserved for the super user First data block=0 Maximum filesystem blocks=4294967296 8 block groups 32768 blocks per group, 32768 fragments per group 8192 inodes per group Superblock backups stored on blocks: 32768, 98304, 163840, 229376 Allocating group tables: done Writing inode tables: done Creating journal (4096 blocks): done Writing superblocks and filesystem accounting information: done tune2fs 1.42.5 (29-Jul-2012) Creating balloon file .balloon-c3a5ae3d-ce7f-43c4-a1ea-c61e2b4504e8 Mounting /dev/ploop20444p1 at /data/vz/private/601.tmp/root.hdd/root.hdd.mnt fstype=ext4 data='' Unmounting device /dev/ploop20444 Opening delta /data/vz/private/601.tmp/root.hdd/root.hdd Adding delta dev=/dev/ploop20444 img=/data/vz/private/601.tmp/root.hdd/root.hdd (rw) Mounting /dev/ploop20444p1 at /var/lib/vz/root/601 fstype=ext4 data='balloon_ino=12,' Creating container private area (debian-7.0-amd64-minimal) Unmounting file system at /var/lib/vz/root/601 Unmounting device /dev/ploop20444 Opening delta /data/vz/private/601/root.hdd/root.hdd Adding delta dev=/dev/ploop20444 img=/data/vz/private/601/root.hdd/root.hdd (rw) /dev/ploop20444p1: clean, 18282/65536 files, 94270/262139 blocks Mounting /dev/ploop20444p1 at /var/lib/vz/root/601 fstype=ext4 data='balloon_ino=12,' Performing postcreate actions Unmounting file system at /var/lib/vz/root/601 Unmounting device /dev/ploop20444 CT configuration saved to /etc/vz/conf/601.conf Container private area was created Now Resize..... debian:~$ sudo vzctl set 601 --diskspace 2G --save Opening delta /data/vz/private/601/root.hdd/root.hdd Adding delta dev=/dev/ploop20444 img=/data/vz/private/601/root.hdd/root.hdd (rw) Mounting /dev/ploop20444p1 at /data/vz/private/601/root.hdd/root.hdd.mnt fstype=ext4 data='balloon_ino=12,' Storing /data/vz/private/601/root.hdd/DiskDescriptor.xml.tmp Growing dev=/dev/ploop20444 size=2101248 sectors (new size=4194304) Storing GPT resize2fs 1.42.5 (29-Jul-2012) Filesystem at /dev/ploop20444p1 is mounted on /data/vz/private/601/root.hdd/root.hdd.mnt; on-line resizing required old_desc_blocks = 1, new_desc_blocks = 1 /sbin/resize2fs: No space left on device While checking for on-line resizing support Error in run_prg_rc (util.c:289): Command /sbin/resize2fs -p /dev/ploop20444p1 2093056k exited with code 1 Unmounting file system at /data/vz/private/601/root.hdd/root.hdd.mnt Unmounting device /dev/ploop20444 Failed to resize image: Error in run_prg_rc (util.c:289): Command /sbin/resize2fs -p /dev/ploop20444p1 2093056k exited with code 1 [26] Error: failed to apply some parameters, not saving configuration file! debian:~$ ---------------------------------------------------------------------------- -- Thanks.
_______________________________________________ Users mailing list Users@openvz.org https://lists.openvz.org/mailman/listinfo/users