This page lists publically-released patches for Veritas Enterprise Products.
For Product GA build, see Veritas Entitlement Management System(VEMS) by clicking the Veritas Support 'Licensing' option.
For information on private patches, contact Veritas Technical Support.
Veritas is making it easier to find all software installers and updates for Veritas products with a completely redesigned experience. NetBackup HotFixes and NetBackup Appliance patches are now also available at the new Veritas Download Center.
Patches for your product can have a variety of names. These names are based on product, component, or package names. For more information on patch naming conventions and the relationship between products, components, and packages, see the SORT online help.
sfs-sles10_x86_64-5.5SP1RP2P3
Sign in if you want to rate this patch.

 Basic information
Release type: P-patch
Release date: 2011-01-07
OS update support: None
Technote: None
Documentation: None
Popularity: 592 viewed    17 downloaded
Download size: 389.93 MB
Checksum: 581048664

 Applies to one or more of the following products:
FileStore 5.5SP1 On SLES10 x86-64

 Obsolete patches, incompatibilities, superseded patches, or other requirements:
None.

 Fixes the following incidents:
2012371, 2092238, 2169238, 2181353, 2186517, 2208690, 2216997, 2217167, 2217389, 2218394, 2223312

 Patch ID:
None.

 Readme file  [Save As...]
Date: 2011-01-07
OS: SLES
OS Version: 10 SP2
Veritas Storage Foundation Scalable File Server (now called Symantec FileStore)
5.5 SP1RP2P3 Patch Upgrade README

CONTENTS
I.   Overview
II.  Upgrade procedure
III. Fixes in the new patch
IV.  Known issues


PATCH ID 			: N/A
PATCH NAME 			: FileStore-sles10_x86_64-patch-5.5SP1RP2P3.tar.gz
BASE PACKAGE NAME		: Symantec FileStore
BASE PACKAGE VERSION 		: 5.5SP1, 5.5SP1RP1, 5.5SP1RP2, 5.5SP1RP2HF1, 5.5SP1RP2HF2
OBSELETE PATCHES 		: N/A
SUPERCEDED PATCHES 		: N/A
INCOMPATIBLE PATCHES 		: N/A
SUPPORTED OS 			: SLES
SUPPORTED OS VERSION		: SLES 10 SP2
CREATION DATE 			: 2011-01-07 
CATEGORY 			: enhancement, performance issue, hang 
REBOOT REQUIRED 		: Yes
SUPPORTS ROLLBACK 		: NO

I. OVERVIEW:
------------
The Veritas Storage Foundation Scalable File Server (now called Symantec FileStore) provides a scalable clustered storage 
solution. This document provides release information for the patch.
Please be noted, we changed our naming version from this patch. we changed "HF" to "P", we called our hot fix as "5.5SP1RP2HF"
before, now we called it as "5.5SP1RP2P". 


II. UPGRADE PROCEDURE:
----------------------
After you have installed or synchronized a new SFS patch into your cluster, the list of available commands may change. 
Please login again to the CLI to access the updated features. Because this is a phased upgrade process, please bring 
down the services manually, then start with the patch installation. After you apply this patch, you can not uninstall it.

To install the patch:
1. Login as master:
   su - master
2. Start the patch install:
   upgrade patch install <URL>


III. FIXES IN THE NEW PATCH:
----------------------------

Etrack Incidents: 2012371, 2092238, 2169238, 2181353, 2186517, 2208690, 2216997, 2217167, 2217389, 2218394, 2223312

SYMANTEC INCIDENT: 1966618 (2012371)

SYMPTOM: Staged upgrade does not  work for single node installations.

DESCRIPTION: Single node installations are supported by Symantec FileStore, but staged upgrades do not work on this 
type of installation. 

RESOLUTION: Fixed in this patch.


SYMANTEC INCIDENT: 2085972 (2092238)
SYMANTEC ESCALATION: 412-409-798

SYMPTOM: The Storage> fs grow command increases VxVM volume to 1TB, but it does not increase VxFS to 1TB.

DESCRIPTION: In some cases, if you use the Storage> fs grow command to increase a file system by small amounts 
(for example, 10MB or 100MB) it works correctly. If you use the Storage> fs grow command to increase a file system 
by large amounts (for example, 1TB) only the volume gets increased, but not the file system.

RESOLUTION: Fixed in this patch by adding resizing checks. If the Storage> fs grow command fails, an error message 
displays.


SYMANTEC INCIDENT: 2169238

SYMPTOM: When the console server and the master node are different, deleting the secondary tier of a file 
system fails.

DESCRIPTION: If the console server and master node are different, and you use the Storage> tier remove command 
to delete the secondary tier of a file system, an unknown error occurs.

RESOLUTION: Fixed in this patch. 


SYMANTEC INCIDENT: 2181486 (2181353)

SYMPTOM: Network> ldap set command does not work correctly when CN, DN, or OU values include blank spaces.

DESCRIPTION: If you use the Network> ldap set command to set client attributes and you include a blank space 
in the value string, the characters you enter after the space are not included in the attribute definition. 

RESOLUTION: Fixed in this patch.


SYMANTEC INCIDENT: 2185788 (2186517)

SYMPTOM: Unable to use the CIFS> set command to set the ntlm_auth value to "no".

DESCRIPTION: When you enter the CIFS> set ntml_auth no command, an error message appears.

RESOLUTION: Fixed in this patch.


SYMANTEC INCIDENT : 2208687 (2208690)
SYMANTEC ESCALATION : 412-729-894

SYMPTOM: Unable to see LUN size correctly in FileStore after LUN resizing.

DESCRIPTION: In some cases, if you resize a LUN, then use the FileStore Storage> disk grow command to grow the 
disk, the following error message appears:

SFS disk ERROR V-288-1370 No change in disk size. Nothing to grow.

RESOLUTION: Fixed in this patch.


SYMANTEC INCIDENT : 2216996 (2216997)
SYMANTEC ESCALATION : 413-258-781

SYMPTOM: Antivirus services will not start on a node after installing the 5.5SP1RP2HF2 patch.

DESCRIPTION: In some cases, after installing the 5.5SP1RP2HF2 patch on all nodes in a cluster, AntiVirus 
services start on some nodes, but not all nodes. 

RESOLUTION: Fixed in this patch. 


SYMANTEC INCIDENT : 2217164 (2217167)
SYMANTEC ESCALATION : 412-971-372
	
SYMPTOM: When Xcopy and Robocopy are used for migrating files to Filestore, only the files and ACL`s of 
the Administrator are migrated successfully.

DESCRIPTION: A "security id" error message appears when using Xcopy or Robocopy to migrate files to FileStore. 
Not all the files are migrated. For example:

Robocopy error no. 1307: Coping NTFS Security to destination directory X:\toto\ 
This security id cannot be defined as an owner of this object 

RESOLUTION: Fixed in this patch.


SYMANTEC INCIDENT : 2218228 (2217389)

SYMPTOM: Support data migrate for CIFS.

Description: When a customer already has data with ACL information on the domain, they want to migrate data to 
the CIFS server smoothly.

Resolution: Fixed in this patch. Added new data_migration yes|no option to the CIFS> set command. For example:

CIFS> set data_migration yes


SYMANTEC INCIDENTS: 2206143 (2218394) and 2223311 (2223312)
SYMANTEC ESCALATION: 412-610-388

SYMPTOM/DESCRIPTION: NFS resource went offline and stalled unexpectedly.

RESOLUTION: Fixed in this patch. Included VxFS 5.0MP3RP3HF32 package for 5.5SP1RP2P3.


IV. KNOWN ISSUES:
-----------------

SYMANTEC INCIDENT: 2103213 (2153051)

SYMPTOM: Cannot access home directory CIFS shares.

DESCRIPTION: After you enter the CIFS> mapuser cifs5 DOMAIN nfs1 command, CIFS users cannot access the home directory 
CIFS shares. 

WORKAROUND: For mapped Active Directory users to access their home directory CIFS shares, use the following path: 
\\filestore\realADuser (instead of \\filestore\homes).



Read and accept Terms of Service