public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
From: Artem Bityutskiy <dedekind1@gmail.com>
To: hejianet <hejianet@linux.vnet.ibm.com>
Cc: linux-mtd@lists.infradead.org
Subject: Re: [question]MTD:unstable bit issues?
Date: Mon, 12 Nov 2012 17:39:59 +0200	[thread overview]
Message-ID: <1352734799.2262.11.camel@sauron.fi.intel.com> (raw)
In-Reply-To: <5087B304.8010903@linux.vnet.ibm.com>

[-- Attachment #1: Type: text/plain, Size: 836 bytes --]

On Wed, 2012-10-24 at 17:21 +0800, hejianet wrote:
> Hi Thomas
> till now, we have no evidence that it is a jffs2.

> we only observed a ubi error msg(not 100% sure it caused this hole):
> 
> Oct 15 20:09:10 (none) kernel: UBI error: ubi_io_write error -5 while writing 2048 bytes to PEB 1663:20480, written 0 bytes
> 
> Besides, it only appeared in power-cut stress cut, so I suspect it is relevant
> to "unstable bits issue". from google information, this issue appears in both
> nand and nor flash, but more frequently in nand.

Unstable bits issue does not give you tons of zeroes. I really think
that this is either a JFFS2 bug - fsync does not work, or your test
scripts have a bug - you power-cut before fsync or you do fsync, then
write more to this file, then power-cut.

-- 
Best Regards,
Artem Bityutskiy

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 836 bytes --]

  reply	other threads:[~2012-11-12 15:39 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-10-24  5:14 [question]MTD:unstable bit issues? hejianet
2012-10-24  8:13 ` Thomas.Betker
2012-10-24  8:52   ` hejianet
2012-10-24  9:01     ` Thomas.Betker
2012-10-24  9:21       ` hejianet
2012-11-12 15:39         ` Artem Bityutskiy [this message]
2012-10-24  9:53   ` Jamie Lokier
2012-11-12 15:37 ` 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=1352734799.2262.11.camel@sauron.fi.intel.com \
    --to=dedekind1@gmail.com \
    --cc=hejianet@linux.vnet.ibm.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