Red Hat Bugzilla – Bug 198301
xfs root filesystem quota problem
Last modified: 2008-05-06 12:06:18 EDT
Description of problem:
The finished initrd image does not seem to support the rootflags= option
required for quota when / is XFS.
Version-Release number of selected component (if applicable):
Adding rootflags=usrquota,grpquota to the kernel boot line has no effect.
No quota activated on /
Should have activated quota on xfs /.
initrd scripts (distro-independent) go like this:
mount /, mostly indicated by root= option or by some other trick
look at /etc/fstab
remount / using the flags in /etc/fstab
This does not work for XFS because activating quota must be done on _the very
first_ mount and is rejected with an error is attempted later. This is why
rootflags= must be used. In environments where kernels with no initrd are used,
the kernel passed rootflags= directly to the xfs code; in environments where
initrds are employed, the initrd scripts must parse it out and pass to the first
mount command (when mounting / readonly).
The latter (parsing rootflags= in initrd) is not supported.
Why can't this just be set in fstab like with other filesystem parameters?
Because, the filesystem that contains fstab must _already_ be mounted using usrquota and/or grpquota, even if it is just mounted read-only.
Peter, essentially quotas on xfs are not a remountable option, IIRC.
Fedora apologizes that these issues have not been resolved yet. We're
sorry it's taken so long for your bug to be properly triaged and acted
on. We appreciate the time you took to report this issue and want to
make sure no important bugs slip through the cracks.
If you're currently running a version of Fedora Core between 1 and 6,
please note that Fedora no longer maintains these releases. We strongly
encourage you to upgrade to a current Fedora release. In order to
refocus our efforts as a project we are flagging all of the open bugs
for releases which are no longer maintained and closing them.
If this bug is still open against Fedora Core 1 through 6, thirty days
from now, it will be closed 'WONTFIX'. If you can reporduce this bug in
the latest Fedora version, please change to the respective version. If
you are unable to do this, please add a comment to this bug requesting
Thanks for your help, and we apologize again that we haven't handled
these issues to this point.
The process we are following is outlined here:
We will be following the process here:
http://fedoraproject.org/wiki/BugZappers/HouseKeeping to ensure this
doesn't happen again.
And if you'd like to join the bug triage team to help make things
better, check out http://fedoraproject.org/wiki/BugZappers
This bug is open for a Fedora version that is no longer maintained and
will not be fixed by Fedora. Therefore we are closing this bug.
If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen thus bug against that version.
Thank you for reporting this bug and we are sorry it could not be fixed.