From: "Austin S. Hemmelgarn" <ahferroin7@gmail.com>
To: Al <6401e46d@opayq.com>, linux-btrfs@vger.kernel.org
Subject: Re: Interjection: autodefrag mount option aye, nae?
Date: Wed, 20 Jan 2016 10:39:58 -0500 [thread overview]
Message-ID: <569FAA4E.1040204@gmail.com> (raw)
In-Reply-To: <loom.20160120T163054-326@post.gmane.org>
On 2016-01-20 10:33, Al wrote:
> [very quietly] I've had autodefrag out of my mount options for a long while
> now. Is that still the recommended position?
I think it really depends on what you're doing. In my case, I usually
have it on, and the only issue I've ever seen is that Chrome sometimes
loads pages from local cache slower than it should be. I also don't use
ridiculous numbers of snapshots either (I use them only to get a stable
view of the filesystem when generating a backup), so I don't have much
experience with how they interact with autodefrag.
next prev parent reply other threads:[~2016-01-20 15:41 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-14 16:13 Query about proposed dedup patches and behaviours James Hogarth
2016-01-14 16:46 ` Austin S. Hemmelgarn
2016-01-14 19:26 ` Liu Bo
2016-01-14 19:41 ` Austin S. Hemmelgarn
2016-01-15 1:47 ` Duncan
2016-01-15 9:33 ` James Hogarth
2016-01-15 12:18 ` Duncan
2016-01-20 15:33 ` Interjection: autodefrag mount option aye, nae? Al
2016-01-20 15:39 ` Austin S. Hemmelgarn [this message]
2016-01-20 18:39 ` Duncan
2016-01-21 20:59 ` Kai Krakow
2016-01-22 12:14 ` Austin S. Hemmelgarn
2016-01-22 19:43 ` Kai Krakow
2016-01-23 22:11 ` Query about proposed dedup patches and behaviours Mark Fasheh
2016-01-24 5:12 ` 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=569FAA4E.1040204@gmail.com \
--to=ahferroin7@gmail.com \
--cc=6401e46d@opayq.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.