OpenVZ Forum


Home » Mailing lists » Users » Filesystem size limit in the vzquota system ?
Filesystem size limit in the vzquota system ? [message #12984] Wed, 16 May 2007 14:39 Go to next message
VALLET Matthieu is currently offline  VALLET Matthieu
Messages: 2
Registered: May 2007
Junior Member
From: openvz.org
Hi!

We have been using OpenVZ for a few months and are really satisfied with
this project. Thanks a lot.

Neithertheless, we have a problem with one out of three virtual server.
On this one, the quota system fails. The only difference with the two
others is the filesystem size that exceed, in this case, 40 gygabites.

It is possible to activate the quota system with a quite small
filesystem and then to progressively increase its size (with rsync for
example). But, if we try to directly start (or restart) a server on such
a big filesystem, it fails with the error :
vzquota : (error) Quota on syscall for 123: Device or resource busy

Is there a size limit for the filesystem of an OpenVZ virtual server,
with quota enabled?

Thanks for your help.

Matthieu Vallet.


-- Disclaimer ------------------------------------
Ce message ainsi que les eventuelles pieces jointes constituent une correspondance privee et confidentielle a l'attention exclusive du destinataire designe ci-dessus. Si vous n'etes pas le destinataire du present message ou une personne susceptible de pouvoir le lui delivrer, il vous est signifie que toute divulgation, distribution ou copie de cette transmission est strictement interdite. Si vous avez recu ce message par erreur, nous vous remercions d'en informer l'expediteur par telephone ou de lui retourner le present message, puis d'effacer immediatement ce message de votre systeme.
***
This e-mail and any attachments is a confidential correspondence intended only for use of the individual or entity named above. If you are not the intended recipient or the agent responsible for delivering the message to the intended recipient, you are hereby notified that any disclosure, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please notify the sender by phone or by replying this message, and then delete this message from your system.
Re: Filesystem size limit in the vzquota system ? [message #12991 is a reply to message #12984] Thu, 17 May 2007 07:54 Go to previous messageGo to next message
Vasily Tarasov is currently offline  Vasily Tarasov
Messages: 1345
Registered: January 2006
Senior Member
From: openvz.org
Hello,

> We have been using OpenVZ for a few months and are really satisfied with
> this project. Thanks a lot.

Thank you for using OpenVZ, we're happy to hear it. :)

>
> Neithertheless, we have a problem with one out of three virtual server.
> On this one, the quota system fails. The only difference with the two
> others is the filesystem size that exceed, in this case, 40 gygabites.
>
> It is possible to activate the quota system with a quite small
> filesystem and then to progressively increase its size (with rsync for
> example). But, if we try to directly start (or restart) a server on such
> a big filesystem, it fails with the error :
> vzquota : (error) Quota on syscall for 123: Device or resource busy
>
> Is there a size limit for the filesystem of an OpenVZ virtual server,
> with quota enabled?


There is no such limit. Actually I don't quite understand your phrase
"progressively increase its (filesystems) size (with rsync for
example)". Do you mean that you just add files to this filesystem and
consequently the amount of busy blocks is increasing?
The most common reason of the error: "vzquota : (error) Quota on syscall
for 123: Device or resource busy" is the presence of Linux disk quota on
the filesystem where vzquota is trying to start. Check it, please.

Thank you,
Vasily.
Re: Filesystem size limit in the vzquota system ? [message #13125 is a reply to message #12991] Mon, 21 May 2007 09:27 Go to previous message
VALLET Matthieu is currently offline  VALLET Matthieu
Messages: 2
Registered: May 2007
Junior Member
From: openvz.org
Hi,

Vasily Tarasov a écrit :
>> Is there a size limit for the filesystem of an OpenVZ virtual server,
>> with quota enabled?
>
>
> There is no such limit. Actually I don't quite understand your phrase
> "progressively increase its (filesystems) size (with rsync for
> example)". Do you mean that you just add files to this filesystem and
> consequently the amount of busy blocks is increasing?
> The most common reason of the error: "vzquota : (error) Quota on syscall
> for 123: Device or resource busy" is the presence of Linux disk quota on
> the filesystem where vzquota is trying to start. Check it, please.

I've just checked the filesystem: there is no standard linux disk quota
activated.

Furthermore, I guess that if it was the case, we could not use OpenVZ
quota for the two (small) virtual servers that works without any problem.

So, let me summarize what we found:
- we created three virtual servers, based on the debian 3.1 template;
- we set OpenVZ quota for each virtual server filesystem;
- in one of the three servers, we added a directory that we want to
share with Samba; this directory contains about 60 Gb of data;
- the two "small" servers start without any problem while the "big" one
gives us the mentionned error (Quota on syscall...);
- if we delete the big directory, the "big" server starts;
- if we then recreate this directory while the server is running and
fill it with the 60 Gb of data, with rsync, the vzquota tool shows the
right figures and the server runs normally;
- if we reboot the physical host afterwards, the "big" server cannot be
restarted as it shows the same error (Quota on syscall...).

We use a Red Hat 4 system, with a 2.6.9-023stab043.2-enterprise kernel.
The version of vzctl is 3.0.16, and vzquota's is 2.5.0.

Thanks for your help.

Matthieu Vallet.


-- Disclaimer ------------------------------------
Ce message ainsi que les eventuelles pieces jointes constituent une correspondance privee et confidentielle a l'attention exclusive du destinataire designe ci-dessus. Si vous n'etes pas le destinataire du present message ou une personne susceptible de pouvoir le lui delivrer, il vous est signifie que toute divulgation, distribution ou copie de cette transmission est strictement interdite. Si vous avez recu ce message par erreur, nous vous remercions d'en informer l'expediteur par telephone ou de lui retourner le present message, puis d'effacer immediatement ce message de votre systeme.
***
This e-mail and any attachments is a confidential correspondence intended only for use of the individual or entity named above. If you are not the intended recipient or the agent responsible for delivering the message to the intended recipient, you are hereby notified that any disclosure, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please notify the sender by phone or by replying this message, and then delete this message from your system.
Previous Topic: IPv6 support in VE
Next Topic: VPS don't start correctly, just 4 proc
Goto Forum:
  


Current Time: Wed Jul 18 22:15:12 GMT 2018