mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: David Woodhouse <dwmw2@infradead.org>
To: Daniel Egger <de@axiros.com>
Cc: cijoml@volny.cz, linux-kernel@vger.kernel.org
Subject: Re: jff2 filesystem in vanilla
Date: Sat, 05 Jun 2004 09:46:51 +0100	[thread overview]
Message-ID: <1086425211.4588.88.camel@imladris.demon.co.uk> (raw)
In-Reply-To: <3F4B6D09-B6CA-11D8-B781-000A958E35DC@axiros.com>

On Sat, 2004-06-05 at 10:27 +0200, Daniel Egger wrote:
> The original version in the 2.4 kernel has a dramatic problem
> leading to FS corruption, at least when used with blkmtd on CF.
> That's why I'm using 2.4 and a CVS snapshot, not only because
> it is much faster.

Can you be more specific? I don't know of any such problems. If they
exist, they give me a potential excuse to update 2.4 to the current code
-- but to be honest I'd rather just leave it in maintenance mode.

> Believe it or not but JFFS2 is the only filesystem that works
> reasonably on CF, especially when the system is used mostly read
> only and the device is cut off from power every now and then. ;)

CF is bog-roll technology. I wouldn't want to use it in production even
with JFFS2 on it -- but at least when it gets confused you'll only lose
a limited amount of data with JFFS2.

If you're going to use JFFS2 on CF, you should really investigate using
the write-buffer we implemented for NAND flash, but without the ECC
parts. It'll mean you write each CF sector once rather than overwriting
the sector each time you add a few bytes to the log.

-- 
dwmw2



  reply	other threads:[~2004-06-05  8:47 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-06-04  8:00 Michal Semler
2004-06-04  9:02 ` Daniel Egger
2004-06-04 23:09   ` David Woodhouse
2004-06-05  8:27     ` Daniel Egger
2004-06-05  8:46       ` David Woodhouse [this message]
2004-06-05 13:38         ` Daniel Egger
2004-06-05 17:01           ` David Woodhouse
2004-06-07 16:19             ` Jörn Engel
2004-06-08  9:31       ` P
2004-06-13  8:39         ` Daniel Egger
2004-06-13 21:33           ` Bernd Eckenfels
2004-06-14 11:45           ` Jörn Engel
2004-06-14 12:03             ` Daniel Egger
2004-06-15  0:12             ` Thomas Gleixner

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=1086425211.4588.88.camel@imladris.demon.co.uk \
    --to=dwmw2@infradead.org \
    --cc=cijoml@volny.cz \
    --cc=de@axiros.com \
    --cc=linux-kernel@vger.kernel.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

all inboxes | Powered by JetHome®