Too Low or 0.00 Disk Usage in DirectAdmin

To verify the partition on our server, must run the next instructions.

df -h

The consequence would rely upon what sort of partition we used on the server. If the server having an /residence partition, then your quota_partition worth might be /residence.

If it was not, then will probably be /, so your quota partition will possible be /.

In some circumstances, you may need a symbolic hyperlink like: /residence –> /usr/residence. In such circumstances, your quota might be identical as above /usr.

Set the partition worth right here, as wanted: /residence

To verify how a lot house is consumed by the system, DirectAdmin will run the next:

/usr/sbin/repquota /residence

NOTE: repquota is a command used to print the general abstract of the server disk utilization and quotas for the required file system.

The place /house is the quota_partition worth being set within the /usr/native/directadmin/conf/directadmin.conf file. (Similar to above examples: /residence, / or /usr ). Then it should return the consequence with a listing of numbers, instance:

/usr/sbin/repquota /residence

*** Report for consumer quotas on machine /dev/hda3

Block grace time: 7days; Inode grace time: 7days

Block limits                File limits

Person            used    comfortable    laborious  grace    used  comfortable  laborious  grace

———————————————————————-

root      —  417796       0       0           7446     0     0

no one    —       4       0       0              1     0     0

bin       —   56880       0       0            510     0     0

majordomo —       8       0       0              2     0     0

diradmin  —       8       0       0              2     0     0

admin     —     200       0       0             44     0     0

consumer123   —     100       0       0             22     0     0

consumer456   —     100       0       0             22     0     0

If the second column ” used ” shouldn’t be displaying something or customers usually are not within the record. Then we are able to run the next quotacheck command.

On Redhat:

 /sbin/quotaoff -a; /sbin/quotacheck -avugm; /sbin/quotaon -a;

FreeBSD:

/usr/sbin/quotaoff -a; /sbin/quotacheck -avug; /usr/sbin/quotaon -a;

If the repquota throwing errors then we have to verify in deeply this with the filesystem /and many others/fstab file, will probably be created mechanically as soon as the OS is put in. At any time when modifications occur on the filesystem will probably be modified mechanically. To verify with this, want to make sure that it incorporates rw, userquota, groupquota line beside the partition that’s utilizing the quotas.

For an instance:

# Gadget                Mountpoint      FStype  Choices            Dump    Move#

/dev/ad0s1a             /residence           ext3     rw,usrquota,grpquota 1       1

/dev/ad0s1e             /tmp            ext3     rw                 2       2

proc                    /proc           procfs   rw                 0       0

On this case, the quota_partition is /residence primarily based on server configuration. Perhaps it should / or /usr in your system.

Or if it was reveals, you might take into account switching to journaled quota to keep away from operating quotacheck after an unclean shutdown:

In that case, as a substitute of “,usrquota,rpquota”, add “,usrjquota=aquota.consumer,grpjquota=aquota.group,jqfmt=vfsv0” to your fstab file.

As soon as the repquota program is returning a standard worth, then you possibly can run the tally to get the proper utilization to point out up in DirectAdmin:

echo “motion=tally&worth=all” >> /usr/native/directadmin/knowledge/activity.queue

This activity.queue command will get picked up by the dataskq binary.   It calls the repquota command and dumps it into /residence/tmp/quota-dump.

Verify /var/log/directadmin/errortaskq.log for any errors with this.

Operating the tally manually for a Person also can assist with debugging these points.

Should you want any additional assist, please do attain our assist division.