Hi,
Engine reports the block size reported by vdsm. Once we get the system up with your 4k storage domain, we can check that engine reports the right value and update it if needed. I think what you should do is:
1. Backup storage domain metadata /path/to/domain/domain-uuid/dom_md
2. Deactivate the storage domain (from engine)
3. Edit the metadata file: - change BLOCK_SIZE to 4096 - delete the checksum line (_SHA_CKSUM=9dde06bbc9f2316efc141565738ff32037b1ff66)
4. Activate the domain
With vdsm < 4.3.6, the domain should be active, ignoring the block size.
5. Upgrade back to 4.3.6
The system should detect the block size and work normally.
6. File ovirt bug for this issue
We need at least to document the way to fix the storage domain manually.
We also should consider checking storage domain metadata during upgrades. I think it will be a better experience if upgrade will fail and you have a working system with older version.
I've tried this procedure and it has worked! Thanks!
If you would like me to file a bug, which component should I log it against?
for vdms. Please include all the logs and db dump as Nir mentioned in previous email (see bellow). Thanks
Please share more data so we can understand the failure:
- complete vdsm log showing the failure to activate the domain - with 4.3.6 - with 4.3.5 (after you downgraded - contents of /rhev/data-center/mnt/_<domaindir>/domain-uuid/dom_md/metadata (assuming your local domain mount is /domaindir) - engine db dump