public inbox for linux-ext4@vger.kernel.org
 help / color / mirror / Atom feed
From: "Lukáš Czerner" <lczerner@redhat.com>
To: Grzegorz Sikorski <g.sikorski@kelvatek.com>
Cc: linux-ext4@vger.kernel.org
Subject: Re: Question about data integrity on SD cards
Date: Wed, 9 Jul 2014 14:51:04 +0200 (CEST)	[thread overview]
Message-ID: <alpine.LFD.2.00.1407091444140.2128@localhost.localdomain> (raw)
In-Reply-To: <53BD32D5.3000804@kelvatek.com>

On Wed, 9 Jul 2014, Grzegorz Sikorski wrote:

> Date: Wed, 09 Jul 2014 13:17:25 +0100
> From: Grzegorz Sikorski <g.sikorski@kelvatek.com>
> To: linux-ext4@vger.kernel.org
> Subject: Question about data integrity on SD cards
> 
> Hi,
> 
> In our project we use SQLite3 database on EXT4 filesystem partition on microSD
> card. On unexpected power failure/system crash or just hardware reset, we
> observe occasional database corruption. SQLite3 developers claim their part is
> free of risk of database corruption, as long as fsync call is doing it's job
> properly. We tried several SD cards, including industrial grade which should
> have proper firmware (at least their manufacturers say there is no risk of
> data corruption on power loss). We tried several different mount settings and
> after some reading we found, that the safest (and slowest) option (that should
> never fail, as far as we understand) would be like:
> rw,relatime,barrier=1,journal_checksum,nodelalloc,data=journal,usrquota
> In spite of all that, we still observe random database corruption on
> power-down/reset. Can you confirm there is no problem in EXT4 filesystem?

There have been reports on SD cards not working correctly on power
failure, most likely due to flush not working correctly. It was
mentioned several times in this huge thread (concerning different
problem, but maybe related)
http://www.spinics.net/lists/linux-ext4/msg43974.html

At this point we do not know about any problems with ext4 file
system regarding fsync functionality. However you have not said
which kernel you are using.

Also, have you tried reproducing it on a different hardware, let's
say SSD, or spinning disk ? Do you have any SD card which seems to
be working reliably across power failures, or did you see that
behaviour with all SD cards you've tested ?

Thanks!
-Lukas

> 
> Best regards,
> Greg
> 
> --
> ExchangeDefender Message Security: Click below to verify authenticity
> https://admin.exchangedefender.com/verify.php?id=s69CHHv3024052&from=g.sikorski@camlintechnologies.com
> 
> 
> --
> 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-09 12:51 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 [this message]
2014-07-09 13:23   ` Grzegorz Sikorski
2014-07-15  7:09     ` David Jander

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=alpine.LFD.2.00.1407091444140.2128@localhost.localdomain \
    --to=lczerner@redhat.com \
    --cc=g.sikorski@kelvatek.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