From: bugzilla-daemon@kernel.org
To: linux-ext4@vger.kernel.org
Subject: [Bug 218932] Serious problem with ext4 with all kernels, auto-commits do not settle to block device
Date: Fri, 19 Jul 2024 12:33:25 +0000 [thread overview]
Message-ID: <bug-218932-13602-LvxXtfNJIW@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-218932-13602@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=218932
Jan Kara (jack@suse.cz) changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |jack@suse.cz
--- Comment #7 from Jan Kara (jack@suse.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.
next prev parent reply other threads:[~2024-07-19 12:33 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-03 11:40 [Bug 218932] New: Serious problem with ext4 with all kernels, auto-commits do not settle to block device bugzilla-daemon
2024-06-05 18:32 ` [Bug 218932] " bugzilla-daemon
2024-06-05 18:39 ` bugzilla-daemon
2024-06-05 20:16 ` bugzilla-daemon
2024-06-05 20:21 ` bugzilla-daemon
2024-06-05 20:47 ` bugzilla-daemon
2024-06-05 21:01 ` bugzilla-daemon
2024-07-19 12:33 ` bugzilla-daemon [this message]
2024-07-19 20:07 ` bugzilla-daemon
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=bug-218932-13602-LvxXtfNJIW@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@kernel.org \
--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