On 11/14/05, Scott Marlowe <smarlowe@g2switchworks.com> wrote: If you were running on top of a RAID 1+0 or RAID 5 array, such an error
would likely never have happened, since it would have been detected by
the controller, and either the bad block would be mapped out or the
drive would be kicked out of the array and you'd get a system alert
telling you you had a bad drive in your array.
Except that he jus said he was running on a RAID5. True this problem would be unlikely on a hardware controlled RAID5 configuration, but not impossible.
Does the log file tell you anymore information?
Have you tried to rerun the query? If so, did you get similar results?
-Josh
