1:34 p.m.
--_000_6A17C71B52524C408E7AAF69103E9E490F72FF7Cfabamailserverf_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Hi
I create a lot of Thin Disk VMs from templates every day, and get "paused d=
ue to no storage space error" and "paused due to unknown storage error" on
=
a few of them.
Sometimes the VMs are resumed a few seconds later but sometime not, but I c=
an resume them myself.
I tried to set
volume_utilization_percent=3D15
volume_utilization_chunk_mb=3D4048
in /etc/vdsm/vdsm.conf on every Host
But the Initial Size of the Disk is always 1GB and then increments to 2GB
4GB would be the maximum Size I need before I destroy the VM. So if the ini=
tial Size would be 4GB the pausing shouldn't happen anymore
Thx a lot for your help
Christian
--_000_6A17C71B52524C408E7AAF69103E9E490F72FF7Cfabamailserverf_
Content-Type: text/html; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
<html xmlns:v=3D"urn:schemas-microsoft-com:vml"
xmlns:o=3D"urn:schemas-micr=
osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word"
=
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml"
xmlns=3D"http:=
//www.w3.org/TR/REC-html40" <head <meta http-equiv=3D"Content-Type"
content=3D"text/html; charset=3Dus-ascii"=
<meta name=3D"Generator" content=3D"Microsoft
Word 15 (filtered medium)" <style><!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0cm;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri",sans-serif;
mso-fareast-language:EN-US;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:#0563C1;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:#954F72;
text-decoration:underline;}
span.E-MailFormatvorlage17
{mso-style-type:personal-compose;
font-family:"Calibri",sans-serif;
color:windowtext;}
.MsoChpDefault
{mso-style-type:export-only;
font-family:"Calibri",sans-serif;
mso-fareast-language:EN-US;}
@page WordSection1
{size:612.0pt 792.0pt;
margin:70.85pt 70.85pt 2.0cm 70.85pt;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" / </xml><![endif]--><!--[if gte mso
9]><xml <o:shapelayout
v:ext=3D"edit" <o:idmap v:ext=3D"edit"
data=3D"1" /
</o:shapelayout></xml><![endif]--
</head <body lang=3D"DE-AT"
link=3D"#0563C1" vlink=3D"#954F72" <div
class=3D"WordSection1" <p
class=3D"MsoNormal"><span
lang=3D"EN-US">Hi<o:p></o:p></span></p <p class=3D"MsoNormal"><span
lang=3D"EN-US">I create a lot of Thin Disk VMs=
from templates every day, and get „paused due to no storage space er=
ror“ and „paused due to unknown storage error“ on a few o=
f them.<o:p></o:p></span></p <p
class=3D"MsoNormal"><span lang=3D"EN-US">Sometimes the VMs
are resumed a=
few seconds later but sometime not, but I can resume them myself.<o:p></o:=
p></span></p <p
class=3D"MsoNormal"><span
lang=3D"EN-US"><o:p> </o:p></span></p <p class=3D"MsoNormal"><span
lang=3D"EN-US">I tried to set<o:p></o:p></span=
></p <p
class=3D"MsoNormal"><span
lang=3D"EN-US">volume_utilization_percent=3D15=
<o:p></o:p></span></p <p
class=3D"MsoNormal"><span
lang=3D"EN-US">volume_utilization_chunk_mb=3D4=
048<o:p></o:p></span></p <p
class=3D"MsoNormal"><span
lang=3D"EN-US"><o:p> </o:p></span></p <p class=3D"MsoNormal"><span
lang=3D"EN-US">in /etc/vdsm/vdsm.conf on every=
Host<o:p></o:p></span></p <p
class=3D"MsoNormal"><span
lang=3D"EN-US"><o:p> </o:p></span></p <p class=3D"MsoNormal"><span
lang=3D"EN-US">But the Initial Size of the Dis=
k is always 1GB and then increments to 2GB<o:p></o:p></span></p <p class=3D"MsoNormal"><span
lang=3D"EN-US"><o:p> </o:p></span></p <p class=3D"MsoNormal"><span
lang=3D"EN-US">4GB would be the maximum Size I=
need before I destroy the VM. So if the initial Size would be 4GB the paus=
ing shouldn’t happen anymore<o:p></o:p></span></p <p class=3D"MsoNormal"><span
lang=3D"EN-US"><o:p> </o:p></span></p <p class=3D"MsoNormal"><span
lang=3D"EN-US">Thx a lot for your help<o:p></o=
:p></span></p <p
class=3D"MsoNormal"><span
lang=3D"EN-US">Christian<o:p></o:p></span></p </div
</body </html
--_000_6A17C71B52524C408E7AAF69103E9E490F72FF7Cfabamailserverf_--
2:23 p.m.
On Fri, May 13, 2016 at 1:34 PM, Grundmann, Christian
<Christian.Grundmann(a)fabasoft.com> wrote:
Hi
I create a lot of Thin Disk VMs from templates every day, and get „paused
due to no storage space error“ and „paused due to unknown storage error“ on
a few of them.
Sometimes the VMs are resumed a few seconds later but sometime not, but I
can resume them myself.
I tried to set
volume_utilization_percent=15
volume_utilization_chunk_mb=4048
This looks correct if this is in the [irs] section of the configuration.
[irs]
# Together with volume_utilization_chunk_mb, set the minimal free
# space before a thin provisioned block volume is extended. Use lower
# values to extend earlier.
# volume_utilization_percent = 50
# Size of extension chunk in megabytes, and together with
# volume_utilization_percent, set the free space limit. Use higher
# values to extend in bigger chunks.
# volume_utilization_chunk_mb = 1024
To get the correct configuration format, you can do:
python /usr/lib/python2.7/site-packages/vdsm/config.py
in /etc/vdsm/vdsm.conf on every Host
But the Initial Size of the Disk is always 1GB and then increments to 2GB
Please share the vdsm.conf file with these settings.
4GB would be the maximum Size I need before I destroy the VM. So if the
initial Size would be 4GB the pausing shouldn’t happen anymore
The initial volume size is always 1GiB, regardless of these settings.
After creating 1GiB lv, we extend the lv volume_utilization_chunk_mb megabytes.
So your setting will result in 1GiB lv, and after you write about
150MiB, it will be extended
to 5GiB.
So I guess that you want to use
volume_utilization_chunk_mb = 3072
Which will give you 4GiB lv after the first extend.
We support initialSize argument when creating volumes - use when importing
external vms (v2v), but it is not exposed in the ui.
If you think think exposing it in the ui is a useful feature, you can
file a bug:
https://bugzilla.redhat.com/enter_bug.cgi?product=ovirt-engine
Nir
2:32 p.m.
Hi,
@ This looks correct if this is in the [irs] section of the configuration.
It is
cat /etc/vdsm/vdsm.conf
[vars]
ssl = true
[addresses]
management_port = 54321
[irs ]
volume_utilization_percent=15
volume_utilization_chunk_mb=4048
do I need a space before and after the = ?
@ We support initialSize argument when creating volumes - use when importing external vms
(v2v), but it is not exposed in the ui.
If you think think exposing it in the ui is a useful feature, you can file a bug:
https://bugzilla.redhat.com/enter_bug.cgi?product=ovirt-engine
I don't need it in the ui, but it would be nice to have it as tuneable
Thx
Christian
-----Ursprüngliche Nachricht-----
Von: Nir Soffer [mailto:nsoffer@redhat.com]
Gesendet: Freitag, 13. Mai 2016 13:24
An: Grundmann, Christian <Christian.Grundmann(a)fabasoft.com>
Cc: users(a)ovirt.org
Betreff: Re: [ovirt-users] volume_utilization_chunk_mb not working
On Fri, May 13, 2016 at 1:34 PM, Grundmann, Christian
<Christian.Grundmann(a)fabasoft.com> wrote:
Hi
I create a lot of Thin Disk VMs from templates every day, and get
„paused due to no storage space error“ and „paused due to unknown
storage error“ on a few of them.
Sometimes the VMs are resumed a few seconds later but sometime not,
but I can resume them myself.
I tried to set
volume_utilization_percent=15
volume_utilization_chunk_mb=4048
This looks correct if this is in the [irs] section of the configuration.
[irs]
# Together with volume_utilization_chunk_mb, set the minimal free # space before a thin
provisioned block volume is extended. Use lower # values to extend earlier.
# volume_utilization_percent = 50
# Size of extension chunk in megabytes, and together with # volume_utilization_percent,
set the free space limit. Use higher # values to extend in bigger chunks.
# volume_utilization_chunk_mb = 1024
To get the correct configuration format, you can do:
python /usr/lib/python2.7/site-packages/vdsm/config.py
in /etc/vdsm/vdsm.conf on every Host
But the Initial Size of the Disk is always 1GB and then increments to
2GB
Please share the vdsm.conf file with these settings.
4GB would be the maximum Size I need before I destroy the VM. So if
the initial Size would be 4GB the pausing shouldn’t happen anymore
The initial volume size is always 1GiB, regardless of these settings.
After creating 1GiB lv, we extend the lv volume_utilization_chunk_mb megabytes.
So your setting will result in 1GiB lv, and after you write about 150MiB, it will be
extended to 5GiB.
So I guess that you want to use
volume_utilization_chunk_mb = 3072
Which will give you 4GiB lv after the first extend.
We support initialSize argument when creating volumes - use when importing external vms
(v2v), but it is not exposed in the ui.
If you think think exposing it in the ui is a useful feature, you can file a bug:
https://bugzilla.redhat.com/enter_bug.cgi?product=ovirt-engine
Nir
2:51 p.m.
On Fri, May 13, 2016 at 2:32 PM, Grundmann, Christian
<Christian.Grundmann(a)fabasoft.com> wrote:
Hi,
@ This looks correct if this is in the [irs] section of the configuration.
It is
cat /etc/vdsm/vdsm.conf
[vars]
ssl = true
[addresses]
management_port = 54321
[irs ]
This is the "irs " section, not the "irs" section :-)
volume_utilization_percent=15
volume_utilization_chunk_mb=4048
do I need a space before and after the = ?
No, it is just more human friendly this way.
@ We support initialSize argument when creating volumes - use when
importing external vms (v2v), but it is not exposed in the ui.
If you think think exposing it in the ui is a useful feature, you can file a bug:
https://bugzilla.redhat.com/enter_bug.cgi?product=ovirt-engine
I don't need it in the ui, but it would be nice to have it as tuneable
I checked the code, and we actually do use volume_utilization_chunk_mb
when we create the initial disk, so getting the configuration to work
will solve your issue.
Nir
2:53 p.m.
Oh, i see
Is there a way to reload the config without going to maintenance mode?
Thx
Christian
-----Ursprüngliche Nachricht-----
Von: Nir Soffer [mailto:nsoffer@redhat.com]
Gesendet: Freitag, 13. Mai 2016 13:52
An: Grundmann, Christian <Christian.Grundmann(a)fabasoft.com>
Cc: users(a)ovirt.org
Betreff: Re: [ovirt-users] volume_utilization_chunk_mb not working
On Fri, May 13, 2016 at 2:32 PM, Grundmann, Christian
<Christian.Grundmann(a)fabasoft.com> wrote:
Hi,
@ This looks correct if this is in the [irs] section of the configuration.
It is
cat /etc/vdsm/vdsm.conf
[vars]
ssl = true
[addresses]
management_port = 54321
[irs ]
This is the "irs " section, not the "irs" section :-)
volume_utilization_percent=15
volume_utilization_chunk_mb=4048
do I need a space before and after the = ?
No, it is just more human friendly this way.
@ We support initialSize argument when creating volumes - use when
importing external vms (v2v), but it is not exposed in the ui.
If you think think exposing it in the ui is a useful feature, you can file a bug:
https://bugzilla.redhat.com/enter_bug.cgi?product=ovirt-engine
I don't need it in the ui, but it would be nice to have it as tuneable
I checked the code, and we actually do use volume_utilization_chunk_mb when we create the
initial disk, so getting the configuration to work will solve your issue.
Nir
3 p.m.
On Fri, May 13, 2016 at 2:53 PM, Grundmann, Christian
<Christian.Grundmann(a)fabasoft.com> wrote:
Oh, i see
Is there a way to reload the config without going to maintenance mode?
You can restart the service.
On the spm this will abort operations like copying disks and like, this is
safe.
Nir
Thx
Christian
-----Ursprüngliche Nachricht-----
Von: Nir Soffer [mailto:nsoffer@redhat.com]
Gesendet: Freitag, 13. Mai 2016 13:52
An: Grundmann, Christian <Christian.Grundmann(a)fabasoft.com>
Cc: users(a)ovirt.org
Betreff: Re: [ovirt-users] volume_utilization_chunk_mb not working
On Fri, May 13, 2016 at 2:32 PM, Grundmann, Christian
<Christian.Grundmann(a)fabasoft.com> wrote:
> Hi,
> @ This looks correct if this is in the [irs] section of the configuration.
> It is
>
> cat /etc/vdsm/vdsm.conf
> [vars]
> ssl = true
>
> [addresses]
> management_port = 54321
>
> [irs ]
This is the "irs " section, not the "irs" section :-)
> volume_utilization_percent=15
> volume_utilization_chunk_mb=4048
>
> do I need a space before and after the = ?
No, it is just more human friendly this way.
> @ We support initialSize argument when creating volumes - use when importing external
vms (v2v), but it is not exposed in the ui.
> If you think think exposing it in the ui is a useful feature, you can file a bug:
> https://bugzilla.redhat.com/enter_bug.cgi?product=ovirt-engine
>
> I don't need it in the ui, but it would be nice to have it as tuneable
I checked the code, and we actually do use volume_utilization_chunk_mb when we create the
initial disk, so getting the configuration to work will solve your issue.
Nir
3:20 p.m.
Hi,
it works now,
Thx a lot
-----Ursprüngliche Nachricht-----
Von: Nir Soffer [mailto:nsoffer@redhat.com]
Gesendet: Freitag, 13. Mai 2016 14:00
An: Grundmann, Christian <Christian.Grundmann(a)fabasoft.com>
Cc: users(a)ovirt.org
Betreff: Re: [ovirt-users] volume_utilization_chunk_mb not working
On Fri, May 13, 2016 at 2:53 PM, Grundmann, Christian
<Christian.Grundmann(a)fabasoft.com> wrote:
Oh, i see
Is there a way to reload the config without going to maintenance mode?
You can restart the service.
On the spm this will abort operations like copying disks and like, this is safe.
Nir
Thx
Christian
-----Ursprüngliche Nachricht-----
Von: Nir Soffer [mailto:nsoffer@redhat.com]
Gesendet: Freitag, 13. Mai 2016 13:52
An: Grundmann, Christian <Christian.Grundmann(a)fabasoft.com>
Cc: users(a)ovirt.org
Betreff: Re: [ovirt-users] volume_utilization_chunk_mb not working
On Fri, May 13, 2016 at 2:32 PM, Grundmann, Christian
<Christian.Grundmann(a)fabasoft.com> wrote:
> Hi,
> @ This looks correct if this is in the [irs] section of the configuration.
> It is
>
> cat /etc/vdsm/vdsm.conf
> [vars]
> ssl = true
>
> [addresses]
> management_port = 54321
>
> [irs ]
This is the "irs " section, not the "irs" section :-)
> volume_utilization_percent=15
> volume_utilization_chunk_mb=4048
>
> do I need a space before and after the = ?
No, it is just more human friendly this way.
> @ We support initialSize argument when creating volumes - use when importing external
vms (v2v), but it is not exposed in the ui.
> If you think think exposing it in the ui is a useful feature, you can file a bug:
> https://bugzilla.redhat.com/enter_bug.cgi?product=ovirt-engine
>
> I don't need it in the ui, but it would be nice to have it as
> tuneable
I checked the code, and we actually do use volume_utilization_chunk_mb when we create the
initial disk, so getting the configuration to work will solve your issue.
Nir
2:31 p.m.
On Fri, May 13, 2016 at 1:34 PM, Grundmann, Christian
<Christian.Grundmann(a)fabasoft.com> wrote:
4GB would be the maximum Size I need before I destroy the VM. So if
the
initial Size would be 4GB the pausing shouldn’t happen anymore
Maybe you want to use preallocated disks instead?
Nir
3115
days inactive
3115
days old
7 comments
2 participants
participants (2)
-
Grundmann, Christian -
Nir Soffer