From: Josef Bacik <josef@redhat.com>
To: Andrew Mahone <andrew.mahone@gmail.com>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: [PATCH] btrfs: ignore unfragmented file checks in defrag when compression enabled
Date: Tue, 19 Jun 2012 11:01:48 -0400 [thread overview]
Message-ID: <20120619150148.GA1705@localhost.localdomain> (raw)
In-Reply-To: <1340040457-16249-2-git-send-email-andrew.mahone@gmail.com>
On Mon, Jun 18, 2012 at 01:27:37PM -0400, Andrew Mahone wrote:
> Inform should_defrag_range if BTRFS_DEFRAG_RANGE_COMPRESS is set. If so, skip
> checks for adjacent extents and extent size when deciding whether to defrag,
> as these can prevent an uncompressed and unfragmented file from being
> compressed as requested.
>
> Signed-off-by: Andrew Mahone <andrew.mahone@gmail.com>
This patch does not apply cleanly at all, please rebase onto btrfs-next and
resend. Thanks,
Josef
next prev parent reply other threads:[~2012-06-19 15:01 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-18 17:27 [PATCH] Ignore unfragmented file checks in defrag when compression enabled Andrew Mahone
2012-06-18 17:27 ` [PATCH] btrfs: ignore " Andrew Mahone
2012-06-19 15:01 ` Josef Bacik [this message]
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=20120619150148.GA1705@localhost.localdomain \
--to=josef@redhat.com \
--cc=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).