public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: "Michael L. Semon" <mlsemon35@gmail.com>
To: sekharan@us.ibm.com
Cc: xfs@oss.sgi.com
Subject: Re: Rambling noise #2: Learning to use the v8 pquota/uquota patchset
Date: Wed, 15 May 2013 17:56:48 -0400	[thread overview]
Message-ID: <519404A0.3030401@gmail.com> (raw)
In-Reply-To: <1368650489.10223.5.camel@chandra-dt.ibm.com>

On 05/15/2013 04:41 PM, Chandra Seetharaman wrote:
> On Tue, 2013-05-14 at 04:52 -0400, Michael L. Semon wrote:
>> 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?
>
> Hi Michael,
>
> I will post the user level changes that accompanies these changes.
>
> With those changes you can do a new mkfs and use pquota and gquota
> together.
>
> Regards,
>
> Chandra

Excellent!

As for the rest of your issues, I'll have to retest very slowly using 
your new userspace patches, documenting every step in order.  It will 
also require before/after runs of xfstests.

I do not know what your patches do for filesystems that already had 
quota on them, so I ask you to check one thing.  It looked like the 
result of the normal `quota` command was having issues.  On my root 
filesystem that was mounted uquota only, the following is the normal 
behavior (as an ordinary user):

mls:~$ quota
Disk quotas for user mls (uid 3001):
      Filesystem  blocks   quota   limit   grace   files   quota   limit 
   grace
       /dev/sda1  165955  262144  327680            2345    8194   16384

However, before I switched out kernels here, such a command just left a 
blank, as if there was no quota there.  If you would at that to your 
list of spot-check tests, that would be great.  It might work fine for 
you.  [For the same situation, `xfs_quota -c quota /` worked just fine.]

You're leading a blind man in the dark, so I thank you for your patience.

Michael

_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs

  reply	other threads:[~2013-05-15 21:57 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-05-14  8:52 Rambling noise #2: Learning to use the v8 pquota/uquota patchset Michael L. Semon
2013-05-14 13:52 ` 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 [this message]
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=519404A0.3030401@gmail.com \
    --to=mlsemon35@gmail.com \
    --cc=sekharan@us.ibm.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