From: Artem Bityutskiy <dedekind1@gmail.com>
To: Alexandre Gambier <a.gambier@ftemaximal.fr>
Cc: linux-mtd@lists.infradead.org
Subject: Re: ubi_eba_init_scan: cannot reserve enough PEBs for bad PEB handling
Date: Tue, 10 Jan 2012 23:23:18 +0200 [thread overview]
Message-ID: <1326230599.2335.4.camel@koala> (raw)
In-Reply-To: <4F0C3339.6070909@ftemaximal.fr>
On Tue, 2012-01-10 at 13:46 +0100, Alexandre Gambier wrote:
> hi everyone,
>
> I use UBI volume and UBIFS on top of a NAND device with an embedded
> video meter.
> Everything works fine except that when a UBI volume is mounted the
> following warning is outputted :
> "UBI warning: ubi_eba_init_scan: cannot reserve enough PEBs for bad PEB
> handling, reserved 0, need 20"
Looks like the pool of reserved PEBs is fully used. Fo how long have you
been using this flash?
> UBI: attaching mtd7 to ubi0
When I see things like mtd7 - I get worried. Do you have 7 partitions on
one chip? Even on old good and reliable chips this was not very good
idea, let alone modern NANDs with all these unstable bits, "radiation"
effects, low eraseblock max. erase count, etc...
BTW, be aware of this problem:
http://linux-mtd.infradead.org/doc/ubifs.html#L_unstable_bits
which has not been solved - we need a brave knight who'd spend time
working on this issue.
Artem.
next prev parent reply other threads:[~2012-01-10 21:23 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-10 12:46 ubi_eba_init_scan: cannot reserve enough PEBs for bad PEB handling Alexandre Gambier
2012-01-10 21:23 ` Artem Bityutskiy [this message]
2012-01-11 8:10 ` Alexandre Gambier
2012-01-14 15:14 ` Artem Bityutskiy
2012-01-16 8:47 ` Alexandre Gambier
2012-01-16 12:24 ` Artem Bityutskiy
2012-01-16 12:28 ` Alexandre Gambier
2012-01-16 12:31 ` Artem Bityutskiy
2012-01-16 16:11 ` Alexandre Gambier
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=1326230599.2335.4.camel@koala \
--to=dedekind1@gmail.com \
--cc=a.gambier@ftemaximal.fr \
--cc=linux-mtd@lists.infradead.org \
/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