Linux EXT4 FS development
 help / color / mirror / Atom feed
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: Wed, 05 Jun 2024 18:32:12 +0000	[thread overview]
Message-ID: <bug-218932-13602-O6Zx2TSx8t@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-218932-13602@https.bugzilla.kernel.org/>

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

Theodore Tso (tytso@mit.edu) changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
                 CC|                            |tytso@mit.edu
         Resolution|---                         |INVALID

--- Comment #1 from Theodore Tso (tytso@mit.edu) ---
This is not a bug.   What you are observing is the dirty writeback for buffered
I/O.   This is configurable; see [1], and in particular the documentation for
dirty_expire_centisecs, which you can query by looking at the contents of
/proc/sys/vm/dirty_expire_centisecs, and which you can configure by writing to
that file (e.g., "cat 500 > /proc/sys/vm/dirty_expire_centisecs").   Note that
changing dirty_expire_centisecs from 3000 (30 seconds) to 500 (5 seconds) will
have performance implications; there are Very Good Reasons why the default is
set to 30 seconds (as well it being the historic default used by Unix systems
for decades).

[1] https://docs.kernel.org/admin-guide/sysctl/vm.html

Note that if you want to make sure something is written to disk, it's best to
explicit about it, using the fsync(2) system call.

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

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

  reply	other threads:[~2024-06-05 18:32 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 ` bugzilla-daemon [this message]
2024-06-05 18:39 ` [Bug 218932] " 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
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-O6Zx2TSx8t@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