public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
From: joern@wohnheim.fh-wedel.de (Jörn Engel)
To: linux-mtd@lists.infradead.org
Subject: not enough blocks for JFFS?
Date: Tue, 25 Mar 2003 01:05:03 +0100	[thread overview]
Message-ID: <20030325000503.GA14469@wohnheim.fh-wedel.de> (raw)
In-Reply-To: <1048483100.3593.3.camel@gobbles>

On Mon, 24 March 2003 15:17:31 -0700, Russ Dill wrote:
> On Sun, 2003-03-23 at 19:31, Tim Wu wrote:
> > Hi! Everybody:
> > 
> > The system I'm working on use a 4MB NOR flash.
> > The block size of the 4MB flash is 64KB.
> > It also has eight smaller(8KB) blocks at bottom.
> > Since, on this system, I don't have much data to write(less than 10KB),
> > a CRAMFS(readonly)+JFFS(writable) combination should be pretty good for me.
> > 
> > Here comes the problem.  The bootloader has occupied the first three 8KB 
> > blocks.  I have only five 8K blocks available for JFFS.  It always fails 
> > when I overwrite an existed file on the JFFS partition.
> 
> Just make a quick user space implementation.

But a filesystem is nicer than a quick user space implementation. :)

Today I have tweaked jffs2 a little to work without compression,
depending on mount options. (patch will follow)

The nice effect of this is that you should be able to work with less
reserved blocks. My estimate is somewhere between one and three. In
Tims case, that would leave him with 16kB net space, enough for his
data. Cool.

Changing the amount of reserved blocks per filesystem (not per kernel)
is a bit tricky. And figuring out, how many are really needed requires
quite a bit of testing or some math. Without compression, math might
even be doable. :)

Tim, would you volunteer to test patches?

J?rn

-- 
The cost of changing business rules is much more expensive for software
than for a secretaty.
-- unknown

  reply	other threads:[~2003-03-25  0:05 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-03-24  2:31 not enough blocks for JFFS? Tim Wu
2003-03-24 22:17 ` Russ Dill
2003-03-25  0:05   ` Jörn Engel [this message]
2003-03-25  2:13     ` Tim Wu
2003-03-25  2:21       ` Russ Dill
2003-03-25 11:24         ` Tim Wu
2003-03-25 12:33         ` Jörn Engel
2003-03-25 19:06           ` Russ Dill
2003-03-26 13:04             ` Jörn Engel
2003-03-25 12:51     ` David Woodhouse
2003-03-25 13:33       ` Jörn Engel
2003-03-25 14:36         ` David Woodhouse
2003-03-26 13:27           ` Jörn Engel
2003-03-30 19:01           ` Jörn Engel
2003-03-30 19:07             ` Jörn Engel
2003-03-30 19:23             ` David Woodhouse
2003-03-30 20:08               ` Jörn Engel
2003-04-07 13:16                 ` Jörn Engel

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=20030325000503.GA14469@wohnheim.fh-wedel.de \
    --to=joern@wohnheim.fh-wedel.de \
    --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