Linux Btrfs filesystem development
 help / color / mirror / Atom feed
From: Duncan <1i5t5.duncan@cox.net>
To: linux-btrfs@vger.kernel.org
Subject: Re: problems with free space cache
Date: Mon, 16 May 2016 05:59:55 +0000 (UTC)	[thread overview]
Message-ID: <pan$d4fda$1f29731$4540c768$ab93bd6f@cox.net> (raw)
In-Reply-To: 85030f6b-b149-ccd2-ea87-42135b9ccd46@cn.fujitsu.com

Qu Wenruo posted on Mon, 16 May 2016 10:24:23 +0800 as excerpted:

> IIRC clear_cache option is fs level option.
> So the first mount with clear_cache, then all subvolume will have
> clear_cache.

Question:  Does clear_cache work with a read-only mount?

I could see it being like the log replay and being done even on ro 
mounts, particularly since unlike the log replay, clear_cache is a 
specific mount option so could be seen as specifically requested even if 
otherwise ro.  Or not.  So I don't know.

He mentioned root, which is normally mounted read-only first.  That's 
what got me thinking about it.  Does that complicate things?

If root is mounted ro without clear_cache by the initr*, will a 
subsequent remount,rw,clear_cache do it?

And for those like me who keep root mounted ro by default, would 
clear_cache work at all, or would it not work until such time as I 
mounted root, or some other subvolume (which I don't have here to worry 
about, but for those who do...) writable?

-- 
Duncan - List replies preferred.   No HTML msgs.
"Every nonfree program has a lord, a master --
and if you use the program, he is your master."  Richard Stallman


  parent reply	other threads:[~2016-05-16  6:00 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-05-16  2:11 problems with free space cache Nicholas D Steeves
2016-05-16  2:24 ` Qu Wenruo
2016-05-16  3:02   ` Nicholas D Steeves
2016-05-16  4:08     ` Qu Wenruo
2016-05-16  5:59   ` Duncan [this message]
2016-05-16  6:20     ` Qu Wenruo
2016-05-16 11:36       ` Austin S. Hemmelgarn
2016-05-17 18:17         ` Nicholas D Steeves
2016-05-18  1:23           ` Qu Wenruo

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='pan$d4fda$1f29731$4540c768$ab93bd6f@cox.net' \
    --to=1i5t5.duncan@cox.net \
    --cc=linux-btrfs@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