From: "Lukáš Czerner" <lczerner@redhat.com>
To: vicentiu.neagoe@ni.com
Cc: linux-ext4@vger.kernel.org
Subject: Re: resilience against power loss
Date: Mon, 28 Jul 2014 10:48:05 +0200 (CEST) [thread overview]
Message-ID: <alpine.LFD.2.00.1407281044200.2077@localhost.localdomain> (raw)
In-Reply-To: <53CE9282.11182.166B0034@vicentiu.neagoe.ni.com>
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.
-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
>
next prev parent reply other threads:[~2014-07-28 8:48 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 [this message]
2014-07-28 15:23 ` Vicentiu Neagoe
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.1407281044200.2077@localhost.localdomain \
--to=lczerner@redhat.com \
--cc=linux-ext4@vger.kernel.org \
--cc=vicentiu.neagoe@ni.com \
/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