From: "John Hall" <john-news1@cambridgetechgroup.com>
To: linux-mtd@lists.infradead.org
Subject: Re: Lost space on JFFS2 partition
Date: Thu, 28 Aug 2003 14:58:31 +0100 [thread overview]
Message-ID: <414.3f4e0a87.b6729@irwin2.crw.uk.net> (raw)
In-Reply-To: 1062070043.8465.1615.camel@hades.cambridge.redhat.com
On 28 August 2003 12:27, David Woodhouse <dwmw2@infradead.org> wrote:
> > I wasn't sure how JFFS2 does its writes, i.e. whether it did each
> > write immediately to the flash, or whether it would build a page or
> > block's worth before writing to the flash. Now I see that each write
> > is done immediately.
> Not on NAND. We _can't_ just write out every tiny node as it happens,
> since we could violate the writes-per-page limit for NAND. We batch
> writes with a write-behind buffer, flushing it if it's got dirty data
> in after a certain amount of time. It was that flushing which was
> causing the problem. Now we trigger garbage-collection to fill it,
> instead of just padding and wasting the space.
OK, that makes sense.
Is the current CVS head considered stable, and will it work correctly
under 2.4 (in fact armlinux 2.4.18-rmk7)?
On a completely different note, is it possible to disable compression in
JFFS2 without hacking the sourcecode?
Cheers,
John
next prev parent reply other threads:[~2003-08-28 14:05 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-28 9:50 Lost space on JFFS2 partition John Hall
2003-08-28 10:23 ` David Woodhouse
2003-08-28 10:28 ` John Hall
2003-08-28 11:27 ` David Woodhouse
2003-08-28 13:58 ` John Hall [this message]
2003-08-28 14:15 ` David Woodhouse
2003-08-28 14:25 ` John Hall
2003-08-28 14:46 ` 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=414.3f4e0a87.b6729@irwin2.crw.uk.net \
--to=john-news1@cambridgetechgroup.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