On 30.07.19 18:32, Vladimir Sementsov-Ogievskiy wrote:
> Enabled by default copy_range ignores compress option. It's definitely
> unexpected for user.
>
> It's broken since introduction of copy_range usage in backup in
> 9ded4a011496.
>
> Signed-off-by: Vladimir Sementsov-Ogievskiy
> ---
> bloc
On 30.07.19 18:32, Vladimir Sementsov-Ogievskiy wrote:
> Enabled by default copy_range ignores compress option. It's definitely
> unexpected for user.
>
> It's broken since introduction of copy_range usage in backup in
> 9ded4a011496.
>
> Signed-off-by: Vladimir Sementsov-Ogievskiy
> ---
> bloc
30.07.2019 21:22, John Snow wrote:
>
>
> On 7/30/19 12:32 PM, Vladimir Sementsov-Ogievskiy wrote:
>> Enabled by default copy_range ignores compress option. It's definitely
>> unexpected for user.
>>
>> It's broken since introduction of copy_range usage in backup in
>> 9ded4a011496.
>>
>> Signed-o
On 7/30/19 12:32 PM, Vladimir Sementsov-Ogievskiy wrote:
> Enabled by default copy_range ignores compress option. It's definitely
> unexpected for user.
>
> It's broken since introduction of copy_range usage in backup in
> 9ded4a011496.
>
> Signed-off-by: Vladimir Sementsov-Ogievskiy
> ---
>
Enabled by default copy_range ignores compress option. It's definitely
unexpected for user.
It's broken since introduction of copy_range usage in backup in
9ded4a011496.
Signed-off-by: Vladimir Sementsov-Ogievskiy
---
block/backup.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --