From: Artem Bityutskiy <dedekind@infradead.org>
To: Hamish Moffatt <hamish@cloud.net.au>
Cc: linux-mtd@lists.infradead.org
Subject: Re: ext2 for read-only file system on UBI
Date: Mon, 19 May 2008 10:57:36 +0300 [thread overview]
Message-ID: <1211183856.27243.35.camel@sauron> (raw)
In-Reply-To: <1211183663.27243.32.camel@sauron>
On Mon, 2008-05-19 at 10:54 +0300, Artem Bityutskiy wrote:
> > Thanks for the links. So, read-write with mtdblock is dangerous
> > (regardless of UBI) because it must erase and rewrite a whole block,
> > right?
>
> Yes, and you loose plenty of data in case of power-cuts.
>
> > Proposed ubiblk (linked from above) would use UBI ops to make the
> > update operation safe.
>
> I have not looked that close at Nancy's patches because I did not like
> her unreasonable copy-paste stuff. But I assume she would do something
> like I proposed here:
>
> http://lists.infradead.org/pipermail/linux-mtd/2008-January/020381.html
Basically the idea is to implement something as straightforward as
mtdblock, but using the "atomic LEB change" [1] operation and do not
loose data in case of power-cuts.
1. http://www.linux-mtd.infradead.org/doc/ubi.html#L_lebchange
--
Best regards,
Artem Bityutskiy (Битюцкий Артём)
prev parent reply other threads:[~2008-05-19 7:58 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-19 6:21 ext2 for read-only file system on UBI Hamish Moffatt
2008-05-19 6:37 ` Artem Bityutskiy
2008-05-19 6:56 ` Hamish Moffatt
2008-05-19 7:08 ` Artem Bityutskiy
2008-05-19 7:44 ` Hamish Moffatt
2008-05-19 7:54 ` Artem Bityutskiy
2008-05-19 7:57 ` Artem Bityutskiy [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=1211183856.27243.35.camel@sauron \
--to=dedekind@infradead.org \
--cc=hamish@cloud.net.au \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.