From: Jan Kara <jack@suse.cz>
To: Christoph Hellwig <hch@infradead.org>
Cc: Jan Kara <jack@suse.cz>, linux-fsdevel@vger.kernel.org
Subject: Re: quota tests
Date: Tue, 6 Sep 2011 16:50:54 +0200 [thread overview]
Message-ID: <20110906145054.GF23747@quack.suse.cz> (raw)
In-Reply-To: <20110906144334.GE23747@quack.suse.cz>
On Tue 06-09-11 16:43:34, Jan Kara wrote:
> On Tue 06-09-11 08:21:16, Christoph Hellwig wrote:
> > do you have some quota test scripts? I've noticed that the quota
> > testing in xfstests really isn't as good as it should be and I'm
> > looking for more existing tests I can integrated before writing new
> > ones from scratch.
> All I had (well, except a tool which verifies sanity of quotactl syscall
> but that's out of scope for xfstests I'd say) is already integrated into
> xfstests.
>
> We have test 219 which tests whether quota measures something sane.
> Test 230 tries to exceed various quota limits and checks that it fails
> roughly at the right moment.
> Tests 231 and 232 check that if we stress the filesystem (fsx, fsstress),
> the resulting quota usage is indeed what we get when we sum up the usage
> using quotacheck (which is worthless for XFS but for ext? filesystems this
> is really useful).
> Test 233 checks running fsstress with quotas set low so that we often hit
> EDQUOT. We also verify that usage matches what quotacheck gets.
> Finally test 234 stresses operations on top of quota files by adding and
> removing quota structures by setquota from several processes.
Oh, and we have test 235 which checks whether quota gets properly
suspended during remount read-only and reenabled during remount read-write.
Honza
--
Jan Kara <jack@suse.cz>
SUSE Labs, CR
prev parent reply other threads:[~2011-09-06 14:50 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-06 12:21 quota tests Christoph Hellwig
2011-09-06 14:43 ` Jan Kara
2011-09-06 14:50 ` Christoph Hellwig
2011-09-06 15:12 ` Jan Kara
2011-09-06 15:15 ` Christoph Hellwig
2011-09-06 14:50 ` Jan Kara [this message]
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=20110906145054.GF23747@quack.suse.cz \
--to=jack@suse.cz \
--cc=hch@infradead.org \
--cc=linux-fsdevel@vger.kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).