From: Ashok M Padmanaban <ashokmp@sasken.com>
To: MTD for Linux <linux-mtd@lists.infradead.org>,
JFFS mailing list <jffs-dev@axis.com>
Subject: mkfs.jffs2
Date: Wed, 22 Aug 2001 21:00:43 +0000 [thread overview]
Message-ID: <3B841D7B.2D9FD324@sasken.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 738 bytes --]
Hi,
The mkfs.jffs2 has some options, in which -e option specifies the
erase block size, which by default is 64KiB.
While making a jffs2 image of a directory (which has some files) of size
3848192 Bytes.
./mkfs.jffs2 -d directory -o jffs2_img -e 128KiB
With default option for erase block size ( 64KiB), the jffs2 image size
was : 1983612 Bytes. ( 1.89 MB)
With -e 128KiB
, the jffs2 image size was : 7687900 Bytes (7.33 MB)
With -e 256KiB
, the jffs2 image size was : 4289164 Bytes (4.09 MB)
Why is that the jffs2 image size is varying with the erase block size.?
If i have an erase size of 256KiB(on flash), is it necessary that i
should build a jffs2 image with the -e 256KiB option.
regards
ashok
[-- Attachment #2: Card for Ashok M Padmanaban --]
[-- Type: text/x-vcard, Size: 356 bytes --]
begin:vcard
n:.m.padmanabhan;ashok
tel;work:5281461/5281229 ext 3096
x-mozilla-html:FALSE
org:sasken communication technologies ltd;internt access solutions
version:2.1
email;internet:ashokmp@sasken.com
title:software engineer
adr;quoted-printable:;;3008,12 th B cross,=0D=0Aindranagar ;banglore;;;india
x-mozilla-cpt:;0
fn:ashok .m.padmanabhan
end:vcard
next reply other threads:[~2001-08-22 15:23 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-08-22 21:00 Ashok M Padmanaban [this message]
2001-08-22 15:44 ` mkfs.jffs2 Russ Dill
-- strict thread matches above, loose matches on Subject: below --
2002-09-05 12:35 mkfs.jffs2 Kenneth Johansson
2004-08-13 12:02 mkfs.jffs2 Stefan Stürke
2004-08-13 12:31 ` mkfs.jffs2 David Woodhouse
2004-08-13 14:45 ` mkfs.jffs2 Stefan Stürke
2004-08-13 14:54 ` mkfs.jffs2 David Woodhouse
2005-02-21 13:28 mkfs.jffs2 Narinder Kumar
2005-02-21 13:58 ` mkfs.jffs2 Artem B. Bityuckiy
2005-02-21 14:18 ` mkfs.jffs2 Narinder Kumar
2005-02-21 15:21 ` mkfs.jffs2 Andrew Victor
2005-02-24 8:11 ` mkfs.jffs2 Narinder Kumar
2005-02-24 13:20 ` mkfs.jffs2 Artem B. Bityuckiy
2005-02-24 13:41 ` mkfs.jffs2 Narinder Kumar
2005-02-21 14:05 ` mkfs.jffs2 Artem B. Bityuckiy
2005-02-21 14:25 ` mkfs.jffs2 Narinder Kumar
2005-02-21 14:35 ` mkfs.jffs2 Artem B. Bityuckiy
2005-02-22 5:03 ` mkfs.jffs2 Narinder Kumar
2005-06-07 9:32 mk.jffs2 Munira Ahmed
2005-06-07 11:10 ` mkfs.jffs2 Jarkko Lavinen
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=3B841D7B.2D9FD324@sasken.com \
--to=ashokmp@sasken.com \
--cc=jffs-dev@axis.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