Home » Mailing lists » Users » vzquota problem with ploop container ....
vzquota problem with ploop container .... [message #47751] |
Fri, 07 September 2012 06:22 ![Go to next message Go to next message](/theme/ovz3/images/down.png) |
Rene Dokbua
Messages: 24 Registered: May 2012
|
Junior Member |
|
|
So now I have created a ploop account, and when I start it I get this error:
# vzctl start 1517
Starting container ...
Adding delta dev=/dev/ploop0 img=/vz2/private/1517/root.hdd/root.hdd (rw)
Mounting /dev/ploop0p1 at /vz2/root/1517 fstype=ext4
data='balloon_ino=12,usrjquota=aquota.user,grpjquota=aquota. group,jqfmt=vfsv0,'
Container is mounted
Adding IP address(es): 209.105.227.151
Setting CPU limit: 50
Setting CPU units: 30000
Setting CPUs: 1
Old quota utils version detected: Quota utilities version 3.13.
Quota utils version should be > 3.16
Container start in progress...
So I checked for the version of Quota installed:
# rpm -qa | grep -i quota
vzquota-3.0.12-1.x86_64
Ok, so it's old .. but ....
# yum update vzquota
Setting up Update Process
No Packages marked for Update
What gives?
|
|
|
|
Re: vzquota problem with ploop container .... [message #47756 is a reply to message #47751] |
Fri, 07 September 2012 15:53 ![Go to previous message Go to previous message](/theme/ovz3/images/up.png) ![Go to next message Go to next message](/theme/ovz3/images/down.png) |
|
This is about native quota tools installed into container, not vzquota.
The message means you will not be able to use usual Unix per user and per
group quota inside this container due to old quota utils installed inside
On Sep 7, 2012 10:24 AM, "Rene C." <openvz@dokbua.com> wrote:
> So now I have created a ploop account, and when I start it I get this
> error:
>
> # vzctl start 1517
> Starting container ...
> Adding delta dev=/dev/ploop0 img=/vz2/private/1517/root.hdd/root.hdd (rw)
> Mounting /dev/ploop0p1 at /vz2/root/1517 fstype=ext4
>
> data='balloon_ino=12,usrjquota=aquota.user,grpjquota=aquota. group,jqfmt=vfsv0,'
> Container is mounted
> Adding IP address(es): 209.105.227.151
> Setting CPU limit: 50
> Setting CPU units: 30000
> Setting CPUs: 1
> Old quota utils version detected: Quota utilities version 3.13.
> Quota utils version should be > 3.16
> Container start in progress...
>
> So I checked for the version of Quota installed:
>
> # rpm -qa | grep -i quota
> vzquota-3.0.12-1.x86_64
>
> Ok, so it's old .. but ....
>
> # yum update vzquota
> Setting up Update Process
> No Packages marked for Update
>
> What gives?
Kir Kolyshkin
|
|
|
Re: vzquota problem with ploop container .... [message #47769 is a reply to message #47756] |
Sat, 08 September 2012 04:54 ![Go to previous message Go to previous message](/theme/ovz3/images/up.png) ![Go to next message Go to next message](/theme/ovz3/images/down.png) |
Rene Dokbua
Messages: 24 Registered: May 2012
|
Junior Member |
|
|
Ah, ok. So checked the container, has the latest version of quota
for Centos 5.8 = 3.13. Is quota for Centos delayed or OVZ a little
ahead?
On Fri, Sep 7, 2012 at 10:53 PM, Kir Kolyshkin <kir@openvz.org> wrote:
> This is about native quota tools installed into container, not vzquota.
>
> The message means you will not be able to use usual Unix per user and per
> group quota inside this container due to old quota utils installed inside
>
> On Sep 7, 2012 10:24 AM, "Rene C." <openvz@dokbua.com> wrote:
>>
>> So now I have created a ploop account, and when I start it I get this
>> error:
>>
>> # vzctl start 1517
>> Starting container ...
>> Adding delta dev=/dev/ploop0 img=/vz2/private/1517/root.hdd/root.hdd (rw)
>> Mounting /dev/ploop0p1 at /vz2/root/1517 fstype=ext4
>>
>> data='balloon_ino=12,usrjquota=aquota.user,grpjquota=aquota. group,jqfmt=vfsv0,'
>> Container is mounted
>> Adding IP address(es): 209.105.227.151
>> Setting CPU limit: 50
>> Setting CPU units: 30000
>> Setting CPUs: 1
>> Old quota utils version detected: Quota utilities version 3.13.
>> Quota utils version should be > 3.16
>> Container start in progress...
>>
>> So I checked for the version of Quota installed:
>>
>> # rpm -qa | grep -i quota
>> vzquota-3.0.12-1.x86_64
>>
>> Ok, so it's old .. but ....
>>
>> # yum update vzquota
>> Setting up Update Process
>> No Packages marked for Update
>>
>> What gives?
|
|
|
Re: vzquota problem with ploop container .... [message #47772 is a reply to message #47769] |
Sat, 08 September 2012 09:04 ![Go to previous message Go to previous message](/theme/ovz3/images/up.png) ![Go to next message Go to next message](/theme/ovz3/images/down.png) |
|
On 09/08/2012 08:54 AM, Rene C. wrote:
> Ah, ok. So checked the container, has the latest version of quota
> for Centos 5.8 = 3.13. Is quota for Centos delayed or OVZ a little
> ahead?
Yes, we are ahead, since we're using ext4 on top of ploop.
The problem is, quota utils < 3.17 doesn't support ext4 quotas. That
essentially means
you will not be able to use in-container per-user and per-group quota on
CentOS on
ploop (unless, of course, you manually upgrade quota utils to >= 3.17).
>
> On Fri, Sep 7, 2012 at 10:53 PM, Kir Kolyshkin <kir@openvz.org> wrote:
>> This is about native quota tools installed into container, not vzquota.
>>
>> The message means you will not be able to use usual Unix per user and per
>> group quota inside this container due to old quota utils installed inside
>>
>> On Sep 7, 2012 10:24 AM, "Rene C." <openvz@dokbua.com> wrote:
>>> So now I have created a ploop account, and when I start it I get this
>>> error:
>>>
>>> # vzctl start 1517
>>> Starting container ...
>>> Adding delta dev=/dev/ploop0 img=/vz2/private/1517/root.hdd/root.hdd (rw)
>>> Mounting /dev/ploop0p1 at /vz2/root/1517 fstype=ext4
>>>
>>> data='balloon_ino=12,usrjquota=aquota.user,grpjquota=aquota. group,jqfmt=vfsv0,'
>>> Container is mounted
>>> Adding IP address(es): 209.105.227.151
>>> Setting CPU limit: 50
>>> Setting CPU units: 30000
>>> Setting CPUs: 1
>>> Old quota utils version detected: Quota utilities version 3.13.
>>> Quota utils version should be > 3.16
>>> Container start in progress...
>>>
>>> So I checked for the version of Quota installed:
>>>
>>> # rpm -qa | grep -i quota
>>> vzquota-3.0.12-1.x86_64
>>>
>>> Ok, so it's old .. but ....
>>>
>>> # yum update vzquota
>>> Setting up Update Process
>>> No Packages marked for Update
>>>
>>> What gives?
>>>
Kir Kolyshkin
|
|
|
Re: vzquota problem with ploop container .... [message #47775 is a reply to message #47769] |
Sat, 08 September 2012 13:41 ![Go to previous message Go to previous message](/theme/ovz3/images/up.png) |
|
On Sep 8, 2012 8:55 AM, "Rene C." <openvz@dokbua.com> wrote:
>
> Ah, ok. So checked the container, has the latest version of quota
> for Centos 5.8 = 3.13. Is quota for Centos delayed or OVZ a little
> ahead?
It basically means you can not use in-container per-user and per-group
quota inside CentOS 5 container on ploop. Unless you manually install newer
quota tools of course.
>
> On Fri, Sep 7, 2012 at 10:53 PM, Kir Kolyshkin <kir@openvz.org> wrote:
> > This is about native quota tools installed into container, not vzquota.
> >
> > The message means you will not be able to use usual Unix per user and
per
> > group quota inside this container due to old quota utils installed
inside
> >
> > On Sep 7, 2012 10:24 AM, "Rene C." <openvz@dokbua.com> wrote:
> >>
> >> So now I have created a ploop account, and when I start it I get this
> >> error:
> >>
> >> # vzctl start 1517
> >> Starting container ...
> >> Adding delta dev=/dev/ploop0 img=/vz2/private/1517/root.hdd/root.hdd
(rw)
> >> Mounting /dev/ploop0p1 at /vz2/root/1517 fstype=ext4
> >>
> >>
data='balloon_ino=12,usrjquota=aquota.user,grpjquota=aquota. group,jqfmt=vfsv0,'
> >> Container is mounted
> >> Adding IP address(es): 209.105.227.151
> >> Setting CPU limit: 50
> >> Setting CPU units: 30000
> >> Setting CPUs: 1
> >> Old quota utils version detected: Quota utilities version 3.13.
> >> Quota utils version should be > 3.16
> >> Container start in progress...
> >>
> >> So I checked for the version of Quota installed:
> >>
> >> # rpm -qa | grep -i quota
> >> vzquota-3.0.12-1.x86_64
> >>
> >> Ok, so it's old .. but ....
> >>
> >> # yum update vzquota
> >> Setting up Update Process
> >> No Packages marked for Update
> >>
> >> What gives?
Kir Kolyshkin
|
|
|
Goto Forum:
Current Time: Sun Aug 25 00:44:32 GMT 2024
Total time taken to generate the page: 0.03218 seconds
|