From: "Vicentiu Neagoe" <vicentiu.neagoe@ni.com>
To: linux-ext4@vger.kernel.org
Subject: Re: resilience against power loss
Date: Mon, 28 Jul 2014 18:23:11 +0300 [thread overview]
Message-ID: <53D66ADF.14170.351043D9@vicentiu.neagoe.ni.com> (raw)
In-Reply-To: <alpine.LFD.2.00.1407281044200.2077@localhost.localdomain>
On 28 Jul 2014 at 10:48, Lukás Czerner wrote:
> On Tue, 22 Jul 2014, vicentiu.neagoe@ni.com wrote:
>
> > Date: Tue, 22 Jul 2014 19:34:10 +0300
> > From: vicentiu.neagoe@ni.com
> > To: linux-ext4@vger.kernel.org
> > Subject: resilience against power loss
> >
> > Hello,
> >
> > I'm trying to configure ext4 to prevent data corruption in case of a
> > power loss.
> >
> > I test by doing a cold reset right after writing to a file.
> > I tried the nodelalloc option, but the file still becomes corrupted
> > with trailing garbage.
> >
> > Using ext3, I either get the old version of the file, or the new
> > version, and there is no corruption.
> >
> > Does nodelalloc not guarantee data integrity?
> >
> > Are there any other options that provide complete resilience against
> > power loss?
>
> Well, that would be fsync. It'll make sure that your data actually reach
> disk and that the disk actually write it from the cache to platters.
I don't have control over how the applications were written, yet I
need the system to not corrupt or lose data in case of a power loss.
I have the partition mounted with the sync option but the issue still
reproduces.
Are there no options on ext4 to provide the same data integrity as
data=ordered on ext3? I also tested with Btrfs and there is no data
corruption on a power loss.
Vicentiu
> -Lukas
>
> >
> > thanks
> >
> > Vicentiu
> > --
> > 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
> >
> --
> 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
--
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
prev parent reply other threads:[~2014-07-28 15:23 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-22 16:34 resilience against power loss vicentiu.neagoe
2014-07-28 8:48 ` Lukáš Czerner
2014-07-28 15:23 ` Vicentiu Neagoe [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=53D66ADF.14170.351043D9@vicentiu.neagoe.ni.com \
--to=vicentiu.neagoe@ni.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