Bug 8896 - warnquota problem
Summary: warnquota problem
Alias: None
Product: Red Hat Linux
Classification: Retired
Component: quota
Version: 6.1
Hardware: i386
OS: Linux
Target Milestone: ---
Assignee: Preston Brown
QA Contact:
: 7898 (view as bug list)
Depends On:
TreeView+ depends on / blocked
Reported: 2000-01-26 14:24 UTC by ulrich
Modified: 2008-05-01 15:37 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Last Closed: 2000-07-27 22:19:23 UTC

Attachments (Terms of Use)

Description ulrich 2000-01-26 14:24:46 UTC
I have enabled user and group quotas on /home
(long time before i upgrade to redhat 6.1), and
/usr/sbin/warnquota is running daily by crontab script.

Since i have upgraded from redhat 5.2 to 6.1 the
root user gets quota warnings every night via mail,
but root user has no quotas.

Other users dont get any mail if the are in violation
with the quota system.

Here is one warnquota mail:

Subject: Disk Quota usage on system


We noticed that you are in violation with the quotasystem
used on this system. We have found the following violations:

                        Block limits               File limits
Filesystem           used    soft    hard  grace    used  soft  hard  grace
/dev/sdd1      --  101344       0       0           3608     0     0

We hope that you will cleanup before your grace period expires.

Basically, this means that the system thinks you are using more disk space
on the above partition(s) than you are allowed.  If you do not delete files
and get below your quota before the grace period expires, the system will
prevent you from creating new files.

For additional assistance, please contact us at support@localhost or via
phone at (xxx) xxx-xxxx or (xxx) xxx-xxxx.

Comment 1 Jeff Johnson 2000-07-27 22:19:21 UTC
*** Bug 7898 has been marked as a duplicate of this bug. ***

Comment 2 Preston Brown 2001-02-01 23:14:40 UTC
This seems to work fine with the quota available in 6.2 and later.

Note You need to log in before you can comment on or make changes to this bug.