linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Sebastian Ochmann <ochmann@informatik.uni-bonn.de>
To: linux-btrfs@vger.kernel.org
Subject: Why does btrfs defrag work worse than making a copy of a file?
Date: Tue, 15 Jul 2014 23:17:26 +0200	[thread overview]
Message-ID: <53C59A66.7010107@informatik.uni-bonn.de> (raw)

Hello,

I have a VirtualBox hard drive image which is quite fragmented even 
after very light use; it is 1.6 GB in size and has around 5000 fragments 
(I'm using "filefrag" to determine the number of fragments). Doing a 
"btrfs fi defrag -f image.vdi" reduced the number of fragments to 3749. 
Even doing a "btrfs fi defrag -f -t 1 image.vdi" which should make sure 
every extent is rewritten (according to the btrfs-progs 3.14.2 manpage) 
does not yield any better result and seems to return immediately. 
Copying the file, however, yields a copy which has only 5 fragments 
(simply doing a cp image.vdi image2.vdi; sync; filefrag image2.vdi).

What do I have to do to defrag the file to the minimal number of 
fragments possible? Am I missing something?

Kernel version 3.15.5, btrfs progs 3.14.2, Arch Linux.

Best regards,
Sebastian

             reply	other threads:[~2014-07-15 21:25 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-15 21:17 Sebastian Ochmann [this message]
2014-07-16  7:53 ` Why does btrfs defrag work worse than making a copy of a file? Liu Bo
2014-07-16 10:50   ` Sebastian Ochmann
2014-07-17  3:36     ` Liu Bo

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=53C59A66.7010107@informatik.uni-bonn.de \
    --to=ochmann@informatik.uni-bonn.de \
    --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).