Ok, absolutely understandable 
Then I think my use case is not very complex and thus I never had problems with netatalk an samba together on xenial using ext4.
Going with option 2, the problem of my first posting persists 
The whole VM is crashing on accessing the AFP-Shares.
Did not try for TimeMachine explicitely, though.
Any Ideas on that? Or should I try, as already suggested, to update the netatalk Jessie-backport to the current version?
I have to admit, that this OMV install is for home use and testing. Before that I had an Ubuntu 16.04.2 with netatalk and samba together which worked out fine. Never had locking issues or something - but this was only accessed by two simultaneous users.
I currently have 2 options:
- AFP for all shares with SMB-read-only for the non-mac clients
- Full SMB with AFP only for Timemachine
Another option is to roll my own Ubuntu VM again... but OMV looks very good and it's a breeze for settings, shares, privileges and so on.
Currently I'm thinking of option 2 with OMV. Do you have any suggestions on which way to go?
Hey @tkaiser,
thanks for that detailed explanation. As Apple is not advocating AFP any more (http://appleinsider.com/articl…mb2-in-os-x-109-mavericks) I can surely live with SMB(2) only.
The only thing right now I need Appletalk for is TimeMachine. Or did I miss something and it is possible via CIFS/SMB in the meantime?
Cheers,
Patrik
btw: Not running something OMV-related on Flash-Media.
Ok,
I'll give you an update as soon as I have time.
Cheers,
Patrik
Can I support you in any way?
Hi,
I'm having the same problem:
ESX 6.5 HPE 650.9.6.5.27 (MicroServer Gen8, P420 Raid 10)
openmediavault 3.0.84 (Erasmus)
openmediavault-netatalk 3.2.10
OS X Sierra 10.12.6
The shares are working over CIFS without any problem. Copied 14GB minutes ago.
But if I use the same shares via AFP and try to list a directory or acces files, the whole VM reboots. The share's root directory is shown, though.
The syslog has no sign for anything that went wrong, as you can see here at 22:51:59:
Jul 26 22:34:16 nas afpd[24861]: Login by pxxxxx (AFP3.4)
Jul 26 22:35:32 nas rrdcached[1093]: flushing old values
Jul 26 22:35:32 nas rrdcached[1093]: rotating journals
Jul 26 22:35:32 nas rrdcached[1093]: started new journal /var/lib/rrdcached/journal/rrd.journal.1501101332.649630
Jul 26 22:35:32 nas rrdcached[1093]: removing old journal /var/lib/rrdcached/journal/rrd.journal.1501094132.649649
Jul 26 22:35:33 nas smartd[973]: Device: /dev/sdc [SAT], open() failed: Kein passendes Gerät gefunden
Jul 26 22:35:33 nas smartd[973]: Sending warning via /usr/share/smartmontools/smartd-runner to root ...
Jul 26 22:35:33 nas smartd[973]: Warning via /usr/share/smartmontools/smartd-runner to root: successful
Jul 26 22:39:01 nas CRON[24926]: (root) CMD ( [ -x /usr/lib/php5/sessionclean ] && /usr/lib/php5/sessionclean)
Jul 26 22:45:01 nas CRON[25025]: (root) CMD (/usr/sbin/omv-mkgraph >/dev/null 2>&1)
Jul 26 22:45:01 nas rrdcached[1093]: Received FLUSHALL
Jul 26 22:51:59 nas rsyslogd: [origin software="rsyslogd" swVersion="8.4.2" x-pid="986" x-info="http://www.rsyslog.com"] start
Jul 26 22:51:59 nas kernel: [ 0.005230] ACPI: 1 ACPI AML tables successfully acquired and loaded
Jul 26 22:51:59 nas kernel: [ 0.005268] Security Framework initialized
Jul 26 22:51:59 nas kernel: [ 0.005270] Yama: disabled by default; enable with sysctl kernel.yama.*
Jul 26 22:51:59 nas kernel: [ 0.005274] AppArmor: AppArmor disabled by boot time parameter
Jul 26 22:51:59 nas kernel: [ 0.005300] Dentry cache hash table entries: 65536 (order: 7, 524288 bytes)
Jul 26 22:51:59 nas kernel: [ 0.005362] Inode-cache hash table entries: 32768 (order: 6, 262144 bytes)
Jul 26 22:51:59 nas kernel: [ 0.005407] Mount-cache hash table entries: 1024 (order: 1, 8192 bytes)
Jul 26 22:51:59 nas kernel: [ 0.005410] Mountpoint-cache hash table entries: 1024 (order: 1, 8192 bytes)Any other hints for hunting down this problem?
All other VMs on this ESXi (mainly Ununtu) are working without any flaws. I've already changed the OMV VM to "Other Linux > 3.x 64bit". On other machines (bare metal and VMs) I have an Ubuntu 16.04 with netatalk 2.2.5-1 installed which works without any problem.
Cheers,
Patrik
//edit:
found this in the daemon.log "^@^@^@^@^":
Jul 26 22:52:01 nas systemd[1]: Reached target Multi-User System.
Jul 26 22:52:01 nas systemd[1]: Starting Beep after system start...
Jul 26 22:52:01 nas systemd[1]: Starting Graphical Interface.
Jul 26 22:52:01 nas systemd[1]: Reached target Graphical Interface.
Jul 26 22:52:01 nas systemd[1]: Starting Update UTMP about System Runlevel Changes...
Jul 26 22:52:01 nas systemd[1]: Started Update UTMP about System Runlevel Changes.
Jul 26 22:52:01 nas avahi-daemon[948]: Service "nas - Web control panel" (/services/website.service) successfully established.
Jul 26 22:52:01 nas avahi-daemon[948]: Service "nas - SSH" (/services/ssh.service) successfully established.
Jul 26 22:52:01 nas avahi-daemon[948]: Service "nas - SMB/CIFS" (/services/smb.service) successfully established.
Jul 26 22:52:01 nas systemd[1]: Started Beep after system start.
Jul 26 22:52:01 nas systemd[1]: Startup finished in 1.828s (kernel) + 4.701s (userspace) = 6.529s.
^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@Jul 26 22:54:04 nas systemd-modules-load[262]: Inserted module 'fuse'
Jul 26 22:54:04 nas systemd[1]: Mounted Huge Pages File System.
Jul 26 22:54:04 nas systemd[1]: Mounted POSIX Message Queue File System.
Jul 26 22:54:04 nas systemd[1]: Mounted Debug File System.
Jul 26 22:54:04 nas systemd[1]: Started Load Kernel Modules.
Jul 26 22:54:04 nas systemd[1]: Mounted Configuration File System.
Jul 26 22:54:04 nas systemd[1]: Mounting FUSE Control File System...
Jul 26 22:54:04 nas systemd[1]: Starting Apply Kernel Variables...
Jul 26 22:54:04 nas systemd[1]: Mounted FUSE Control File System.
Jul 26 22:54:04 nas systemd[1]: Started Nameserver information manager.
Jul 26 22:54:04 nas systemd[1]: Started Apply Kernel Variables.