From: Duncan <1i5t5.duncan@cox.net>
To: linux-btrfs@vger.kernel.org
Subject: Re: btrfs fi defrag does not defrag files >256kB?
Date: Thu, 28 Jul 2016 17:25:53 +0000 (UTC) [thread overview]
Message-ID: <pan$650d6$3849d593$f6774951$ae97703b@cox.net> (raw)
In-Reply-To: 20160728105555.GR30795@twin.jikos.cz
David Sterba posted on Thu, 28 Jul 2016 12:55:55 +0200 as excerpted:
> On Wed, Jul 27, 2016 at 01:19:01PM -0400, Nicholas D Steeves wrote:
>> > In that regard a defrag -t 32M recommendation is reasonable for a
>> > converted filesystem, tho you can certainly go larger... to 1 GiB as
>> > I said.
And... I see that the progs v4.7-rc1 release has the 32M default.
=:^)
--
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:[~2016-07-28 17:26 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-26 23:03 btrfs fi defrag -r -t 32M? What is actually happening? Nicholas D Steeves
2016-07-27 1:10 ` Duncan
2016-07-27 17:19 ` btrfs fi defrag does not defrag files >256kB? Nicholas D Steeves
2016-07-28 5:14 ` Duncan
2016-07-28 10:55 ` David Sterba
2016-07-28 17:25 ` Duncan [this message]
2016-07-28 17:53 ` Nicholas D Steeves
2016-07-29 3:56 ` 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$650d6$3849d593$f6774951$ae97703b@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;
as well as URLs for NNTP newsgroup(s).