[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]

[linux-lvm] lvreduce & lvextend problem fix

I'm trying to use LVM because of its snapshot and extend/reduce feature.
But I found that they have some problem so I started debugging and found
Please verify that and do further debugging.

lvreduce calls pv_release_pe() to mark unnecessary PEs.
while doing that it does following calculation.

	pe_index = ( vg->lv[i]->lv_current_pe[p].pe -
		LVM_VGDA_SIZE ( vg->pv[pv_num]) / SECTOR_SIZE) /

I don't know why you don't just use p instead of long calculation but 
problem is vg->lv[i]->lv_current_pe[p].pe is not 8192 bytes aligned and
first pe value is bigger than 8192.
In my case it was 8352. And it frees worng PE.

If I subtract 1 from pe_index or just use p then it works fine.
So questions
Why lv_current_pe[x].pe is not 8192 aligned, Is it intended? does it mean
PEs are not aligned in physical disk?
Why does the long calculation is needed only to get the same value with p? 
     when is the case that pe_index is different from p? scattered PEs in
one VG?


[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]