public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
From: linux newbie <linux.newbie79@gmail.com>
To: "Anders Grafström" <grfstrm@users.sourceforge.net>
Cc: Manoj <manoj23@gmail.com>, linux-mtd@lists.infradead.org
Subject: Re: JFFS2 crash in linux-2.6.30
Date: Tue, 25 Aug 2009 15:47:40 +1000	[thread overview]
Message-ID: <a64f67eb0908242247v7b10551q96c63b95f66bd41c@mail.gmail.com> (raw)
In-Reply-To: <4A926F79.4030700@users.sourceforge.net>

Hi All,

Thanks for your support.

I havent set CONFIG_JFFS2_FS_WBUF_VERIFY and after enabling it, its
working fine.

Thanking You

On Mon, Aug 24, 2009 at 8:46 PM, Anders
Grafström<grfstrm@users.sourceforge.net> wrote:
> 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?
>
> ______________________________________________________
> Linux MTD discussion mailing list
> http://lists.infradead.org/mailman/listinfo/linux-mtd/
>

  reply	other threads:[~2009-08-25  5:47 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
2009-08-25  5:47       ` linux newbie [this message]
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=a64f67eb0908242247v7b10551q96c63b95f66bd41c@mail.gmail.com \
    --to=linux.newbie79@gmail.com \
    --cc=grfstrm@users.sourceforge.net \
    --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