2 Replies Latest reply: Mar 12, 2010 5:38 AM by slowfranklin
youheresupport Level 1 Level 1 (0 points)
Hello all –

I’m running a small OS X/FCP based video editing environment that has an Open-E “NAS R3” device at the heart of it (basically, a Linux based dedicated NAS device, used often in enterprise-critical sorts of applications). Editors on working on at least three (3) workstations, editing projects and media in place on the NAS. Scratch disks are also set to the NAS, so that editors can open any project on any workstation. The ReadyNAS device itself supports AFP natively, and we’ve been connecting that way.

Running said NAS with OS X 10.4.11 through OS X 10.5, the system worked flawlessly. After Snow Leopard, I began to encounter major stability and performance issues with OS X 10.6.2 (Snow Leopard) and AFP. They are:
1. After logon one or more additional, seemingly identical icons would appear in Finder. One of the icons would work correctly. The additional icons would not. After clicking on the extra icons, the file names and folder names shown within would be unresponsive, would occasionally have incorrect names. These garbled file names seem to correspond to files that were “color coded” in OS X finder. After removing the color coding, the still remained garbled.
2. After a couple of days – following upgrading a second workstation which displayed the same issues – a new set of issues occurred on the second workstation. Rendering in Final Cut caused the system to hang (spinning wheel or non-responsive), or render would seem to complete but would actually have failed and not occurred.
3. Eventually, projects opened in Final Cut would show disconnected media, even when media was verified in Finder to be in place and intact.
4. Performance in file copies from the NAS to locally attached storage is about 10% slower in OS X 10.6.2 than in 10.4.11

In short, there appears to be a compatibility issue between the NAS and the implementation of AFP in OS X 10.6.2. Any advice on work arounds, fixes and other solutions? Any chances of Apple admitting this issue exists and fixing it?

Mac OS X (10.6.2)