From: David Woodhouse <dwmw2@infradead.org>
To: Victor Tse <victortse@avantwave.com>
Cc: linux-mtd@lists.infradead.org
Subject: Re: jffs2 BUG() in gc.c:135 "Checked all inodes but still..."
Date: Fri, 20 Sep 2002 15:36:53 +0100 [thread overview]
Message-ID: <14573.1032532613@redhat.com> (raw)
In-Reply-To: <1032494909.1059.41.camel@www.avantwave.com>
victortse@avantwave.com said:
> Then reboot withing umounting: http://www.avantwave.com/~victortse/
> jffs2.log2.gz
Hmmm.
jffs2_scan_inode_node(): Node at 0x001aa4a8
Node is ino #46, version 1599. Range 0x3a1000-0x3a2000
jffs2_scan_inode_node(): Node at 0x001aae44
Node is ino #46, version 1600. Range 0x3a2000-0x3a25a8
jffs2_scan_inode_node(): Node at 0x001ab250
Node is ino #46, version 1601. Range 0x3a25a8-0x3a3000
<...>
Node at 001ab250 (0) is a data node
version 1601, highest_version now 1602
dnode @001ab250: ver 1601, offset 3a25a8, dsize 0a58
Unknown INCOMPAT nodetype FFFF at 001AAE44
Node at 001aa4a8 (0) is a data node
version 1599, highest_version now 1602
dnode @001aa4a8: ver 1599, offset 3a1000, dsize 1000
Node at 001aa000 (0) is a data node
<...>
Checked all inodes but still 0x40c bytes of unchecked space?
<...>
clean_list: 001aa000 (used 00001bf0, dirty 00000000, wasted 00000004, unchecked 0000040c, free 00000000)
<...>
kernel BUG at gc.c:135!
So on scan we read a real node from 0x1aae44, but later on during the
readinode we find 0xFFFF as its nodetype. What's _really_ on the flash at
0x1aae44? Is this 100% repeatable with the failure being in the same place?
(And can you reduce the baud rate on your serial console till whatever
you're using for logging can actually keep up)
I can fix the fact that we screw up the accounting and hit the BUG() when we
get this error. But the error should never happen, and if your nodes are
turning into 0xFFFF you are going to lose data. What flash hardware, driver,
etc?
--
dwmw2
next prev parent reply other threads:[~2002-09-20 14:36 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-09-19 10:54 jffs2 BUG() in gc.c:135 "Checked all inodes but still..." Victor Tse
2002-09-19 10:59 ` David Woodhouse
2002-09-20 4:08 ` Victor Tse
2002-09-20 14:36 ` David Woodhouse [this message]
2002-09-20 14:56 ` 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=14573.1032532613@redhat.com \
--to=dwmw2@infradead.org \
--cc=linux-mtd@lists.infradead.org \
--cc=victortse@avantwave.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