From: David Woodhouse <dwmw2@infradead.org>
To: mike <mikelee@avantwave.com>
Cc: linux-mtd@lists.infradead.org
Subject: Re: jffs2 minimum mtd block size
Date: Wed, 01 Dec 2004 09:48:18 +0000 [thread overview]
Message-ID: <1101894498.4574.104.camel@localhost.localdomain> (raw)
In-Reply-To: <41AD826A.3030809@avantwave.com>
On Wed, 2004-12-01 at 16:35 +0800, mike wrote:
> Dear all
> I want to ask about minimum mtdblock size which jffs2 need . Why i
> ask is because i try to make a 128kbyte mtdblock for my system status
> storage, it fails. And i repartition to 1MB, it consumes the flash
> nearly 600KB without any data.
> Am i do something wrong? or there is a minimum size for jffs2.
> If it is, Could i conclude that jffs2 do not suit to store small
> size of data. And which filesystem expertise can suggest me for this
> purpose?
It needs at least one or two eraseblocks free for garbage collection;
currently it's a little more conservative than that though. You can
reduce the reserved space in jffs2_calc_trigger_levels() in build.c
--
dwmw2
prev parent reply other threads:[~2004-12-01 9:48 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-01 8:35 jffs2 minimum mtd block size mike
2004-12-01 9:48 ` David Woodhouse [this message]
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=1101894498.4574.104.camel@localhost.localdomain \
--to=dwmw2@infradead.org \
--cc=linux-mtd@lists.infradead.org \
--cc=mikelee@avantwave.com \
/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