From: Grant Edwards <grant.b.edwards@gmail.com>
To: linux-mtd@lists.infradead.org
Subject: Question about mkfs.jffs2 "-s" option
Date: Wed, 2 May 2012 16:08:38 +0000 (UTC) [thread overview]
Message-ID: <jnrm65$im4$1@dough.gmane.org> (raw)
[apologies if this isn't the right forum for mkfs.jffs2 questions]
According the the mkfs.jffs2 man page (from mtd-utils 1.4.8):
-s, --pagesize=SIZE
Use page size SIZE. The default is 4 KiB. This size is the
maximum size of a data node.
I'm using NAND flash with an erase size of 128K.
I've got a directory tree with 68 files. A few are largish (100KB),
but most of them small (a few hundred bytes or less). They contain a
total of 680K bytes of data and take up 900K of space on an ext2
filesystem.
When I do a "mkfs.jffs2 -e128 -l -n" I get a jffs2 image with a size
of 300K. That seems reasonable.
If I specify a page size of 4K (which according to the man page is the
default) by doing "mkfs.jffs2 -e128 -s4KiB -n -l", I get a jffs2 image
with a size of 12MB.
According to the man page the default page size is 4K, so specifying a
page size of 4K shouldn't change anything, right?
Why does specifying a page size of 4K make the jffs2 image 40X larger?
The NAND flash I'm using has to be written in 4K blocks -- isn't that
the "page size"?
--
Grant Edwards grant.b.edwards Yow! Either CONFESS now or
at we go to "PEOPLE'S COURT"!!
gmail.com
next reply other threads:[~2012-05-02 16:10 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-02 16:08 Grant Edwards [this message]
2012-05-03 6:51 ` Question about mkfs.jffs2 "-s" option Shmulik Ladkani
2012-05-03 14:11 ` Grant Edwards
2012-05-03 7:35 ` Ricard Wanderlof
2012-05-03 14:12 ` Grant Edwards
2012-05-03 18:13 ` Shmulik Ladkani
2012-05-03 18:21 ` Grant Edwards
2012-05-04 7:15 ` Artem Bityutskiy
2012-05-04 12:00 ` Shmulik Ladkani
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='jnrm65$im4$1@dough.gmane.org' \
--to=grant.b.edwards@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.