From: Artem Bityutskiy <dedekind1@gmail.com>
To: Eric Millbrandt <emillbrandt@dekaresearch.com>
Cc: "'linux-mtd@lists.infradead.org'" <linux-mtd@lists.infradead.org>
Subject: RE: ubi volume unmountable after power cut
Date: Mon, 22 Aug 2011 17:35:07 +0300 [thread overview]
Message-ID: <1314023711.2644.124.camel@sauron> (raw)
In-Reply-To: <0A40042D85E7C84DB443060EC44B3FD32A723D86EB@dekaexchange07.deka.local>
On Mon, 2011-08-22 at 10:28 -0400, Eric Millbrandt wrote:
> > -----Original Message-----
> > From: Artem Bityutskiy [mailto:dedekind1@gmail.com]
> > Sent: Monday, August 22, 2011 09:44
> > To: Eric Millbrandt
> > Cc: 'linux-mtd@lists.infradead.org'
> > Subject: RE: ubi volume unmountable after power cut
> >
>
> > Yeah, sorry, no idea. Is this reproducible on other devices?
> >
> We have only seen this one occurrence, hopefully this will be a rare error.
Although you said that pulling the backport tree did not help, I think
it still should be done because it may help to _prevent_ this happening,
even though it did not help _recovering_ from that corruption. The
reason why I emphasize this is because there were a lot of power-cut
tolerance fixes there.
But of course, there is a risk to get new bug with the updates, as
always.
--
Best Regards,
Artem Bityutskiy
next prev parent reply other threads:[~2011-08-22 14:33 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-10 19:46 ubi volume unmountable after power cut Eric Millbrandt
2011-08-12 15:25 ` Matthieu CASTET
2011-08-19 12:11 ` Artem Bityutskiy
2011-08-19 13:42 ` Eric Millbrandt
2011-08-19 15:16 ` Artem Bityutskiy
2011-08-19 17:50 ` Eric Millbrandt
2011-08-22 13:43 ` Artem Bityutskiy
2011-08-22 14:28 ` Eric Millbrandt
2011-08-22 14:35 ` Artem Bityutskiy [this message]
2011-08-22 14:40 ` Eric Millbrandt
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=1314023711.2644.124.camel@sauron \
--to=dedekind1@gmail.com \
--cc=emillbrandt@dekaresearch.com \
--cc=linux-mtd@lists.infradead.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.