public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
From: "Jörn Engel" <joern@wohnheim.fh-wedel.de>
To: David Woodhouse <dwmw2@infradead.org>
Cc: Miraj Mohamed <miraj@procsys.com>,
	jffs-dev@axis.com, linux-mtd@lists.infradead.org
Subject: Re: mirroring in JFFS2
Date: Tue, 12 Nov 2002 18:15:00 +0100	[thread overview]
Message-ID: <20021112171500.GF5031@wohnheim.fh-wedel.de> (raw)
In-Reply-To: <449.1037117917@passion.cambridge.redhat.com>

On Tue, 12 November 2002 16:18:37 +0000, David Woodhouse wrote:
> 
> RAID is done at the wrong layer. The file system knows stuff about the
> contents of the media which a block device driver cannot possibly know. So
> you end up having a RAID rebuild take ages to reconstruct parts of the disc
> which the file system _knows_ are currently unused, etc. 

This is an implementation problem, the RAID driver could as well
reconstruct on the fly and give pending requests priority. No need to
duplicate the code in all the filesystems.

> Getting back to JFFS2, the same applies -- if you have a bad block in one 
> of your flash chips, what do you do about it? Refrain from using the 
> equivalent block in the other chip? Have some kind of block remapper 
> underneath JFFS2, which keeps a whole lot of address information which is 
> in fact entirely superfluous to the file system?

The bad block point does make sense. Hard disks usually work
completely or fail completely. Point taken.

> I think it does want to be done in the file system, or possibly even in a 
> layer _above_ the individual file system, which duplicates writes to two or 
> more underlying file systems of a mountpoint, and do whatever's deemed 
> appropriate for reads. Doing it in the individual file system is probably 
> easier, if less interesting :)

RAID over filesystems would be fun, for sure. But in this case, you
have me convinced, jffs2 is the best place to put it into.

Jörn

-- 
Geld macht nicht glücklich.
Glück macht nicht satt.

  reply	other threads:[~2002-11-12 16:45 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <3DD0D966.E6D877EC@procsys.com>
2002-11-12 16:08 ` mirroring in JFFS2 Jörn Engel
2002-11-12 16:18   ` David Woodhouse
2002-11-12 17:15     ` Jörn Engel [this message]
2002-11-12 17:22     ` Alan Cox
2002-11-12 17:07       ` David Woodhouse
2002-11-12 17:27         ` 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=20021112171500.GF5031@wohnheim.fh-wedel.de \
    --to=joern@wohnheim.fh-wedel.de \
    --cc=dwmw2@infradead.org \
    --cc=jffs-dev@axis.com \
    --cc=linux-mtd@lists.infradead.org \
    --cc=miraj@procsys.com \
    /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