From: Matthieu CASTET <matthieu.castet@parrot.fr>
To: David Woodhouse <dwmw2@infradead.org>
Cc: linux-mtd@lists.infradead.org
Subject: Re: jffs2 Erase Block Summary overhead
Date: Mon, 19 Feb 2007 11:58:58 +0100 [thread overview]
Message-ID: <45D982F2.6050804@parrot.fr> (raw)
In-Reply-To: <1171879537.7600.5.camel@pmac.infradead.org>
Hi,
David Woodhouse a écrit :
>
> There's a lot of redundant information in the summary; I think we could
> halve it fairly easily.
That would be great :)
> I don't believe your 20% figure though -- that's
> too high. You really can't rely on the output of df.
>
But the jffs2 layer say "no space left on device", so the it is really full.
For more information on the test procedure, I fill the jffs2 filesystem
with someting like :
"i=0; while true; do dd if=/dev/urandom of=file.$i count=1024;
i=$(($i+1));done"
And I can create only 93 complete files, a incomplete file of 430 KB
(and there should be 4 MB taken file others files).
May be I am on a worse test case ?
If I remove "Erase Block Summary", I can really fill the jffs2 up to
60MB [1] instead of 51MB.
Thanks,
Matthieu
[1]
# time mount /dev/mtdblock3 -t jffs2 /tmp/mnt/ ; time cat
/tmp/mnt/root/file.1 > /dev/null ; du -sh /tmp/mnt; df
real 0m 11.91s
user 0m 0.00s
sys 0m 11.91s
real 0m 0.36s
user 0m 0.01s
sys 0m 0.35s
59.8M /tmp/mnt
Filesystem Size Used Available Use% Mounted on
/dev/ram0 4.4M 4.4M 0 100% /
none 7.0M 16.0k 7.0M 0% /tmp
none 7.0M 16.0k 7.0M 0% /tmp
tmpfs 7.0M 16.0k 7.0M 0% /tmp
/dev/mtdblock3 61.5M 60.9M 640.0k 99% /tmp/mnt
next prev parent reply other threads:[~2007-02-19 10:59 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-15 15:30 jffs2 Erase Block Summary overhead Matthieu CASTET
2007-02-19 10:05 ` David Woodhouse
2007-02-19 10:58 ` Matthieu CASTET [this message]
2007-02-19 11:15 ` Matthieu CASTET
2007-02-19 11:10 ` Indrek Kruusa
2007-02-20 8:45 ` Matthieu CASTET
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=45D982F2.6050804@parrot.fr \
--to=matthieu.castet@parrot.fr \
--cc=dwmw2@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 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.