5 ms·

I run several FreeNAS installations on HP MicroServers. What I want is not some fancy UI but help with running FreeNAS with Apple clients. Which is currently h

I run several FreeNAS installations on HP MicroServers. What I want is not some fancy UI but help with running FreeNAS with Apple clients. Which is currently hard to do (this is partly due to FreeNAS and partly due to Apple). If it's not possible, say so. If it is possible, add a switch for Apple clients and export volumes the best way possible (also with MS Office hacks) - without the need to hack and tinker for a long time.

deleted 9y ago
[deleted]
myrandomcomment 9y ago
Why? I run a FreeNAS mini at home with all Apple serving NFS to them. I have a single AFP share for Time Machine backups. At work we have a TrueNAS and 50+ MacBook Pros with a Time Machine share and NFS shares for anything else.
- _Codemonkeyism 9y ago
  Mostly left over temporary files and directories MS Office uses to lock things, or during saving, or Apple uses to safely delete files. Some applications like Affinity can't often save to network shares from FreeNAS. Users then save to Desktop and afterwards to the network shares. Also lots of permission problems, especially in mixed Apple/Windows setups. Only good thing are ZFS snapshots b/c users often delete files they didn't want to delete in the first place.
  - snuxoll 9y ago
    > Also lots of permission problems, especially in mixed Apple/Windows setups. If you just stick with SMB this shouldn't be an issue. The unfortunate reality is the permission model different file sharing protocols use is different, which is why FreeNAS asks you upfront which permission model you want to use when you create a ZFS dataset. If you're running a mixed environment and Windows is anywhere in that mix, just use SMB and save yourself the headache.
  - myrandomcomment 9y ago
    You need to check your permissions model for the volume vs the share type. That is the issue 99% of the time. Simplest is to go all NFS for everything or all SMB for everything. Both work.
user5994461 9y ago
Same thing. Except freenas was so hard to configure and integrate. I removed it and tried a windows server instead. After installation, the network shares were accessible right away from my other windows machines. So much easier.
- _Codemonkeyism 9y ago
  Yes, will use a windows server next time too.
leonroy 9y ago
I recently went through a lot of issues with macOS and FreeNAS. For SMB shares you can get pretty perfect support by ensuring the share level option called 'VFS Objects' has catia, fruit, aio_pthread and streams_xattr. It's in the official docs too if you wanted more information about it. https://doc.freenas.org/9.10/sharing.html https://doc.freenas.org/9.10/sharing.html
rsync 9y ago
This isn't helpful in the context of an office/work environment with mixed clients and non-technical folks, etc. But for your own use, you might have much better success on a mac client system with macfuse/sshfs. I don't bother to connect my mac to my (FreeBSD) file server via smb/samba at all anymore - I just use sshfs. I wish I could do that with my Sonos system and then I wouldn't have to run samba at all ...
- posixplz 9y ago
  Some of us would rather not provide interactive login credentials to our speakers. I'll stick with smbfs for my Sonos, thanks!

deleted 9y ago

[deleted]

myrandomcomment 9y ago

Why? I run a FreeNAS mini at home with all Apple serving NFS to them. I have a single AFP share for Time Machine backups. At work we have a TrueNAS and 50+ MacBook Pros with a Time Machine share and NFS shares for anything else.

_Codemonkeyism 9y ago
Mostly left over temporary files and directories MS Office uses to lock things, or during saving, or Apple uses to safely delete files. Some applications like Affinity can't often save to network shares from FreeNAS. Users then save to Desktop and afterwards to the network shares. Also lots of permission problems, especially in mixed Apple/Windows setups. Only good thing are ZFS snapshots b/c users often delete files they didn't want to delete in the first place.
- snuxoll 9y ago
  > Also lots of permission problems, especially in mixed Apple/Windows setups. If you just stick with SMB this shouldn't be an issue. The unfortunate reality is the permission model different file sharing protocols use is different, which is why FreeNAS asks you upfront which permission model you want to use when you create a ZFS dataset. If you're running a mixed environment and Windows is anywhere in that mix, just use SMB and save yourself the headache.
- myrandomcomment 9y ago
  You need to check your permissions model for the volume vs the share type. That is the issue 99% of the time. Simplest is to go all NFS for everything or all SMB for everything. Both work.

user5994461 9y ago

Same thing. Except freenas was so hard to configure and integrate. I removed it and tried a windows server instead. After installation, the network shares were accessible right away from my other windows machines. So much easier.

_Codemonkeyism 9y ago
Yes, will use a windows server next time too.

leonroy 9y ago

I recently went through a lot of issues with macOS and FreeNAS. For SMB shares you can get pretty perfect support by ensuring the share level option called 'VFS Objects' has catia, fruit, aio_pthread and streams_xattr. It's in the official docs too if you wanted more information about it. https://doc.freenas.org/9.10/sharing.html https://doc.freenas.org/9.10/sharing.html

rsync 9y ago

This isn't helpful in the context of an office/work environment with mixed clients and non-technical folks, etc. But for your own use, you might have much better success on a mac client system with macfuse/sshfs. I don't bother to connect my mac to my (FreeBSD) file server via smb/samba at all anymore - I just use sshfs. I wish I could do that with my Sonos system and then I wouldn't have to run samba at all ...

posixplz 9y ago
Some of us would rather not provide interactive login credentials to our speakers. I'll stick with smbfs for my Sonos, thanks!