public inbox for linux-ext4@vger.kernel.org
 help / color / mirror / Atom feed
From: David Jander <david@protonic.nl>
To: Grzegorz Sikorski <g.sikorski@kelvatek.com>
Cc: "Lukáš Czerner" <lczerner@redhat.com>, linux-ext4@vger.kernel.org
Subject: Re: Question about data integrity on SD cards
Date: Tue, 15 Jul 2014 09:09:36 +0200	[thread overview]
Message-ID: <20140715090936.44531046@archvile> (raw)
In-Reply-To: <53BD4251.3070501@kelvatek.com>

On Wed, 09 Jul 2014 14:23:29 +0100
Grzegorz Sikorski <g.sikorski@kelvatek.com> wrote:

> We are using 2.6.37 version and we may have some issues with underlying 
> mmc-host driver. We also tested our setup on newer kernels as well as 
> different media with similar results, but I was not involved in these 
> tests, so cannot give any details straight away.
> 
> But my main question was partially answered by you. I just need a 
> confirmation that design of our system should in general be OK, as we 
> may expect random power downs occasionally. So do you think it is 
> possible (in general) to build embedded system with SQLite3 database on 
> EXT4 filesystem on SD card that is not fragile on unexpected power 
> sequence? Do you know what type of SD card would be recommended in this 
> case? Are our mounting options fine?

Sorry for the late reaction. In case you still wonder, no. It is not possible
to do this with common (COTS) SD cards in general. Due to their nature, SD
cards can corrupt even data that is not being written to when power is
interrupted during a write (or read) action. There is no filesystem that can
protect you from that.

And btw, the thread Lukáš mentioned is about a bug in ext4, not really about
problems with SD cards.

If you need robust flash storage, please look at MMC 4.41+ enhanced mode and
"reliable-write" functionality. Without these two functions combined, it is
not possible to do what you want to do. I have not seen (non embedded) MMC
cards (in actual SD/MMC-card format) that support version 4.41 or newer of the
(e)MMC standard, but it may be possible that someone makes them.... that might be
a solution for your problem.

Best regards,

-- 
David Jander
Protonic Holland.
--
To unsubscribe from this list: send the line "unsubscribe linux-ext4" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

      reply	other threads:[~2014-07-15  7:09 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-09 12:17 Question about data integrity on SD cards Grzegorz Sikorski
2014-07-09 12:51 ` Lukáš Czerner
2014-07-09 13:23   ` Grzegorz Sikorski
2014-07-15  7:09     ` David Jander [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=20140715090936.44531046@archvile \
    --to=david@protonic.nl \
    --cc=g.sikorski@kelvatek.com \
    --cc=lczerner@redhat.com \
    --cc=linux-ext4@vger.kernel.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