From: Duncan <1i5t5.duncan@cox.net>
To: linux-btrfs@vger.kernel.org
Subject: Re: applications hang on a btrfs spanning two partitions
Date: Mon, 14 Jan 2019 05:49:58 +0000 (UTC) [thread overview]
Message-ID: <pan$4ced2$4d8a896d$78f71764$55651a6d@cox.net> (raw)
In-Reply-To: aeaf4b99-a9d5-6335-67f3-e7f851e50b32@florianstecker.de
Florian Stecker posted on Sat, 12 Jan 2019 11:19:14 +0100 as excerpted:
> $ mount | grep btrfs
> /dev/sda8 on / type btrfs
> (rw,relatime,ssd,space_cache,subvolid=5,subvol=/)
Unlikely to be apropos to the problem at hand, but FYI...
Unless you have a known reason not to[1], running noatime with btrfs
instead of the kernel-default relatime is strongly recommended,
especially if you use btrfs snapshotting on the filesystem.
The reasoning is that even tho relatime reduces the default access-time
updates to once a day, it still likely-unnecessarily turns otherwise read-
only operations into read-write operations, and atimes are metadata,
which btrfs always COWs (copy-on-writes), meaning atime updates can
trigger cascading metadata block-writes and much larger than
anticipated[2] write-amplification, potentially hurting performance, yes,
even for relatime, depending on your usage.
In addition, if you're using snapshotting and not using noatime, it can
easily happen that a large portion of the change between one snapshot and
the next is simply atime updates, thus making the space referenced
exclusively by individual affected snapshots far larger than it would
otherwise be.
---
[1] mutt is AFAIK the only widely used application that still depends on
atime updates, and it only does so in certain modes, not with mbox-format
mailboxes, for instance. So unless you're using it, or your backup
solution happens to use atime, chances are quite high that noatime won't
disrupt your usage at all.
[2] Larger than anticipated write-amplification: Especially when you
/thought/ you were only reading the files and hadn't considered the atime
update that read could trigger, thus effectively generating infinity
write amplification because the read access did an atime update and
turned what otherwise wouldn't be a write operation at all into one!
--
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
next prev parent reply other threads:[~2019-01-14 5:52 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-08 19:38 applications hang on a btrfs spanning two partitions Florian Stecker
2019-01-09 6:24 ` Nikolay Borisov
2019-01-09 9:16 ` Florian Stecker
2019-01-09 10:03 ` Nikolay Borisov
2019-01-09 20:10 ` Florian Stecker
2019-01-12 2:12 ` Chris Murphy
2019-01-12 10:19 ` Florian Stecker
2019-01-14 5:49 ` Duncan [this message]
2019-01-14 11:35 ` Marc Joliet
2019-01-15 8:33 ` Duncan
2019-01-15 22:40 ` Marc Joliet
2019-01-17 11:15 ` Duncan
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$4ced2$4d8a896d$78f71764$55651a6d@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