June 20, 20197 yr Presently if disks are running hot (45C+), the array health check reports as 'FAIL'. This is technically not correct: 1) Parity is valid 2) No disks have reported failures 3) Disks are operating properly Proposals: 1) Create an option to report array as 'WARN' if disks are running hot 2) Ignore high disk temps and only validate parity and cache pool status and report accordingly, which in this case should be 'PASS'. NOTE: - Same thing goes for array status report (health check) when parity check is running, it shouldn't be FAIL, it should be PASS. - Now if it is rebuilding - it should be WARN as the correction process has begun and it is in progress. - If no rebuilding is in place, no parity check and we have a failed disks in either array or a cache pool - FAIL, that's a legitimate failure that should trigger a failure notification. Cheers. Edited June 20, 20197 yr by ezhik
Archived
This topic is now archived and is closed to further replies.