mirroring in JFFS2
joern at wohnheim.fh-wedel.de
Tue Nov 12 12:15:00 EST 2002
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.
Geld macht nicht glücklich.
Glück macht nicht satt.
More information about the linux-mtd