Bug 1402315

This is controlled by a engine option that can be changed by engine-config tool (MaxDiskSize [1]). We do not test bigger disks and you will be entering to untested territory. You can try it out and see if this works for you.
We are not planning to change this, therefore closing.


[1] https://www.ovirt.org/develop/developer-guide/engine/engine-config-options/

You can also open a RFE on this, but please provide the use case that requires this.

Could you please help me. I cant set it ..

[root@ovm2 ~]# engine-config -g MaxDiskSize
Error fetching MaxDiskSize value: no such entry. Please verify key name and property file support.
[root@ovm2 ~]# engine-config -s MaxDiskSize=20480
Error setting MaxDiskSize's value. No such entry.

In RHEV is limit 2147483648 GB ...

Modified is not the correct state for this bug, moving back to new since it has been reopened.

Can you please attach a full sos report?

(In reply to boruvka.michal from comment #3)
> Could you please help me. I cant set it ..
> 
> [root@ovm2 ~]# engine-config -g MaxDiskSize
> Error fetching MaxDiskSize value: no such entry. Please verify key name and
> property file support.
> [root@ovm2 ~]# engine-config -s MaxDiskSize=20480
> Error setting MaxDiskSize's value. No such entry.

The config value's name is MaxBlockDiskSize, and not MaxDiskSize as (wrongly) noted in comment 1.

I've created a pull request to fix the mistake in the site that mislead Yaniv:
https://github.com/oVirt/ovirt-site/pull/644

(In reply to Allon Mureinik from comment #6)
> (In reply to boruvka.michal from comment #3)
> > Could you please help me. I cant set it ..
> > 
> > [root@ovm2 ~]# engine-config -g MaxDiskSize
> > Error fetching MaxDiskSize value: no such entry. Please verify key name and
> > property file support.
> > [root@ovm2 ~]# engine-config -s MaxDiskSize=20480
> > Error setting MaxDiskSize's value. No such entry.
> 
> The config value's name is MaxBlockDiskSize, and not MaxDiskSize as
> (wrongly) noted in comment 1.
> 
> I've created a pull request to fix the mistake in the site that mislead
> Yaniv:
> https://github.com/oVirt/ovirt-site/pull/644

I have got the same error with MaxBlockDiskSize.

[root@ovm2 ~]# engine-config -g MaxBlockDiskSize
Error fetching MaxBlockDiskSize value: no such entry. Please verify key name and property file support.

Sandro - this is a bug (or at least an inconsistency) in the tool. In the engine, many (most) config values don't have entries in the database, and the default is used from the code.
The engine-config tool doesn't use the regular engine's code, but reimplmenents its own DAOs, and thus can't handle keys that are only used with a default value that isn't in the database.
Moving to integration team to decide how (whether?) to handle this.

For now you can change this in the engine DB in vdc_options as a workaround.

(In reply to Allon Mureinik from comment #8)
> Sandro - this is a bug (or at least an inconsistency) in the tool. In the
> engine, many (most) config values don't have entries in the database, and
> the default is used from the code.
> The engine-config tool doesn't use the regular engine's code, but
> reimplmenents its own DAOs, and thus can't handle keys that are only used
> with a default value that isn't in the database.
> Moving to integration team to decide how (whether?) to handle this.
This statement may have been premature. Even with such a key in the database, the tool doesn't seem to retrieve it.
Sandro, can someone from your team take a look at this? Either I'm being incredibly daft, or we have a nasty bug here.

Arg, that's daft of me. This property isn't registered in engine-config.properties. 
It's a trivial fix, although I'm not sure if we'd want to expose this to users. Yaniv - your call.

(In reply to Allon Mureinik from comment #11)
> Arg, that's daft of me. This property isn't registered in
> engine-config.properties. 
> It's a trivial fix, although I'm not sure if we'd want to expose this to
> users. Yaniv - your call.

We should support that, since it is only the tested limit on the real limit.
User may want to do this as in the reporter use case.

I have add to engine-config.properties these lines:
MaxBlockDiskSize.description="Max disk size"
MaxBlockDiskSize.type=Integer

and now engine-config works fine.

Thank you

(In reply to boruvka.michal from comment #13)
> I have add to engine-config.properties these lines:
> MaxBlockDiskSize.description="Max disk size"
> MaxBlockDiskSize.type=Integer
> 
> and now engine-config works fine.
> 
> Thank you
Yup, that's the trivial fix I meant in comment 11.
I've posted a patch to gerrit, see in the external references.

Verified over ovirt-engine-4.1.0-0.4.master.20170116141310.gita30debd.el7.centos

[root@storage-ge-05 ~]# engine-config -g MaxBlockDiskSize
MaxBlockDiskSize: 8192 version: general

As expected