1. I have some suspicions around what might cause some cache corruptions, but the honest answer to your query is that I don’t know for sure. Resources in the cache and the associated tracking files are not updated together in a transactional fashion, so anything that interferes with an update to either could lead to “corruptions.” Suggesting anything more than that is just guesswork on my part.

2. As far as reliability of the BLOB cache in 2010, I do know that a number of improvements have been made … but I don’t know if any “reliability” improvements have been made. The improvements I’m aware of are tied primarily to scalability and multimedia serving. For example, byte range support is now available for those using the IIS media extensions; with those in play, for example, users can jump to different points in a media clip and have content stream without the need to seek through all the content between where they were (in the clip) and their new position. The process to fetch content is now chunked, too, to improve the speed with which content is initially served back. If you look at the cache structure (on disk) now, as well, there have been some changes. Does any of that mean better reliability? Again, I just don’t know. Many of the underlying operational mechanisms are still the same, so I don’t know if we’ll see any differences during normal usage.

Sorry that I don’t have better answers for you, Brad. If you happen to see changes or differences, though, I’d love to hear about your observations :-)

2) Do you know if the blob cache is more reliable / less likely to corrupt in SP2010 and has it changed much between the 2 versions..

thanks
Brad