From: A L <crimsoncottage@gmail.com>
To: linux-btrfs@vger.kernel.org
Subject: Re: Is autodefrag recommended?
Date: Tue, 5 Sep 2017 14:36:06 +0200 (GMT+02:00) [thread overview]
Message-ID: <967c296.1c5a576e.15e520a6623@gmail.com> (raw)
In-Reply-To: <710ec5d1-adbf-4ce5-50a5-8b8266ccb672@rqc.ru>
There is a drawback in that defragmentation re-dups data that is previously deduped or shared in snapshots/subvolumes.
---- From: Marat Khalili <mkh@rqc.ru> -- Sent: 2017-09-04 - 11:31 ----
> Hello list,
> good time of the day,
>
> More than once I see mentioned in this list that autodefrag option
> solves problems with no apparent drawbacks, but it's not the default.
> Can you recommend to just switch it on indiscriminately on all
> installations?
>
> I'm currently on kernel 4.4, can switch to 4.10 if necessary (it's
> Ubuntu that gives us this strange choice, no idea why it's not 4.9).
> Only spinning rust here, no SSDs.
>
> --
>
> With Best Regards,
> Marat Khalili
> --
> To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2017-09-05 12:36 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-04 9:31 Is autodefrag recommended? Marat Khalili
2017-09-04 10:23 ` Henk Slager
2017-09-04 10:34 ` Duncan
2017-09-04 11:09 ` Henk Slager
2017-09-04 22:27 ` Duncan
2017-09-04 10:54 ` Hugo Mills
2017-09-05 11:45 ` Austin S. Hemmelgarn
2017-09-05 12:49 ` Henk Slager
2017-09-05 13:00 ` Austin S. Hemmelgarn
2017-09-05 12:36 ` A L [this message]
2017-09-05 14:01 ` Is autodefrag recommended? -- re-duplication??? Marat Khalili
2017-09-05 14:39 ` Hugo Mills
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=967c296.1c5a576e.15e520a6623@gmail.com \
--to=crimsoncottage@gmail.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 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).