10 May
2021
10 May
'21
6:20 a.m.
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.