NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Weird AFP permissions?
I'm using OS X 10.5.6 and 10.5.7 to connect via AFP to a ReadyNAS Pro running RAIDiator 4.2.5. When I copy files to the NAS, the resulting permissions normally look like this (using OS X's "Get Info" window):
user: adam, permissions: read & write
group: MTE, permissions: read & write
world: everyone, permissions:read & write
(And yes, I have advanced AFP permissions set to grant read & write to group and to world.)
But sometimes they look like this:
user: (unknown), permissions:read & write
group: avahi, permissions: read & write
world: everyone, permissions: read & write
Sometimes these oddball user & group names come and go; sometimes they persist. I can reset them using Frontview, but if I try to deal with them in the Get Info window, the file typically becomes unreadable (until I reset permissions on the entire share via Frontview).
The answer to the unreadability problem is "don't do that", grin, but what about the substitution of (unknown) for my user name, and avahi for MTE? If I decide to restrict read/write ops to the MTE group instead of everyone, then the file becomes unusable because the group changes from MTE to avahi, how do I fix the problem without changing file permissions on every file on the share?
Has anyone else seen this? Any suggestions as to why this is happening, and how to prevent it?
user: adam, permissions: read & write
group: MTE, permissions: read & write
world: everyone, permissions:read & write
(And yes, I have advanced AFP permissions set to grant read & write to group and to world.)
But sometimes they look like this:
user: (unknown), permissions:read & write
group: avahi, permissions: read & write
world: everyone, permissions: read & write
Sometimes these oddball user & group names come and go; sometimes they persist. I can reset them using Frontview, but if I try to deal with them in the Get Info window, the file typically becomes unreadable (until I reset permissions on the entire share via Frontview).
The answer to the unreadability problem is "don't do that", grin, but what about the substitution of (unknown) for my user name, and avahi for MTE? If I decide to restrict read/write ops to the MTE group instead of everyone, then the file becomes unusable because the group changes from MTE to avahi, how do I fix the problem without changing file permissions on every file on the share?
Has anyone else seen this? Any suggestions as to why this is happening, and how to prevent it?
14 Replies
Replies have been turned off for this discussion
- Another bump on this thread. Would really like an official response from Jedi Council.
I see similar things, but I'm also working with an Active Directory setup. I have everything checked to enable non-owners to read/write/delete/etc., but for some reason these do not work. I was able to work around it on CIFS by changing the Windows permissions after logging in as admin, but this doesn't affect AFP.
My only workaround is to reset permissions in the Advanced tab of the share. My issue seems to be specifically related to when one user creates a file, other users cannot edit. Sames goes for folders. - Has anyone tested FW 4.2.21 that just came out?
- Updated to 4.2.21 this morning.
Still the same ‘Something wrong with the volume's CNID DB, using temporary CNIB DB instead.... ... switching to read only mode’
Need to get an answer to this fast as it's really restricting me. - I'm also having this issue.
ReadyNAS 102 running OS 6.1.2
using AFP on an iMac running 10.8.5
I have no permissions after a system crash.
My username shows up as (unknown)
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
