From: Andrew Mahone <andrew.mahone@gmail.com>
To: linux-btrfs@vger.kernel.org
Cc: Andrew Mahone <andrew.mahone@gmail.com>
Subject: [PATCH] Ignore unfragmented file checks in defrag when compression enabled
Date: Mon, 18 Jun 2012 13:27:36 -0400 [thread overview]
Message-ID: <1340040457-16249-1-git-send-email-andrew.mahone@gmail.com> (raw)
I noticed that btrfs fi defrag -c<method> can't be used to compress files
unless they are fragmented. This patch corrects the problem, by informing
should_defrag_range if compression is enabled, and skipping tests for extent
and adjacent extents if it is.
Andrew Mahone (1):
btrfs: ignore unfragmented file checks in defrag when compression
enabled
fs/btrfs/ioctl.c | 10 ++++++----
1 file changed, 6 insertions(+), 4 deletions(-)
--
1.7.10.2
next reply other threads:[~2012-06-18 17:35 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-18 17:27 Andrew Mahone [this message]
2012-06-18 17:27 ` [PATCH] btrfs: ignore unfragmented file checks in defrag when compression enabled Andrew Mahone
2012-06-19 15:01 ` Josef Bacik
2012-06-20 1:08 ` [PATCH] btrfs: ignore unfragmented file checks in defrag when compression enabled - rebased Andrew Mahone
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=1340040457-16249-1-git-send-email-andrew.mahone@gmail.com \
--to=andrew.mahone@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).