From: Artem Bityutskiy <dedekind1@gmail.com>
To: Ricard Wanderlof <ricard.wanderlof@axis.com>
Cc: "Ivan Djelic" <ivan.djelic@parrot.com>,
"linux-mtd@lists.infradead.org" <linux-mtd@lists.infradead.org>,
"Jean-Sébastien Gagnon" <jsgagnon@vizimax.com>
Subject: RE: UBIFS recovery fails
Date: Sat, 29 Oct 2011 22:43:50 +0300 [thread overview]
Message-ID: <1319917436.2126.0.camel@koala> (raw)
In-Reply-To: <Pine.LNX.4.64.1110240857490.30940@lnxricardw.se.axis.com>
On Mon, 2011-10-24 at 09:00 +0200, Ricard Wanderlof wrote:
> How would UBI+ubifs compare to jffs2 in this respect? I would naïvely
> assume that since jffs2 doesn't do any scrubbing, it would just return ok
> if the data happened to be read correctly that time, and something like an
> I/O error if the data was faulty, but without taking any special action in
> that case?
Yes, I think so.
Artem.
next prev parent reply other threads:[~2011-10-29 19:44 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-17 13:29 UBIFS recovery fails Daniel Kuhn
2011-10-17 20:17 ` Artem Bityutskiy
2011-10-18 8:11 ` Ricard Wanderlof
2011-10-18 8:42 ` Ivan Djelic
2011-10-20 16:37 ` Artem Bityutskiy
2011-10-20 16:36 ` Artem Bityutskiy
2011-10-18 8:29 ` Ivan Djelic
2011-10-19 15:15 ` Artem Bityutskiy
2011-10-19 17:27 ` Ivan Djelic
2011-10-18 12:47 ` Jean-Sébastien Gagnon
2011-10-18 14:54 ` Ivan Djelic
2011-10-18 15:10 ` Jean-Sébastien Gagnon
2011-10-18 15:32 ` Ivan Djelic
2011-10-18 16:05 ` Jean-Sébastien Gagnon
2011-10-19 6:50 ` Ricard Wanderlof
2011-10-19 10:22 ` Ivan Djelic
2011-10-19 12:17 ` Atlant Schmidt
2011-10-19 12:52 ` Ricard Wanderlof
2011-10-19 13:30 ` Atlant Schmidt
2011-10-20 16:43 ` Artem Bityutskiy
2011-10-24 7:00 ` Ricard Wanderlof
2011-10-29 19:43 ` Artem Bityutskiy [this message]
2011-10-20 14:14 ` Artem Bityutskiy
2011-10-18 15:29 ` Daniel Kuhn
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=1319917436.2126.0.camel@koala \
--to=dedekind1@gmail.com \
--cc=ivan.djelic@parrot.com \
--cc=jsgagnon@vizimax.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).