From: Eric Sandeen <sandeen@redhat.com>
To: Josef Bacik <jbacik@fusionio.com>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: [PATCH] xfstests: make fs for 274 larger
Date: Fri, 21 Jun 2013 16:53:54 -0500 [thread overview]
Message-ID: <51C4CB72.9080705@redhat.com> (raw)
In-Reply-To: <1371846648-21841-1-git-send-email-jbacik@fusionio.com>
On 6/21/13 3:30 PM, Josef Bacik wrote:
> 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 seperation and allows us to pass this test. Thanks,
It'd be nice if we could force btrfs into the other mode just for this
test, but it's probably harmless to just make everyone else bigger.
Makes the test take longer though, another gig to write.
Did you test other filesystems w/ the change?
Seems like a reasonable & expedient solution though, so:
Reviewed-by: Eric Sandeen <sandeen@redhat.com>
> Signed-off-by: Josef Bacik <jbacik@fusionio.com>
> ---
> tests/generic/274 | 2 +-
> 1 files changed, 1 insertions(+), 1 deletions(-)
>
> 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
>
next prev parent reply other threads:[~2013-06-21 21:53 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-21 20:30 [PATCH] xfstests: make fs for 274 larger Josef Bacik
2013-06-21 21:53 ` Eric Sandeen [this message]
2013-06-24 13:33 ` Josef Bacik
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=51C4CB72.9080705@redhat.com \
--to=sandeen@redhat.com \
--cc=jbacik@fusionio.com \
--cc=linux-btrfs@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).