public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
From: Artem Bityutskiy <dedekind1@gmail.com>
To: Gilles <gilles.ganault@free.fr>
Cc: linux-mtd@lists.infradead.org
Subject: Re: "warning!: only 995 of 1984 eraseblocks have valid erase counter"
Date: Thu, 23 Jun 2011 17:30:57 +0300	[thread overview]
Message-ID: <1308839462.23597.5.camel@sauron> (raw)
In-Reply-To: <2016071dvg4slfufk95id9ov68n2kvbp4j@4ax.com>

On Thu, 2011-06-23 at 11:19 +0200, Gilles wrote:
> On Thu, 23 Jun 2011 12:14:01 +0300, Artem Bityutskiy
> <dedekind1@gmail.com> wrote:
> >I think it is self-explanatory. Please, ask specific question. WRT to
> >consequences - it should not be critical.
> 
> I went ahead, answered yes, and it seems to work OK, but I was curious
> to understand what the message really means.

What exactly is unclear in the messages? :-)

> Before reflashing memory with an image, does ubiformat always warn the
> user that the empty blocks after the image will have their erase
> counter set to the average computed from the used blocks, regardless
> of their actual usage so far?

Yes. If you properly use tools - you should never see the warnings. Most
probably you flash images using UBI-unaware tools, or you erase the
flash using UBI-unaware tools like flash_erase or do it in u-boot.

But I agree that ubiformat could probably be smarter and avoid printing
this warning if half of the flash is UBI-formatted and the other half is
empty.

Current logic is - if not everything is UBI-formatted - warn. But it
could be - if not everything is UBI-formatted and the eraseblocks are
not empty - warn. Feel free to send a patch :-)

-- 
Best Regards,
Artem Bityutskiy

      reply	other threads:[~2011-06-23 14:30 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-06-19 10:37 "warning!: only 995 of 1984 eraseblocks have valid erase counter" Gilles
2011-06-23  9:14 ` Artem Bityutskiy
2011-06-23  9:19   ` Gilles
2011-06-23 14:30     ` Artem Bityutskiy [this message]

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=1308839462.23597.5.camel@sauron \
    --to=dedekind1@gmail.com \
    --cc=gilles.ganault@free.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