public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
From: Fabrice GIRARDOT <fgirardot@besancon.parkeon.com>
To: linux-mtd@lists.infradead.org
Subject: [JFFS2] Garbage collector says "Checked all inodes but still 0x5e3d0 bytes of unchecked space?"
Date: Tue, 08 Apr 2008 16:59:23 +0200	[thread overview]
Message-ID: <47FB884B.9050301@besancon.parkeon.com> (raw)


Hi all.

I'm using a JFFS2 root filesystem on a 2.6.12 Linux kernel,
powered by an ARM9 cpu.
My storage hardware is a 128 MBytes NAND device.

Sometimes, after several unclean system resets, JFFS2's garbage
collector outputs this message :
"Checked all inodes but still 0x5e3d0 bytes of unchecked space?
  kernel BUG at fs/jffs2/gc.c:139!"

As far as I understand, the GC has checked the last inode,
but has still some unchecked space. Since this should not occur,
the code in jffs2's file gc.c reaches a "BUG()" statement.

Some search on this problem did not provides me with much
information.
I found a message in 2002 where the problem could be an hardware
problem (same data not read twice identically), and an other
one sent in 2006 where the "unchecked_size" may be badly computed.

I don't know which exact version of jffs2 I'm using ; my gc.c
file is version 1.144 on 21-dec-2004, which may look a bit old.
Unfortunately, I can not switch to a newer kernel version.

Does somebody has more information on this problem ?
Is it a bug in jffs2 and/or its GC ? Is it fixed ?
Could it be an harwdare problem, confusing jffs2 ?

Any information is welcome.


Regards,

-- 
Fabrice GIRARDOT

             reply	other threads:[~2008-04-08 14:59 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-04-08 14:59 Fabrice GIRARDOT [this message]
2008-04-09  4:48 ` [JFFS2] Garbage collector says "Checked all inodes but still 0x5e3d0 bytes of unchecked space?" Heiko Schocher

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=47FB884B.9050301@besancon.parkeon.com \
    --to=fgirardot@besancon.parkeon.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