From: Jamie Lokier <jamie@shareable.org>
To: Josh Boyer <jwboyer@gmail.com>
Cc: linux-mtd@lists.infradead.org, Duke <ezbonites@gmail.com>
Subject: Re: jffs2: too few erase blocks
Date: Thu, 25 Oct 2007 23:15:53 +0100 [thread overview]
Message-ID: <20071025221553.GA29785@mail.shareable.org> (raw)
In-Reply-To: <20071025092225.410ca383@weaponx.rchland.ibm.com>
Josh Boyer wrote:
> > Hi All,
> > What's the deal with "too few erase blocks" message?
> > Is one block too few for a jffs2 partition?
> > My block size if 256K and I created a small jffs2 256K partition for
> > read/writing.
> > Is this really too small for jffs2? If so, is there anything I can do for this?
>
> Yes, it's too small. JFFS2 requires a certain percentage of blocks in
> the partition to be reserved for it's usage. At one point, it was 5
> eraseblocks.
Fwiw, 5 blocks worth of free space is no guarantee that it'll be fine.
I have a 1MB JFFS2 partition with 64kB eraseblocks. That's 320kB in 5
blocks. But it can return disk full errors when reporting more than
320kB free with 'df' (somewhere between 5 and 6 blocks worth), and it
can also do strange things shortly before it returns disk full errors,
like spending lots of CPU on GC.
-- Jamie
next prev parent reply other threads:[~2007-10-26 0:37 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-25 14:06 jffs2: too few erase blocks Duke
2007-10-25 14:22 ` Josh Boyer
2007-10-25 22:15 ` Jamie Lokier [this message]
2007-10-26 17:00 ` Duke
2007-10-26 21:02 ` Duke
2007-10-28 18:02 ` Jamie Lokier
2007-10-29 2:59 ` David Woodhouse
2007-10-29 14:38 ` Jörn Engel
2007-10-29 20:51 ` Jamie Lokier
2007-10-29 21:40 ` David Woodhouse
2007-10-29 22:50 ` Jamie Lokier
2007-10-29 21:54 ` Jörn Engel
2007-10-29 22:46 ` Jamie Lokier
2007-10-30 16:09 ` Jörn Engel
2007-10-30 20:08 ` Duke
2007-10-30 20:19 ` Jörn Engel
2007-10-30 21:42 ` Duke
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=20071025221553.GA29785@mail.shareable.org \
--to=jamie@shareable.org \
--cc=ezbonites@gmail.com \
--cc=jwboyer@gmail.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