From: Josef Bacik <josef@toxicpanda.com>
To: Johannes Thumshirn <jth@kernel.org>, Eryu Guan <guaneryu@gmail.com>
Cc: Qu Wenruo <wqu@suse.com>,
linux-btrfs@vger.kernel.org, fstests@vger.kernel.org,
Damien Le Moal <Damien.LeMoal@wdc.com>
Subject: Re: [PATCH] btrfs/139: require 2GB scratch dev
Date: Fri, 3 Jan 2020 10:42:54 -0500 [thread overview]
Message-ID: <e204cc04-b270-c5cc-6ab9-3d46183765aa@toxicpanda.com> (raw)
In-Reply-To: <20200103112905.1078-1-jth@kernel.org>
On 1/3/20 6:29 AM, Johannes Thumshirn wrote:
> In my testing on 1GB zram devices btrfs/139 usually fails with
> ENOSPC.
>
> Add a requirement for 2GB scratch devices (empirically measured).
>
> Signed-off-by: Johannes Thumshirn <jth@kernel.org>
Reviewed-by: Josef Bacik <josef@toxicpanda.com>
Thanks,
Josef
prev parent reply other threads:[~2020-01-03 15:42 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-03 11:29 [PATCH] btrfs/139: require 2GB scratch dev Johannes Thumshirn
2020-01-03 15:42 ` Josef Bacik [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=e204cc04-b270-c5cc-6ab9-3d46183765aa@toxicpanda.com \
--to=josef@toxicpanda.com \
--cc=Damien.LeMoal@wdc.com \
--cc=fstests@vger.kernel.org \
--cc=guaneryu@gmail.com \
--cc=jth@kernel.org \
--cc=linux-btrfs@vger.kernel.org \
--cc=wqu@suse.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