From: KimM <kmnet1@gmail.com>
To: linux-mtd@lists.infradead.org
Subject: JFFS2 Garbage collector on 2.6.16
Date: Mon, 07 Aug 2006 09:56:25 +0200 [thread overview]
Message-ID: <pan.2006.08.07.07.56.24.475480@gmail.com> (raw)
Hi all
I have a question regarding the JFFS2 garbage collector.
On my AT91RM9200 system I have a 22 MB JFFS2 RW partition. The mount time
is OK, but the problem is that the garbage collector starts to run and
locks down the system for additional 60-120 seconds!
What happens is:
The System boots
busybox init rcS runs
/ is remounted RW
I get a login prompt
The garbage collector starts/continues to runs I type in login and
password
The system stalls until the garbage collector finishes.
Now, I traced the problem and found that the long runtime of the garbage
collector is causes by a few large files on my system (~6MB). While the GC
process the inodes of any single file, the FS is locked, which is why my
user apps stalls. More specifically, JFFS2 spends it's time in:
jffs2_do_read_inode_internal()
which is called from:
jjffs2_garbage_collect_pass() ->
ffs2_do_crccheck_inode() ->
jffs2_do_read_inode_internal()
Reading the README.Locking explains the GC locking, but I was wondering if
this is really desired behaviour, and if there is anything I can do to
speed up things. I am not brave enough to just change the locking
mechanism...;-)
I should mention that I get the same behaviour on 2.6.17.6...
BTW: what is the correct mail list for strictly JFFS2 related topics? I
tried jffs-dev@axis.com & linux.file-systems.jffs@gmane.org without
success...
BR
Kim
reply other threads:[~2006-08-07 8:19 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=pan.2006.08.07.07.56.24.475480@gmail.com \
--to=kmnet1@gmail.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.