From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-GB; rv:1.3) Gecko/20030314
Description of problem:
The messages log for this machine is logging two kinds of quota related errors.
.. kernel: VFS: Inserting already present quota entry (block 89).
.. kernel: VFS: Error -5 occured while creating quota.
.. kernel: VFS: Quota for id 2082 referenced but not present.
.. kernel: VFS: Can't read quota structure for id 2082.
The net effect seems to be that the users concerned have no quota on the system
and are therefore unregulated as to the disk space they use.
Trying to over-write the affected user's quota settings using "edquota -p" seems
to work initially, but does kick out a load of errors as (A) above.
If "quota -v <username>" is run straight away, the tables look complete, but if
this is repeated at intervals, the quota setting drop off the disks concerned
one by one, until the table is empty again. It can also be seen occasionally
that the entries can come back again on this same user with no additional
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Login as root
2. "edquota fred" (where fred is a user from a logged error)
3. Check /var/log/messages
4. Find another new logged error for that user.
Have done the usual searches (bugzilla, google etc) for similar problems, but
The machine has 1285 users configured, all of which are governed by quotas. The
highest UID on the system is 2263. The user whos UID is 2263 does not show this
Of the 1200+ users on the system, less than 10 exhibit this problem.
I am unsure as to how long this has been a problem, as it predates the saved log
files for this machines and does not occur on any of the other machines I have
I am unsure as to whether this problem occurs on the later kernels for this OS
version. There is a scheduled reboot planned to bring in the latest kernel.
Thanks for the bug report. However, Red Hat no longer maintains this version of
the product. Please upgrade to the latest version and open a new bug if the problem
The Fedora Legacy project (http://fedoralegacy.org/) maintains some older releases,
and if you believe this bug is interesting to them, please report the problem in
the bug tracker at: http://bugzilla.fedora.us/