From: David Nicol <davidnicol@gmail.com>
To: Chris Mason <chris.mason@oracle.com>
Cc: Erik Logtenberg <erik@logtenberg.eu>,
linux-btrfs <linux-btrfs@vger.kernel.org>
Subject: Re: What do the arguments of btrfs filesystem defragment do?
Date: Thu, 16 Dec 2010 14:48:53 -0600 [thread overview]
Message-ID: <AANLkTim+hLJOFQcmEJnQVv1verv2x+0-8uwPzLw=tBp-@mail.gmail.com> (raw)
In-Reply-To: <1292440771-sup-9278@think>
On Wed, Dec 15, 2010 at 1:20 PM, Chris Mason <chris.mason@oracle.com> w=
rote:
>>
>> Is there a decent way to have btrfs compress already existing files
>> (that were written before compression was enabled) without hurting a=
ny
>> of the internal structures such as snapshots?
>
> I'm afraid not yet. =C2=A0There is code for this in the btrfs balance
> routines, but we haven't yet adapted it to the defragment command.
>
> -chris
with enough disk space, if the OP adds a compressed device, deletes
the original device, adds it back as compressed, and then deletes the
temporary device, would that work?
--
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:[~2010-12-16 20:48 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-15 16:06 What do the arguments of btrfs filesystem defragment do? Erik Logtenberg
2010-12-15 19:08 ` Chris Mason
2010-12-15 19:14 ` Erik Logtenberg
2010-12-15 19:20 ` Chris Mason
2010-12-15 19:26 ` Erik Logtenberg
2010-12-15 19:57 ` Chris Mason
2010-12-16 8:41 ` Oystein Viggen
2010-12-16 20:48 ` David Nicol [this message]
2010-12-15 19:18 ` Goffredo Baroncelli
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='AANLkTim+hLJOFQcmEJnQVv1verv2x+0-8uwPzLw=tBp-@mail.gmail.com' \
--to=davidnicol@gmail.com \
--cc=chris.mason@oracle.com \
--cc=erik@logtenberg.eu \
--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).