linux-ext4.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jan Kara <jack@suse.cz>
To: Raymond Jennings <shentino@gmail.com>
Cc: linux-ext4@vger.kernel.org
Subject: Re: Question about dirty data for unlinked files
Date: Wed, 29 Mar 2017 13:23:46 +0200	[thread overview]
Message-ID: <20170329112346.GB18467@quack2.suse.cz> (raw)
In-Reply-To: <CAGDaZ_qFMGuNMGzvOyStmtC9ZcCH3knHrhaOiP8HvmaphcWvVw@mail.gmail.com>

On Thu 23-03-17 13:07:23, Raymond Jennings wrote:
> If you delete a file (and don't have it open), and there's a bunch of
> dirty data for that file still in page cache, does all that dirty data
> disappear or does it still get written back?

The dirty data just gets discarded when the inode is deleted. In fact if
the file fits in memory (and in dirty_limit), none of the data need to make
it to disk.

								Honza

-- 
Jan Kara <jack@suse.com>
SUSE Labs, CR

      reply	other threads:[~2017-03-29 11:23 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-23 20:07 Question about dirty data for unlinked files Raymond Jennings
2017-03-29 11:23 ` Jan Kara [this message]

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=20170329112346.GB18467@quack2.suse.cz \
    --to=jack@suse.cz \
    --cc=linux-ext4@vger.kernel.org \
    --cc=shentino@gmail.com \
    /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).