AFP Permission issues after new FW update

sphardy wrote:
planetaaron wrote: I believe the uid is set by the client (aka your computer, not the readyNAS) Unfortunately that is not correct - AFP access is more like CIFS than NFS in this regard To enable AFP access you must create an account on the NAS. When you then connect via AFP as that created user, all files/folders assume the UID and GID of the NAS account, not the client

Ok, I'll take your word for it. :)

I have to say this whole experience has been a bit of a disappointment. In addition to the issues already outlined, I had a ton of problems copying files from/back to the ReadyNAS when I was backing up my 1TB iTunes library. The whole point of using AFP was to ensure that I didn't have filesystem incompatibilities between my local and remote drives, however when trying to copy in both directions, it was not a simple drag & drop. I was getting all kinds of errors like "File has illegal characters", "File name too long", and "A file/directory with that name already exists" (this one due to being able to create case sensitive directories & files on the readyNAS that were not allowed locally).

It's possible that the AFP spec has changed and this is more of a protocol issue than a ReadyNAS problem, but the end result was a frustrating user experience. I ended up having to just do an rsync and then reconcile the colliding file names manually. I haven't even tried yet to start up my iTunes library now that I've copied it back to the readyNAS. I have a sneaking suspicion it won't be seamless.