From: Erik Logtenberg <erik@logtenberg.eu>
To: linux-btrfs@vger.kernel.org
Subject: What do the arguments of btrfs filesystem defragment do?
Date: Wed, 15 Dec 2010 17:06:03 +0100 [thread overview]
Message-ID: <4D08E76B.40400@logtenberg.eu> (raw)
Hi,
I would like to know that the arguments of "btrfs filesystem defragment"
do. According to the built-in help page, the invocation is as follows:
> btrfs filesystem defragment [-vcf] [-s start] [-l len] [-t
> size] <file>|<dir> [<file>|<dir>...]
> Defragment a file or a directory.
Unfortunately I can't find any documentation on the meaning of these
arguments. The man page doesn't list these arguments:
> filesystem defragment <file>|<dir> [<file>|<dir>...]
> Defragment files and/or directories.
Also the online documentation [1] is identical to the man page.
[1] https://btrfs.wiki.kernel.org/index.php/Btrfs(command)
On a somewhat related note I did find another page on the wiki [2] that
explains a bit on the defragmenting subject, more specifically it
mentions this rather important caveat:
> 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.
I hope someone can shed some light on these subjects.
Kind regards,
Erik.
next reply other threads:[~2010-12-15 16:06 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-15 16:06 Erik Logtenberg [this message]
2010-12-15 19:08 ` What do the arguments of btrfs filesystem defragment do? 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
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=4D08E76B.40400@logtenberg.eu \
--to=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.