On Fri, 13 Apr 2001, Matt Simerson wrote:
> Actually, I believe it reports based upon the contents of the BLOCKSIZE
> environment variable which is 1k or 1024 bytes for the purposes of this
> discussion. In either case, you'll notice that the reporting shown below
> accurately shows that the users quota is very near the limit and the quota
> is set at 350MB.
>
> Interestingly enough, I added check_quotas="YES" to /etc/rc.conf and
> rebooted. That fixed that users quota problem. I'm not sure if it was the
> rebooting (and clearing the kernels idea of what the quota should be) or if
> running quotacheck in single user mode did it. I have to guess the former
> because quotacheck's results should not vary dependent on whether the
> machine is single user or not.
A while ago, I wanted to be sure that quotas were working and did some
tests (on 3.4 release I think). In general, they worked as expected,
except that when root changed a file's ownership, the quotas did not
seem to reflect the change.
I thought this was fixed in 4.x (when I did some more tests), but maybe
this is still an issue? Are there file ownership changes going on?
Another thought is that this user may have had files still open. Even
if you "remove" a file, it really does not go away until the last open
handle is closed.
All the best,
-Richard
-------------------------------------------
Richard Hodges | Matriplex, inc.
Product Manager | 769 Basque Way
[EMAIL PROTECTED] | Carson City, NV 89706
775-886-6477 | www.matriplex.com
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
