linux-mtd.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: Brian Norris <computersforpeace@gmail.com>
To: Leon Pollak <leonp@plris.com>
Cc: linux-mtd@lists.infradead.org
Subject: Re: What is wrong?
Date: Wed, 26 Feb 2014 17:11:48 -0800	[thread overview]
Message-ID: <20140227011148.GI4194@ld-irv-0074> (raw)
In-Reply-To: <4315632.KkRm7kzq26@leonp.plris.com>

Hi Leon,

On Wed, Feb 26, 2014 at 04:07:21PM +0200, Leon Pollak wrote:
> I use JFFS2 version 2.2.(NAND)(SUMMARY)(C) 2001-2006 Red Hat, Inc. 
> (comes with MontaVistaPro 5.0). Kernel 2.6.18.
> I prepare JFFS2 partition with mkfs.jffs2 and sumtool and burn it with 
> flash_eraseall and 'nandwrite -p'.
> Everything works fine.
> 
> The NAND is write protected by HW and the partition is mounted as RO. 
> At some moment I need to update a small file. 
> So I do: 
> - HW write protect off, 
> - remount RW, 
> - update file, 
> - sync, 
> - remount RO, 
> - write protect on.
> 
> Looking at linux console I see a lot of messages like:
> Erase at 0x00400000 failed immediately: errno -5
> Erase at 0x003e0000 failed immediately: errno -5
> ......
> Erase at 0x00340000 failed immediately: errno -5
> jffs2_flush_wbuf(): Write failed with -5
> Write of 2016 bytes at 0x002578a0 failed. returned -5, retlen 0
> Not marking the space at 0x002578a0 as dirty because the flash driver 
> returned retlen zero.
> 
> 
> This is repeated for a long time, but everything seems work OK.
> The sequential starts and even file updates are also OK, without error 
> messages.
> 
> What do I do wrong? Thanks a lot.

It's possible you're seeing symptoms of this:

https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=807612db2f9940b9fa6deaef054eb16d51bd3e00

It seems like maybe JFFS2 is still doing some GC and/or write flushing
after the remount.

Could try this?

 - HW write protect off, 
 - remount RW, 
 - update file, 
 - sync, 
 - remount RO, 
 - sync, <---------- add this, to see if you're experiencing any
                     writeback after remount
 - write protect on.

Brian

  reply	other threads:[~2014-02-27  1:12 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-02-26 14:07 What is wrong? Leon Pollak
2014-02-27  1:11 ` Brian Norris [this message]
2014-02-27  1:13   ` Brian Norris
     [not found]   ` <1553411.O1igofskp7@leonp.plris.com>
2014-02-27 21:22     ` Brian Norris
2014-03-03 21:13       ` Andrew Ruder
2014-03-04  8:33         ` Brian Norris
2014-03-04  8:54           ` Leon Pollak
2014-03-04 16:40             ` Andrew Ruder
2014-03-30  7:16             ` What is wrong? - Cont Leon Pollak
2014-03-27 11:50           ` What is wrong? Leon Pollak

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=20140227011148.GI4194@ld-irv-0074 \
    --to=computersforpeace@gmail.com \
    --cc=leonp@plris.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;
as well as URLs for NNTP newsgroup(s).