Disk Quota Widget doesn't work

[demonotaku]

The Disk Quota Widget doesn’t work on a fresh OVH install of Quick box

[JMSolo]

Alright, I noticed that I did leave some important details out after you brought this up.

I have edited the wiki on this issue and this should resolve your issue.

How to set Quotas to /home partition till fix arrives

There are known issue with any server using /home as the primary mount partition. The solution would be to reset quotas and assign them to that particular mount as quotas within the script are mounted to / This fix isn’t too terribly complicated and will be built into a future version. In the meantime, try this out: quotaoff -a service quota stop mount -o remount /home quotacheck -auMF vfsv1 quotaon -uv /home service quota start It is possible you will need to edit the /etc/fstab file as we…

[demonotaku]

I updated with those settings and still doesn’t work on 16.4 with /home

[JMSolo]

You typed in setdisk to change the users quota after modifying the files as well as the quota mount partition?

If you’d be so kind, could you drag and drop here a screen of the widget? Also, are there any errors when you type setdisk?

[demonotaku]

As soon as I hit enter on the amount it immediately closes my ssh connection

[JMSolo]

Interesting. What are the results of cat /etc/fstab?

Also, if you’re comfortable with it. You can submit your server details to me (via PM (sudo or better)) and I will login and patch up whatever I find may be wrong here.

[demonotaku]

proc /proc proc defaults 0 0
/dev/md/0 none swap sw 0 0
/dev/md/1 /boot ext3 defaults 0 0
/dev/md/2 / ext4 defaults 0 0
/dev/md/3 /home ext4 usrquota,errors=remount-ro 0 0

Sent you details

[JMSolo]

It looks like your quota service wasn’t set properly. I reset your mount and ran the setdisk command as root. Temporarily set the users disk quota to 5GB. Checked the dashboard and all looks well. Let me know if you have any other questions.

PS: I have logged out of your server and dashboard UI and tossed credentials. YOu may additionally delete them from the PM for added assurance.

Update

---

Looks like there is a particular bug in the arithmetic of the setdisk command. Any disk settings should be done in full arguments, i.e; 500GB, 4TB, 12TB etc. It will throw an error when a decimal is placed in the setting of the quota. Thus, 1.5TB, 6.8TB and on and on will issue an error. If 8.4TB is needed, then this value must be converted to GB, i.e; 8601GB.

A good online tool for conversion can be found here.

I will either work on including a script that can convert these values in a human readable way, or possibly include a means to actually convert these decimal values automagically when inserted.

Thanks @demonotaku for your time, your report and permitting me access to your server to reveal this.