Have you seen this yet?
Drive bypass events are situations which cause the ESH to bypass a drive port thus making it inaccessible by the host and isolating the drive from the loop. There are primarily two different kinds of drive Bypass Events:
- Threshold Bypasses - Situations where the ESH detects that a certain kind of error is occurring for a specific period of time and the determination is made to bypass the port because of accumulated errors over time or over the amount of data flowing through the loop.
- Policy Bypasses - Situations where the ESH detects a critical problem and bypasses a drive in order to maintain the integrity of the loop. This might be a "situational" problem which later clears, but once a drive is bypassed, it will remain bypassed until manually cleared by removing and reseating the drive, or by power cycling of the shelf.
- Self Bypasses - The hard drive electronics determine that the internal circuitry cannot function properly anymore. Thus the drive itself calls to be removed from the loop.
Hope it helps
We have one case in netapp for disk failure(or disk went offline).In that case log ,I came across the word disk bypass.so i used it as disk bypass.Is it right to use?
What is the solution for drive bypass?
I just had a situation where a disk was bypassed. "DISK_FAIL - Bypassed by ESH" "Bypassed due to the drive self bypass".
We didn't get any information when checking FAS> aggr status -f. There were no broken disks. The autosupport did show disks on position 11 and 13 but not 12.
We didn't actively do anything to fix this, approx one hour from failure the disk got inserted into the system by itself.
Not sure if this was a Threshold Bypasses?
Couldn't be the Policy Bypass, because we didn't do anything of the following "...it will remain bypassed until manually cleared by removing and reseating the drive, or by power cycling of the shelf."