All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jan Stancek <jstancek@redhat.com>
To: ltp@lists.linux.it
Subject: [LTP] [PATCH] [RFC] zram01: Fix on ppc64le
Date: Tue, 15 Aug 2017 08:48:31 -0400 (EDT)	[thread overview]
Message-ID: <226751203.1704912.1502801311592.JavaMail.zimbra@redhat.com> (raw)
In-Reply-To: <20170815123801.GD20715@rei.lan>



----- Original Message -----
> Hi!
> > > Looks like we went off-topic and the zram01.sh test wasn't fixed in the
> > > end and it still fails on ppc64le.
> > > 
> > > I guess I can prepare a patch that checks if there is enough free RAM
> > > for a minimal Btrfs fs but I would still like to obtain the minimal size
> > > from mkfs.btrfs. Does that sound reasonable?
> > 
> > Do you mean these messages from mkfs.btrfs:
> >   "ERROR: minimum size for each btrfs device is 41943040"
> > or some other way to find minimal supported size?
> 
> Do do not know other way that the one used in the original patch, i.e.
> running mkfs.btrfs on /dev/null and parsing the output.
> 
> Or is there something better than that?

Other than picking a number by ourselves, nothing comes to mind.
Numbers from mkfs.btrfs error message seem too low, even 2.5x
larger number still fails:

# modprobe brd rd_nr=1 rd_size=100000
# mkfs.btrfs /dev/ram0 
btrfs-progs v4.9.1
See http://btrfs.wiki.kernel.org for more information.

ERROR: not enough free space to allocate chunk

Regards,
Jan

  reply	other threads:[~2017-08-15 12:48 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-01-31 13:44 [LTP] [PATCH] [RFC] zram01: Fix on ppc64le Cyril Hrubis
2017-01-31 16:14 ` Jan Stancek
2017-02-01  9:45   ` Cyril Hrubis
2017-02-01 10:59     ` Jan Stancek
2017-02-02 15:22       ` Cyril Hrubis
2017-02-08 11:10         ` Cyril Hrubis
2017-02-09 12:02           ` Cyril Hrubis
2017-02-09 13:24             ` Jan Stancek
2017-02-09 14:00               ` Cyril Hrubis
2017-02-09 14:48                 ` Jan Stancek
2017-02-09 14:56                   ` Cyril Hrubis
2017-08-15  9:23 ` Cyril Hrubis
2017-08-15 11:44   ` Jan Stancek
2017-08-15 12:38     ` Cyril Hrubis
2017-08-15 12:48       ` Jan Stancek [this message]
2017-08-15 12:57         ` 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=226751203.1704912.1502801311592.JavaMail.zimbra@redhat.com \
    --to=jstancek@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.