On Wed, Mar 20, 2013 at 04:19:16PM +1100, Brian May wrote:
> On 19 March 2013 17:31, Dave Chinner <david@xxxxxxxxxxxxx> wrote:
> > Which tells me exactly what is happening.
> > The project quotas are not on the filesystem you directed the the
> > quota command at, and xfs_quota is telling you that it can't find
> > the mount point for the configured project quotas on /home. Either:
> Thanks for your response.
> I am kind of confused still. I asked for user quotas, with the -u flag. Why
> should it be trying to lookup project quotas?
Because the quota command does mount point and project quota
initialisation (i.e. global state) before it parses any specific
> I only want to get the report of user quotas. I only want to get the report
> for one filesystem. A filesystem that
> doesn't support project quotas, which should be fine because I am not
> asking for project quotas.
The issues project quota configuration is global information, and
the initialisation code is not aware of the fact that:
a) you are not asking for project quota information; and
b) you are not asking for information about a mount point
that doesn't have any project quotas on it.
> > # xfs_quota -x -c "quota -N -u brian"
> This prints the quota information 20 times. Huh?
How many mount points do you have? 20?
> > or
> > # xfs_quota -x -c "quota -N -u brian" /home /share
> This prints the quota information 2 times. Huh?
The command has once for each of the mount points, and the command
itself iterates mount points because you haven't given it a mount
point to look at. So, double iteration. This same problem was fixed
for the report command by setting it to be a global command i.e. the
fix I mentioned previously that you tested should prevent this
second case, and maybe even the first.
There are several layers of interactions here, and that's why I need
to have a think about it to understand it fully and fix it....