I too am astonished, but it was definitely it. The split second it was done rebuilding the problem went away. I was sitting there recalling my command history and my co-worker was running various ls commands.
I did not run any diagnostic commands such as statit. By the time we tracked it down to being the netapp in the first place, we were busy failing over apps to another site and scurrying around. I think we are using 6.4.1 (not connected to work right now). Other volumes were not effected. Have you ever yanked a parity disk?
--- Dirk Schmiedt Dirk.Schmiedt@munich.netsurf.de wrote:
Hello Jerry
I need more informations:
Which ONTAP Version are you using? With or without disk prefailing/copying? Did you start any ps -z ; wait one minute ; ps -c 1 traces? => Which processes make your CPU busy? Did you use statit (for showing usage and response times of every single disk) or wafl_susp (suspense reasons inside WAFL) for analysis?
Basically, I also would be astonished if the reconstruct of a "parity" disk would be the reason of this effect. I "kill" at least one random disk per week for demonstration/training purposes and haven't this effect yet (luckily :-) or sadly :-( because it would be interesting to analyze it ;-) )
Regards! Dirk
Jerry wrote:
Anyone ever experience really bad performance when rebuilding a parity disk?
...
-- oo _\o oo__o' oo _\o Erfolg haben ist: /\ \ o/ ' /\ \ Einmal oefter / o oo / aufstehen als man ------oo----<^^^^^>______o_'_------oo---- hinfaellt. ;-)
Success is: Stand up one more often than the times you stumbled.
_______________________________ Do you Yahoo!? Declare Yourself - Register online to vote today! http://vote.yahoo.com