linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Darrick J. Wong" <djwong@kernel.org>
To: Phillip Susi <phill@thesusis.net>
Cc: Dave Chinner <david@fromorbit.com>,
	linux-fsdevel@vger.kernel.org, Theodore Ts'o <tytso@mit.edu>
Subject: Re: Uneccesary flushes waking up suspended disks
Date: Fri, 15 Mar 2024 21:38:42 -0700	[thread overview]
Message-ID: <20240316043842.GR6184@frogsfrogsfrogs> (raw)
In-Reply-To: <87h6h78uar.fsf@vps.thesusis.net>

On Fri, Mar 15, 2024 at 10:05:16AM -0400, Phillip Susi wrote:
> Dave Chinner <david@fromorbit.com> writes:
> 
> > How do other filesystems behave? Is this a problem just on specific
> > filesystems?
> 
> I finally got around to testing other filesystems and surprisingly, it
> seems this is only a problem for ext4.  I tried btrfs, f2fs, jfs, udf,
> and xfs.  xfs even uses the same jbd2 for journaling that ext4 does
> doesn't it?

No, xfs has its own logging code.

> I just formatted a clean fs, synced, and ran blktrace, then synced
> again, and only ext4 emits a flush on the second sync.

Heh.  Maybe we should deprecate ext4 then? :)

(Just kidding!)

--D

  reply	other threads:[~2024-03-16  4:38 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-07 13:53 Uneccesary flushes waking up suspended disks Phillip Susi
2024-03-07 15:37 ` Theodore Ts'o
2024-03-08 20:54   ` Phillip Susi
2024-03-09 17:37     ` Theodore Ts'o
2024-03-12 20:35       ` Phillip Susi
2024-03-11  1:32 ` Dave Chinner
2024-03-15 14:05   ` Phillip Susi
2024-03-16  4:38     ` Darrick J. Wong [this message]
2024-03-16 18:35     ` Phillip Susi
2024-03-17 22:45     ` Dave Chinner
2024-03-20 12:38       ` Phillip Susi
2024-03-20 21:58         ` Dave Chinner
2024-03-25 17:09           ` Phillip Susi

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=20240316043842.GR6184@frogsfrogsfrogs \
    --to=djwong@kernel.org \
    --cc=david@fromorbit.com \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=phill@thesusis.net \
    --cc=tytso@mit.edu \
    /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;
as well as URLs for NNTP newsgroup(s).