From: Cyril Hrubis <chrubis@suse.cz>
To: ltp@lists.linux.it
Subject: [LTP] [PATCH 2/2] mkfs01: extend the loop device size to 256M
Date: Wed, 27 Jul 2016 11:25:08 +0200 [thread overview]
Message-ID: <20160727092508.GC10645@rei.lan> (raw)
In-Reply-To: <20160727092210.GB10645@rei.lan>
Hi!
> As far as I can tell 150MB should suffice as well, at least for me the
> btrfs-progs v4.3.1+ requests at least 136MB. Or did they increase the
^
Should have been v4.5.1+
The v4.3.1+ increased the minimal size to 100MB.
--
Cyril Hrubis
chrubis@suse.cz
next prev parent reply other threads:[~2016-07-27 9:25 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-27 5:44 [LTP] [PATCH 1/2] test.sh: make the loop device size can be customized Li Wang
2016-07-27 5:44 ` [LTP] [PATCH 2/2] mkfs01: extend the loop device size to 256M Li Wang
2016-07-27 9:22 ` Cyril Hrubis
2016-07-27 9:25 ` Cyril Hrubis [this message]
2016-07-27 10:28 ` Li Wang
2016-07-27 9:17 ` [LTP] [PATCH 1/2] test.sh: make the loop device size can be customized Cyril Hrubis
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=20160727092508.GC10645@rei.lan \
--to=chrubis@suse.cz \
--cc=ltp@lists.linux.it \
/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.