From: "Brian T" <btuch@usa.net>
To: <linux-mtd@lists.infradead.org>
Subject: free_list / free_size messages
Date: Wed, 10 Mar 2004 12:12:21 -0600 [thread overview]
Message-ID: <002901c406cb$3c049ec0$fd0ba8c0@briantpc> (raw)
Hi,
Since moving from JFFS2 2.1 to 2.2, I have noticed klog messages I didn't
see before. It only seems to happen after a fresh flash when writing data
to the romfs. sometimes I get a few messages, but this time I only got the
one:
Mar 10 12:07:25 klogd: Eep. Block 0x00120000 taken from free_list had
free_size of 0x00000038!!
It seems to recover, and I cannot find any corrupt files. I see this error
also listed in the 2.1 source code, but never actually *got* the error
before.
Could someone explain what would cause it? Sorry if this has been discussed
before, I didn't see anything on it when searching.
Thanks,
-Brian
next reply other threads:[~2004-03-10 18:09 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-10 18:12 Brian T [this message]
2004-03-15 21:28 ` free_list / free_size messages Brian T
2004-03-15 21:46 ` David Woodhouse
2004-03-16 4:46 ` Brad Campbell
2004-03-16 8:11 ` David Woodhouse
2004-03-17 17:32 ` Brian T
2004-03-17 17:35 ` 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='002901c406cb$3c049ec0$fd0ba8c0@briantpc' \
--to=btuch@usa.net \
--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