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 12:14:01 +0300 [thread overview]
Message-ID: <1308820444.19443.0.camel@sauron> (raw)
In-Reply-To: <o4krv69m77vomji84cs3flljf6obpgfgcs@4ax.com>
On Sun, 2011-06-19 at 12:37 +0200, Gilles wrote:
> Hello
>
> After "make" built rootfs.ubifs, I ran ubinize before uploading the
> file to a web server.
>
> I then downloaded that file on a uClinux appliance, and ran the
> following command to format /dev/mtd2 with the image:
> =========
> ubiformat /dev/mtd2 -s 512 -f rootfs.ubi.img
> =========
>
> This command triggers the following warning:
> =========
> ...
> libscan: scanning eraseblock 1982 -- 99 % complete MTD_ioctl
> MTD_read
> libscan: scanning eraseblock 1983 -- 100 % complete MTD_ioctl
> MTD_read
>
> ubiformat: 995 eraseblocks have valid erase counter, mean value is 14
> ubiformat: 989 eraseblocks are supposedly empty
> ubiformat: warning!: only 995 of 1984 eraseblocks have valid erase
> counter
> ubiformat: mean erase counter 14 will be used for the rest of
> eraseblock
> ubiformat: continue? (yes/no)
> =========
>
> Running just "ubiformat /dev/mtd2 -s 512" triggers the same warning.
>
> I don't know what the warning really means, and what the consequences
> are when answering "yes". Could someone tell me?
I think it is self-explanatory. Please, ask specific question. WRT to
consequences - it should not be critical.
--
Best Regards,
Artem Bityutskiy
next prev parent reply other threads:[~2011-06-23 9:13 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 [this message]
2011-06-23 9:19 ` Gilles
2011-06-23 14:30 ` 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=1308820444.19443.0.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 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.