Server OS: FreeBSD 10
Client OS: OSX 10.9.2
Netatalk: 3.1.1

afpd -V
afpd 3.1.1 - Apple Filing Protocol (AFP) daemon of Netatalk

This program is free software; you can redistribute it and/or modify it under
the terms of the GNU General Public License as published by the Free Software
Foundation; either version 2 of the License, or (at your option) any later
version. Please see the file COPYING for further information and details.

afpd has been compiled with support for these features:

          AFP versions: 2.2 3.0 3.1 3.2 3.3 3.4 
         CNID backends: dbd last tdb 
      Zeroconf support: No
  TCP wrappers support: Yes
         Quota support: No
   Admin group support: Yes
    Valid shell checks: Yes
      cracklib support: No
            EA support:         ad | sys
           ACL support:         No
          LDAP support: No
         D-Bus support: No
     Spotlight support: No
         DTrace probes: No

              afp.conf: /usr/local/etc/afp.conf
           extmap.conf: /usr/local/etc/extmap.conf
       state directory: /var/netatalk/
    afp_signature.conf: /var/netatalk/afp_signature.conf
      afp_voluuid.conf: /var/netatalk/afp_voluuid.conf
       UAM search path: /usr/local/libexec/netatalk-uams//
  Server messages path: /var/netatalk/msg/

User home directories are mounted via AFP and have their ~/Library directory symbolically linked to local disk.  We found that browsers, email and instant message clients write many files and use files outside of ~/Library/Cache so we decided to symbolically link the entire ~/Library directory to local disk.  We have seen a big performance improvement from this change.

Periodically the symbolic link points to nothing.  This is obvious to the user as their applications all complain.  When running an ls -l in their home directory you see
  Library >

You have to run the command below to continue
  rm Library; ln -s /Users/${username}/Library Library

The rm command complains, but functionality is restored and you are left with a hint.
  .afpDeleted777668 -> /Users/${username}/Library

Has anyone seen this issue and what can be done?

Jason Breitman