From: Peter Grayson <pgrayson@realmsys.com>
To: linux-mtd@lists.infradead.org
Subject: Latest jffs2 broken?
Date: Tue, 23 Aug 2005 17:36:26 -0600 [thread overview]
Message-ID: <1124840186.7086.19.camel@localhost.localdomain> (raw)
I am trying to use the latest mtd from cvs. There appears to be a
problem with jffs2 -- I'm surprised this has not tripped up anyone else
yet. I am seeing a kernel oops when I do the following procedure: erase
an mtd partition, mount the partition as jffs2, touch a file, unmount,
and remount.
This is fully reproducible for me. I am running the latest mtd cvs (as
of 8/23/2005) on a 2.6.10 kernel. I am using a 32MB partition for this
test, but it is not obvious that the partition size matters. My nand
part has a 2048-byte page size and 128 kB eraseblock size.
I have included the output showing the problem. Debug level is set to 1.
Has anyone else run into this?
Pete
---- Debug output below ----
# flash_eraseall -jq /dev/mtd3
# mount /mnt/mtdb3
# touch /mnt/mtdb3/foo
jffs2: No clean, dirty _or_ erasable blocks to GC from! Where are they
all?
jffs2: Couldn't find erase block to garbage collect!
# umount /mnt/mtdb3
# mount /mnt/mtdb3
kernel BUG in read_unknown at fs/jffs2/readinode.c:353!
Oops: Exception in kernel mode, sig: 5 [#1]
TASK = c0601190[74] 'jffs2_gcd_mtd3' THREAD: c044c000
Last syscall: -1
NIP [c00ad818] jffs2_do_read_inode_internal+0x804/0x1220
LR [c00ad1f4] jffs2_do_read_inode_internal+0x1e0/0x1220
Call trace:
[c00ae2a4] jffs2_do_crccheck_inode+0x70/0xcc
[c00b2de4] jffs2_garbage_collect_pass+0x284/0xa80
[c00b4fc8] jffs2_garbage_collect_thread+0x1a0/0x1f4
[c0004f6c] kernel_thread+0x44/0x60
next reply other threads:[~2005-08-23 23:36 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-23 23:36 Peter Grayson [this message]
2005-08-26 12:24 ` Latest jffs2 broken? Ferenc Havasi
2005-08-26 20:01 ` Peter Grayson
2005-09-01 5:02 ` Peter Grayson
2005-09-06 9:00 ` Artem B. Bityuckiy
2005-09-06 9:52 ` Peter Grayson
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=1124840186.7086.19.camel@localhost.localdomain \
--to=pgrayson@realmsys.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.