From: Jan Kara <jack@suse.cz>
To: xfs@oss.sgi.com
Cc: hch@infradead.org
Subject: Quota tests for XFSQA
Date: Wed, 19 May 2010 01:36:13 +0200 [thread overview]
Message-ID: <1274225776-26987-1-git-send-email-jack@suse.cz> (raw)
Hi,
in this series are three tests I have written (basically gathered from
various scripts) for XFSQA. The test quota accounting and also limits
basic enforcement for VFS quotas (i.e. mainly ext? filesystems). Could
the tests be included?
I'd like to add two more tests (fsstress running under 'nobody' with quota
limits tightly set so that we get often EDQUOT failures) and a test where
setquota would be stressing addition and removal of quota structures.
Hopefully I'll get to it later this week.
Honza
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next reply other threads:[~2010-05-18 23:34 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-18 23:36 Jan Kara [this message]
2010-05-18 23:36 ` [PATCH 1/3] Test basic quota enforcement Jan Kara
2010-05-19 0:55 ` Dave Chinner
2010-05-18 23:36 ` [PATCH 2/3] Add test of quota accounting using fsx Jan Kara
2010-05-18 23:36 ` [PATCH 3/3] Add quota test with fsstress 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=1274225776-26987-1-git-send-email-jack@suse.cz \
--to=jack@suse.cz \
--cc=hch@infradead.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