From: Artem Bityutskiy <dedekind1@gmail.com>
To: j ram <buggyballs@gmail.com>
Cc: linux-mtd@lists.infradead.org
Subject: Re: Mounting JFFS2 partitions as read-only and CRC failures
Date: Mon, 26 Jul 2010 07:58:29 +0300 [thread overview]
Message-ID: <1280120309.14917.17.camel@localhost> (raw)
In-Reply-To: <AANLkTilV0_Ya6fSC4m7jX2kMqnNMDD8-RcampJxxwcDU@mail.gmail.com>
On Thu, 2010-07-22 at 11:14 -0700, j ram wrote:
> Hi,
> I have a question.
> I've encountered JFFS2 CRC errors on the lines of
> Name CRC failed on node at 0x00b620c8: Read 0x640c8ca3, calculated 0x795111fe
>
> According to http://www.linux-mtd.infradead.org/faq/jffs2.html#L_messages,
> JFFS2 CRC failure messages could mean node corruption caused by media
> corruption or unclean reboots.
>
> If the JFFS2 partition is mounted as read-only, is it safe to conclude
> that node corruption is unlikely?
>
> Appreciate any insight
Read disturbs can lead to bit-flips which can develop into hard errors.
On SLC this is difficult do achieve but possible, although it may
require millions of reads, on MLC this is achievable more easily.
So the answer is - not, you cannot conclude that.
--
Best Regards,
Artem Bityutskiy (Артём Битюцкий)
prev parent reply other threads:[~2010-07-26 4:59 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-22 18:14 Mounting JFFS2 partitions as read-only and CRC failures j ram
2010-07-26 4:58 ` Artem Bityutskiy [this message]
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=1280120309.14917.17.camel@localhost \
--to=dedekind1@gmail.com \
--cc=buggyballs@gmail.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