linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Filipe Manana <fdmanana@gmail.com>
To: Hugo Mills <hugo@carfax.org.uk>,
	Donald Pearson <donaldwhpearson@gmail.com>,
	Btrfs BTRFS <linux-btrfs@vger.kernel.org>
Subject: Re: defrag vs autodefrag
Date: Mon, 21 Dec 2015 09:28:37 +0000	[thread overview]
Message-ID: <CAL3q7H6TGU2rz+zP8hcHxaDGx47nTrCndYvP9ArS+Z0HmZ86=A@mail.gmail.com> (raw)
In-Reply-To: <20151221081432.GR26782@carfax.org.uk>

On Mon, Dec 21, 2015 at 8:14 AM, Hugo Mills <hugo@carfax.org.uk> wrote:
> On Sun, Dec 20, 2015 at 07:26:07PM -0600, Donald Pearson wrote:
>> I read an implication in a different thread that defrag and autodefrag
>> behave differently in that autodefrag is more snapshot friendly for
>> COW data.
>>
>> Did I understand that correctly?  I have not been doing defrag on my
>> virtual machine image directory because I do use a snapshot schedule
>> and the way I understood things, a defrag would basically decouple the
>> live data from the snapshots and greatly increase utilization.
>>
>> It sounded like autodefrag does not have this problem?
>
>    Correct.

Hum?
How is that so? Snapshot-aware defrag was disabled almost 2 years ago,
and that piece of code is used both by a "manual" defrag (ioctl) and
by automatic defrag.

>
>> If that's true, is there any case where it would not be best practice
>> to mount with autodefrag enabled?
>
>    When you are already tight on I/O bandwidth for your application.
> autodefrag increases the amount of I/O the disks do (because it's
> rewriting parts of the file near each write, as well as just the piece
> that's being written by userspace).
>
>    Hugo.
>
> --
> Hugo Mills             | UNIX: Japanese brand of food containers
> hugo@... carfax.org.uk |
> http://carfax.org.uk/  |
> PGP: E2AB1DE4          |



-- 
Filipe David Manana,

"Reasonable men adapt themselves to the world.
 Unreasonable men adapt the world to themselves.
 That's why all progress depends on unreasonable men."

  reply	other threads:[~2015-12-21  9:28 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-12-21  1:26 defrag vs autodefrag Donald Pearson
2015-12-21  3:22 ` Duncan
2015-12-21  8:14 ` Hugo Mills
2015-12-21  9:28   ` Filipe Manana [this message]
2015-12-22 20:16     ` Christoph Anton Mitterer
2015-12-22 20:30     ` Hugo Mills
2015-12-23  2:16       ` Duncan
2015-12-27  3:03     ` [PATCH] improve documentation of snapshot unaware defrag Christoph Anton Mitterer
2015-12-27  3:10       ` Christoph Anton Mitterer
2015-12-27  7:09       ` Duncan
2015-12-28  0:50         ` Christoph Anton Mitterer
2015-12-28  1:58           ` Hugo Mills
2015-12-28  2:07             ` Christoph Anton Mitterer
2015-12-28  9:12             ` Duncan
2015-12-28  2:51           ` Duncan
2015-12-28  3:03             ` Christoph Anton Mitterer
2015-12-28  6: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='CAL3q7H6TGU2rz+zP8hcHxaDGx47nTrCndYvP9ArS+Z0HmZ86=A@mail.gmail.com' \
    --to=fdmanana@gmail.com \
    --cc=donaldwhpearson@gmail.com \
    --cc=hugo@carfax.org.uk \
    --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).