From: Duncan <1i5t5.duncan@cox.net>
To: linux-btrfs@vger.kernel.org
Subject: Re: [PATCH] improve documentation of snapshot unaware defrag
Date: Sun, 27 Dec 2015 07:09:41 +0000 (UTC) [thread overview]
Message-ID: <pan$3bca9$74a60ba5$bf56792f$3c0040ca@cox.net> (raw)
In-Reply-To: 1451185407-11422-1-git-send-email-mail@christoph.anton.mitterer.name
Christoph Anton Mitterer posted on Sun, 27 Dec 2015 04:03:27 +0100 as
excerpted:
[Rewrapped here but all added lines.]
> +WARNING: Defragmenting with Linux kernel versions < 3.9 or ≥ 3.14-rc2
> as well as
> +with Linux stable kernel versions ≥ 3.10.31, ≥ 3.12.12 or ≥
> 3.13.4 will break up
> +the ref-links of CoW data (for example files copied with
> `cp --reflink`,
> +snapshots or de-duplicated data).
> +This may cause considerable increase of space usage depending on the
> broken up +ref-links.
Thanks. I had looked at that a few times and thought it needed updated,
but I think it hadn't reached my pain threshold yet[1], so I hadn't yet
posted about it.
Glad it reached someone's pain threshold. =:^)
---
[1] Pain threshold: Or more like, I was always doing something else at
the time, which is probably everybody else's excuse too. But by contrast
it can be noted that I posted right away when I noticed the mkfs.btrfs
manpage totally lost raid1 mode with one update, because I use it,
regardless of what else I was doing. I guess that must have hit my pain
threshold...
--
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:[~2015-12-27 7:10 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
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 [this message]
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='pan$3bca9$74a60ba5$bf56792f$3c0040ca@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).