Our system uses 1x RMSP3AD160F and 2x RSP3MD088F. The system load during weekend is much low but both Patrol Read and Consistency Check still cannot be completed together during weekend. We plan to pick up one of them that suits for our system. Can you provide the detail of PR and CC?
We also observe the performance effect from PR is higher than CC. Is this expected? What causes it?
Thanks for you answer.
Here is what I find online :-
"a consistency check ONLY tests areas of the disks which contain data and parity, not unused areas of the arrays disks, a patrol read checks every sector of the involved disks. With todays larger disks the patrol read test is more important then a CC. Patrol reads find error in unused areas of the disks involved which are not normally found until the unused areas are written to or tested. Now, if enough areas are read/written to in a short period of time, and a threshold of bad areas are found, the raid will fail, especially during a rebuild. The Consistency check tool was developed in a time when disk were expected to grow to less then a hundred megabytes. Patrol reads came much latter, as the disks became much larger and raid failures were increasing, primarily during rebuilds. As to the power of each tool, Patrol Reads does most of what a CC does, an inconsistency due to a faulty read/write/or disk error will be found by a PR. As is a consistency errors not caused by a physical disk error is rare, over all consistency errors are very rare (my experience), physical sector errors are far more common."
Would be safe to only run patrol read weekly, totally skipping the consistency check at all?