13.1 Known Issues

13.1.1 AFP Does Not Come Up After Upgrading to OES 2018 or Later if Service Proxy is Configured

AFP service configured with service proxy fails to come up after upgrading to OES 2018 or later. This is because the service proxy users are not migrated to OES Credential Store (OCS). To resolve this issue, perform the following:

  1. Login as root user.

  2. Run yast2 novell-afp and then enter eDirectory user password.

  3. Specify the AFP proxy user password.

  4. Click Next and continue with AFP configuration.

  5. Verify the AFP service is up and running by using the following command:

    systemctl status novell-afptcpd.service

  6. Verify the service entry is present in OES Credential Store by using the following command:

    oescredstore -l

13.1.2 AFP Does Not Support NSS Volumes With ZID Value Greater Than the 32-bit Limit

On Mac, when you access the NSS volumes with ZID value greater than the 32-bit limit, AFP users might experience abnormal behavior while performing the file operations on that volume.

  • If the ZID value for NSS volume is less than the 32-bit limit, AFP users can access and perform any file operation on this volume. Therefore, it is recommended to set zid32 to restrict the ZID from crossing the 32-bit limit.

    • For local volumes, add zid32 in the mount option for the volume in /etc/fstab.

    • For shared volumes, add zid32 to the volume’s /opt in the resource load script.

    For more information on how to set ZID mode in local and shared volumes, see Setting and Viewing the ZID Mode for a Volume in the OES 2018 SP3: NSS File System Administration Guide for Linux.

  • If the ZID value for NSS volume has already crossed the 32-bit limit, it is recommended to use CIFS or NCP protocol to access this volume.

Also, you can configure AFP users to access only those volumes with ZID value less than the 32-bit limit by using the iManager AFP Management plug-in.

13.1.3 Owner’s Name Not Displayed in the Macintosh Client

The owner’s name is not displayed when you right-click a folder.

Micro Focus has no current plans to fix this.

13.1.4 File Level Trustees Are Deleted When a File is Modified

File level trustees might be deleted when a file is modified, depending on how the application works with files it opens for writing. Some third-party applications record changes in a temporary file in order to save internal memory or as a safety net to prevent data loss due to a power failure, system crash, or human error. When a user saves the changes, the application deletes the original file, and saves the temporary file with same name as the original file. In response to the deletion instruction, the file system deletes the original file as well as any file level trustees set on the file. The file system is not application aware; that is, it does not track the ultimate intent of the applications that you might use.

For more information, see File-Level Trustees in the OES 2018: File Systems Management Guide.

13.1.5 AFP Does Not Support DST Shadow Volumes

AFP does not support Dynamic Storage Technology Shadow volumes. The AFP users are able to see only the data that is on the primary volume. Primary or secondary volumes that are used in a DST shadow volume should not be exposed through AFP.