public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
From: enrico benetti <enrico.benetti@bluewind.it>
To: linux-mtd@lists.infradead.org
Subject: UBIFS: power cut test on 2.6.35 + NOR
Date: Thu, 27 Jun 2013 08:44:23 +0200	[thread overview]
Message-ID: <51CBDF47.709@bluewind.it> (raw)

Hi All,
I'd need a hint on the best way to go on with my development.

I'm working on a custom target based on 2.6.35.3 kernel with NOR device.

UBIFS R/W partitions seem not robust against power cut tests: I'm using
integck 1.4.9 and I can have unrecoverable errors on tested volume when
performing real power cuts.

First of all, I've done several MTD stress tests to validate the low
level driver.
I've checked git repos, and
http://git.infradead.org/users/dedekind/ubifs-v2.6.35.git/  
<http://git.infradead.org/users/dedekind/ubifs-v2.6.35.git/shortlog>
is updated to 08/2012 (that is approx 3.7.1 kernel revision) and no more
supported.

  From several discussions on the list I think the best way to solve (or
at least to have a better behaviour with ubi/ubifs) could be to get the
patches from this repo and merge them with my sources.

Do you agree or is it better to do more investigation on current issues?

Thanks in advance for your support,
Enrico

             reply	other threads:[~2013-06-27  6:45 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-06-27  6:44 enrico benetti [this message]
2013-06-27  9:32 ` UBIFS: power cut test on 2.6.35 + NOR Norbert van Bolhuis
2013-06-27 10:47 ` Mats Kärrman
2013-06-27 12:56   ` enrico benetti
2013-06-27 13:01     ` Mats Kärrman
2013-06-28 13:36       ` enrico benetti
2013-06-28 15:03         ` enrico benetti
2013-06-29  2:08         ` Brian Norris
2013-07-01  2:23           ` Huang Shijie

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=51CBDF47.709@bluewind.it \
    --to=enrico.benetti@bluewind.it \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox