From: Rich Johnston <rjohnston@sgi.com>
To: Josef Bacik <jbacik@fusionio.com>, <linux-btrfs@vger.kernel.org>,
<xfs@oss.sgi.com>
Subject: Re: [PATCH 5/8] xfstests: generic/274 increase scratch fs size to 2g
Date: Tue, 22 Oct 2013 15:25:51 -0500 [thread overview]
Message-ID: <5266DF4F.8010403@sgi.com> (raw)
In-Reply-To: <1382120790-31060-5-git-send-email-jbacik@fusionio.com>
Patch does not apply, already committed.
Thanks
--Rich
commit 859f127da2ee6d49faa41cafd4ed362aa526e4a0
Author: Josef Bacik <jbacik@fusionio.com>
Date: Fri Jun 21 20:31:10 2013 +0000
xfstests: make fs for 274 larger
Btrfs will default to mixed block groups for 1 gigabyte file
systems and
smaller, which means data and metadata share the same area. This makes
generic/274 fail for us because we cannot reserve enough metadata
space to do
our writes. Bumping the scratch fs up to 2 gigabytes allows us to
do our normal
metadata/data separation and allows us to pass this test. Thanks,
Signed-off-by: Josef Bacik <jbacik@fusionio.com>
Reviewed-by: Ben Myers <bpm@sgi.com>
Signed-off-by: Rich Johnston <rjohnston@sgi.com>
diff --git a/tests/generic/274 b/tests/generic/274
index da45fab..7c4887f 100755
--- a/tests/generic/274
+++ b/tests/generic/274
@@ -57,7 +57,7 @@ echo "------------------------------"
rm -f $seqres.full
umount $SCRATCH_DEV 2>/dev/null
-_scratch_mkfs_sized $((1 * 1024 * 1024 * 1024)) >>$seqres.full 2>&1
+_scratch_mkfs_sized $((2 * 1024 * 1024 * 1024)) >>$seqres.full 2>&1
_scratch_mount
# Create a 4k file and Allocate 4M past EOF on that file
WARNING: multiple messages have this Message-ID (diff)
From: Rich Johnston <rjohnston@sgi.com>
To: Josef Bacik <jbacik@fusionio.com>,
linux-btrfs@vger.kernel.org, xfs@oss.sgi.com
Subject: Re: [PATCH 5/8] xfstests: generic/274 increase scratch fs size to 2g
Date: Tue, 22 Oct 2013 15:25:51 -0500 [thread overview]
Message-ID: <5266DF4F.8010403@sgi.com> (raw)
In-Reply-To: <1382120790-31060-5-git-send-email-jbacik@fusionio.com>
Patch does not apply, already committed.
Thanks
--Rich
commit 859f127da2ee6d49faa41cafd4ed362aa526e4a0
Author: Josef Bacik <jbacik@fusionio.com>
Date: Fri Jun 21 20:31:10 2013 +0000
xfstests: make fs for 274 larger
Btrfs will default to mixed block groups for 1 gigabyte file
systems and
smaller, which means data and metadata share the same area. This makes
generic/274 fail for us because we cannot reserve enough metadata
space to do
our writes. Bumping the scratch fs up to 2 gigabytes allows us to
do our normal
metadata/data separation and allows us to pass this test. Thanks,
Signed-off-by: Josef Bacik <jbacik@fusionio.com>
Reviewed-by: Ben Myers <bpm@sgi.com>
Signed-off-by: Rich Johnston <rjohnston@sgi.com>
diff --git a/tests/generic/274 b/tests/generic/274
index da45fab..7c4887f 100755
--- a/tests/generic/274
+++ b/tests/generic/274
@@ -57,7 +57,7 @@ echo "------------------------------"
rm -f $seqres.full
umount $SCRATCH_DEV 2>/dev/null
-_scratch_mkfs_sized $((1 * 1024 * 1024 * 1024)) >>$seqres.full 2>&1
+_scratch_mkfs_sized $((2 * 1024 * 1024 * 1024)) >>$seqres.full 2>&1
_scratch_mount
# Create a 4k file and Allocate 4M past EOF on that file
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2013-10-22 20:25 UTC|newest]
Thread overview: 46+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-18 18:26 [PATCH 1/8] xfstests: fix btrfs/002 to not use the scratch dev pool Josef Bacik
2013-10-18 18:26 ` Josef Bacik
2013-10-18 18:26 ` [PATCH 2/8] xfstests: add regression test for kernel bz 60673 Josef Bacik
2013-10-18 18:26 ` Josef Bacik
2013-10-21 15:03 ` Eric Sandeen
2013-10-21 15:03 ` Eric Sandeen
2013-10-21 15:09 ` Josef Bacik
2013-10-21 15:09 ` Josef Bacik
2013-10-21 15:14 ` Eric Sandeen
2013-10-21 15:14 ` Eric Sandeen
2013-10-21 15:21 ` Eric Sandeen
2013-10-21 15:21 ` Eric Sandeen
2013-10-18 18:26 ` [PATCH 3/8] xfstests: stat the dev we're removing to make sure its' really gone V2 Josef Bacik
2013-10-18 18:26 ` Josef Bacik
2013-10-21 15:07 ` Eric Sandeen
2013-10-21 15:07 ` Eric Sandeen
2013-10-21 15:10 ` Josef Bacik
2013-10-21 15:10 ` Josef Bacik
2013-10-18 18:26 ` [PATCH 4/8] xfstests: btrfs/016: a hole punching send test Josef Bacik
2013-10-18 18:26 ` Josef Bacik
2013-10-21 15:22 ` Eric Sandeen
2013-10-21 15:22 ` Eric Sandeen
2013-10-22 21:02 ` Rich Johnston
2013-10-22 21:02 ` Rich Johnston
2013-10-18 18:26 ` [PATCH 5/8] xfstests: generic/274 increase scratch fs size to 2g Josef Bacik
2013-10-18 18:26 ` Josef Bacik
2013-10-21 15:29 ` Eric Sandeen
2013-10-21 15:29 ` Eric Sandeen
2013-10-22 20:25 ` Rich Johnston [this message]
2013-10-22 20:25 ` Rich Johnston
2013-10-18 18:26 ` [PATCH 6/8] xfstests: generic/311: add a few more test cases Josef Bacik
2013-10-18 18:26 ` Josef Bacik
2013-10-21 15:37 ` Eric Sandeen
2013-10-21 15:37 ` Eric Sandeen
2013-10-18 18:26 ` [PATCH 7/8] xfstests: btrfs/017: add a regression test for snapshot creation Josef Bacik
2013-10-18 18:26 ` Josef Bacik
2013-10-22 21:06 ` Rich Johnston
2013-10-22 21:06 ` Rich Johnston
2013-10-18 18:26 ` [PATCH 8/8] xfstests: btrfs/018: a regression test for subvolume rename Josef Bacik
2013-10-18 18:26 ` Josef Bacik
2013-10-21 15:38 ` Eric Sandeen
2013-10-21 15:38 ` Eric Sandeen
2013-10-22 21:09 ` Rich Johnston
2013-10-22 21:09 ` Rich Johnston
2013-10-22 20:57 ` [PATCH 1/8] xfstests: fix btrfs/002 to not use the scratch dev pool Rich Johnston
2013-10-22 20:57 ` Rich Johnston
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=5266DF4F.8010403@sgi.com \
--to=rjohnston@sgi.com \
--cc=jbacik@fusionio.com \
--cc=linux-btrfs@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.