Hi,
Sorry for the late reply.
On Fri, Aug 14, 2015 at 10:19:16AM -0500, Eric Sandeen wrote:
> On 8/13/15 3:47 AM, Liu Bo wrote:
> > Btrfs has a problem when defraging a file which has a large fragment'ed
> > range,
> > it'd leave the tail extent as a seperate extent instead of merging it with
>
On Fri, Aug 14, 2015 at 10:19:16AM -0500, Eric Sandeen wrote:
> On 8/13/15 3:47 AM, Liu Bo wrote:
> > Btrfs has a problem when defraging a file which has a large fragment'ed
> > range,
> > it'd leave the tail extent as a seperate extent instead of merging it with
> > previous extents.
> >
> > Thi
On 8/13/15 3:47 AM, Liu Bo wrote:
> Btrfs has a problem when defraging a file which has a large fragment'ed range,
> it'd leave the tail extent as a seperate extent instead of merging it with
> previous extents.
>
> This makes generic/018 recognize the above regression.
Sorry for the late review,
On Thu, Aug 13, 2015 at 10:43 AM, Filipe David Manana
wrote:
> On Thu, Aug 13, 2015 at 9:47 AM, Liu Bo wrote:
>> Btrfs has a problem when defraging a file which has a large fragment'ed
>> range,
>> it'd leave the tail extent as a seperate extent instead of merging it with
>> previous extents.
>>
On Thu, Aug 13, 2015 at 9:47 AM, Liu Bo wrote:
> Btrfs has a problem when defraging a file which has a large fragment'ed range,
> it'd leave the tail extent as a seperate extent instead of merging it with
> previous extents.
>
> This makes generic/018 recognize the above regression.
>
> Meanwhile,
Btrfs has a problem when defraging a file which has a large fragment'ed range,
it'd leave the tail extent as a seperate extent instead of merging it with
previous extents.
This makes generic/018 recognize the above regression.
Meanwhile, I find that in the case of 'write backwards sync but contig
