"blocks" is the current usage for that user in blocks of 1Kb. Note that this can be more or less than what du reports for a user's home dir because the user may own files located in other drirectories or not all of the files in their home dir may be owned by them.

In this case du reports 100Mb, but repquota for that user only shows 66.24Mb. This indicates that some of the data in /var/www/html/mark is owned by someone else. To set a 500Mb limit you'd set say 450000 for the soft limit and 500000 for the hard limit.

Restore full virtual machine or individual guest files from 19 common file systems directly from the backup file. Schedule VM backups with PowerShell scripts. Set desired time, lean back and let the script to notify you via email upon completion.

To answer some of your questions yes i've rebooted with the fstab changes

i tried this to turn on quotas but it only works for the /dev/hdc3 swap partition
if i try with my main partition i get this

quotaon /dev/hdc2

quotaon: /dev/hdc2 not found in fstab

>>Note that this can be more or less than what du reports for a user's home dir because the user may own files located in other drirectories or not all of the files in their home dir may be owned by them.

Yes this is another problem as i have placed the sites entire new users under thier Group id into his main folder so everytime he adds a user in webmin for his mail they get mail stored in the a subroot of his folder.
this is why i want to allow him 500mb where right now its at 100mb

Now that seems wierd. Your quotaon seems to be from 3.01, but the version furnished with RH 9 is 3.06. And I'm pretty sure that I remember it as supporting the -p option. Is this quota package one that you added to the system, and if so from where?

/usr/bin/quotaon -a -p
-bash: /usr/bin/quotaon: No such file or directory
[root@s root]# /sbin/quotaon -a -p
group quota on / (/dev/hdc2) is off
user quota on / (/dev/hdc2) is off
group quota on /boot (/dev/hdc1) is off
user quota on /boot (/dev/hdc1) is off
[root@s root]# /sbin/quotaon /
[root@s root]# /sbin/quotaon -a -p
group quota on / (/dev/hdc2) is on
user quota on / (/dev/hdc2) is on
group quota on /boot (/dev/hdc1) is off
user quota on /boot (/dev/hdc1) is off
[root@s root]#

-- man quotacheck ---
-f Forces checking and writing of new quota files on filesystems
with quotas enabled. This is not recommended as the created
quota files may be out of sync.
-------
So don't use -f.

While it is possible for the information in the quota files to get out of sync with usage, in my experience this hasn't been a big problem. And, given the amount of caching that occurs on an EXT3 file system and the fact that your quotas are on the root file system, the safest approach would be a reboot occasionally to force an update of the quota files since the root file system can't be remounted in read-only mode during the quotacheck.

I'd suggest printing out the quota usage (repquota), reboot, and comparing usage maybe after a week or so to see if you have a problem. If there aren't any serious differences across a reboot wait about a month and check again. From doing that a few times you'll be able to determine if this is something that needs regular attention.

What I'm recommending is that you not attempt to run quotacheck from cron. First, in a safe way, find out if you have a problem with quota's getting out of sync with usage as I suggested above. If it turns out that you do have a problem you can then investigate how best to solve it.