Closed kinvaris closed 7 years ago
This should do the trick: https://github.com/openvstorage/openvstorage-health-check/commit/6deb3146bf4a656f3d4c390dd0457e7d33664c45
This commit is without caching because we've not taken in account that namespaces that have been in the cache need to be deleted. This will be in a future release
Output of attended:
root@ovs-node01-1604:~# ovs healthcheck alba disk-safety
[INFO] Checking disk safety on backend: mybackend02
[INFO] Checking policy `1,2` with max. disk safety `2`
[SUCCESS] All data is safe on backend `mybackend02` with `6` namespace(s)
[INFO] Checking disk safety on backend: mybackend
[INFO] Checking policy `1,2` with max. disk safety `2`
[SUCCESS] All data is safe on backend `mybackend` with `6` namespace(s)
[INFO] Checking disk safety on backend: mybackend-global
[INFO] Checking policy `1,2` with max. disk safety `2`
[WARNING] The disk safety of `5` namespace(s) is `1`, max. disk safety is `2`:
06773eb5-c56e-4319-88ff-b2fc7d0140b6 with 100% of its objects,
4368bb53-c3a2-47fa-881d-cbb52deed282 with 100% of its objects,
cfa76aec-9687-4a69-9a12-261d55d805a1 with 100% of its objects,
e0aaab1c-2197-41ed-b4d4-a489c9ab24b0 with 100% of its objects,
e88c88c9-632c-4975-b39f-e9993e352560 with 100% of its objects
[INFO] Recap of alba disk-safety!
[INFO] ======================
[INFO] SUCCESS=2 FAILED=0 SKIPPED=0 WARNING=1 EXCEPTION=0
Unattended:
root@ovs-node01-1604:~# ovs healthcheck alba disk-safety unattended
disk-safety-mybackend SUCCESS
disk-safety-mybackend-global WARNING
disk-safety-mybackend02 SUCCESS
Silent:
'disk-safety-mybackend': 'SUCCESS',
'disk-safety-mybackend-global': 'WARNING',
'disk-safety-mybackend02': 'SUCCESS',
Problem description
Disk safety says 1 disk is lost but it isn't
Logs
Possible solution
As seen in the logs we see the namespace has a disksafety of 1 because 1,2,2 but in reality it should be 1,2,3 (in alba itself). This causes the hc to throw a failure with 1 disk lost. But in reality there are no disk lost because
applicable_dead_osds
is not taken in account. Its on 0 because we only have 2 osds instead of 3.Additional information
Setup
Hyperconverged
Packages