Bug 27310 - Quotas turned on during boot up when quota isn't used
Quotas turned on during boot up when quota isn't used
Product: Red Hat Linux
Classification: Retired
Component: initscripts (Show other bugs)
i386 Linux
medium Severity medium
: ---
: ---
Assigned To: Bill Nottingham
David Lawrence
Depends On:
  Show dependency treegraph
Reported: 2001-02-12 19:37 EST by Mike Chambers
Modified: 2014-03-16 22:18 EDT (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2001-02-12 19:37:58 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Mike Chambers 2001-02-12 19:37:54 EST
From Bugzilla Helper:
User-Agent: Mozilla/4.0 (compatible; MSIE 5.5; Windows NT 5.0)

No matter if using the installed kernel, or upgrading via redhat update, 
or compiling 2.4.x, you get the user and group quotas turned on message 
even if it wasn't compiled into the kernel.  You also get the message even 
if it was and no quota set up.

Reproducible: Always
Steps to Reproduce:

Actual Results:  Feb 11 22:55:23 linux rc.sysinit: Turning on user and 
group quotas for local filesystems:  succeeded

Expected Results:  If quotas aren't used, you shouldn't see any quota 
messages unless configured to do so.

I don't use quotas on my machine, and haven't configured anything to use 
them, so therefore shouldn't see any messages about quotas.

If quota is compiled to the kernel, but not used, maybe you shouldn't see 
the message, or see it but changed to not being used or something.
Comment 1 Bill Nottingham 2001-02-12 19:43:02 EST
Changing it to check for whether they are enabled requires parsing the
fstab to find all the filesystems, and then look at each filesystem's
contents to determine if quotas are enabled for that particular filesystem.
It's faster/more efficient to just leave it the way it is; it doesn't
actually harm anything.

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