From: Artem Bityutskiy <dedekind@infradead.org>
To: Manoj <manoj23@gmail.com>
Cc: linux-mtd@lists.infradead.org
Subject: Re: write error while using UBI/UBIFS
Date: Mon, 08 Jun 2009 08:59:39 +0300 [thread overview]
Message-ID: <1244440779.5847.334.camel@localhost.localdomain> (raw)
In-Reply-To: <1c3f4270906052005y7a50a810sa60daf5a8850bcec@mail.gmail.com>
Hi,
On Fri, 2009-06-05 at 20:05 -0700, Manoj wrote:
> I have created a ubi image that I have programmed to NAND flash using
> ubiformat. After I mount the ubifs, I am trying to write a 3MB file to
> the flash and I am seeing some issues.
Please, make sure you have all the latest UBI and UBIFS fixes:
http://www.linux-mtd.infradead.org/doc/ubifs.html#L_source
I think I fixed debugging problems recently. I suspect this fix may
help you:
http://git.infradead.org/ubi-2.6.git?a=commit;h=f9fd3ec55e099ccd6894d7e639e2419c53a823e0
> I have enabled UBI debug and CONFIG_MTD_NAND_VERIFY_WRITE.
Please, also take this into account:
http://www.linux-mtd.infradead.org/faq/ubi.html#L_subpage_verify_fail
> Also, as an experiment, I used mtd_debug utility to write a 10MB image
> to the flash and I don't see any issues there. So, it doesn't sound
> like a driver issue?
> HW ECC is enabled and I am presuming that no maintenance data is
> stored in spare area for UBI/UBIFS (from documentation). I don't see
> errors with ECC off.
Enabling debugging checks for verification is good. But please, bear
in mind that they make your system slower.
If you enable just debugging - it is light-weight, but if you also
enable additional checks - they are very slow, so you should later
disable them.
--
Best regards,
Artem Bityutskiy (Битюцкий Артём)
next prev parent reply other threads:[~2009-06-08 6:00 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-06 3:05 write error while using UBI/UBIFS Manoj
2009-06-08 5:59 ` Artem Bityutskiy [this message]
2009-06-09 2:13 ` Manoj
2009-06-09 5:30 ` Artem Bityutskiy
2009-06-11 1:43 ` Manoj
2009-06-11 6:10 ` 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=1244440779.5847.334.camel@localhost.localdomain \
--to=dedekind@infradead.org \
--cc=linux-mtd@lists.infradead.org \
--cc=manoj23@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox