linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Austin S. Hemmelgarn" <ahferroin7@gmail.com>
To: "Janos Toth F." <toth.f.janos@gmail.com>,
	Btrfs BTRFS <linux-btrfs@vger.kernel.org>
Subject: Re: lazytime mount option—no support in Btrfs
Date: Tue, 21 Aug 2018 10:10:04 -0400	[thread overview]
Message-ID: <774d8406-d8c8-f26b-b176-8ac954c59722@gmail.com> (raw)
In-Reply-To: <CANznX5EwH-DSNzFwCiUrLgxA8P_nrNQoVfPQDQ=v6jM2_dEHAw@mail.gmail.com>

On 2018-08-21 09:32, Janos Toth F. wrote:
>>>> so pretty much everyone who wants to avoid the overhead from them can just
>>>> use the `noatime` mount option.
> 
> It would be great if someone finally fixed this old bug then:
> https://bugzilla.kernel.org/show_bug.cgi?id=61601
> Until then, it seems practically impossible to use both noatime (this
> can't be added as rootflag in the command line and won't apply if the
> kernel already mounted the root as RW) and space-cache-v2 (has to be
> added as a rootflag along with RW to take effect) for the root
> filesystem (at least without an init*fs, which I never use, so can't
> tell).
> 
Last I knew, it was fixed.  Of course, it's been quite a while since I 
last tried this, as I run locally patched kernels that have `noatime` as 
the default instead of `relatime`.

Also, once you've got the space cache set up by mounting once writable 
with the appropriate flag and then waiting for it to initialize, you 
should not ever need to specify the `space_cache` option again.

  reply	other threads:[~2018-08-21 17:30 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-08-13 11:50 lazytime mount option—no support in Btrfs Adam Hunt
2017-08-14 13:19 ` Austin S. Hemmelgarn
2018-08-18 20:45 ` waxhead
2018-08-19  8:37   ` Martin Steigerwald
2018-08-19 10:25     ` Andrei Borzenkov
2018-08-20 12:16       ` Austin S. Hemmelgarn
2018-08-21 12:06         ` Adam Borowski
2018-08-21 12:17           ` Austin S. Hemmelgarn
2018-08-21 13:32             ` Janos Toth F.
2018-08-21 14:10               ` Austin S. Hemmelgarn [this message]
2018-08-21 16:05                 ` David Sterba
2018-08-21 17:01                   ` Austin S. Hemmelgarn
2018-08-22  3:57                     ` Duncan
2018-08-22 11:30                       ` Austin S. Hemmelgarn
2018-08-23  4:46                         ` Duncan
2018-08-22 13:48                     ` David Sterba
2018-08-22 13:56                       ` Austin S. Hemmelgarn
2018-08-22 15:01                         ` David Sterba
2018-08-22 16:59                           ` Austin S. Hemmelgarn
2018-08-23 23:33                 ` Janos Toth F.

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=774d8406-d8c8-f26b-b176-8ac954c59722@gmail.com \
    --to=ahferroin7@gmail.com \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=toth.f.janos@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).