AFP Permission Issues | Can't Create Folders!

[Juliano Arantes]

Hello!

I've searched and read everything AFP related in the forum and couldn't find a solution to my problem...
Currently running FreeNAS-9.2.1.6-RELEASE-x64 (ddd1e39) on the following hardware:

Intel Pentium CPU G2020 @ 2.90GHz
Supermicro X9SCM-F
16GB RAM DDR3 1.333Mhz
2 x 1TB WD Red

I'm new to FreeNAS but had no problems installing and configuring everything but the AFP shares.
It works using CIFS, but as we only have Macs I don't want to use it and the speed wasn't good either!

My setup is actually pretty simple. I have one dataset called "plexmedia" where I'll store some pictures. I've created a user called "estudio" and made it part of a group called "onovodia". Than I've created an AFP share and set "Allow List: estudio" and "Read-write Access: estudio".

After that I can successfully login and transfer files to the share, deleting files is also not a problem. But for some unknown reason I can't create folders!

I've created the dataset choosing "Share type = Apple" and set the owner to "estudio" and the group to "onovodia". I've also chosen "Permission Type = Windows/Mac ACL". Checking folder permissions with getfacl returns:

# file: plexmedia
# owner: estudio
# group: onovodia
owner@:rwxpDdaARWcCos:fd----:allow
group@:rwxpDdaARWcCos:fd----:allow
everyone@:r-x---a-R-c---:fd----:allow

I've read on other threads I should not use the "Full Name" to login and that's also not the case...

Any help? I've been trying everything I could for three days...

 

[Juliano Arantes]

Forgot to mention the same thing happens in every client, all of them using OSX Mavericks 10.9.4!

 

[Dennis.kulmosen]

I am actually having the same issue. Even after upgrading from a 9.2.1.5 where everything works with making folders. After upgrading to 9.2.1.6 you cant create folders. I have looked in afp.conf but it has the correct folder permissions.

 

[Dennis.kulmosen]

I have opened a bug report.

https://bugs.freenas.org/issues/5751

Please add you info to it also so we can have this solved quickly.

 

[Juliano Arantes]

Awesome, I'll do it right now! Thanks.

 

[fracai]

I've seen this occasionally and it's always been cleared up by restarting the AFP service.

 

[Dennis.kulmosen]

This happens after a completely fresh install and also after a GUI upgrade. I have tried restarting the AFP without luck.

 

[fracai]

I've seen that too, issues after z new install, and at least in my case the service restart fixed things.

Just relating my experience.

 

[pleuroma]

Having the same issue as above. Everything is configured for afp and worked great. Out of the blue I cannot write anything to the drives no matter how I configure permissions. Anyone had any luck resolving this?

 

[Dennis.kulmosen]

Follow the bug report. ;-)
Its been solved. As a quickfix you can in terminal do:
setfacl -b path/to/AFPshare
This will remove the ACL's on your share, and it will default to posix.


Sent from my iPhone using Tapatalk

 

[Yaniv]

Follow the bug report. ;-)
Its been solved. As a quickfix you can in terminal do:
setfacl -b path/to/AFPshare
This will remove the ACL's on your share, and it will default to posix.

Can't believe it was that simple! Thank you so much! Worked for me.

 

[Ben Wong]

Just experienced this error where I could read/write files but not create directories. This is what I did. My NAS is on FreeNAS 9.3.

Let's assume my main share is: /mnt/datapool/main/media

1. ssh into the NAS
2. cd /mnt/datapool/main
3. find media -type d -print0 | xargs -0 -n1 setfacl -b

Since setfacl isn't recursive, this will find all directories and sub-directories and fix the ACL on them.

 

[Soypat]

I fixed by doing the following:

1- Delete the AFP sharing.
2- Create a new AFP Sharing.
3- Set all the permission checkboxes on.
4- uncheck "AFP3 Unix Privs"

I beleive that the step 4 was the key one.

Good luck!

 

[3agl3]

I fixed by doing the following:

1- Delete the AFP sharing.
2- Create a new AFP Sharing.
3- Set all the permission checkboxes on.
4- uncheck "AFP3 Unix Privs"

I beleive that the step 4 was the key one.

Good luck!

I can confirm that just doing step 4 worked for me. Thanks.

 

[calebmcd]

I fixed by doing the following
1. Updated to the December 20, 2018 build
unchecked "AFP3 Unix Privs
This seemed to cause the issue for me.