From: Christoph Anton Mitterer <calestyo@scientia.net>
To: fdmanana@gmail.com, Hugo Mills <hugo@carfax.org.uk>,
Btrfs BTRFS <linux-btrfs@vger.kernel.org>
Subject: Re: defrag vs autodefrag
Date: Tue, 22 Dec 2015 21:16:33 +0100 [thread overview]
Message-ID: <1450815393.5520.6.camel@scientia.net> (raw)
In-Reply-To: <CAL3q7H6TGU2rz+zP8hcHxaDGx47nTrCndYvP9ArS+Z0HmZ86=A@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 656 bytes --]
On Mon, 2015-12-21 at 09:28 +0000, Filipe Manana wrote:
> 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.
Thanks for clearing that up.
Could someone then please add an according warning to the btrfs-
mount(5) manpage, as there is for btrfs-filesystem(5)?!
It really shouldn't happen that such dramatic changes get done without
being properly documented and making it quite likely that some user's
filesystems get "blown up" (well at least in the sense that quite some
space may be eaten up).
Cheers,
Chris.
[-- Attachment #2: smime.p7s --]
[-- Type: application/x-pkcs7-signature, Size: 5313 bytes --]
next prev parent reply other threads:[~2015-12-22 20:16 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 [this message]
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=1450815393.5520.6.camel@scientia.net \
--to=calestyo@scientia.net \
--cc=fdmanana@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).