From: "\"David Müller (ELSOFT AG)\"" <d.mueller@elsoft.ch>
To: dedekind@infradead.org
Cc: linux-mtd@lists.infradead.org
Subject: Re: JFFS2 access delay
Date: Wed, 25 May 2005 10:01:53 +0200 [thread overview]
Message-ID: <429430F1.2080208@elsoft.ch> (raw)
In-Reply-To: <1116944005.16577.23.camel@sauron.oktetlabs.ru>
Hello
Artem B. Bityuckiy wrote:
>> During this delay, "jffs2_gcd_mtd1" is consuming a large amount of
>> CPU time but the rest of the system seems to be well.
"ls" delay time goes up to over 6 minutes for a tar file containing 1000
files.
> This is normal JFFS2 behaviour (unfortunately). Just after mount
> JFFS2 starts checking process which consumes resources.
This is a little bit of a problem if your system's root file system is
on this partition, blocking the whole boot process :-(
What puzzles me is the fact that the tar file building process
triggers this "weak" point in JFFS2. Tar simply concatenates its input
files together and writes them to the output file (at least this is my
idea of how tar works). So on the file system level, i don't see much
of a difference between a functionality used by "tar" or by "cp". What
is so special about tar?
> What is the size of your flash?
The JFFS2 partition has 126MiB, the whole NAND flash has a size of 128MiB.
Dave
next prev parent reply other threads:[~2005-05-25 8:01 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-24 12:40 JFFS2 access delay "David Müller (ELSOFT AG)"
2005-05-24 14:13 ` Artem B. Bityuckiy
2005-05-25 8:01 ` "David Müller (ELSOFT AG)" [this message]
2005-05-25 8:14 ` Artem B. Bityuckiy
2005-05-24 14:55 ` Jörn Engel
2005-05-25 8:02 ` "David Müller (ELSOFT AG)"
2005-05-25 8:27 ` Artem B. Bityuckiy
2005-05-25 10:06 ` Jörn Engel
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=429430F1.2080208@elsoft.ch \
--to=d.mueller@elsoft.ch \
--cc=dedekind@infradead.org \
--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