From: Dave Chinner <david@fromorbit.com>
To: Brian May <brian@microcomaustralia.com.au>
Cc: 695640@bugs.debian.org, Ben Myers <bpm@sgi.com>
Subject: Bug#695640: xfs_quota: cannot find mount point for path: Success
Date: Wed, 20 Mar 2013 22:09:35 +1100 [thread overview]
Message-ID: <20130320110935.GE17758@dastard> (raw)
In-Reply-To: <CAA0ZO6AxFzinTv_COhK6GqnRpSiYW95otznKvYKiWZB5+=CyBg@mail.gmail.com>
On Wed, Mar 20, 2013 at 04:19:16PM +1100, Brian May wrote:
> On 19 March 2013 17:31, Dave Chinner <david@fromorbit.com> 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:
> >
>
> Hello,
>
> 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
command.
> 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....
Cheers,
Dave.
--
Dave Chinner
david@fromorbit.com
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2013-03-20 11:15 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-11 2:35 Bug#695640: xfs_quota: cannot find mount point for path: Success Brian May
[not found] ` <20121211221419.GZ27055@sgi.com>
[not found] ` <CAA0ZO6APzwQCX=yf=qq8NkmjwDHVsgRBNCgN3KNW3RLgAWB=8A@mail.gmail.com>
[not found] ` <20121211223700.GA27055@sgi.com>
[not found] ` <CAA0ZO6BOUXTMpdrR-r=__-ZaAM6X39h2SisYXLfTTraTcttr+g@mail.gmail.com>
[not found] ` <20121211231533.GG16353@dastard>
[not found] ` <CAA0ZO6BvLQGt_9G-FSi+ZMCzJh_kmb1z2bdoPPwaVMVVK1UXJw@mail.gmail.com>
2013-03-18 0:30 ` Brian May
2013-03-18 22:48 ` Dave Chinner
2013-03-19 4:51 ` Brian May
2013-03-19 6:31 ` Dave Chinner
2013-03-20 5:19 ` Brian May
2013-03-20 11:09 ` Dave Chinner [this message]
2013-04-17 23:38 ` Brian May
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20130320110935.GE17758@dastard \
--to=david@fromorbit.com \
--cc=695640@bugs.debian.org \
--cc=bpm@sgi.com \
--cc=brian@microcomaustralia.com.au \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox