From: Alexey Kodanev <alexey.kodanev@oracle.com>
To: ltp@lists.linux.it
Subject: [LTP] [PATCH] zram: extend the zram3 disksize to 40MB
Date: Mon, 25 Jul 2016 14:25:21 +0300 [thread overview]
Message-ID: <5795F721.3@oracle.com> (raw)
In-Reply-To: <5795F4E4.20005@oracle.com>
On 07/25/2016 02:15 PM, Alexey Kodanev wrote:
> Hi,
> On 07/13/2016 11:59 AM, Cyril Hrubis wrote:
>> Hi!
>>> It failed to format btrfs on /dev/zram3 device since the
>>> disk size is too small (btrfs-progs is v4.4.1).
>>>
>>> The error msg we catched:
>>>
>>> zram01 3 TINFO : make ext3 filesystem on /dev/zram0
>>> zram01 3 TINFO : make ext4 filesystem on /dev/zram1
>>> zram01 3 TINFO : make xfs filesystem on /dev/zram2
>>> zram01 3 TINFO : make btrfs filesystem on /dev/zram3
>>> '/dev/zram3' is too small to make a usable filesystem
>>> Minimum size for each btrfs device is 41943040.
>>> btrfs-progs v4.4.1
>>> See http://btrfs.wiki.kernel.org for more information.
>>> zram01 3 TFAIL : failed to make btrfs on /dev/zram3
>>> zram01 4 TINFO : zram cleanup
>> I've got the exact same failure with btrfs-progs 4.5.1 just recently,
>> the fix looks good to me.
>
> Looks good to me too. Patch applied.
Also noted that in case btrfs is not supported, ext2 will be used with 40MB.
I think it shouldn't be a problem, just one more change that patch made.
>
> Best regards,
> Alexey
>
>> And btw it looks like we need to increase the default loop device size
>> again since btrfs-progs 4.5.1 seems to request at least 136MB for mkfs01
>> test...
>>
>
>
prev parent reply other threads:[~2016-07-25 11:25 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-11 11:57 [LTP] [PATCH] zram: extend the zram3 disksize to 40MB Li Wang
2016-07-13 8:59 ` Cyril Hrubis
2016-07-25 11:15 ` Alexey Kodanev
2016-07-25 11:25 ` Alexey Kodanev [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=5795F721.3@oracle.com \
--to=alexey.kodanev@oracle.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.