linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Andrei Borzenkov <arvidjaar@gmail.com>
To: Hans van Kranenburg <hans.van.kranenburg@mendix.com>,
	Matt McKinnon <matt@techsquare.com>,
	linux-btrfs@vger.kernel.org
Subject: Re: btrfs-transacti hammering the system
Date: Fri, 1 Dec 2017 20:13:52 +0300	[thread overview]
Message-ID: <09218217-6c17-80df-380a-6c20366c70f3@gmail.com> (raw)
In-Reply-To: <5ecddad2-bb6a-2991-c8d0-be97a4541b0d@mendix.com>

01.12.2017 20:06, Hans van Kranenburg пишет:
> 
> Additional tips (forgot to ask for your /proc/mounts before):
> * Use the noatime mount option, so that only accessing files does not
> lead to changes in metadata,

Is not 'lazytime" default today? It gives you correct atime + no extra
metadata update cause by update of atime only.

  reply	other threads:[~2017-12-01 17:13 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-12-01 14:25 btrfs-transacti hammering the system Matt McKinnon
2017-12-01 14:52 ` Hans van Kranenburg
2017-12-01 15:24   ` Matt McKinnon
2017-12-01 15:39     ` Hans van Kranenburg
2017-12-01 15:42       ` Matt McKinnon
2017-12-01 16:31       ` Matt McKinnon
2017-12-01 17:06         ` Hans van Kranenburg
2017-12-01 17:13           ` Andrei Borzenkov [this message]
2017-12-01 18:04             ` Austin S. Hemmelgarn
2017-12-02 19:42               ` Andrei Borzenkov
2017-12-01 17:34           ` Matt McKinnon
2017-12-01 17:57             ` Holger Hoffstätte
2017-12-01 18:24               ` Hans van Kranenburg
2017-12-01 19:07                 ` Matt McKinnon
2017-12-01 21:03                   ` Chris Murphy
2017-12-01 21:47           ` Duncan
2017-12-01 21:50             ` Matt McKinnon
2017-12-04 12:18               ` Austin S. Hemmelgarn
2017-12-04 14:10                 ` Duncan
2017-12-04 14:30                   ` Austin S. Hemmelgarn

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=09218217-6c17-80df-380a-6c20366c70f3@gmail.com \
    --to=arvidjaar@gmail.com \
    --cc=hans.van.kranenburg@mendix.com \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=matt@techsquare.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).