| lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
|
Open Source and information security mailing list archives
| ||
|
Message-ID: <alpine.LFD.2.00.1407281044200.2077@localhost.localdomain> Date: Mon, 28 Jul 2014 10:48:05 +0200 (CEST) From: Lukáš Czerner <lczerner@...hat.com> To: vicentiu.neagoe@...com cc: linux-ext4@...r.kernel.org Subject: Re: resilience against power loss On Tue, 22 Jul 2014, vicentiu.neagoe@...com wrote: > Date: Tue, 22 Jul 2014 19:34:10 +0300 > From: vicentiu.neagoe@...com > To: linux-ext4@...r.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@...r.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@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists