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: Tue, 19 Mar 2013 17:31:04 +1100 [thread overview]
Message-ID: <20130319063104.GA6369@dastard> (raw)
In-Reply-To: <CAA0ZO6BVwPP9McKA=vn1+21gHpRCQP9P963nsSjY_zXHWeszrg@mail.gmail.com>
On Tue, Mar 19, 2013 at 03:51:30PM +1100, Brian May wrote:
> On 19 March 2013 09:48, Dave Chinner <david@fromorbit.com> wrote:
>
> > > Did my strace output help diagnose this bug?
> >
> > No, but it's most likely the same problem as fixed in commit
> > 19473a2ac. Can you add this to quota/quot.c:quot_init():
> >
> > + quot_cmd.flags = CMD_FLAG_GLOBAL;
> >
> > And see if the problem goes away?
> >
>
> I made this change to the version in Debian squeeze.
>
> I didn't see any change in behaviour :-(
>
> hq ~ # xfs_quota -x -c "quota -N -u brian" /home
> xfs_quota: cannot find mount point for path `/share/systems': Success
> xfs_quota: cannot find mount point for path `/share/cs': Success
> xfs_quota: cannot find mount point for path `/share/cas': Success
> xfs_quota: cannot find mount point for path `/share/cfcp': Success
> xfs_quota: cannot find mount point for path `/share/lgs': Success
> xfs_quota: cannot find mount point for path `/share/common': Success
> xfs_quota: cannot find mount point for path `/share/summer': Success
> /dev/mapper/hq-home 3800752 0 0 00 [--------] /home
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:
# xfs_quota -x -c "quota -N -u brian"
or
# xfs_quota -x -c "quota -N -u brian" /home /share
will not output the error message because xfs_quota knows about the
locations of the project quotas.
Yes, it's not obvious what is happening here but technically it
isn't a bug, either, because you told xfs_quota not to load
information about any other mountpoint.
I'll have a think about how to make this output less .... obtuse.
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-19 6:33 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 [this message]
2013-03-20 5:19 ` Brian May
2013-03-20 11:09 ` Dave Chinner
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=20130319063104.GA6369@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