Hide Forgot
Created attachment 501117 [details] hsm log Description of problem: vdsm doesn't check volume limitation before extending volume of a vm. virsh -r domblkinfo 121 /rhev/data-center/06b29e0f-8c22-431e-a6f1-75989a582c52/2b27b725-9063-4a27-899a-3ec8d02c1ade/images/8c7091de-f0b3-4026-81cd-3f6014839e27/ea9050e5-94b6-45ca-8445-ccfa64bd5788 Capacity: 10737418240 Allocation: 1078459904 Physical: 42949672960 Version-Release number of selected component (if applicable): vdsm-4.9-67.el6.x86_64 How reproducible: happened on several vms on large scale environment after lots of lvextend failures Steps to Reproduce: 1.no clear reproducer 2. 3. Actual results: Expected results: Additional info:
Created attachment 501118 [details] spm log
vm id = 1df7c00a-0566-4df7-868c-95b2942f42b3
For sparse volumes we should avoid lvExtend beyond volume size
(In reply to comment #4) > For sparse volumes we should avoid lvExtend beyond volume size doesn't qcow have an overhead and built-in bloading which may exceed it?
(In reply to comment #5) > (In reply to comment #4) > > For sparse volumes we should avoid lvExtend beyond volume size > > doesn't qcow have an overhead and built-in bloating which may exceed it? yes, and as far as I recall, the bloat is not strictly bounded. But qcow2 files that are twice as big as their content are probably slow and should be recreated, so it might be a good idea not to lvExtend blindly beyond (twice?) image size.
(In reply to comment #6) > (In reply to comment #5) > > (In reply to comment #4) > > > For sparse volumes we should avoid lvExtend beyond volume size > > > > doesn't qcow have an overhead and built-in bloating which may exceed it? > > yes, and as far as I recall, the bloat is not strictly bounded. But qcow2 files > that are twice as big as their content are probably slow and should be > recreated, so it might be a good idea not to lvExtend blindly beyond (twice?) > image size. That's a feature (just preventing is not good. You need to convert to raw once you reach full volume size or even before that).
Closing old bugs. If this issue is still relevant/important in current version, please re-open the bug.