From: Omar Sandoval <osandov@osandov.com>
To: Dave Chinner <david@fromorbit.com>
Cc: linux-btrfs@vger.kernel.org, fstests@vger.kernel.org,
Eryu Guan <guaneryu@gmail.com>,
kernel-team@fb.com
Subject: Re: [PATCH 2/2] generic/427: used mixed mode for Btrfs
Date: Wed, 11 Apr 2018 18:04:31 -0700 [thread overview]
Message-ID: <20180412010431.GB25451@vader> (raw)
In-Reply-To: <20180412005630.GH729@dastard>
On Thu, Apr 12, 2018 at 10:56:30AM +1000, Dave Chinner wrote:
> On Wed, Apr 11, 2018 at 04:47:30PM -0700, Omar Sandoval wrote:
> > From: Omar Sandoval <osandov@fb.com>
> >
> > This test creates a 256 MB filesystem and then writes a 200 MB file.
> > With separate data and metadata, Btrfs will run out of data space since
> > it needs to allocate some metadata space. Use mixed mode, which is the
> > recommendation for smaller filesystems.
> >
> > Signed-off-by: Omar Sandoval <osandov@fb.com>
> > ---
> > tests/generic/427 | 2 ++
> > 1 file changed, 2 insertions(+)
> >
> > diff --git a/tests/generic/427 b/tests/generic/427
> > index 9cde5f50..b2cb4526 100755
> > --- a/tests/generic/427
> > +++ b/tests/generic/427
> > @@ -55,6 +55,8 @@ _require_test_program "feature"
> > _require_aiodio aio-dio-eof-race
> >
> > # limit the filesystem size, to save the time of filling filesystem
> > +# Btrfs needs to use mixed mode for such a small filesystem
> > +[ "$FSTYP" = "btrfs" ] && MKFS_OPTIONS="$MKFS_OPTIONS -M"
>
>
> _scratch_mkfs_sized() should already be adding this for small btrfs
> filesystems. Yup, it does:
>
> btrfs)
> local mixed_opt=
> (( fssize <= 100 * 1024 * 1024 )) && mixed_opt='--mixed'
> $MKFS_BTRFS_PROG $MKFS_OPTIONS $mixed_opt -b $fssize $SCRATCH_DEV
> ;;
>
> > _scratch_mkfs_sized $((256 * 1024 * 1024)) >>$seqres.full 2>&1
>
> But this uses a filesystem larger than the mixed mode threshold in
> _scratch_mkfs_sized(). Please update the generic threshold rather
> than special case this test.
I missed this, thanks, I'll send a v2.
prev parent reply other threads:[~2018-04-12 1:04 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-11 23:47 [PATCH 1/2] aio-dio-eof-race: handle aio pwrite errors and short reads Omar Sandoval
2018-04-11 23:47 ` [PATCH 2/2] generic/427: used mixed mode for Btrfs Omar Sandoval
2018-04-12 0:56 ` Dave Chinner
2018-04-12 1:04 ` Omar Sandoval [this message]
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=20180412010431.GB25451@vader \
--to=osandov@osandov.com \
--cc=david@fromorbit.com \
--cc=fstests@vger.kernel.org \
--cc=guaneryu@gmail.com \
--cc=kernel-team@fb.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