public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
From: Simon Haynes <simon@baydel.com>
To: David Woodhouse <dwmw2@infradead.org>
Cc: linux-mtd@lists.infradead.org
Subject: Re: JFFS2 Corruption.
Date: Mon, 8 Mar 2004 15:10:09 +0000	[thread overview]
Message-ID: <AC8EC7070E8A@baydel.com> (raw)
In-Reply-To: <1078327901.4619.21.camel@hades.cambridge.redhat.com>

On Wednesday 03 Mar 2004 3:31 pm, David Woodhouse wrote:
> On Thu, 2004-02-26 at 11:08 +0000, Simon Haynes wrote:
> > Beyond that I don't really know what I am looking for in the log. I can
>
> We could try to be slightly quieter about such things, but then we might
> actually miss something which _is_ a problem. Better to be concerned
> when there isn't a problem, than to be blissfully unaware when there
> _is_ one. Perhaps.

As you suggested I have changed the JFFS2 remount code to flush wbuf when the 
filesystem is mounted read only. As I said via IRC I have performed tens of 
reboots and I have not seen any CRC messages. 

Now on occasions, when the kernel is mounting JFFS2 as root on NAND I get.

NAND device: Manufacturer ID: 0xec, Chip ID: 0x79 (Samsung NAND 128MiB 3,3V)
Creating 3 MTD partitions on "NAND 128MiB 3,3V":
0x00000000-0x01000000 : "Boot / config partition"
mtd: Giving out device 0 to Boot / config partition
0x01000000-0x05000000 : "JFFS2 Root Filesystem partition"
mtd: Giving out device 1 to JFFS2 Root Filesystem partition
0x05000000-0x08000000 : "Write Cache Backup partition"
mtd: Giving out device 2 to Write Cache Backup partition
NET4: Linux TCP/IP 1.0 for NET4.0
IP Protocols: ICMP, UDP, TCP
IP: routing cache hash table of 512 buckets, 4Kbytes
TCP: Hash tables configured (established 4096 bind 4096)
NET4: Unix domain sockets 1.0/SMP for Linux NET4.0.
jffs2: Erase block size too small (16KiB). Using virtual blocks size (32KiB) 
instead
ofs 0x00c00400 has already been seen. Skipping
jffs2_scan_eraseblock(): Magic bitmask 0x1985 not found at 0x00c00408: 0x273c 
instead
jffs2_scan_eraseblock(): Magic bitmask 0x1985 not found at 0x00c00420: 0x404d 
instead
jffs2_scan_eraseblock(): Magic bitmask 0x1985 not found at 0x00c00424: 0x404d 
instead
jffs2_scan_eraseblock(): Magic bitmask 0x1985 not found at 0x00c00428: 0x404d 
instead
jffs2_scan_eraseblock(): Magic bitmask 0x1985 not found at 0x00c0043c: 0x0f33 
instead
jffs2_scan_eraseblock(): Magic bitmask 0x1985 not found at 0x00c00440: 0x88f8 
instead
jffs2_scan_eraseblock(): Magic bitmask 0x1985 not found at 0x00c00444: 0x4d61 
instead
jffs2_scan_eraseblock(): Magic bitmask 0x1985 not found at 0x00c00448: 0x2039 
instead
jffs2_scan_eraseblock(): Magic bitmask 0x1985 not found at 0x00c0044c: 0x343a 
instead
jffs2_scan_eraseblock(): Magic bitmask 0x1985 not found at 0x00c00450: 0x3a32 
instead
Further such events for this erase block will not be printed

Can you suggest what might be going on ?

Cheers

Simon.

  reply	other threads:[~2004-03-08 15:33 UTC|newest]

Thread overview: 38+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-02-19 16:48 JFFS2 Corruption simon
2004-02-23 11:07 ` simon
2004-02-24  9:48   ` simon
2004-02-24 12:00     ` David Woodhouse
2004-02-24 12:54       ` Simon Haynes
2004-02-24 13:04       ` Simon Haynes
2004-02-24 13:40         ` Simon Haynes
2004-02-24 14:22           ` David Woodhouse
2004-02-24 14:25             ` Simon Haynes
2004-02-24 14:56               ` David Woodhouse
2004-02-24 14:58                 ` Simon Haynes
2004-02-24 15:35                   ` David Woodhouse
2004-02-24 15:47                     ` Simon Haynes
2004-02-24 16:14                       ` David Woodhouse
2004-02-24 16:17                         ` Simon Haynes
2004-02-24 16:51                           ` David Woodhouse
2004-02-24 17:05                             ` Simon Haynes
2004-02-24 18:05                               ` David Woodhouse
2004-02-24 18:04                                 ` Simon Haynes
2004-02-25  9:49                                 ` simon
2004-02-25 10:25                                   ` David Woodhouse
2004-02-26 11:08                                     ` Simon Haynes
2004-02-26 11:55                                       ` David Woodhouse
2004-03-03 15:31                                       ` David Woodhouse
2004-03-08 15:10                                         ` Simon Haynes [this message]
2004-03-09 15:33                                           ` Simon Haynes
2004-03-16 16:14                                             ` David Woodhouse
2004-03-19 10:37                                               ` Simon Haynes
2004-03-19 11:11                                                 ` David Woodhouse
2004-02-24 17:12                             ` Simon Haynes
2004-02-24 16:55                           ` David Woodhouse
  -- strict thread matches above, loose matches on Subject: below --
2004-02-05 13:15 JFFS2 corruption Florian Schirmer
2004-02-08 10:37 ` David Woodhouse
2004-02-08 11:38   ` Florian Schirmer
2004-02-08 11:53     ` David Woodhouse
2004-02-08 17:02       ` Florian Schirmer
2004-02-08 17:13         ` David Woodhouse
2004-02-08 11:28 ` David Woodhouse

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=AC8EC7070E8A@baydel.com \
    --to=simon@baydel.com \
    --cc=dwmw2@infradead.org \
    --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