From: Marc Singer <elf@buici.com>
To: David Woodhouse <dwmw2@infradead.org>
Cc: linux-mtd@lists.infradead.org
Subject: Re: Can 256K erase blocks work with JFFS2?
Date: Sun, 15 Feb 2004 08:54:55 -0800 [thread overview]
Message-ID: <20040215165455.GA31480@buici.com> (raw)
In-Reply-To: <1076843296.4484.2.camel@imladris.demon.co.uk>
On Sun, Feb 15, 2004 at 11:08:16AM +0000, David Woodhouse wrote:
> On Sun, 2004-02-15 at 01:53 -0800, Marc Singer wrote:
> > When creating the jffs2 filesystem, if I set the erase block size to
> > 256 then the filesystem created is twice the size of my total flash
> > capacity--can't use it. The default of 64 produces a modest
> > filesystem of 5MB.
>
> 256 would be a problem. 256KiB would be fine. Precisely what did you
> tell mkfs.jffs2, and what version of mkfs.jffs2 is it? Only recent
> versions will _assume_ you're lying if you tell it 256 bytes, and
> silently assume 256KiB instead.
I see. The help isn't clear about what SIZE means.
elf@florence ~...coastal/arm > mkfs.jffs2 -v
mkfs.jffs2 revision 1.19
This version appears to have the code that understands that 256 means
KiB.
And, it still produces an image that is substantially larger that the
source data as well as being larger than the total available flash.
elf@florence ~...coastal/arm > mkfs.jffs2 -e 256kb -r root -o toucan.jffs
elf@florence ~...coastal/arm > ls -l toucan.jffs
-rw-rw-r-- 1 elf elf 18640820 Feb 15 08:52 toucan.jffs
elf@florence ~...coastal/arm > du -s root
5432 root
next prev parent reply other threads:[~2004-02-15 16:54 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-15 9:53 Can 256K erase blocks work with JFFS2? Marc Singer
2004-02-15 11:08 ` David Woodhouse
2004-02-15 16:54 ` Marc Singer [this message]
2004-02-15 17:05 ` David Woodhouse
2004-02-15 17:24 ` David Woodhouse
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=20040215165455.GA31480@buici.com \
--to=elf@buici.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox