11.1 Known issues

11.1.1 CIFS Does Not Start If Samba is Running

Description: CIFS server does not come up if the Samba server is running.

Cause: Novell CIFS cannot coexist with Samba daemons as they both use the same port.

Action: Log in to the OES server as root. Use the following commands to stop the Samba daemons and restart the CIFS server:

  • rcsmb stop

  • rcnmb stop

  • rcnovell-cifs start

11.1.2 Different Tree Migration Is Not Available in the Migration Tool

Description: The Different Tree scenario is not supported in the Migration Tool.

Action: Use the following workaround:

  1. Migrate the File System from the source server to the target server, using the Different Tree scenario.

    For detailed information see, Migrating Data to a Server in a Different Tree in the OES 11 SP3: Migration Tool Administration Guide.

  2. Reconfigure CIFS by using YaST on the target server.

    For detailed YaST configuration steps, see Section 5.1, Installing CIFS during the OES 11 SP3 Installation and Section 5.2, Installing CIFS after the OES 11 SP3 Installation.

11.1.3 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 11 SP3: File Systems Management Guide.