From: Richard Weinberger <richard@nod.at>
To: Marcin Adamski <mass85@tlen.pl>
Cc: linux-mtd@lists.infradead.org
Subject: Re: File in JFFS2 corrupted after power loss during removal of other files
Date: Tue, 05 May 2015 17:44:32 +0200 [thread overview]
Message-ID: <5548E560.5090106@nod.at> (raw)
In-Reply-To: <5b5133fc.589863a5.5548ddf5.c47c7@tlen.pl>
Am 05.05.2015 um 17:12 schrieb Marcin Adamski:
> On Mon, May 5, 2015 at 16:35, Richard Weinberger <richard.weinberger@gmail.com> wrote:
>> I'd say "it's complicated". :)
>>
>> UBIFS was created to deal with such situations.
>> If you want to be on the safe side, use it.
>>
>
> I'm afraid it is too late for me to use UBIFS, as I need to perform upgrade of my devices in the field and migration from JFFS2 to UBIFS seems impossible (at least without some additional free space in flash).
>
> I concluded that JFFS2 should also handle this kind of scenarios after reading about CRC failures in http://www.linux-mtd.infradead.org/faq/jffs2.html#L_messages
AFAIK it depends on the corruption. But JFFS2 predates me. :)
Usually in such situations I inspect the corrupt image by hand.
Maybe it is also an hardware issue. Is this NAND flash?
Thanks,
//richard
next prev parent reply other threads:[~2015-05-05 15:45 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-04 12:42 File in JFFS2 corrupted after power loss during removal of other files Marcin Adamski
2015-05-05 14:35 ` Richard Weinberger
2015-05-05 15:12 ` Marcin Adamski
2015-05-05 15:44 ` Richard Weinberger [this message]
2015-05-05 16:51 ` File in JFFS2 corrupted after power loss during removal of otherfiles Marcin Adamski
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=5548E560.5090106@nod.at \
--to=richard@nod.at \
--cc=linux-mtd@lists.infradead.org \
--cc=mass85@tlen.pl \
/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