linux-ext4 - Re: Commit Interval and Delayed Allocation

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

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <CA+a=Yy4KjhA5N2=ooc3Z405wfGDg2fsUH7qvF=iwJ9hiQM7zkw@mail.gmail.com>
Date:	Tue, 13 Nov 2012 19:37:20 +0800
From:	Peng Tao <bergwolf@...il.com>
To:	"Theodore Ts'o" <tytso@....edu>
Cc:	"Nelson, John R" <John_Nelson@...dent.uml.edu>,
	"linux-ext4@...r.kernel.org" <linux-ext4@...r.kernel.org>
Subject: Re: Commit Interval and Delayed Allocation

On Sat, Nov 10, 2012 at 10:58 AM, Theodore Ts'o <tytso@....edu> wrote:
> On Sat, Nov 10, 2012 at 12:40:42AM +0000, Nelson, John R wrote:
>> Hi,
>>   Say if ext4 commits every 5 seconds, does this mean whatever is
>>buffered for delayed allocation is flushed every 5 seconds as well?
>
> No; there is a separate 30 second timer which is used for writeback
> thread.
>
> For ext3 in data=ordered mode, we will flush out dirty pages for
> inodes which have been written to make sure that stale data can never
> get revealed.
>
> But in delayed allocation, there is no risk that stale data can get
> revealed until we actually allocate the data blocks.
>
Hi Ted,

Then ext4.txt seems need updating? If I understand you correctly, I'd
expect to lose 30 seconds of data rather than 5 seconds if data is
delayed allocated.

172 commit=nrsec    (*)     Ext4 can be told to sync all its data and metadata
173                         every 'nrsec' seconds. The default value
is 5 seconds.
174                         This means that if you lose your power,
you will lose
175                         as much as the latest 5 seconds of work (your
176                         filesystem will not be damaged though, thanks to the
177                         journaling).  This default value (or any low value)
178                         will hurt performance, but it's good for
data-safety.
179                         Setting it to 0 will have the same effect as leaving
180                         it at the default (5 seconds).
181                         Setting it to very large values will improve
182                         performance.

-- 
Thanks,
Tao
--
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