All of lore.kernel.org
 help / color / mirror / Atom feed
From: "\"David Müller (ELSOFT AG)\"" <d.mueller@elsoft.ch>
To: linux-mtd@lists.infradead.org
Subject: JFFS2 access delay
Date: Tue, 24 May 2005 14:40:49 +0200	[thread overview]
Message-ID: <429320D1.2060003@elsoft.ch> (raw)

Hello

While playing around with JFFS2 on a NAND flash on an ARM based board,
i'm facing a strange problem:


First i create a tar file (using BusyBox's builtin tar command) on a
fresh formatted JFFS2 filesytems from a directory containing about 500
1kB files like this:

~ # flash_eraseall -j /dev/mtd/1
Erasing 16 Kibyte @ 1ea8000 -- 24 % complete. Cleanmarker written at
1ea8000.
Skipping bad block at 0x01eac000
Erasing 16 Kibyte @ 7dfc000 -- 99 % complete. Cleanmarker written at
7dfc000.
~ # mount -t jffs2 /dev/mtdblock/1 /mnt/hd/
~ # tar -cf /mnt/hd/t.tar /tmp/test
tar: Removing leading '/' from member names
~ # time ls -l /mnt/hd/
-rw-r--r--    1 root     root       769536 Jan  1 00:23 t.tar
real    0m 0.05s
user    0m 0.00s
sys     0m 0.04s


Everything seems to be fine. But if i unmount and remount the JFFS2
partition, the first "ls" to the JFFS2 takes quite some time:

~ # umount /mnt/hd/
~ # mount -t jffs2 /dev/mtdblock/1 /mnt/hd/
~ # time ls -l /mnt/hd/
-rw-r--r--    1 root     root       769536 Jan  1 00:23 t.tar
real    1m 32.68s
user    0m 0.01s
sys     0m 7.13s


During this delay, "jffs2_gcd_mtd1" is consuming a large amount of CPU
time but the rest of the system seems to be well.


If i don't build the tar file directly on the JFFS2 partition, but just
copy the final file over from another partition, there isn't such a delay:

~ # umount /mnt/hd/
~ # mount -t jffs2 /dev/mtdblock/1 /mnt/hd/
~ # time ls -l /mnt/hd/
-rw-r--r--    1 root     root       769536 Jan  1 00:53 t.tar
real    0m 0.07s
user    0m 0.01s
sys     0m 0.04s


I'm using linux 2.6.11. I also gave the latest MTD CVS code a try, but
with the same result.

Does this ring a bell? Any idea how to cure this behaviour?


Dave

             reply	other threads:[~2005-05-24 13:50 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-05-24 12:40 "David Müller (ELSOFT AG)" [this message]
2005-05-24 14:13 ` JFFS2 access delay Artem B. Bityuckiy
2005-05-25  8:01   ` "David Müller (ELSOFT AG)"
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=429320D1.2060003@elsoft.ch \
    --to=d.mueller@elsoft.ch \
    --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.