From: Josef Bacik <jbacik@fb.com>
To: <dsterba@suse.cz>, <linux-btrfs@vger.kernel.org>
Subject: Re: [PATCH] Btrfs: disable snapshot aware defrag for now
Date: Mon, 3 Feb 2014 12:27:56 -0500 [thread overview]
Message-ID: <52EFD19C.3050404@fb.com> (raw)
In-Reply-To: <20140203144802.GK1364@twin.jikos.cz>
On 02/03/2014 09:48 AM, David Sterba wrote:
> On Wed, Jan 29, 2014 at 04:05:30PM -0500, Josef Bacik wrote:
>> It's just broken and it's taking a lot of effort to fix it, so for now just
>> disable it so people can defrag in peace. Thanks,
>>
>> Cc: stable@vger.kernel.org
>> Signed-off-by: Josef Bacik <jbacik@fb.com>
>> ---
>> fs/btrfs/inode.c | 2 +-
>> 1 file changed, 1 insertion(+), 1 deletion(-)
>>
>> diff --git a/fs/btrfs/inode.c b/fs/btrfs/inode.c
>> index 3b65987..8c0bc31 100644
>> --- a/fs/btrfs/inode.c
>> +++ b/fs/btrfs/inode.c
>> @@ -2628,7 +2628,7 @@ static int btrfs_finish_ordered_io(struct btrfs_ordered_extent *ordered_extent)
>> EXTENT_DEFRAG, 1, cached_state);
>> if (ret) {
>> u64 last_snapshot = btrfs_root_last_snapshot(&root->root_item);
>> - if (last_snapshot >= BTRFS_I(inode)->generation)
>> + if (0 && last_snapshot >= BTRFS_I(inode)->generation)
> That's not very flexible, how are we supposed to test that in the
> meantime? Editing sources is not the peferred way.
Well since I'm the only one currently working on fixing it I'm not
worried about it. If anybody else wants to fix it they can easily
change it themselves. It is so totally broken that I don't want it
being turned on by anybody who can't edit this and change it
themselves. Thanks,
Josef
next prev parent reply other threads:[~2014-02-03 17:28 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-29 21:05 [PATCH] Btrfs: disable snapshot aware defrag for now Josef Bacik
2014-02-03 14:48 ` David Sterba
2014-02-03 17:27 ` Josef Bacik [this message]
2014-02-04 3:19 ` Roger Binns
2014-02-04 14:07 ` Josef Bacik
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=52EFD19C.3050404@fb.com \
--to=jbacik@fb.com \
--cc=dsterba@suse.cz \
--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).