[ovirt-users] Re: [ANN] oVirt 4.3.6 is now generally available
On Fri, Sep 27, 2019 at 4:13 PM Sandro Bonazzola <sbonazzo(a)redhat.com>
wrote:
Il giorno ven 27 set 2019 alle ore 11:31 Rik Theys <
Rik.Theys(a)esat.kuleuven.be> ha scritto:
> Hi,
>
> After upgrading to 4.3.6, my storage domain can no longer be activated,
> rendering my data center useless.
>
Hello Rik,
Did you get the exact engine log, why the storage domain can't be
activated. ?
Could you send the engine.log ?
> My storage domain is local storage on a filesystem backed by VDO/LVM. It
> seems 4.3.6 has added support for 4k storage.
>
Do you have gluster in this combination of VDO/LVM ?
There are some QEMU fixes that
is required for 4K storage to work with
oVirt.
These fixes will be part of CentOS 7.7 batch update 2
My VDO does not have the 'emulate512' flag set.
>
This means your VDO volume would have been configured as a 4K' native device
by
default.
Was it this way, before updating to oVirt 4.3.6 ?
I believe so, because you can't change the block size of VDO on the fly.
So my guess is that you are running fortunate with 4K VDO volume
> I've tried downgrading all packages on the host to the previous versions
> (with ioprocess 1.2), but this does not seem to make any difference. Should
> I also downgrade the engine to 4.3.5 to get this to work again. I expected
> the downgrade of the host to be sufficient.
>
> As an alternative I guess I could enable the emulate512 flag on VDO but I
> can not find how to do this on an existing VDO volume. Is this possible?
>
As state above, this is not possible.
Once VDO volume is created, its block size
can't be changed dynamically.
-- Satheesaran S ( sas )
Attachments:
- attachment.html (text/html — 5.9 KB)