The latest patch(es) : sfs-sles10_x86_64-5.6RP1P4HF6 

 Basic information
Release type: Rolling Patch
Release date: 2011-06-07
OS update support: None
Technote: None
Documentation: None
Popularity: 594 viewed    64 downloaded
Download size: 516.13 MB
Checksum: 1767292133

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

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

This patch is obsolete. It is superseded by: Release date
sfs-sles10_x86_64-5.6RP1P4HF6 2013-09-17

 Fixes the following incidents:
2226756, 2320508, 2326350, 2329636, 2338936, 2354391, 2356009, 2358043, 2358185, 2362117, 2362675, 2363436, 2364733, 2364870, 2366333, 2370899, 2373627, 2390876, 2391987

 Patch ID:

Readme file
Date: 2011-05-26
OS Version: 10 SP3
Symantec FileStore 
5.6 Rolling Patch 1 (RP1) Upgrade README

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

PATCH NAME 			: FileStore-sles10_x86_64-patch-5.6RP1.tar.gz
BASE PACKAGE NAME		: Symantec FileStore
CREATION DATE 			: 2011-05-23
CATEGORY 			: enhancement, performance issue

Symantec FileStore provides a scalable clustered storage solution. This document provides release information for the patch.

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 cannot uninstall it. Please take notice that the 5.6 RP1 patch can only be installed on 5.6 or 5.6 P1 or 5.6 P2 or 5.6 P3.

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

IMPORTANT: Full upgrade instructions are included in the FileStore 5.6 Release Notes. IMPORTANT: Please note the following revision:

When you upgrade:

* Symantec recommends that you remove I/O fencing before upgrading any cluster node or exporting your current configuration. Use the Storage> fencing off command first followed by the Storage> fencing destroy command to remove I/O fencing. This step is not required, but it is suggested for a clean upgrade. 


Etrack Incidents: 2373627, 2226756, 2320508, 2326350, 2329636, 2338936, 2356009, 2358043, 2358185, 2362117, 2362675, 2363436, 2364870, 2366333, 2370899, 2364733, 2391987, 2390876, 2354391

Errors/Problems Fixed:
2374715, 2373627 Rebooting a node initiates a full file system check (fsck) which causes the file system to fail.
2227071, 2226756 When creating or bringing online a 10TB file system with a 1024 block size, out-of-memory situations may occur.
2322461, 2320508 A newly-added node cannot find the iSCSI storage.
2327429, 2326350 The IO hangs when one of the arrays is disconnected for a mirrored volume.
2246654, 2329636 The Network> ldap show users command does not work for an LDAP Distinguished Name (DN) account, but it does work for anonymous login accounts.
2282747, 2338936 In the process of shrinking the file system, the file system is out of inodes.
2301813, 2356009 For a scheduled replication job, no job failed (or job aborted) messages appear in the system log (syslog) or event log (sfsfs_event_log).
2328803, 2358043 The dfree.sh script does not work well for file systems with names of more than 8 characters. For example: /vx/cifs_home
2256248, 2358185 The Storage> snapshot list command displays the wrong ctime and mtime values when a replication job is running.
2361316, 2362117 When more than one host is responding to an IP, the NFS share which was added to the client will fault.
2362872, 2362675 Replication for a CIFS share with the full_acl option causes inode corruption; a kernel panic occurs after a replication job is completed, a replication job is disabled, or the system reboots.
2362871, 2363436 A home directory share can be set to an offline file system.
2365592, 2364870 Permission inconsistencies can occur for CIFS shares with full_acl settings.
2366869, 2366333 VIP failover works when a network cable is removed, but VIP failback does not work when the connection is restored.
2365601, 2370899 The layout of a file system becomes mirrored after creating a mirrored-stripe file system with a long file system name.
2387609, 2364733 User quota corruption occurs when there are more than 4500 users created and the user quota is set with softlimit = 3.5GB and hardlimit = 4GB.
2391987, 2391987 Need to remove inode cache limit.
2390876          An out-of-date Symantec logo displays in FileStore online Help.
2355622, 2354391 The processes initiated by the run_SF agentlet can consume too much memory.

IV. Known Issues:

Etrack Incident: 2352422

Symptom: The GUI goes offline during a patch upgrade from FileStore 5.6 to FileStore 5.6 RP1.

Description: When you upgrade from FileStore 5.6 to FileStore 5.6 RP1, some of the FileStore services, including the FileStore Management Console (gui service), may be OFFLINE instead of ONLINE.

Workaround: Use the Support> services show command to verify the state of the FileStore services. Use the Support> services online servicename command to bring a service back online. For example, enter the following command:

Support> services online gui

to bring the gui service back online.

Etrack Incident: 2196782

Symptom: Unable to use the FileStore Management Console (GUI) to install a device driver from the FileStore Driver Update Disk (DUD).

Description: When you use the Settings > Upgrade feature in the FileStore Management Console to unstall a DUD device driver, the upgrade fails.

Workaround: Use the FileStore Upgrade> patch install and the Upgrade> patch duduninstall CLI commands to install and uninstall device drivers.  

Etrack Incident: 2281651

Symptom: Cannot detach pools that contain an NLM internal file system.

Description: In some cases, when you run the Storage> pool detachset command, the following error message displays: "SFS Storage ERROR V-288-2265 One of the pools you want to detach contains FileStore internal file system (_nlm_). Cannot detach pool containing this special file system." 

NLM is a FileStore internal file system which the cluster uses for storing NFS lock manager (NLM) data and the replication database. This cluster-wide file system is created transparently when the first file system is created and is deleted when the last file system is deleted. 

Workround: There is no workaround for this issue. It will be fixed in a future release. To avoid this issue, create the pool to be detached after the NLM file system has been created. 

Read and accept Terms of Service