From: Artem Bityutskiy <dedekind1@gmail.com>
To: Ricard Wanderlof <ricard.wanderlof@axis.com>
Cc: Linux mtd <linux-mtd@lists.infradead.org>
Subject: Re: power cut resiliency - ubifs vs. jffs2
Date: Fri, 20 May 2011 16:48:54 +0300 [thread overview]
Message-ID: <1305899334.2630.146.camel@localhost> (raw)
In-Reply-To: <Pine.LNX.4.64.1105201357010.15966@lnxricardw.se.axis.com>
On Fri, 2011-05-20 at 13:59 +0200, Ricard Wanderlof wrote:
> I'm trying to get some grip on how jffs2 fares in comparison with ubifs
> when it comes to managing unexpected power cuts when the system is
> operating. What I've found in the UBIFS FAQ is encouraging, but I was
> wondering if anyone has any practical experience comparing the two in a
> real system?
UBIFS is very stable WRT to power cuts. But the unstable bits problem is
still not solved.
Cannot say anything about JFFS2 - it has not been maintained very well
lately, but I believe the unstable bits problem is there as well.
--
Best Regards,
Artem Bityutskiy (Артём Битюцкий)
prev parent reply other threads:[~2011-05-20 13:52 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-20 11:59 power cut resiliency - ubifs vs. jffs2 Ricard Wanderlof
2011-05-20 13:48 ` 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=1305899334.2630.146.camel@localhost \
--to=dedekind1@gmail.com \
--cc=linux-mtd@lists.infradead.org \
--cc=ricard.wanderlof@axis.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;
as well as URLs for NNTP newsgroup(s).