From: Thomas Gleixner <tglx@linutronix.de>
To: "Jörn Engel" <joern@wohnheim.fh-wedel.de>,
"David Woodhouse" <dwmw2@infradead.org>
Cc: joakim.tjernlund@lumentis.se,
Herman Oosthuysen <Herman@wirelessnetworksinc.com>,
linux-mtd@lists.infradead.org
Subject: Re: JFFS2 Config / FAQ
Date: Mon, 25 Nov 2002 20:32:45 +0100 [thread overview]
Message-ID: <200211252032.45725.tglx@linutronix.de> (raw)
In-Reply-To: <20021125183858.GA26478@wohnheim.fh-wedel.de>
On Monday 25 November 2002 19:38, Jörn Engel wrote:
> On Mon, 25 November 2002 16:19:53 +0000, David Woodhouse wrote:
> > joakim.tjernlund@lumentis.se said:
> > > I think it's 5 blocks currently. It should be possible to lower that
> > > count, but that needs testing.
> >
> > It was tested. It broke. http://mhonarc.axis.se/jffs-dev/msg01495.html
>
> Yes, it broke with a smaller number. But wether that smaller number
> was 4, 1 or 0 is unknown.
>
> I would expect 3 or 4 to be fine, but not bet more than a beer on it.
In August this year I made some cleanup in the GC algorithms, as they went
into an endless GC loop, when the fs was filling up to 100%. I tried also to
reduce blocks, 4 worked sometimes, 3 broke always.
It depends on the filesizes you have on your fs (deleted or overwritten). But
with 5 I was not able to break it again.
--
Thomas
____________________________________________________
linutronix - competence in embedded & realtime linux
http://www.linutronix.de
mail: tglx@linutronix.de
next prev parent reply other threads:[~2002-11-25 19:04 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-17 6:32 JFFS2 basic question xuli
2002-10-17 10:43 ` Wolfgang Denk
2002-10-17 20:46 ` Xiaogeng (Shawn) Jin
2002-10-17 21:17 ` Xiaogeng (Shawn) Jin
2002-11-25 16:06 ` JFFS2 Config / FAQ Herman Oosthuysen
2002-11-25 16:08 ` David Woodhouse
2002-11-25 16:15 ` Joakim Tjernlund
2002-11-25 16:19 ` David Woodhouse
2002-11-25 18:38 ` Jörn Engel
2002-11-25 19:32 ` Thomas Gleixner [this message]
2002-11-25 20:20 ` johan.adolfsson
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=200211252032.45725.tglx@linutronix.de \
--to=tglx@linutronix.de \
--cc=Herman@wirelessnetworksinc.com \
--cc=dwmw2@infradead.org \
--cc=joakim.tjernlund@lumentis.se \
--cc=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