Quota OpenVZ

[drMacFaulty]

Hello all,

I already found another thread discussing a topic very related to this, will try to dig that up and add it here, but how can I check whether Quota has been enabled on my VPS? I tried the following:

Code: Select all

Command: mount -l
/vz/private/3701 on / type simfs (rw,relatime)
proc on /proc type proc (rw,nosuid,nodev,noexec,relatime)
sysfs on /sys type sysfs (rw,nosuid,nodev,noexec,relatime)
none on /dev type devtmpfs (rw,nosuid,noexec,relatime,mode=755)
none on /dev/pts type devpts (rw,nosuid,noexec,relatime,gid=5,mode=620,ptmxmode=000)
none on /proc/sys/fs/binfmt_misc type binfmt_misc (rw,nosuid,nodev,noexec,relatime)
none on /run type tmpfs (rw,nosuid,noexec,relatime,size=104860k,mode=755)
none on /run/lock type tmpfs (rw,nosuid,nodev,noexec,relatime,size=5120k)
none on /run/shm type tmpfs (rw,nosuid,nodev,noexec,relatime,size=419420k)
none on /run/user type tmpfs (rw,nosuid,nodev,noexec,relatime,size=102400k,mode=755)

I don't see quota anywhere. Is there another way to check this easily? At the moment, space is not limited (you can overwrite your max. package space.

If somebody can help me, that'll be great!

Thanks!

edit: What do I need to do to enable quota on my OpenVZ VPS container?
edit2: I contacted service provider and they enabled OpenVZ (see below code block for mount -l command). But now I can still upload a file which is larger than the max account space :confused: Can somebody walk me through the steps necessary to check what's where going wrong? Thanks!

Code: Select all

Command: mount -l
/vz/private/3701 on / type simfs (rw,relatime,usrquota,grpquota)
proc on /proc type proc (rw,nosuid,nodev,noexec,relatime)
sysfs on /sys type sysfs (rw,nosuid,nodev,noexec,relatime)
none on /dev type devtmpfs (rw,nosuid,noexec,relatime,mode=755)
none on /dev/pts type devpts (rw,nosuid,noexec,relatime,gid=5,mode=620,ptmxmode=000)
none on /proc/sys/fs/binfmt_misc type binfmt_misc (rw,nosuid,nodev,noexec,relatime)
none on /run type tmpfs (rw,nosuid,noexec,relatime,size=104860k,mode=755)
none on /run/lock type tmpfs (rw,nosuid,nodev,noexec,relatime,size=5120k)
none on /run/shm type tmpfs (rw,nosuid,nodev,noexec,relatime,size=419420k)
none on /run/user type tmpfs (rw,nosuid,nodev,noexec,relatime,size=102400k,mode=755)

[drMacFaulty]

As I already mentioned, the service provider enabled quota for me as you can see in my previous post. I re-installed Vesta and enabled the DISK_QUOTA variable in the /usr/local/vesta/conf/vesta.conf configuration file and after that I created a package with low resources and a user assigned to that package (say 50MB webspace).

I am still able to upload files, larger than the max space assigned (I uploaded a 100MB test file and it got through and stayed in the account web/public_html folder). If I run the command

Code: Select all

$ quota testUser

, I get the message that this user has no quota assigned (none).

What's going wrong? Would really like to have disk quotas as I know this should be possible.

[imperio]

Hi, drMacFaulty
now quota don't working, this function will be in release with bug-fixes

[drMacFaulty]

Hi, drMacFaulty
now quota don't working, this function will be in release with bug-fixes

Thanks for getting back to me Imperio :) Any idea when that release will be scheduled? Or is this still on the drawing table?

[imperio]

I think that release will be in the next few days

[drMacFaulty]

I think that release will be in the next few days

That'll be great :D Will wait it out then before trying it again on a fresh server.

Thanks :)

[drMacFaulty]

I updated Vesta now, but still when running quota, nobody has a limit. Do I need to run a special command from Vesta to update this and what do I need to set the DISK_QUOTA var to in vesta.conf? It was no and I changed it to yes, but to no avail. :(

Or is it not implemented, because time window wasn't large enough? :)

edit: package version is 0.9.8-9.

[imperio]

drMacFaulty
the release has not yet been

[drMacFaulty]

drMacFaulty
the release has not yet been

Oh, do excuse me as I thought that this update (0.9.8-9) was a bugfix release with that support, but I couldn't find it yet by version history on the site, so I assumed it would be integrated.