On Thu, Feb 7, 2013 at 6:28 PM, David Sterba <d...@jikos.cz> wrote:
> On Thu, Feb 07, 2013 at 03:38:34PM -0600, Mitch Harder wrote:
>> --- a/fs/btrfs/relocation.c
>> +++ b/fs/btrfs/relocation.c
>> @@ -144,7 +144,7 @@ struct tree_block {
>> unsigned int key_ready:1;
>> };
>>
>> -#define MAX_EXTENTS 128
>> +#define MAX_EXTENTS 512
>
> Is this really related to compression? IIRC I've seen it only in context
> of batch work in reloc, but not anywhere near compression. (I may be
> wrong of course, just checking).
>
When you defragment compressed extents, it will run through relocation.
If autodefrag is enabled, I found most everything I touched was
running through relocation.
It has been a while since I looked at the issue, but I think balancing
your data will also run through relocation.
--
To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
