> I have seen drives ack writes without requesting any > data, return the wrong relative offsets to the > controller..etc > I have seen the FC interface chips do lots of things > that led to data corruption... > > I would wager that 90% of the data corruptions that > we looked at on the T3/6120 platforms were not array > firmware issues, but host, drive, or FC microcode > issues....
OK. I can accept that. To me, that's all the more reason to run ZFS, with so many failure points inbetween. The point is, in the great scheme of things, I lost data. I don't have the FW rev or details any more, that was several years ago (2000). Last time I used a T3, I set it up as a JBOD with SVM RAID1+0. It was a thing of beauty to behold, in both setup and performance. > BTW, Most RAID5 implementations do not verify parity > every time they pull data from a drive....so in that > respect they are all open to not catching silent data > corruptions. It is funny to hear management go down > the warpath about implementing data integrity > features, as long as it does not affect performance... I wish our management went down that "warpath". Except, they're completely incompetent and don't understand squat about technology. Good thing they're in IT management! This message posted from opensolaris.org _______________________________________________ storage-discuss mailing list [email protected] http://mail.opensolaris.org/mailman/listinfo/storage-discuss
