From: Simon Haynes <simon@baydel.com>
To: David Woodhouse <dwmw2@infradead.org>
Cc: linux-mtd@lists.infradead.org
Subject: Re: JFFS2 Corruption.
Date: Tue, 9 Mar 2004 15:33:09 +0000 [thread overview]
Message-ID: <B1CA6BCA5B0C@baydel.com> (raw)
In-Reply-To: <AC8EC7070E8A@baydel.com>
On Monday 08 Mar 2004 3:10 pm, Simon Haynes wrote:
> 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
> ofs 0x00c00400 has already been seen. Skipping
> jffs2_scan_eraseblock(): Magic bitmask 0x1985 not found at 0x00c00408:
> 0x273c instead
Since lunch interrupted our converstation yesterday I have tried a few
things. The SMC partition I was using was 64 Mb and contained a bad block. I
modified the kernel to make this partition 48Mb. I booted root over nfs and
tried to rebuild root on the SMC. I can no longer mount the original SMC so I
tried a new one which worked OK.
-bash-2.05b# /mtd/eraseall /dev/mtd1 > /dev/null
nand_erase: attempt to erase a bad block at page 0x0001ee60
/mtd/eraseall: /dev/mtd1: MTD Erase failure: Input/output error
-bash-2.05b# mount -t jffs2 /dev/ram1 /smc
Cowardly refusing to erase blocks on filesystem with no valid JFFS2 nodes
empty_blocks 2047, bad_blocks 0, c->nr_blocks 2048
mount: wrong fs type, bad option, bad superblock on /dev/ram1,
or too many mounted file systems
-bash-2.05b# /mtd/eraseall /dev/mtd1 > /dev/null
-bash-2.05b# mount -t jffs2 /dev/ram1 /smc
-bash-2.05b#
After 5 reboots the new SMC gave this magic bitmask failure.
jffs2: Erase block size too small (16KiB). Using virtual blocks size (32KiB)
instead
ofs 0x000a8400 has already been seen. Skipping, jeb 0xa8000, sector size
0x8000
saved ofs 0x000a8000, previous 0xa7fff, buf_len 0x7c00, scanned 0x0
jffs2_scan_eraseblock(): Magic bitmask 0x1985 not found at 0x000a8408: 0x273c
instead, 0x0
jffs2_scan_eraseblock(): Magic bitmask 0x1985 not found at 0x000a841c: 0x000b
instead, 0x0
jffs2_scan_eraseblock(): Magic bitmask 0x1985 not found at 0x000a8420: 0x404d
.
.
.
It would appear that the first buffer location does not contain 0xFFFFFFFF
and cleanmarkerfound is set but I don't know what this means to JFFS2.
I then switched the partition back to 64Mb, set the kernel to use the read
only block device and hacked the MAJOR number for JFFS2 to be the same as
/dev/ram. I have rebooted the system at least 20 times and as yet I have not
seen any errors.
I am unsure as where to go next besides trying more reboots.
Any ideas ?
Cheers
Simon.
next prev parent reply other threads:[~2004-03-09 16:11 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
2004-03-09 15:33 ` Simon Haynes [this message]
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=B1CA6BCA5B0C@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