| Re: Strange CT creation problem with ploop-1.2.1 and vzkernel-2.6.32-042stab054.5 [message #46413 is a reply to message #46412] |
Sat, 19 May 2012 07:56  |
Paparaciz
Messages: 302
Registered: August 2009
|
Senior Member |
|
|
http://bugzilla.openvz.org/show_bug.cgi?id=2249
On Sat, May 19, 2012 at 10:01 AM, Peter Schultze <petersch@cs.ucla.edu> wrote:
>> Mounting /dev/ploop1p1 at /vz/root/775 fstype=ext4 data='balloon_ino=12,'
>> Creating container private area (centos-6.2-x86-devel)
>> tar: ./etc/rc.d/init.d/saslauthd: Cannot write: No space left on device
>> tar: ./etc/rc.d/init.d/nscd: Cannot open: No space left on device
>> tar: ./etc/rc.d/init.d/rdisc: Cannot open: No space left on device
>
>
> I am seeing exactly the same problem on a 32-bit CentOS 6.2 machine with
>
> vzkernel-2.6.32-042stab055.10.i686
> ploop-lib-1.2-1.i386
> vzctl-lib-3.2-1.i386
>
> OS installation into a newly created CT fails because nothing can be written
> to the newly created ploop storage.
>
> When the same machine is reverted to 042stab054.3.i686 the ploop container
> creation is working working fine again.
>
> The problem seems to occur under all newer kernels beginning with
> 042stab054.4, including 042stab055.11
>
> There is no problem on a 64-bit CentOS 6.2 machine
> with vzkernel-2.6.32-042stab055.10.x86_64
>
> Could it be that this is only happening with the recent 32-bit kernels?
>
|
|
|
|
OpenVZ Forum
Members
Search
Help
Register
Login
Home
