From: "Anders Grafström" <grfstrm@users.sourceforge.net>
To: linux newbie <linux.newbie79@gmail.com>
Cc: Manoj <manoj23@gmail.com>, linux-mtd@lists.infradead.org
Subject: Re: JFFS2 crash in linux-2.6.30
Date: Mon, 24 Aug 2009 12:46:17 +0200 [thread overview]
Message-ID: <4A926F79.4030700@users.sourceforge.net> (raw)
In-Reply-To: <a64f67eb0908231707k80cf8c9m11e9074c11c48abe@mail.gmail.com>
linux newbie wrote:
> I tried this patch, after which I am not getting crash, but instead it shows
> cp: input/output error. and this is not consistent. somtimes, file
> copying is perfect and some times its not.
You get this when you write to a dnode whose previous data resides
in a NAND block that has gone bad.
Have you set CONFIG_JFFS2_FS_WBUF_VERIFY?
next prev parent reply other threads:[~2009-08-24 10:46 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-21 6:31 JFFS2 crash in linux-2.6.30 linux newbie
2009-08-21 18:08 ` Manoj
2009-08-24 0:07 ` linux newbie
2009-08-24 10:46 ` Anders Grafström [this message]
2009-08-25 5:47 ` linux newbie
2009-08-28 1:18 ` linux newbie
2009-08-28 1:49 ` Manoj
2009-08-28 1:52 ` linux newbie
2009-08-28 6:15 ` linux newbie
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=4A926F79.4030700@users.sourceforge.net \
--to=grfstrm@users.sourceforge.net \
--cc=linux-mtd@lists.infradead.org \
--cc=linux.newbie79@gmail.com \
--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