Not sure if anyone’s had much experience with Adobe apps running on an Xsan volume but they appear to be pretty flakey. Had a look at what’s going on and it *may* be the fact that Xsan doesn’t support exchangedata(2) which would make sense with the amount of data things like Illustrator in particular put in resource forks.
Symptoms vary but mainly seem to be gradual file corruption. Anyone know any way to work around this?
Nice to see it’s not just me then Wonder if Xsan will be made more transparent to the system, basically more HFS-like. The lack of ACLs is a bit of a pain as well.
Lot of problems with AFP. We moved our customer over to SMB and problems are mostly gone.
Now we only have to bother with the SMB problems, which are File Name length.
They use CS1 here all day and works flawless now.
We use 10.4.3 with XSAN 1.2 clients are mostly 10.4.5
The main problem i was having with my users was that users were getting end of file errors when trying to save to the san from Photoshop. The workaround was to go to
Preferences > File Handling
In the file saving options > image previews choose Never save. After that Photoshop and Xsan played real nice together.
Comments are closed