From: "Pedro I. Sanchez" <psanchez@fosstel.com>
To: linux-mtd@lists.infradead.org
Subject: UBIFS and MLC NAND Flash
Date: Mon, 22 Mar 2010 12:57:39 -0400 [thread overview]
Message-ID: <4BA7A183.7040206@fosstel.com> (raw)
Hello,
I have a few questions regarding this topic.
1. The UBIFS FAQ has a summary of the state of the support for MLC NAND
flash here:
http://www.linux-mtd.infradead.org/faq/ubifs.html#L_ubifs_mlc
The question is, is this still the case? Does the FAQ reflect the
current state of affairs?
2. I have several boards with MLC NAND flash running the Linux kernel
2.6.29 and UBIFS. I am seeing a fairly large rate of file "corruption"
errors, files that all of a sudden become unreadable. Curiously enough,
they have been read-only files in all cases, program executables and
shared libraries.
Would upgrading to a more recent kernel, or back porting the latest
UBIFS code, help? Shall I expect better support for MLC NAND flash in
the latest UBIFS code?
3. I am also seeing other errors where it is the U-Boot or the Kernel
partitions that become corrupted. UBIFS is not involved there directly
since these partitions are at the mtd level and outside the UBI layer.
More specifically, my flash is partitioned as mtd0, mtd1, mtd2, mtd3,
mtd4. Only mtd4 has UBI/UBIFS on top. Is it possible that some flash
handling problems in UBIFS (mtd4) "spill over" other non-UBIFS mtd
partitions?
4. Other than minimizing flash writes, is there any other suggestion on
what to do to improve on the failure rate I see in the file system?
Thank you in advance, I would very much appreciate you answers.
--
Pedro
next reply other threads:[~2010-03-22 16:57 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-22 16:57 Pedro I. Sanchez [this message]
2010-04-08 8:22 ` UBIFS and MLC NAND Flash Artem Bityutskiy
2010-04-19 21:57 ` twebb
2010-04-19 23:52 ` Pedro I. Sanchez
2010-05-03 14:48 ` Pedro I. Sanchez
2010-05-04 14:17 ` 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=4BA7A183.7040206@fosstel.com \
--to=psanchez@fosstel.com \
--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;
as well as URLs for NNTP newsgroup(s).