From: Richard Weinberger <richard@nod.at>
To: hujianyang <hujianyang@huawei.com>
Cc: linux-mtd <linux-mtd@lists.infradead.org>,
Sheng Yong <shengyong1@huawei.com>,
dedekind1@gmail.com
Subject: Re: [RFC] UBIFS recovery
Date: Mon, 09 Feb 2015 12:05:02 +0100 [thread overview]
Message-ID: <54D8945E.4060807@nod.at> (raw)
In-Reply-To: <54D88E31.10402@huawei.com>
Am 09.02.2015 um 11:38 schrieb hujianyang:
> Hi Artem and Richard,
>
> On 2015/2/9 15:57, Richard Weinberger wrote:
>> Am 09.02.2015 um 08:51 schrieb Artem Bityutskiy:
>>> On Mon, 2015-02-09 at 10:34 +0800, hujianyang wrote:
>>>> Good suggestions. I will try to realize periodically commit first. But I
>>>> don't know if this feature is really needed. Switch to R/O and revert to
>>>> last comitted state? But we just consider about log before, never think
>>>> about index.
>>>
>>> I think the right way to approach this problem is to come up with a high
>>> level summary of the problems we are trying to solve, and the solutions,
>>> along with some analysis of the solutions. This does not have to be very
>>> detailed, but it should put everyone involved into the same page.
>>
>> Agreed. I fear we're talking about different things. :)
>>
>
> I'm afraid I didn't express the use case of the corruption recovery feature.
> UBIFS is used mostly in embedded environment. After products selling out,
> it's hard to debug it. So the production team may consider any failure that
> could happen and put the recovery method into their operation scripts/utilities.
>
> Flash corruption is a problem they need to care about. Using high quality
> cell is not enough, ECC error could not be avoid. So a recovery method which
> is provided by filesystem itself is required. This feature is not used by
> us, the developer of kernel, but the production team. They know little about
> linux kernel. So the easier interface we provide, the much effective recovery
> method of the products they could make. So, Artem, I'm agree with your another
> email mail about R-gadget and H-gadget.
>
> I think mount R/O is a good beginning. We don't need consider much about how
> to recover but can provide a usable(in some cases) file-system. And a R/O
> mount means we could do some cleanup to revert to this R/O state. This R/O
> mount should be provided by driver itself without any userspace tools.
So, at the end of the day you want an UBIFS that can deal with randomly failed PEBs?
Thanks,
//richard
next prev parent reply other threads:[~2015-02-09 11:05 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-05 9:47 [RFC] UBIFS recovery hujianyang
2015-02-05 13:09 ` shengyong
2015-02-06 17:21 ` Artem Bityutskiy
2015-02-05 15:08 ` Steve deRosier
2015-02-05 23:36 ` Richard Weinberger
2015-02-09 12:08 ` Richard Weinberger
2015-02-06 17:26 ` Artem Bityutskiy
2015-02-06 17:33 ` Richard Weinberger
2015-02-06 17:40 ` Artem Bityutskiy
2015-02-06 17:43 ` Richard Weinberger
2015-02-09 3:00 ` hujianyang
2015-02-09 7:56 ` Richard Weinberger
2015-02-09 8:26 ` Artem Bityutskiy
2015-02-09 11:04 ` Richard Weinberger
2015-02-09 11:36 ` Artem Bityutskiy
2015-02-09 11:48 ` Richard Weinberger
2015-02-09 2:48 ` hujianyang
2015-02-09 3:09 ` hujianyang
2015-02-06 17:02 ` Artem Bityutskiy
2015-02-09 2:34 ` hujianyang
2015-02-09 7:51 ` Artem Bityutskiy
2015-02-09 7:57 ` Richard Weinberger
2015-02-09 10:38 ` hujianyang
2015-02-09 11:05 ` Richard Weinberger [this message]
2015-02-09 11:23 ` hujianyang
2015-02-09 11:18 ` Artem Bityutskiy
2015-02-09 12:02 ` hujianyang
2015-02-09 12:12 ` Ricard Wanderlof
2015-02-09 12:38 ` hujianyang
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=54D8945E.4060807@nod.at \
--to=richard@nod.at \
--cc=dedekind1@gmail.com \
--cc=hujianyang@huawei.com \
--cc=linux-mtd@lists.infradead.org \
--cc=shengyong1@huawei.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