It is because of a serious bug on cluster.lookup-optimize, it cause me few VM
image corruption after new brick added. Although cluster.lookup-optimize
theoretically impact all file not just shards. However, after ran many round
verification test, corruption doesn't happen when shards disabled. Therefore
I'm interested to see why shards is essential in oVirt defaults.
_______________________________________________
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/privacy-policy.html
oVirt Code of Conduct:
https://www.ovirt.org/community/about/community-guidelines/
List Archives:
https://lists.ovirt.org/archives/list/users@ovirt.org/message/VVEWEV5ESWLUCRJ4RD5FNJAIKRUQ3O7X/