From: Artem Bityutskiy <dedekind@infradead.org>
To: Canella Matteo <Matteo.Canella@mta.it>
Cc: "linux-mtd@lists.infradead.org" <linux-mtd@lists.infradead.org>
Subject: Re: Problem in erasing a nand flash with ubiformat
Date: Wed, 10 Jun 2009 11:35:37 +0300 [thread overview]
Message-ID: <1244622937.5847.396.camel@localhost.localdomain> (raw)
In-Reply-To: <BD9F3F3F5A6CCF4BA032B9FED4DD312E893B13@mta-digimail.MTA.INT>
On Wed, 2009-06-10 at 10:27 +0200, Canella Matteo wrote:
> Hi all,
> I have a question for Artem,
> I'm running a problem with ubiformat and I saw this email from you:
>
> http://lists.infradead.org/pipermail/linux-mtd/2009-January/024285.htm
>
> I'm having the same problem, ubiformat fails to format a nand flash because it is not able to erase a block.
> flash_eraseall just ignore this erase problem.
Sorry, I am not sure what you mean. You say that ubiformat gets an
erase error and instead of marking the eraseblock as bad it exits?
Are you using the newest ubiformat version from the mtd-utils git
tree?
The latest ubiformat does have code which makrs a block as bad on
write and erase errors. See the 'mark_bad()' function. If this
does not work for you, could you please try to use gdb and figure
out why? The code currently tries to mark the eraseblock as bad
only in case of an EIO errors, may be this is the problem?
> Do you think ubiformat should physically mark this block as bad eraseblock? Or should it just ignore it?
Yes it should. And there is already code in ubiformat which implements
this.
> Why currently ubiformat or flash_eraseall does not mark these as bad blocks?
It does. Make sure you use the latest ubiformat. Not sure about
flash_eraseall, I do not use it nowadays.
--
Best regards,
Artem Bityutskiy (Битюцкий Артём)
next prev parent reply other threads:[~2009-06-10 8:35 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-10 8:27 Problem in erasing a nand flash with ubiformat Canella Matteo
2009-06-10 8:35 ` Artem Bityutskiy [this message]
2009-06-10 10:01 ` Canella Matteo
2009-06-10 10:40 ` 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=1244622937.5847.396.camel@localhost.localdomain \
--to=dedekind@infradead.org \
--cc=Matteo.Canella@mta.it \
--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