From: Jeff Liu <jeff.liu@oracle.com>
To: "xfs@oss.sgi.com" <xfs@oss.sgi.com>
Subject: [PATCH v2 0/4] xfstests: introduce xfs tests 304/305 to verify turn quota/project quota off
Date: Tue, 03 Dec 2013 19:58:27 +0800 [thread overview]
Message-ID: <529DC763.8000007@oracle.com> (raw)
Hi Folks,
Here is the 2nd version for introducing two new xfs specified tests to verify that
we can turn group/project quotas off while user quota is on and fsstress is running.
As a preparation step, the 1st patch is trying to introduce a couple of pre-checkup
routines to verify that if mkfs.xfs and kernel are have crc feature or not as per
Dave's comments.
v1->v2:
- Introduce _require_xfs_mkfs_crc to verify if mkfs.xfs have crc feature or not
- Introduce _require_xfs_crc to verify if xfs kernel have crc feature or not
- xfs/299, remove v5 super block number "5" from golden output file
- Re-number both test cases to xfs/304 and xfs/305 separately
- Redirect "Version 5 superblock detected. xfsprogs has EXPERIMENTAL support enabled!
Use of these features is at your own risk!" to /dev/null from mkfs.xfs for all those
changes.
Thanks,
-Jeff
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
reply other threads:[~2013-12-03 11:58 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=529DC763.8000007@oracle.com \
--to=jeff.liu@oracle.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