S SamTzu Renowned Member Mar 27, 2009 529 17 83 Helsinki, Finland sami.mattila.eu Sep 7, 2013 #1 Why are quotas being recalculated even though they are not enabled by the OpenVZ container? vzquota : (warning) Incorrect quota shutdown for id 164, recalculating disk usage Click to expand...
Why are quotas being recalculated even though they are not enabled by the OpenVZ container? vzquota : (warning) Incorrect quota shutdown for id 164, recalculating disk usage Click to expand...
S SamTzu Renowned Member Mar 27, 2009 529 17 83 Helsinki, Finland sami.mattila.eu Sep 7, 2013 #2 That takes 4ever on BIG disks.
S SamTzu Renowned Member Mar 27, 2009 529 17 83 Helsinki, Finland sami.mattila.eu Sep 8, 2013 #3 After upgrading to 3.1 I have to do this on any big OpenVZ containers... vzquota off 164 vzquota : (error) Quota is not running for id 164 vzquota : (warning) Repairing quota: it was incorrectly marked as running for id 164 Click to expand...
After upgrading to 3.1 I have to do this on any big OpenVZ containers... vzquota off 164 vzquota : (error) Quota is not running for id 164 vzquota : (warning) Repairing quota: it was incorrectly marked as running for id 164 Click to expand...
S SamTzu Renowned Member Mar 27, 2009 529 17 83 Helsinki, Finland sami.mattila.eu Dec 3, 2013 #4 It seems that this is only the case on the default "local" storage that came with Proxmox. On other additional LVM storage on the same hardware quota is not forced on.
It seems that this is only the case on the default "local" storage that came with Proxmox. On other additional LVM storage on the same hardware quota is not forced on.
