From: Ben Myers <bpm@sgi.com>
To: Josef Bacik <jbacik@fusionio.com>
Cc: xfs@oss.sgi.com
Subject: Re: [PATCH] xfstests: make fs for 274 larger
Date: Mon, 8 Jul 2013 16:30:01 -0500 [thread overview]
Message-ID: <20130708213001.GJ20932@sgi.com> (raw)
In-Reply-To: <1371846670-21882-1-git-send-email-jbacik@fusionio.com>
On Fri, Jun 21, 2013 at 04:31:10PM -0400, 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,
>
> Signed-off-by: Josef Bacik <jbacik@fusionio.com>
XFS and ext4 still passed with this patch.
Reviewed-by: Ben Myers <bpm@sgi.com>
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2013-07-08 21:30 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-21 20:31 [PATCH] xfstests: make fs for 274 larger Josef Bacik
2013-07-08 21:30 ` Ben Myers [this message]
2013-10-18 20:10 ` 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=20130708213001.GJ20932@sgi.com \
--to=bpm@sgi.com \
--cc=jbacik@fusionio.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