From owner-freebsd-isp Tue Oct 14 11:41:29 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id LAA09109 for isp-outgoing; Tue, 14 Oct 1997 11:41:29 -0700 (PDT) (envelope-from owner-freebsd-isp) Received: from eharden.com (eharden.com [207.193.60.129]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id LAA09100 for ; Tue, 14 Oct 1997 11:41:23 -0700 (PDT) (envelope-from bad@uhf.wireless.net) Received: from uhf.wireless.net (pp8.eharden.com [207.193.60.154]) by eharden.com (8.8.7/8.8.5) with ESMTP id NAA15663; Tue, 14 Oct 1997 13:45:03 -0500 (CDT) Received: from localhost (bad@localhost) by uhf.wireless.net (8.8.7/8.8.7) with SMTP id OAA04955; Tue, 14 Oct 1997 14:42:46 -0400 (EDT) Date: Tue, 14 Oct 1997 14:42:44 -0400 (EDT) From: Bernie Doehner To: Cliff Addy cc: Alexander Litvin , freebsd-isp@FreeBSD.ORG Subject: Re: Quota and Mail Spool Files In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-isp@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Just a quick comment. When I was running 2.2.2-R, after a particular bad system crash, quota.user and quota.group on my quota'ed drive become corruped (one of them actualy grew to about 200MB), and also reported abnormal/incorrect values. What size are your quota.user and quota.group files? I assume you are running quotacheck -a from /etc/rc? Bernie > No, the quota system is indisputably broken. We've had continuous > problems with it not enforcing quotas and incorrectly reporting usage. > For example, I have a brand-new user that repquota claims is more than > 100% over quota with no grace period left: > > tootim +- 127264 40960 51200 none 325 0 0 > > yet this user only has 365K in their directory. A find on the drive shows > no other files owned by them. And they are perfectly able to upload and > create new files. > > Numerous posts on the subject have resulted in no responses. I'd say the > only way to help with your problem is to hack mail.local to specifically > stat the mail spool of the user and reject it if it's too large. > >