David Ritter
Cadet
- Joined
- Mar 14, 2014
- Messages
- 8
Hi all,
I have setup several FreeNAS based servers and have been generally very happy with their performance and ease of setup and use.
Several of my end users on Macs have informed me that they occasionally get an odd error message when saving files to their FreeNAS afp volumes.
This error usually happens with Photoshop but they indicate that it also happens with InDesign.
The error message usually reads like this;
'Could not save as "file name goes here.tif" because write access was not granted.'
Here is a screen cap of the message dialog.
http://i.imgur.com/RdlSGIA.png
I initially thought this might be due to an error in my permissions setup so I have my users connecting as one user. In the afp volume setup I have checked all the boxes in the default file and directory permissions setup. I have set the default umask to 000. The single user account I have them using is a local account not controlled by any domain controller. I have crowned the afp volumes so the one user account has complete ownership of the files and directories on the afp share.
The FreeNAS we are using is currently version 9.2.0. I have tested for this error on newer versions of FreeNAS and the issue still exists.
According to what I have read about setting up the afp volumes all this should allow my one user to have complete unfettered access to mounted afp volumes.
I have tested for this issue using Mac OS 10.6.8, Mac OS 10.7.5 and the latest Mac OS 10.9.2 - the issue occurs with all Mac OS versions I have tested.
When this error happens another error shows up in the console I have pasted it below.
Mar 14 12:57:07 phoenix afpd[29827]: ad_rtruncate("/mnt/phoenix-zfs/production/phx-vol6/*NEW WEB BANNERS/AUDIO EXPRESS/10.03.13/Dorsey 200x263.tif"): No such file or directory
Currently when this error happens my users have to save the file in a different location or with an altered file name. After this successful save they move the file back to here it belongs or they rename it in the Mac Finder back to the original name.
This error is not a consistent thing which makes tracking down the cause even more difficult.
Please let me know if I need to provide any additional info on this issue.
I have setup several FreeNAS based servers and have been generally very happy with their performance and ease of setup and use.
Several of my end users on Macs have informed me that they occasionally get an odd error message when saving files to their FreeNAS afp volumes.
This error usually happens with Photoshop but they indicate that it also happens with InDesign.
The error message usually reads like this;
'Could not save as "file name goes here.tif" because write access was not granted.'
Here is a screen cap of the message dialog.
http://i.imgur.com/RdlSGIA.png
I initially thought this might be due to an error in my permissions setup so I have my users connecting as one user. In the afp volume setup I have checked all the boxes in the default file and directory permissions setup. I have set the default umask to 000. The single user account I have them using is a local account not controlled by any domain controller. I have crowned the afp volumes so the one user account has complete ownership of the files and directories on the afp share.
The FreeNAS we are using is currently version 9.2.0. I have tested for this error on newer versions of FreeNAS and the issue still exists.
According to what I have read about setting up the afp volumes all this should allow my one user to have complete unfettered access to mounted afp volumes.
I have tested for this issue using Mac OS 10.6.8, Mac OS 10.7.5 and the latest Mac OS 10.9.2 - the issue occurs with all Mac OS versions I have tested.
When this error happens another error shows up in the console I have pasted it below.
Mar 14 12:57:07 phoenix afpd[29827]: ad_rtruncate("/mnt/phoenix-zfs/production/phx-vol6/*NEW WEB BANNERS/AUDIO EXPRESS/10.03.13/Dorsey 200x263.tif"): No such file or directory
Currently when this error happens my users have to save the file in a different location or with an altered file name. After this successful save they move the file back to here it belongs or they rename it in the Mac Finder back to the original name.
This error is not a consistent thing which makes tracking down the cause even more difficult.
Please let me know if I need to provide any additional info on this issue.