All of lore.kernel.org
 help / color / mirror / Atom feed
From: Phillip Susi <phill@thesusis.net>
To: Dave Chinner <david@fromorbit.com>
Cc: linux-fsdevel@vger.kernel.org, Theodore Ts'o <tytso@mit.edu>
Subject: Re: Uneccesary flushes waking up suspended disks
Date: Wed, 20 Mar 2024 08:38:52 -0400	[thread overview]
Message-ID: <87r0g5ulgj.fsf@vps.thesusis.net> (raw)
In-Reply-To: <ZfdyoJ90mxRLzELg@dread.disaster.area>

Dave Chinner <david@fromorbit.com> writes:

> That's what I expected - I would have been surprised if you found
> problems across multiple filesystems...

How do the other filesystems know they don't need to issue a flush?
While this particular method of reproducing the problem ( sync without
touching the filesystem ) only shows on ext4, I'm not sure this isn't
still a broader problem.

Say that a program writes some data to a file.  Due to cache pressure,
the dirty pages get written to the disk.  Some time later, the disk is
runtime suspended ( which flushes its write cache ).  After that,
someone does some kind of sync ( whole fs or individual file ).  Doesn't
the FS *have* to issue a flush at that point?  Even though there is
nothing in the disk's cache, the FS doesn't know that.


  reply	other threads:[~2024-03-20 12: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
2024-03-16 18:35     ` Phillip Susi
2024-03-17 22:45     ` Dave Chinner
2024-03-20 12:38       ` Phillip Susi [this message]
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=87r0g5ulgj.fsf@vps.thesusis.net \
    --to=phill@thesusis.net \
    --cc=david@fromorbit.com \
    --cc=linux-fsdevel@vger.kernel.org \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.