[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <8e61baf3-a78e-d17f-ebe2-cd56d6c52259@nod.at>
Date: Mon, 29 May 2017 10:42:37 +0200
From: Richard Weinberger <richard@....at>
To: Hyunchul Lee <hyc.lee@...il.com>
Cc: Artem Bityutskiy <dedekind1@...il.com>, adrian.hunter@...el.com,
linux-kernel@...r.kernel.org, kernel-team@....com,
linux-mtd@...ts.infradead.org, linux-fsdevel@...r.kernel.org,
Christoph Hellwig <hch@...radead.org>
Subject: Re: [PATCH] ubifs: Add freeze support
Hyunchul,
Am 29.05.2017 um 04:24 schrieb Hyunchul Lee:
>>> This is just broken. First ubifs should still properly propagate
>>> the errors, and second freezing/unfreezing read only file systems is
>>> perfectly valid,
>>
>> it is right.
>
> if updating TNC is failed, ubifs might become inconsistant and be switched to
> read-only mode. for example, when ubifs_jnl_update is called to create a file,
> if inserting a znode for new inode is failed, TNC has only a znode for
> new dentry. and this can be only recoverd by replay.
>
> is it required to fix this?
UBIFS is designed to be power-cut tolerant.
So, UBIFS must not corrupt in any case.
Which failure are you facing?
I have the feeling that you try to paper over some other issue. :-)
Thanks,
//richard
Powered by blists - more mailing lists