[Users] Problems encountered increasing CT diskspace with layout=ploop

[Sirk Johannsen]

Hi,

here is the Bugzilla  Bug ID: 2225
http://bugzilla.openvz.org/show_bug.cgi?id=2225

dmesg is:
[14476.673338] EXT4-fs (ploop0p1): mounted filesystem with ordered data
mode. Opts:
[14476.674206] EXT4-fs (ploop0p1): loaded balloon from 12 (0 blocks)
[14476.719799] CT: 102: started

Thanks for caring and all.
By the way. ploop is really awesome ! Exactly what I have been looking for
in OpenVZ for month.
It really solves a lot of problems with having containers on plain nfs.

many thanks,

Sirk

2012/3/27 Kir Kolyshkin <kir at openvz.org>

>  Hi,
>>
>> Sorry for not posting in Buguzilla.
>> I found this thread an figured it was the right place to discuss.
>> Do you want me to open a bug in bugzilla ?
>>
>
> Yes please.
>
>  Here is the mount line:
>> /dev/ploop0p1 /srv/vz/root/102 ext4 rw,relatime,barrier=1,data=**ordered
>> 0 0
>>
>
> Right, no balloon_ino option...
>
>
>
>>
>> btw. resizing while the container is stopped does work.
>>
>> Here is some output:
>> vzctl set 102 --diskspace 77G --save
>> Can't ioctl mount_point: No such file or directory
>> Failed to resize image: Can't ioctl mount_point: No such file or
>> directory [3]
>> CT configuration saved to /etc/vz/conf/102.conf
>> [root at testsystem1 ~]# cat /proc/mounts | grep -w 102 | grep ploop
>> /dev/ploop0p1 /srv/vz/root/102 ext4 rw,relatime,barrier=1,data=**ordered
>> 0 0
>> [root at testsystem1 ~]# vzctl stop 102
>> Stopping container ...
>> Container was stopped
>> Umounting fs at /srv/vz/root/102
>> Unmounting device /dev/ploop0
>> Container is unmounted
>> [root at testsystem1 ~]# vzctl set 102 --diskspace 77G --save
>> Adding delta dev=/dev/ploop0 img=/srv/vz/private/102/root.**hdd/root.hdd
>> (rw)
>> Mounting /dev/ploop0p1 at /srv/vz/private/102/root.hdd/**root.hdd.mnt
>> fstype=ext4 data='balloon_ino=12,'
>> Growing dev=/dev/ploop0 size=150720512 sectors (new size=161480704)
>> Storing GPT
>> Executing: /sbin/resize2fs -p /dev/ploop0p1
>> resize2fs 1.41.12 (17-May-2010)
>> Das Dateisystem auf /dev/ploop0p1 ist auf /srv/vz/private/102/root.hdd/**root.hdd.mnt
>> eingehängt; Online-Grössenveränderung nötig
>> old desc_blocks = 5, new_desc_blocks = 5
>> Führe eine Online-Grössenänderung von /dev/ploop0p1 auf 20184827 (4k)
>> Blöcke durch.
>> Das Dateisystem auf /dev/ploop0p1 ist nun 20184827 Blöcke groß.
>>
>> Executing: /sbin/tune2fs -r 1009254 /dev/ploop0p1
>> tune2fs 1.41.12 (17-May-2010)
>> Setze die Anzahl der reservierten Blöcke auf 1009254
>> Umounting fs at /srv/vz/private/102/root.hdd/**root.hdd.mnt
>> Unmounting device /dev/ploop0
>> CT configuration saved to /etc/vz/conf/102.conf
>>
>> After starting it again, it is not working anymore:
>>
>> vzctl start 102
>> Starting container ...
>> Adding delta dev=/dev/ploop0 img=/srv/vz/private/102/root.**hdd/root.hdd
>> (rw)
>> Mounting /dev/ploop0p1 at /srv/vz/root/102 fstype=ext4
>> data='balloon_ino=12,'
>>
>
> See -- balloon_ino option is passed on...
>
>
>  Container is mounted
>> Adding IP address(es): 192.168.2.12
>> Setting CPU limit: 400
>> Setting CPU units: 1000
>> Setting CPUs: 4
>> Container start in progress...
>>
>> [root at testsystem1 ~]# cat /proc/mounts | grep -w 102 | grep ploop
>> /dev/ploop0p1 /srv/vz/root/102 ext4 rw,relatime,barrier=1,data=**ordered
>> 0 0
>>
>
> but it is not here. Hmm.
>
> Can you check the dmesg please?
>
> There should be something like
> [597088.246208]  ploop3: p1
> [597088.288093] EXT4-fs (ploop3p1): mounted filesystem with ordered data
> mode. Opts:
> [597088.290410] EXT4-fs (ploop3p1): loaded balloon from 12 (0 blocks)
> [597088.458139] CT: 123: started
>
>
>


-- 
Satzmedia GmbH

Altonaer Poststraße 9
22767 Hamburg
Tel:  +49 (0) 40 - 1 888 969 - 140
Fax: +49 (0) 40 - 1 888 969 - 200
E-Mail: s.johannsen at satzmedia.de
E-Business-Lösungen: http://www.satzmedia.de
Amtsgericht Hamburg, HRB 71729
Ust-IDNr. DE201979921
Geschäftsführer:
Dipl.-Kfm. Christian Satz
Dipl.-Inform. Markus Meyer-Westphal

-- 


-- 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://openvz.org/pipermail/users/attachments/20120327/c2d0a101/attachment-0001.html