From: "Jörn Engel" <joern@wohnheim.fh-wedel.de>
To: David Woodhouse <dwmw2@infradead.org>
Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>,
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:27:51 +0100 [thread overview]
Message-ID: <20021112172751.GG5031@wohnheim.fh-wedel.de> (raw)
In-Reply-To: <6310.1037120842@passion.cambridge.redhat.com>
On Tue, 12 November 2002 17:07:22 +0000, David Woodhouse wrote:
>
> But it's not too bad -- you GC on _both_ media till you have enough space
> on them both for the write you want to do, then you allow the allocation
> call to return, do the write to both media and return. Some detail in
> sorting out the case where a page write crosses an eraseblock boundary and
> ends up split into two on one or both media, but that's not really too hard
> conceptually -- I suspect it'd make an ugly mess of the code though.
I wonder if it would make sense to expand the erase marker a bit in
this case. For two devices, the erase marker on each device holds the
number of the corresponding block on the other. This would allow you
to prioritize bad block recovery, once you find one.
This is quite a special case, though. More devices and the procedure
is pointless. Different device types and the procedure is not
possible.
Jörn
--
"Translations are and will always be problematic. They inflict violence
upon two languages." (translation from German)
prev parent reply other threads:[~2002-11-12 16:57 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
2002-11-12 17:22 ` Alan Cox
2002-11-12 17:07 ` David Woodhouse
2002-11-12 17:27 ` Jörn Engel [this message]
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=20021112172751.GG5031@wohnheim.fh-wedel.de \
--to=joern@wohnheim.fh-wedel.de \
--cc=alan@lxorguk.ukuu.org.uk \
--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