I've experienced this (Score 2, Informative)

For me it was Visual Studio files, the scenario is I have a solution in a directory on the Home Server that I open in VS and start to edit. I save very often, as a force of habit, and randomly VS would say that the solution file or the project file was invalid. I would open it in a text editor and it's garbled, should be plain text. The work around I use is to do all editing on my local drive and copy the contents to the Home Server when done. I have not had any issue with file corruption since, also I have not had data corruption issues with programs that edit my pictures or music files directly on the Home Server. It has something to do with the way they implemented the drive extender. Bittorrent downloads require the same type of workaround, download somewhere and then copy to Home Server, but you can seed from the Home Server with no issues. It will be nice to have a fix.