Originated: November 20, 2015
********************************************************************************

Patch-163853: Patch for OneFS 7.2.0.4. This patch addresses multiple issues
that affect the SMB and authentication services.

--------------------------------------------------------------------------------

This patch can be installed on clusters running the following OneFS version: 
7.2.0.4

This patch conflicts with the following patch:
patch-162714

If any conflicting patches are installed on the cluster, you must remove them
before installing this patch.

********************************************************************************

RESOLVED ISSUES

* Bug ID 160739
  If OneFS SMB 2 symbolic link translation was disabled on the cluster,
  symbolic links to directories could not be deleted.
  
  Note:
  OneFS SMB 2 symbolic link translation is disabled by running the following
  command:
  
  isi_gconfigregistry.Services.lwio.Parameters.Drivers.onefs.SMB2Symlinks=0

* Bug ID 162368
  A change to the way OneFS 7.2.0.4 handled access to the directories within
  an SMB share could have prevented SMB clients from renaming directories or
  files within SMB shares. This issue occurred if the object the SMB client
  was attempting to rename was contained within a share to which the client
  had been granted only the Traverse Folder/Execute File permission. In OneFS
  7.2.0.4, if an SMB client attempted to rename an object within an affected
  SMB share, an error appeared on the client and the object was not renamed.

  The exact error that appeared depended on the operating system from which
  the client was connecting to the cluster and the method the client was
  using to access the base directory or subdirectory. 
  
  For example, if a Windows client was connected to the cluster over SMB 2,
  any attempts to rename a file through Windows Explorer resulted in the
  following error:
  
  The file 'file' is too large for the destination file system
  
  However, if a Windows client was connected to the cluster over SMB 2,
  any attempts to rename a file through the command line interface resulted
  in the following error:
  
  The parameter is incorrect.
  
  If a Windows client was connected to the cluster over SMB 1, any attempts
  to rename a file through the command line interface resulted in the
  following error:
   
  The system cannot find the file specified.

* Bug ID 163479
  On clusters running OneFS 7.1.1.6, 7.1.1.7, 7.2.0.4 or 7.2.1.0, if an SMB
  client sent a request to initiate an SMB 1 session on the cluster and then
  re-sent the request, the second SMB 1 request was blocked until the first
  request was processed. On networks where responses to requests were
  frequently delayed--for example, if a domain controller was slow to process
  authentication requests--it was possible for the blocked session requests to
  become permanently stuck. If this occurred, the lwio process on the affected
  node stopped responding, no new connections to the node could be
  established and existing connections might have been disconnected. In some
  cases, the lwsm and lwio processes had to be restarted in order to resolve
  the issue.
 
********************************************************************************

CHANGED FILES

* /usr/likewise/lib/lwio-driver/srv.so
  (MD5 = 980e0fd169aef74b6faf2625b7695cb2)

* /usr/likewise/lib/lwio-driver/onefs.so
  (MD5 = 65179245270664820caaa490fe4cd2ca)

********************************************************************************

INSTALLATION/REMOVAL IMPACTS

During installation or removal of this patch, the SMB and authentication
services are unavailable and SMB client connections to the cluster are
disconnected. After the patch is installed, SMB clients must reestablish a
connection to the cluster.

********************************************************************************

IMPORTANT!  
VERIFY CLUSTER-FREE SPACE
If there is insufficient free space and you attempt to install or remove a
patch, the process might not complete successfully. An incomplete patch
installation or patch removal can leave the cluster in an inaccessible state.

Before installing or removing a patch, verify that your cluster has enough
free space to perform the procedure. For more information about maintaining
sufficient free space on an Isilon cluster, see the Best Practices Guide for
Maintaining Enough Free Space on Isilon Clusters and Pools:
https://support.emc.com/docu48119.
   
********************************************************************************

REMOVE CONFLICTING PATCHES

If any conflicting patches are installed on the cluster, perform the following
procedure to remove them before installing this patch.

IMPORTANT!

Read the INSTALLATION/REMOVAL IMPACTS in the README for the conflicting patch
before performing this procedure.

1. Verify that your cluster has enough free space to remove this patch.

2. Open an SSH connection on any node in the cluster and log in using the root
   account.

   NOTE: If the procedure is being done on a compliance mode cluster, log in
   using the compadmin account.

3. To remove this patch, run the following command, where <ID> is the patch
   ID of the patch to be removed:
   
   isi pkg delete patch-<ID>

4. To verify that this patch was removed, run the following command:
     
   isi pkg info

5. Confirm that patch-<ID> does not appear in the list of installed packages.

********************************************************************************

INSTALLING THIS PATCH

IMPORTANT!
Read INSTALLATION/REMOVAL IMPACTS before performing this procedure.
   
1. Verify that your cluster has enough free space to install this patch.

2. Open an SSH connection on any node in the cluster and log in by using the
   root account.

   NOTE: If the patch is being installed on a compliance mode cluster, log in
   using the compadmin account.

3. Copy the patch-163853.tgz file to the /ifs/data directory on the cluster.

4. Run the following command to change to the /ifs/data directory:
   
   cd /ifs/data

5. To extract the patch file, run the following command:

   tar -zxvf patch-163853.tgz

6. To install this patch, run the following command:

   isi pkg install patch-163853.tar

7. To verify that this patch is installed, run the following command:
  
   isi pkg info

8. Confirm that patch-163853 appears in the list of installed packages.

********************************************************************************

REMOVING THIS PATCH

If you need to remove this patch, complete the steps below.

IMPORTANT!
Read INSTALLATION/REMOVAL IMPACTS before performing this procedure.

1. Verify that your cluster has enough free space to remove this patch.

2. Open an SSH connection on any node in the cluster and log in using the
   root account.

   NOTE: If the patch is being removed from a compliance mode cluster, log in
   using the compadmin account.

3. To remove this patch, run the following command:

   isi pkg delete patch-163853

4. To verify that this patch was removed, run the following command:

   isi pkg info

5. Confirm that patch-163853 does not appear in the list of installed packages.

********************************************************************************
