from the console:
Thu Jul 24 21:29:42 EDT [mgr.stack.string:notice]: Panic string: WAFL hung. in process wafl_hipri on release NetApp Release 6.1.3 Thu Jul 24 21:29:42 EDT [mgr.stack.at:notice]: Panic occurred at: Fri Jul 25 01:22:32 2003 Thu Jul 24 21:29:42 EDT [mgr.stack.proc:notice]: Panic in process: wafl_hipri Thu Jul 24 21:29:43 EDT [mgr.stack.framename:notice]: Stack frame 0: sk_panic(0xfffffc00005e64f0) + 0x394 Thu Jul 24 21:29:43 EDT [mgr.stack.framename:notice]: Stack frame 1: check_water_marks(0xfffffc000049d900) + 0xe0 Thu Jul 24 21:29:43 EDT [mgr.stack.framename:notice]: Stack frame 2: wafl_timer(0xfffffc000049d880) + 0x54 Thu Jul 24 21:29:43 EDT [mgr.stack.framename:notice]: Stack frame 3: wafl_process_one_msg(0xfffffc00005037a0) + 0x690 Thu Jul 24 21:29:43 EDT [mgr.stack.framename:notice]: Stack frame 4: wafl_hipri(0xfffffc0000502a80) + 0x164 Thu Jul 24 21:29:43 EDT [mgr.stack.framename:notice]: Stack frame 5: sk_hw_save_state_and_loop(0xfffffc00003f92e0) + 0x70 Thu Jul 24 21:29:43 EDT [asup.sendError.throttled:info]: Too many autosupport messages in too short a time: throttling REBOOT (panic) mail.
a disk died. it started to rebuild on a spare, the above continued to happen several times so I thought maybe the spare it was trying to rebuild on was bad so I pulled it out. It came back up and began to rebuild on a different spare and the above happened again. Is it possible that this other spare is also bad? What else could it be?
Thanks Dan Finn