From: ching <lsching17@gmail.com>
To: linux-btrfs@vger.kernel.org
Subject: enquiry about defrag
Date: Sun, 09 Sep 2012 08:03:44 +0800 [thread overview]
Message-ID: <504BDCE0.8020407@gmail.com> (raw)
Hi all,
i am new on btrfs, i am testing KVM on btrfs (host: kernel x86-64 3.5.3), the performance is reasonable.
I have two question on defrag, can someone help me?
1. According to btrfs wiki, defragment a COW file will produce two unrelated files.
Does it apply to the "autodefrag" mount option?
2. Is there any command for the fragmentation status of a file/dir ? e.g. fragment size, number of fragments.
next reply other threads:[~2012-09-09 0:03 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-09 0:03 ching [this message]
2012-09-09 0:30 ` enquiry about defrag Jan Steffens
2012-09-09 7:49 ` ching
2012-09-09 9:11 ` Fajar A. Nugraha
2012-09-09 12:05 ` ching
2012-09-10 12:19 ` ching
2012-09-10 13:10 ` Liu Bo
2012-09-10 23:21 ` ching
2012-09-11 1:28 ` Li Zefan
2012-09-11 11:12 ` ching
2012-09-10 9:23 ` Alex Lyakas
2012-09-11 11:12 ` ching
2012-09-11 11:45 ` David Sterba
2012-09-11 23:33 ` ching
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=504BDCE0.8020407@gmail.com \
--to=lsching17@gmail.com \
--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).