i used to think about that until it happened. now i worry.
ontap handles it by halting.
i rebooted and reconstruction continued; it halted again, etc.
to escape i set "bypass_media_errors" to on and held my breath until the reconstruction was completed.
moist palms were the order of the day.
a wafl_check after completion ran clean so perhaps the errors were bogus.
a good case for minimal size raid groups. (i try the hold the 72GB disks to not more than 10 disks/raid group, so it's do as i say not as i do)
-paul
Paul Caron wrote:
Don't you worry about having another medium error on a different disk in the same volume (i.e. your parity disk) during the disk reconstruction? I believe that would count as a multiple disk failure since the disk that was failed for replacement would no longer be available for parity reconstruction. Dunno exactly how ONTAP would handle this since I've never experienced a medium error during reconstruction....yet.
Date: Thu, 15 Aug 2002 11:46:49 -0400 From: "Paul J. Bell" paul.bell@rbccm.com X-Accept-Language: en MIME-Version: 1.0 To: Paul Caron caron@sig.com CC: toasters@mathworks.com Subject: Re: X235_SCHT5073F10 Medium Errors Content-Transfer-Encoding: 7bit X-OriginalArrivalTime: 15 Aug 2002 15:46:54.0986 (UTC)
FILETIME=[FB1EDEA0:01C24472]
i also have seen too many occurrences of these errors. if i see the same
disk two - three weeks in a row i replace the disk. overkill? perhaps, but why take the risk.
-paul
-- "There is magic in the web" - Shakespeare (Othello, Act 3, Scene 4)