From: Richard Weinberger <richard@nod.at>
To: Oleksij Rempel <linux@rempel-privat.de>,
t kevin <kevint324@gmail.com>,
linux-mtd@lists.infradead.org
Subject: Re: Get error -74 (ECC error) during ubiattach
Date: Sat, 20 Dec 2014 11:12:54 +0100 [thread overview]
Message-ID: <54954BA6.7050304@nod.at> (raw)
In-Reply-To: <549549E3.7000903@rempel-privat.de>
Am 20.12.2014 um 11:05 schrieb Oleksij Rempel:
> Am 20.12.2014 um 11:02 schrieb Richard Weinberger:
>> Am 20.12.2014 um 11:00 schrieb Oleksij Rempel:
>>> Am 20.12.2014 um 10:27 schrieb Richard Weinberger:
>>>> Hi!
>>>>
>>>> Am 20.12.2014 um 04:43 schrieb t kevin:
>>>>> So for uncorrectable ECC error ( e.g., bad block) the only way out is
>>>>> to do a fresh ubiformat?
>>>>> For device like harddisk you get bad blocks all the time, if it is not
>>>>> in the critical sector things can be fixed as much as possible by fsck
>>>>> so I was looking for something like fsck.ubifs.
>>>>
>>>> An uncorrectable ECC error means that more bits flipped than your ECC
>>>> algorithm can fix.
>>>
>>> At same time uncorrectable ECC error mean, the page was erase and there
>>> is no ECC sum. Something should be written to create ECC.
>>
>> Which would be a driver bug and needs fixing.
>
> No at all. If driver get request to erase page, it should do it and
> nothing more.
> There are use cases where erase means erase, and not erase + write ecc.
Raw mode is a different thing.
> It is not a driver bug!
If users on top of MTD read from an erased block it has to return 0xFF bytes and
not an ECC error.
IOW if mtd_erase() -> mtd_read() causes an ECC error with your driver it needs
fixing.
Thanks,
//richard
next prev parent reply other threads:[~2014-12-20 10:13 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-19 12:24 Get error -74 (ECC error) during ubiattach t kevin
2014-12-19 13:49 ` Richard Weinberger
2014-12-20 3:43 ` t kevin
2014-12-20 9:27 ` Richard Weinberger
2014-12-20 10:00 ` Oleksij Rempel
2014-12-20 10:02 ` Richard Weinberger
2014-12-20 10:05 ` Oleksij Rempel
2014-12-20 10:12 ` Richard Weinberger [this message]
2014-12-20 10:16 ` Oleksij Rempel
2014-12-20 14:05 ` Oleksij Rempel
2014-12-19 15:31 ` Tanya Brokhman
2014-12-20 3:48 ` t kevin
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=54954BA6.7050304@nod.at \
--to=richard@nod.at \
--cc=kevint324@gmail.com \
--cc=linux-mtd@lists.infradead.org \
--cc=linux@rempel-privat.de \
/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).