All of lore.kernel.org
 help / color / mirror / Atom feed
From: Chris Mason <chris.mason@oracle.com>
To: Erik Logtenberg <erik@logtenberg.eu>
Cc: linux-btrfs <linux-btrfs@vger.kernel.org>
Subject: Re: What do the arguments of btrfs filesystem defragment do?
Date: Wed, 15 Dec 2010 14:20:06 -0500	[thread overview]
Message-ID: <1292440771-sup-9278@think> (raw)
In-Reply-To: <4D091387.9050905@logtenberg.eu>

Excerpts from Erik Logtenberg's message of 2010-12-15 14:14:15 -0500:
> Chris, thank you very much for your explanation. Indeed this clears
> things up a bit.
> 
> >>> Caveat: Defragmenting a file which has a COW copy (either a snapshot
> >>> copy or one made with bcp or cp --reflinks) will produce two unrelated
> >>> files. If you defragment a subvolume that has a snapshot, you will
> >>> roughly double the disk usage, as the snapshot files are no longer COW
> >>> images of the originals.
> >>
> >> [2] https://btrfs.wiki.kernel.org/index.php/Problem_FAQ
> >>
> >> >From what I've heard on IRC this is still the case in current versions,
> >> but the Btrfs(command) documentation contains no mention of this.
> > 
> > This is still true.
> 
> Is there a decent way to have btrfs compress already existing files
> (that were written before compression was enabled) without hurting any
> of the internal structures such as snapshots?

I'm afraid not yet.  There is code for this in the btrfs balance
routines, but we haven't yet adapted it to the defragment command.

-chris

  reply	other threads:[~2010-12-15 19:20 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 [this message]
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
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=1292440771-sup-9278@think \
    --to=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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.