public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Eric Sandeen <sandeen@sandeen.net>
To: Jan Kara <jack@suse.cz>
Cc: hch@infradead.org, xfs@oss.sgi.com
Subject: Re: [PATCH 4/8] Add test of quota accounting using fsx
Date: Wed, 09 Jun 2010 12:49:49 -0500	[thread overview]
Message-ID: <4C0FD43D.3040803@sandeen.net> (raw)
In-Reply-To: <1274710459-11446-5-git-send-email-jack@suse.cz>

Jan Kara wrote:
> Run fsx (and also several fsx threads in parallel) and verify that
> quota accounting is correct after they finish.

Jan, I'm having trouble with this one on XFS for some reason, with our 
RHEL6 kernel and quota-3.17...

+Disabling group quota enforcement and accounting on /dev/mapper/VolGroup00-testvol2
+Disabling user quota enforcement and accounting on /dev/mapper/VolGroup00-testvol2
+repquota: Mountpoint (or device) /mnt/testarea/scratch not found or has no quota enabled.
+repquota: Not all specified mountpoints are using quota.
+repquota: Mountpoint (or device) /mnt/testarea/scratch not found or has no quota enabled.
+repquota: Not all specified mountpoints are using quota.

...

however if I remove the quotaon calls (off / on settings) in check_usage()
then it works:

check_usage()
{
        # quotaon -f -u -g $SCRATCH_MNT 2>/dev/null
        repquota -u -g $SCRATCH_MNT  | grep -v "^root" | filter_scratch \
                >$tmp.orig
        quotacheck -u -g $SCRATCH_MNT 2>/dev/null
        repquota -u -g $SCRATCH_MNT  | grep -v "^root" | filter_scratch \
                >$tmp.checked
        # quotaon -u -g $SCRATCH_MNT 2>/dev/null
        diff $tmp.orig $tmp.checked
}


Seems like 2 issues: noisy disable messages, and repquota failing when disabled.

Any ideas?

Thanks,
-Eric

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

  reply	other threads:[~2010-06-09 17:47 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-05-24 14:14 [PATCH 0/8 v3] Quota tests for XFSQA Jan Kara
2010-05-24 14:14 ` [PATCH 1/8] Fix test whether kernel supports quotas Jan Kara
2010-05-24 14:14 ` [PATCH 2/8] Fix fallocate() test Jan Kara
2010-05-24 14:14 ` [PATCH 3/8] Test basic quota enforcement Jan Kara
2010-05-25 10:06   ` Christoph Hellwig
2010-05-25 14:41     ` Jan Kara
2010-05-25 20:39     ` Jan Kara
2010-05-27 16:30       ` Christoph Hellwig
2010-05-27 17:08         ` Jan Kara
2010-05-24 14:14 ` [PATCH 4/8] Add test of quota accounting using fsx Jan Kara
2010-06-09 17:49   ` Eric Sandeen [this message]
2010-06-10 10:58     ` Jan Kara
2010-06-10 16:50       ` Eric Sandeen
2010-06-10 20:43         ` Eric Sandeen
2010-06-14 12:46           ` Jan Kara
2010-06-14 10:48         ` Jan Kara
2010-06-15  9:55     ` Jan Kara
2010-07-26 21:46       ` Eric Sandeen
2010-07-27  8:15         ` Jan Kara
2010-07-27  8:48           ` Jan Kara
2010-07-27 13:11             ` Eric Sandeen
2010-05-24 14:14 ` [PATCH 5/8] Add quota test with fsstress Jan Kara
2010-05-24 14:14 ` [PATCH 6/8] Add quota accounting test when fsstress is run and quota limits are set low Jan Kara
2010-05-24 14:14 ` [PATCH 7/8] Add test of quota limit and info setting Jan Kara
2010-05-24 14:14 ` [PATCH 8/8] Add test for quota accounting after remount read only Jan Kara

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=4C0FD43D.3040803@sandeen.net \
    --to=sandeen@sandeen.net \
    --cc=hch@infradead.org \
    --cc=jack@suse.cz \
    --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