From: Sergei Sharonov <sergei.sharonov@halliburton.com>
To: linux-mtd@lists.infradead.org
Subject: Re: mounting jffs2
Date: Wed, 13 Apr 2005 17:51:01 +0000 (UTC) [thread overview]
Message-ID: <loom.20050413T193912-984@post.gmane.org> (raw)
In-Reply-To: 1113404557.23175.23.camel@sauron.oktetlabs.ru
Hi,
> > Hmm.. ls is not a writer but it is blocked as well.
> It may be blocked but for shorter time (checking one ore few inodes, not
> all). Do you have very big files or directories with a lot of L1
> children ?
Nope. Just three files: one is 200 MBytes, two others are small.
# time mount /mnt/flash/
real 1m33.528s
user 0m0.010s
sys 1m33.421s
# time ls /mnt/flash/
blockno1 junk test1
real 20m54.573s
user 0m0.010s
sys 9m32.519s
#
This is not usable for embedded application. Have I run into a bug or that
is just how things are with jffs2 on big NANDs? Is that a problem with
a 200 MByte file?
Sergei Sharonov
next prev parent reply other threads:[~2005-04-13 17:56 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-13 13:25 mounting jffs2 Sergei Sharonov
2005-04-13 13:50 ` Artem B. Bityuckiy
2005-04-13 14:22 ` Sergei Sharonov
2005-04-13 15:02 ` Artem B. Bityuckiy
2005-04-13 17:51 ` Sergei Sharonov [this message]
2005-04-14 8:41 ` Artem B. Bityuckiy
2005-04-14 12:39 ` Sergei Sharonov
2005-04-14 13:11 ` Artem B. Bityuckiy
2005-04-14 14:15 ` Sergei Sharonov
2005-04-14 15:18 ` Artem B. Bityuckiy
2005-04-13 15:18 ` Artem B. Bityuckiy
2005-04-14 20:39 ` Sergei Sharonov
2005-04-14 9:01 ` Ferenc Havasi
2005-04-14 9:15 ` Artem B. Bityuckiy
2005-04-20 14:59 ` Sergei Sharonov
2005-04-20 15:20 ` Artem B. Bityuckiy
2005-04-20 16:34 ` Sergei Sharonov
2005-04-21 7:48 ` Artem B. Bityuckiy
2005-04-21 14:30 ` Ferenc Havasi
2005-04-21 15:31 ` Artem B. Bityuckiy
2005-04-26 13:35 ` Zoltan Sogor
2005-04-26 13:51 ` Artem B. Bityuckiy
2005-04-27 9:39 ` Zoltan Sogor
2005-04-21 15:34 ` Sergei Sharonov
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=loom.20050413T193912-984@post.gmane.org \
--to=sergei.sharonov@halliburton.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