From: Artem Bityutskiy <dedekind1@gmail.com>
To: "Matthew L. Creech" <mlcreech@gmail.com>
Cc: linux-mtd@lists.infradead.org
Subject: Re: ubi_eba_init_scan: cannot reserve enough PEBs
Date: Mon, 02 Aug 2010 07:22:04 +0300 [thread overview]
Message-ID: <1280722924.4363.0.camel@localhost.localdomain> (raw)
In-Reply-To: <AANLkTikgmnRZHwN64xCFaO7F71xHaGXWo3WZ62u4939u@mail.gmail.com>
On Fri, 2010-07-30 at 13:51 -0400, Matthew L. Creech wrote:
> On Fri, Jul 30, 2010 at 12:12 PM, Artem Bityutskiy <dedekind1@gmail.com> wrote:
> >
> > Something like this, I guess, would be good enough?
> >
> ...
> > + * o if this is a new UBI image, then just print the warning
> > + * o if this is an UBI image which has already been used for some time, print
> > + * a warning only if we can reserve less than 10% of the expected amount of
> > + * the reserved PEB.
> > + *
> > + * The idea is that when UBI is used, PEBs become bad, and the reserved pool
> > + * of PEBs becomes smaller, which is normal and we do not want to scare users
> > + * with a warning every time they attach the MTD device. This was an issue
> > + * reported by real users.
>
> This sounds like a good compromise to me. I was wondering whether
> we'd still want to warn in the case in which nearly all of the reserve
> PEBs had been exhausted, and using a 10% threshold seems like a good
> way to accomplish that without scaring others unnecessarily. :)
Pushed this patch to ubi-2.6.git
--
Best Regards,
Artem Bityutskiy (Артём Битюцкий)
next prev parent reply other threads:[~2010-08-02 4:22 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-22 18:37 ubi_eba_init_scan: cannot reserve enough PEBs Matthew L. Creech
2010-07-26 5:21 ` Artem Bityutskiy
2010-07-26 21:13 ` Matthew L. Creech
2010-07-27 15:12 ` Artem Bityutskiy
2010-07-27 15:21 ` Artem Bityutskiy
2010-07-28 5:46 ` Stefani Seibold
2010-08-22 15:04 ` Artem Bityutskiy
2010-08-31 12:09 ` Stefani Seibold
2010-09-01 15:47 ` Artem Bityutskiy
2010-09-02 6:47 ` Stefani Seibold
2010-09-02 9:45 ` Artem Bityutskiy
2010-08-22 15:02 ` Artem Bityutskiy
2010-07-27 20:47 ` Matthew L. Creech
2010-07-30 16:12 ` Artem Bityutskiy
2010-07-30 17:51 ` Matthew L. Creech
2010-08-02 4:22 ` Artem Bityutskiy [this message]
2010-08-22 18:30 ` Artem Bityutskiy
2010-08-24 22:38 ` Matthew L. Creech
2010-08-25 3:51 ` Artem Bityutskiy
2010-08-31 15:36 ` Matthew L. Creech
2010-09-01 18:57 ` Artem Bityutskiy
2010-09-06 9:17 ` Artem Bityutskiy
2010-09-07 15:59 ` Matthew L. Creech
2010-09-07 17:17 ` Artem Bityutskiy
2010-09-07 17:48 ` Artem Bityutskiy
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=1280722924.4363.0.camel@localhost.localdomain \
--to=dedekind1@gmail.com \
--cc=linux-mtd@lists.infradead.org \
--cc=mlcreech@gmail.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;
as well as URLs for NNTP newsgroup(s).