From: Eric Sandeen <sandeen@sandeen.net>
To: Jan Kara <jack@suse.cz>
Cc: hch@infradead.org, ext4 development <linux-ext4@vger.kernel.org>,
xfs@oss.sgi.com
Subject: Re: [PATCH 4/8] Add test of quota accounting using fsx
Date: Mon, 26 Jul 2010 16:46:17 -0500 [thread overview]
Message-ID: <4C4E0229.5040002@sandeen.net> (raw)
In-Reply-To: <20100615095505.GB3347@quack.suse.cz>
On 06/15/2010 04:55 AM, Jan Kara wrote:
> On Wed 09-06-10 12:49:49, Eric Sandeen wrote:
>> 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...
> OK, attached is an improvement to the XFSQA tests after which all quota
> tests pass for XFS just fine.
> The second patch is just minor general improvement of _require_scratch
> macro.
> Could they be added to XFSQA repository? Thanks.
Jan, I've got some ext4 failures reported on these, although I can't hit
them, so not quite sure what's going on.
In 231:
+< fsgqa -- 760 0 0 3 0 0
+---
+> fsgqa -- 764 0 0 3 0 0
+14c14
+< fsgqa -- 760 0 0 3 0 0
+---
+> fsgqa -- 764 0 0 3 0 0
after the quotacheck & repquota we have 4 more blocks. Maybe this
is due to my accounting of metadata blocks at write time, and not
before ... would it be reasonable to put a sync call as the first
line of check_usage() ?
Also in 233:
+< #501 -- 15392 0 0 998 0 0
+< #501 -- 15392 32000 32000 998 1000 1000
+---
+> #501 +- 32084 32000 32000 7days 998 1000 1000
+> #501 -- 32084 0 0 998 0 0
"7days" magically appeared after the quotacheck. Not sure what's going
on there...
Thanks,
-Eric
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2010-07-26 21:43 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
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 [this message]
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=4C4E0229.5040002@sandeen.net \
--to=sandeen@sandeen.net \
--cc=hch@infradead.org \
--cc=jack@suse.cz \
--cc=linux-ext4@vger.kernel.org \
--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