linux-ext4 - [Bug 218932] Serious problem with ext4 with all kernels, auto-commits do not settle to block device

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] [thread-next>] [day] [month] [year] [list]

Message-ID: <bug-218932-13602-LvxXtfNJIW@https.bugzilla.kernel.org/>
Date: Fri, 19 Jul 2024 12:33:25 +0000
From: bugzilla-daemon@...nel.org
To: linux-ext4@...r.kernel.org
Subject: [Bug 218932] Serious problem with ext4 with all kernels,
 auto-commits do not settle to block device

https://bugzilla.kernel.org/show_bug.cgi?id=218932

Jan Kara (jack@...e.cz) changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |jack@...e.cz

--- Comment #7 from Jan Kara (jack@...e.cz) ---
Not sure where you've got the URL in comment 5 from but it is an ancient
version of the documentation. This text has been fixed in 2018. Current version
of the documentation is at
https://www.kernel.org/doc/html/latest/admin-guide/ext4.html and has:

commit=nrsec (*)

    This setting limits the maximum age of the running transaction to ‘nrsec’
seconds. The default value is 5 seconds. This means that if you lose your
power, you will lose as much as the latest 5 seconds of metadata changes (your
filesystem will not be damaged though, thanks to the journaling). This default
value (or any low value) will hurt performance, but it’s good for data-safety.
Setting it to 0 will have the same effect as leaving it at the default (5
seconds). Setting it to very large values will improve performance. Note that
due to delayed allocation even older data can be lost on power failure since
writeback of those data begins only after time set in
/proc/sys/vm/dirty_expire_centisecs.

-- 
You may reply to this email to add a comment.

You are receiving this mail because:
You are watching the assignee of the bug.