# From Brian Smith

I recently ran into this issue with a customer of mine.  What happen 
is that the Quota database file got out of wack.  The fix is simple 
enough.  The "experts" recommend booting into single user mode to do 
the fix.  Some times that isn't feasible.  Other "experts" recommend 
shutting down services that access the "/home" partition (that is 
where quotas are enabled).

I did the fix with out booting single user and with out shutting down 
services.  BUT!!!!!  The box had 10 users on it, so it took just a few 
seconds.  If you have a fair amount of users sucking up space, I 
recommend single user mode, or shutting down services.

How ever you decide to do it, this "should" fix it.

Check the user's quota first:
  repquota /home | head -n5; repquota /home | grep USERNAMEHERE

Fix the quota issue:
  quotaoff -u /home/
  quotacheck /home/ -m
  quotaon -u /home/

Verify it fixed the problem
  repquota /home | head -n5; repquota /home | grep USERNAMEHERE

That command shows the header of the repquota output so that you know 
what each column name is.