From: Artem Bityutskiy <dedekind1@gmail.com>
To: twebb <taliaferro62@gmail.com>
Cc: Lei Wen <leiwen@marvell.com>, linux-mtd@lists.infradead.org
Subject: Re: UBIFS failed to recover master node
Date: Tue, 08 Jun 2010 17:17:28 +0300 [thread overview]
Message-ID: <1276006648.5677.20.camel@localhost> (raw)
In-Reply-To: <AANLkTin31PwUfXVHGV89VGrWG89RbIcY1L1I_VEO7mSk@mail.gmail.com>
On Tue, 2010-06-08 at 09:44 -0400, twebb wrote:
> I've attached a log file that captures the problem I'm seeing.
twebb, you did not enable debugging messages. But it looks like they are
not actually needed.
> The
> log includes failures on 2 of 4 UBIFS volumes that are part of a
> single MTD device (and shows the other 2 volumes being
> mounted/umounted without error).
>
> It appears from the log that the problem is associated with "corrupt
> empty space" which can be seen in the log at lines 28, 313, 347, and
> 359. Could this be HW ECC failing to correct bit errors on reads?
> Any suggestions on what this problem would be helpful.
Yes, HW fails to correct bit errors. Why these errors are there - this
it the question. May be MLC-related. You need to debug this. Or send me
your board, I can try to take a look
Did you enable UBI extra self checks?
Best Regards,
Artem Bityutskiy (Артём Битюцкий)
next prev parent reply other threads:[~2010-06-08 14:19 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-24 15:22 UBIFS failed to recover master node twebb
2010-05-25 5:05 ` Artem Bityutskiy
2010-05-26 16:06 ` twebb
2010-05-26 16:32 ` Artem Bityutskiy
2010-06-08 13:44 ` twebb
2010-06-08 14:17 ` Artem Bityutskiy [this message]
2010-06-08 15:00 ` twebb
2010-06-08 15:23 ` twebb
2010-06-08 15:33 ` twebb
2010-06-10 13:08 ` twebb
2010-06-10 13:14 ` Artem Bityutskiy
2010-05-25 5:06 ` Artem Bityutskiy
2010-06-28 8:21 ` re
2010-07-13 8: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=1276006648.5677.20.camel@localhost \
--to=dedekind1@gmail.com \
--cc=leiwen@marvell.com \
--cc=linux-mtd@lists.infradead.org \
--cc=taliaferro62@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 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.