From: Bruce Penrod <bmpenrod@endruntechnologies.com>
To: linux-mtd@lists.infradead.org
Subject: JFFS2 messages at shutdown
Date: Mon, 16 Feb 2004 22:50:04 -0800 [thread overview]
Message-ID: <4031B99C.2040908@endruntechnologies.com> (raw)
I am using the MTD/JFFS2 contained in kernel 2.4.20 on a board with a
FLASH configuration that is essentially the AMD NETSC520 evaluation
board, i.e. two AM29LV641 chips on a 32 bit bus. The erase block size
for the two chips together is 128KB. I have two JFFS2 partitions, each
having 1024KB, so I meet the 5 erase blocks minimum requirement.
Everything seems to be working OK, and has been for quite some time.
However, there does seem to be a discrepancy between what df reports on
the jffs2 partitions and what the actual files sizes stored there are.
Perhaps this has been fixed in a later version?
The other question I have is whether or not to worry about these
messages, which are displayed while INIT is running the shutdown script:
jffs2: No clean _or_ dirty blocks to GC from! Where are they all?
jffs2: Couldn't find erase block to garbage collect!
Thanks,
Bruce
reply other threads:[~2004-02-17 6:50 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=4031B99C.2040908@endruntechnologies.com \
--to=bmpenrod@endruntechnologies.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