From: Josef Bacik <josef@redhat.com>
To: xfs@oss.sgi.com
Subject: [PATCH] Xfstests: make _scratch_mkfs_sized work for btrfs
Date: Tue, 30 Nov 2010 16:50:39 -0500 [thread overview]
Message-ID: <1291153839-12317-1-git-send-email-josef@redhat.com> (raw)
This patch simply makes _scratch_mkfs_sized work right for btrfs. I've run a
few of the tests that use _scratch_mkfs_sized (204 and 226) and everything seems
to work right now. Thanks,
Signed-off-by: Josef Bacik <josef@redhat.com>
---
common.rc | 3 +++
1 files changed, 3 insertions(+), 0 deletions(-)
diff --git a/common.rc b/common.rc
index 459bdf5..58e7318 100644
--- a/common.rc
+++ b/common.rc
@@ -329,6 +329,9 @@ _scratch_mkfs_sized()
ext2|ext3|ext4)
/sbin/mkfs.$FSTYP $MKFS_OPTIONS -b $blocksize $SCRATCH_DEV $blocks
;;
+ btrfs)
+ /sbin/mkfs.$FSTYP $MKFS_OPTIONS $SCRATCH_DEV -b $fssize
+ ;;
*)
_notrun "Filesystem $FSTYP not supported in _scratch_mkfs_sized"
;;
--
1.6.6.1
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next reply other threads:[~2010-11-30 21:58 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-30 21:50 Josef Bacik [this message]
2010-11-30 22:26 ` [PATCH] Xfstests: make _scratch_mkfs_sized work for btrfs Christoph Hellwig
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=1291153839-12317-1-git-send-email-josef@redhat.com \
--to=josef@redhat.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