Displaying 3 results from an estimated 3 matches for "cachedata".
Did you mean:
cache_data
2017 Apr 08
2
lvm cache + qemu-kvm stops working after about 20GB of writes
....10 *7.70*
sdd 1.50 0.00 76.00 *199.00* 0.65 0.78
10.66 0.02 0.07 0.16 0.04 0.07 *1.85*
Stuff i've checked/tried:
- The data in the cached LV has then not exceeded even half of the
space, so this should not happen. It even happens when only 20% of
cachedata is used.
- It seems to be triggerd most of the time when %cpy/sync column of `lvs
-a` is about 30%. But this is not always the case!
- changing the cachepolicy from cleaner to smq, wait (check flush ready
with lvs -a) and then back to smq seems to help /sometimes/! But not
always...
lvchange --...
2017 Apr 10
0
lvm cache + qemu-kvm stops working after about 20GB of writes
...0.00 76.00 *199.00* 0.65 0.78
> 10.66 0.02 0.07 0.16 0.04 0.07 *1.85*
>
>
> Stuff i've checked/tried:
>
> - The data in the cached LV has then not exceeded even half of the space,
> so this should not happen. It even happens when only 20% of cachedata is
> used.
> - It seems to be triggerd most of the time when %cpy/sync column of `lvs
> -a` is about 30%. But this is not always the case!
> - changing the cachepolicy from cleaner to smq, wait (check flush ready
> with lvs -a) and then back to smq seems to help *sometimes*! But not...
2017 Apr 20
2
lvm cache + qemu-kvm stops working after about 20GB of writes
...*199.00* 0.65 0.78
> 10.66 0.02 0.07 0.16 0.04 0.07 *1.85*
>
>
> Stuff i've checked/tried:
>
> - The data in the cached LV has then not exceeded even half of the
> space, so this should not happen. It even happens when only 20% of
> cachedata is used.
> - It seems to be triggerd most of the time when %cpy/sync column
> of `lvs -a` is about 30%. But this is not always the case!
> - changing the cachepolicy from cleaner to smq, wait (check flush
> ready with lvs -a) and then back to smq seems to help /sometimes...