SOLVED Strange AFP Issue

[chrispage1]

Hi,

I am having a strange issue with my AFP shares. Please see my ServerFault issue that I have created for more information and screenshots on the issue -

http://serverfault.com/questions/639960/afp-share-mounting-issues

 

[dlavigne]

Which version of FreeNAS? Is each share on its own dataset? Unix or Windows permissions?

 

[chrispage1]

@dlavigne I'm running 9.2.1.8. Each share is on it's own dataset and running UNIX permissions.

Despite the folder being greyed out, when you first access it you can still create folders, delete things etc.

 

[chrispage1]

@dlavigne OK I finally got this sorted by using Windows datasets instead of Linux and recopying over all the data. Appreciate your help - now FreeNas is actively storing just over 6TB of data on RAIDZ2. Lets hope it keeps things nice and redundant! Thanks :)

 

[NineFingers]

Can you tell a little of what you did? I'm having various AFP sharing issues as well.

 

[chrispage1]

@NineFingers I just created new ZFS Datasets with the Permission type to be Windows and set the permissions recursively. I also created a user and group called 'shareuser' and then assigned all of my users that have AFP access to the 'shareuser' group.

Hope that helps.

 

[NineFingers]

... and created your AFP share upon the Windows-type ZFS Dataset?

 

[NineFingers]

also, what OSX version are you running?

 

[chrispage1]

@NineFingers exactly, set the AFP name and path to the relevant ZFS Dataset, then set the allow list to @shareuser and the read-write access field to @shareuser (meaning the shareuser group can read and write on this share) and unchecked 'AFP3 Unix Privs' field.

We are running a combination Mavericks and Yosemite. What is the particular issue you are having?

 

[NineFingers]

Well, you just touched on part of my issue. I've been neglecting the "@" for group names. argh.

I'm on Yosemite, and I've just been having real inconsistencies... like "Failure to open <NasName>"... and other issues that aren't coming to mind right now. I'll test your suggestion tonight.

Thanks for your help!!

 

[NineFingers]

... I've gotta keep researching. I've got to be doing something fundamentally wrong... likely on the OSX side. For one thing, it usually prompts me for my OSX password in order to copy a file to the NAS, and will fail anyway, saying I don't even have permission to read the file that I OWN. And in the cases where it actually copies, it's painfully slow.

 

[cyberjock]

... I've gotta keep researching. I've got to be doing something fundamentally wrong... likely on the OSX side. For one thing, it usually prompts me for my OSX password in order to copy a file to the NAS, and will fail anyway, saying I don't even have permission to read the file that I OWN. And in the cases where it actually copies, it's painfully slow.

Believe it or not, it is entirely possible to be the owner and not have permission to the file. It's all about how the file permissions are set up. ;)

 

[NineFingers]

My major problem is that I can copy files into the NAS, but not folders... even just trying to create a new folder there fails. Any ideas?

 

[NineFingers]

To add a little detail to my issues... I have a Synology device onto which I can copy these folders with no issues. So, clearly, it's something about FreeNAS that I don't have set up correctly.

 

[Dennis.kulmosen]

With afp you have 2 places that needs to have apropiate permissions.
1. The ZFS dataset needs to have correct owner and group.
2. As mentioned higher in this thread, the afp share also needs ti have correct permissions setup.

I can post pictures tommorow if you like.


Sent from my iPhone using Tapatalk

 

[NineFingers]

I can post pictures tommorow if you like. :)

If you have time, yes, I'd like to make sure I'm doing it right.

 

[Dennis.kulmosen]

Hope these pictures makes sense.

 

[NineFingers]

The thing I see that I know I didn't do is to set the group write permissions. I'll give that a go tonight. Thanks!

 

[NineFingers]

I've decided my issue is Yosemite. I re-installed Mavericks onto one of my machines, and all works fine... even to a share that fails under Yosemite. A confusing thing is that Yosemite and Synology play together fine, so there must be something quirky about FreeNas/Yosemite. Anyway... I'm off to figure out how to revert my machines back to Mavericks.

 

[Dennis.kulmosen]

Have in mind that in Yosemite if you type cmd+k and type in an ip adress it will default to the smb protocol. So in other words you need to force the afp protocol by typing afp://ip-adress