Photoshop cs4 new system integration and network problems

Question

Hi there!
I am new to the forums, but I will just dive right into my issue rather than introducing myself:
I recently did a new hardware install (16 TB of clustered storage) at a mograph studio that are heavy users of Photoshop CS4, amongst other things.  Prior to the new storage, they primarily used an Xserve with attached RAID device, and CS3.  They are now experience high amounts of file corruption on PSDs from saving over the network.  I am, of course, aware the Adobe does not support network saving, due to the plethora of problems that may exist and the difficulty of recreating such varied environments.  I also know that neither Apple nor Adobe seem overtly concerned with this problem, although they may have fixed it with updates in CS3.  The users are aware of this fact, but continue to stress that they had "no problems what so ever on the xserve".
Basically, aside from the facts that are available in http://kb2.adobe.com/cps/406/kb406793.html and found on the forums, has ANYONE found an exceptable work around for these sort of issues.  Also, we tried the "save as" fix that was posted on these forums, and that did not work either.
Please, any help is extremely appreciated.  Thanks

Answer 1

If you have a working network and servers -- it can work. (and does for most of the servers inside Adobe, and those in my home)
But if anything (OS, network, server) malfunctions -- the process breaks in difficult to diagnose ways.
Photoshop is already following all the safe file save guidelines, testing for permissions, testing for space availability, etc.  But still things fail on networks.  And when we look into the failures, it's rarely the same cause and usually can't be worked around in any reasonable manner.
As application developers, we're frustrated too.  We know it can work.  We know it should work.  But some things are too far beyond our control.
Bottom line:  Finder and Explorer add a lot more error checking to server file copies, and do their copies in relatively simple patterns (unlike file saves that can involve random seeks and writes, depending on the format).  Saving locally and copying to the server afterward is going to be safer (adds at least 2 more layers of error checking).  The same goes for copying from the server then opening -- though we see far fewer errors reading from a server than writing to a server.