From: Li Wang <liwang@redhat.com>
To: ltp@lists.linux.it
Subject: [LTP] [PATCH 2/2] mkfs01: extend the loop device size to 256M
Date: Wed, 27 Jul 2016 18:28:55 +0800 [thread overview]
Message-ID: <20160727102855.GA19654@gmail.com> (raw)
In-Reply-To: <20160727092210.GB10645@rei.lan>
On Wed, Jul 27, 2016 at 11:22:10AM +0200, Cyril Hrubis wrote:
> Hi!
> > Signed-off-by: Li Wang <liwang@redhat.com>
> > ---
> > testcases/commands/mkfs/mkfs01.sh | 3 ++-
> > 1 file changed, 2 insertions(+), 1 deletion(-)
> >
> > diff --git a/testcases/commands/mkfs/mkfs01.sh b/testcases/commands/mkfs/mkfs01.sh
> > index eda9829..9a26899 100755
> > --- a/testcases/commands/mkfs/mkfs01.sh
> > +++ b/testcases/commands/mkfs/mkfs01.sh
> > @@ -32,7 +32,8 @@ setup()
> >
> > tst_tmpdir
> >
> > - tst_acquire_device
> > + # set test_dev.img size
> > + tst_acquire_device 256
>
> 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
> minimal size again?
No, I just let to 256M in case that they increase that again.
>
> And I guess that we should bump the size in runltp script as well.
I didn't think of that.
Ok, Let me think it over and rewrite a new method.
Regards,
Li Wang
next prev parent reply other threads:[~2016-07-27 10:28 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
2016-07-27 10:28 ` Li Wang [this message]
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=20160727102855.GA19654@gmail.com \
--to=liwang@redhat.com \
--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.