From: "Michael L. Semon" <mlsemon35@gmail.com>
To: xfs@oss.sgi.com
Subject: Rambling noise #2: Learning to use the v8 pquota/uquota patchset
Date: Tue, 14 May 2013 04:52:22 -0400 [thread overview]
Message-ID: <5191FB46.2080300@gmail.com> (raw)
Hi! I seem to have no luck in getting v8 of the pquota/uquota patchset
working and have it pass xfstests with flying colors. Is v8 of the
pquota/gquota patchset sufficient to make the new separate pquota/gquota
bits work? Or is it an incremental patchset?
The basic functionality works, in my opinion, and I hope nobody wastes
time with a nice, educated reply. It would be mostly wasted on me and
is better saved for somebody else. A reply of "do this...and
this...btw, how did this test come out?" would be welcomed, though ;-)
Anyway, some vague observations as I grasp for straws...
1) The xfstests quota group tests seem to fail in different ways than
the way they did before applying the patches.
2) Nothing has oopsed.
3) In testing using the `xfs_quota -x` command, the patches seem to
work. On `mount -t xfs -o gquota` mounts, using the quota command from
within the xfs_quota shell, the group quotas show but not the projid
quotas. On `mount -t xfs -o pquota` mounts, the projid quotas show but
not the gquota mounts. This is different than the old behavior, where
the gquota numbers might be recycled into projid numbers.
4) The results of `xfsquota -c print` are confusing. Maybe they're
showing the XFS view when they show things like
'uqnoenforce,gquota,pquota' for a mount that is gquota only. They're
doubly confusing once /etc/projid and /etc/projects have been set up.
The 'gqnoenforce' and 'pqnoenforce' flags show up at times for reasons
that are unknown to me.
5) `mount -t xfs -o gquota,pquota` is not possible at this time.
6) The patches applied cleanly to a git Linux 3.10-rc1 kernel + xfs-oss,
with only whitespace errors reported.
7) I question whether 'bsoft=' has a visible effect on projid quotas,
whether using your patches or not. Did it ever work?
8) I had no feel on whether the filesystem had to be mounted once as
gquota, then once as pquota, for the full dual functionality to work.
9) It looks like xfs_repair doesn't ruin anything, but the `xfsquota -c
print` output looks a little different on the next mount.
That's about all that could be put together in a coherent manner. Sleep
awaits.
The PC is a 32-bit Pentium 4. In addition to the kernel mentioned in
(6), there are a few J. Liu and Dave Chinner patches applied as well.
Best of luck!
Michael
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next reply other threads:[~2013-05-14 8:52 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-14 8:52 Michael L. Semon [this message]
2013-05-14 13:52 ` Rambling noise #2: Learning to use the v8 pquota/uquota patchset Jeff Liu
2013-05-14 17:01 ` Michael L. Semon
2013-05-15 7:13 ` Michael L. Semon
2013-05-15 13:16 ` Jeff Liu
2013-05-15 21:43 ` Dave Chinner
2013-05-15 20:41 ` Chandra Seetharaman
2013-05-15 21:56 ` Michael L. Semon
2013-05-15 22:12 ` Chandra Seetharaman
2013-05-15 21:01 ` Chandra Seetharaman
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=5191FB46.2080300@gmail.com \
--to=mlsemon35@gmail.com \
--cc=xfs@oss.sgi.com \
/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