Mac Pro :: OS X Corruption Of Raid 5 And 6 Arrays?

I was inquiring as to buying a raid-6 array from a well known company. I received the following as part of a pre-sales discussion. I have never heard this before, but wanted to seek others opinions as it sounds just too bizarre to be true - I mean how can people run snow leopard server if this is the case and manage data? He is recommending Raid-0 arrays backed up to another raid-0 array nightly, fwiw. For the record, I'm looking at Atto hardware cards and mini-SAS 8 bay enclosures, not software raid. Text of interest:

"These days a drive failure isn't the most common means of losing data. What we see the most problems with is what's called data corruption. It's when the data stored on a drive becomes scrambled for one of several reasons. On a software based RAID 0 it's usually easily repaired with tools like Disk Warrior or Tech Tools Pro. When the problem occurs on a Hardware based RAID 5 or RAID 6 the parity can quickly become unreadable making the RAID unusable by the computer. There are no tools that can repair the corruption on a parity RAID once it reaches a certain point. The problem arises because the parity data is stored across all of the drives, and in the case of a RAID 6 it has 2 sets of parity stored on each drive making corruption a huge problem.

If everything is going correctly and your workflow is correct you shouldn't see much corruption. We do see a lot occurring when video is stored on drives, and at times software or OS updates cause corruption all by themselves. OSX is famous for the problem since 10.5 came out. One common way to create problems for yourself is dragging and dropping files from one location to another. When you drag and drop you do not get the whole file, some of the index is lost. Do this enough and you'll have a problem because it's cumulative. Try this; do a "Get Info" on a file and note the file size. Then drag that file to another location and do a "Get Info" on the destination file copy. You'll see that the new copy is smaller, it's lost some index data. Do this enough and the file can become unreadable and will have to be repaired. Do it enough on a parity RAID and you can make the file unreadable and irreparable."