From: Richard Weinberger <richard.weinberger@gmail.com>
To: Rickard X Andersson <Rickard.Andersson@axis.com>
Cc: "richard@nod.at" <richard@nod.at>,
"linux-mtd@lists.infradead.org" <linux-mtd@lists.infradead.org>,
"dedekind1@gmail.com" <dedekind1@gmail.com>
Subject: Re: ubi2 error: ubi_refill_pools: no free eraseblocks
Date: Thu, 28 May 2020 08:59:50 +0200 [thread overview]
Message-ID: <CAFLxGvzg7pCkE6fPYp9ELUimOOvnhB0RzBy5eCGsrnoYPV9UHA@mail.gmail.com> (raw)
In-Reply-To: <e90b59f8c1f842cca8a6db59239a9d67@XBOX02.axis.com>
On Wed, May 27, 2020 at 3:21 PM Rickard X Andersson
<Rickard.Andersson@axis.com> wrote:
> During a stress test we get the following error:
>
> "ubi2 error: ubi_refill_pools: no free eraseblocks"
>
> Is this something we need to take some action to solve or is it unharmful?
It basically means that you're draining free blocks faster than it can
produce (by erasing outdated ones, etc..).
So nothing harmful but I'd worry if you face this during normal
operation (non-stresstest).
Mostly because when this situation happens UBI has to do many things
synchronously and things will get
slow.
--
Thanks,
//richard
______________________________________________________
Linux MTD discussion mailing list
http://lists.infradead.org/mailman/listinfo/linux-mtd/
next prev parent reply other threads:[~2020-05-28 7:00 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-27 13:20 ubi2 error: ubi_refill_pools: no free eraseblocks Rickard X Andersson
2020-05-28 6:59 ` Richard Weinberger [this message]
[not found] ` <0ce6e992f6f24238bcb599f84aef243d@axis.com>
2022-01-12 11:21 ` ubi2 error: scan_pool: unable to read EC header! PEB:569 err:1 Richard Weinberger
[not found] ` <d1e8b25b76df4e7aa428a411bceabdb3@axis.com>
2022-01-14 18:49 ` SV: " Richard Weinberger
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=CAFLxGvzg7pCkE6fPYp9ELUimOOvnhB0RzBy5eCGsrnoYPV9UHA@mail.gmail.com \
--to=richard.weinberger@gmail.com \
--cc=Rickard.Andersson@axis.com \
--cc=dedekind1@gmail.com \
--cc=linux-mtd@lists.infradead.org \
--cc=richard@nod.at \
/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.