From: Boris Brezillon <boris.brezillon@free-electrons.com>
To: Ralf Schlatterbeck <rsc@runtux.com>
Cc: linux-mtd@lists.infradead.org
Subject: Re: init_constants_early: too small LEBs?
Date: Sun, 20 Nov 2016 10:51:41 +0100 [thread overview]
Message-ID: <20161120105141.69e66105@bbrezillon> (raw)
In-Reply-To: <20161119212508.GA5237@runtux.com>
Hi Ralf,
On Sat, 19 Nov 2016 22:25:08 +0100
Ralf Schlatterbeck <rsc@runtux.com> wrote:
> I'm trying to get an ubifs on a 2MB NOR flash.
>
> I'm following the usual steps for generating everything from inside the
> embedded system:
> ubiformat /dev/mtd7
> ubiattach /dev/ubi_ctrl -m 7 -d 7
> ubimkvol /dev/ubi7 -N testvol -s 1968KiB
>
> But when I try to mount I'm getting:
> # mount -t ubifs /dev/ubi7_0 /mnt/
> mount: mounting /dev/ubi7_0 on /mnt/ failed: Invalid argument
>
> and the kernel log tells me:
> Nov 19 21:07:33 board kernel: UBIFS error (pid 1504):
> init_constants_early: too small LEBs (3968 bytes), min. is 15360 bytes
>
> Any advice on what to try next?
>
> Should I use a jffs2 on top of UBI using gluebi or run jffs2 on the
> naked md device instead?
Why not putting JFFS2 directly on your MTD device (no UBI in the
middle).
> I'd really like to be bad block tolerant but
> don't know if this makes sense with NOR-Flash (of this size) at all.
You shouldn't need UBI, AFAIR, JFFS2 already deals with
wear-leveling/bad-block problems.
Regards,
Boris
next prev parent reply other threads:[~2016-11-20 9:52 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-19 21:25 init_constants_early: too small LEBs? Ralf Schlatterbeck
2016-11-20 9:51 ` Boris Brezillon [this message]
2016-11-20 12:00 ` Ralf Schlatterbeck
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=20161120105141.69e66105@bbrezillon \
--to=boris.brezillon@free-electrons.com \
--cc=linux-mtd@lists.infradead.org \
--cc=rsc@runtux.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