OpenVZ Forum


Home » Mailing lists » Users » adventures with layout=ploop
Re: adventures with layout=ploop [message #45621 is a reply to message #45619] Fri, 23 March 2012 00:06 Go to previous messageGo to previous message
jjs - mainphrame is currently offline  jjs - mainphrame
Messages: 44
Registered: January 2012
Member
Hi Kir,

[root@mrmber ~]# uname -a
Linux mrmber.mainphrame.net 2.6.32-042stab052.8 #1 SMP Wed Mar 14 16:02:48
MSK 2012 i686 i686 i386 GNU/Linux

There was no dmesg content generated by the attempt to create the CT with
ploop layout; /var/log/vzctl.log contained only this:

2012-03-22T17:01:46-0700 vzctl : CT 779 : Unable to get full ostemplate
name for debian-5.0-x86
2012-03-22T17:01:46-0700 vzctl : CT 779 : Creating image:
/vz/private/779.tmp/root.hdd/root.hdd size=2306867K
2012-03-22T17:01:46-0700 : PLOOP_IOC_ADD_DELTA
/vz/private/779.tmp/root.hdd/root.hdd: Invalid argument
2012-03-22T17:01:46-0700 vzctl : CT 779 : Failed to create image:
PLOOP_IOC_ADD_DELTA /vz/private/779.tmp/root.hdd/root.hdd: Invalid argument
[3]
2012-03-22T17:01:46-0700 vzctl : CT 779 : Creation of container private
area failed

Regards,

Joe

On Thu, Mar 22, 2012 at 12:26 PM, Kir Kolyshkin <kir@openvz.org> wrote:

> On 03/22/2012 09:42 PM, jjs - mainphrame wrote:
>
>> My test platform is centos-6.2 32 bit. I had successfully created
>> ploop-based containers when testing the ploop and vzctl from git last week.
>> Today I installed the released ploop and vzctl rpms to test further.
>>
>
> Which kernel it is?
>
> Anything in dmesg output?
>
>
>
>> When I issue a command to create a ploop-based container, vzctl is unable
>> to complete the operation, exiting with errors:
>>
>> [root@mrmber ~]# vzctl create 777 --layout=ploop --config=vswap-256m
>> --ostemplate=debian-5.0-x86
>> Unable to get full ostemplate name for debian-5.0-x86
>> Creating image: /vz/private/777.tmp/root.hdd/**root.hdd size=2306867K
>> Creating delta /vz/private/777.tmp/root.hdd/**root.hdd bs=2048
>> size=4613734 sectors
>> Storing /vz/private/777.tmp/root.hdd/**DiskDescriptor.xml
>> Adding delta dev=/dev/ploop0 img=/vz/private/777.tmp/root.**hdd/root.hdd
>> (rw)
>> PLOOP_IOC_ADD_DELTA /vz/private/777.tmp/root.hdd/**root.hdd: Invalid
>> argument
>> Failed to create image: PLOOP_IOC_ADD_DELTA /vz/private/777.tmp/root.hdd/
>> **root.hdd: Invalid argument [3]
>> Creation of container private area failed
>> [root@mrmber ~]#
>>
>>
>> When I issue a command to create a container with the same parameters
>> except using layout=simfs instead of ploop, vzctl succeeds:
>>
>> [root@mrmber ~]# vzctl create 777 --layout=simfs --config=vswap-256m
>> --ostemplate=debian-5.0-x86
>> Unable to get full ostemplate name for debian-5.0-x86
>> Creating container private area (debian-5.0-x86)
>> Performing postcreate actions
>> CT configuration saved to /etc/vz/conf/777.conf
>> Container private area was created
>> [root@mrmber ~]#
>>
>> Where should I be looking to solve this mystery?
>>
>> Regards,
>>
>> Joe
>>
>>
>


http://static.openvz.org/userbars/openvz-user.png
 
Read Message
Read Message
Read Message
Read Message
Previous Topic: Processes in D state when vzctl chkpnt suspend
Next Topic: Problems encountered increasing CT diskspace with layout=ploop
Goto Forum:
  


Current Time: Thu Aug 15 05:43:33 GMT 2024

Total time taken to generate the page: 0.03569 seconds