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

 Basic information
Release type: Hot Fix
Release date: 2013-06-17
OS update support: None
Technote: None
Documentation: None
Popularity: 839 viewed    7 downloaded
Download size: 805.38 MB
Checksum: 496104263

 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:
2941404, 3091650, 3124036, 3142729, 3142733, 3142746, 3197611

 Patch ID:

Readme file
Date: 2013-05-27
OS Version: 10 SP3
Symantec FileStore 
5.6 RP1 P4 HF5 Patch Upgrade README


PATCH ID                        : N/A
PATCH NAME                      : SFSFS-patch-5.6RP1P4HF5_rc3_2013_05_27.tar.gz
BASE PACKAGE NAME               : Symantec FileStore
BASE PACKAGE VERSION            : 5.6
OBSELETE PATCHES                : N/A
SUPPORTED OS                    : SLES
CREATION DATE                   : 2013-05-27
CATEGORY                        : enhancement, performance issue
REBOOT REQUIRED                 : Yes
SUPPORTS ROLLBACK               : NO

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

After you have installed or synchronized a new Symantec FileStore patch into your cluster, the list of available commands may change. Please login again to the CLI to access the updated features. 

IMPORTANT: There is a downtime for the services during an upgrade. The actual downtime will be a little longer than it takes to reboot the system. To avoid data loss, Symantec FileStore recommends that customers stop 
I/O processing completely during a patch upgrade.  

After you apply this patch, you cannot uninstall it. The 5.6RP1P4HF5 patch can only be installed on 5.6, 5.6P1, 5.6P2, 5.6P3, 5.6RP1, 5.6RP1P1,  5.6RP1P2, 5.6RP1P3, 5.6RP1P4, 5.6RP1P4HF1, 5.6RP1P4HF2, 5.6RP1P4HF3, or 5.6RP1P4HF4.

If you are upgrading on a replication source cluster:
	1)	Pause running jobs. 
	2)	Upgrade the cluster.
	3)	Resume all paused replication jobs.
If you are upgrading on a replication target cluster:
	1)	On the target cluster, check "echo listfset | fsdb -t vxfs /dev/vx/rdsk/sfsdg/<replication target fs> | grep -w \"\" | wc -l"
		a.	If the command returns 0. 
		b.	If the job is in the running state, pause the job from the source console.
		c.	Go to step 3.
	2)	If the above command returns non-zero:
		a.	If the job is in a running state, pause the job from the source console.
		b.	Umount the checkpoint first using the command "cfsumount /vx/<destination fs checkpoint>".  
		c.	Fsclustadm -v showprimary <destination fs>.
		d.	Except for the file system primary node, run "hagrp offline <vrts_destination fs group> -sys <non primary node(s)>".
		e.	Once you have run "hagrp -offline" on the non-primary nodes, run "vxumount -f -o mntunlock=VCS <destination fs>" on the primary node. 
	3)	Upgrade the cluster. After upgrading the online file systems that are offline in 2(b) and 2(d) steps, run the following commands after the upgrade:
		a) Run this command on all nodes, "hagrp -online <vrts_destination fs group> -sys <nodename>".
		b) cfsmount /vx/<destination fs checkpoint>.
		c) Resume all paused replication jobs.

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

IMPORTANT: Full upgrade instructions are included in the Symantec FileStore 5.6 Release Notes. Please note the following revisions
When you upgrade:

Symantec FileStore 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: 2941404, 3091650, 3124036, 3142729, 3142733, 3142746, 3197611
Errors/Problems Fixed:

        2941404    `cli>storage snapshot schedule delete fs_name` deletes both file systems with and without "-"(hyphens). An example would be file systems named fs01 and fs01-mrr. Hyphens are not handled properly.
        3091650    Global lock file (/opt/VRTSnasgw/log/nasgwlock.lock) becomes corrupted if the `cli>cluster reboot all` command is called while a replication job is still running. After a reboot, the `cli>upgrade show` comand cannot get a global lock anymore.
        3124036    When a replication source/destination has 200 million files, the `cli>replication job resync` command runs infinitely. The `cli>replication job rsync` command quits due to an "out of memory" error, and the system re-tries the command again and again.
        3142729    `cli>replication job enable` fails because `cfsmount()` called by `rep_cfsmount()` returns 23. This return value may indicate that the mount operation is still ongoing after a timeout. Because `cfsmount( )` has a return value of 23, FileStore needs to check on all the nodes to determine if the mount completed successfully.
        3142733    16 replication jobs running simultaneously causes errors in setting extended attributes. If you have one replication job running, you do not see these errors.
        3142746    When running a replication job with a schedule, the user received the following errors: "Error in setting extended attributes" and "Failed to get response from destination cluster." When executing the `cli>replication job status` command, the output displays "Enabled" instead of the "Failed" state.
        3197611    CIFS/CTDB service stops working after applying an upgrade patch from FileStore 5.6GA to 5.6RP1P4HF5RC2. This does not happen when upgrading from 5.6RP1P4HF4RC10 to HF5RC2.  This appears to be a mismatch between the CTDB version and its environment settings. 	


Etrack: 3061565

Symptom:  When attempting to destroy snapshots using File Systems > Snapshots > Destroy, the operation takes too long using the Symantec FileStore Management Console (GUI).

Description: When deleting snapshots using the Destroy button on the File Systems > Snapshots page, this operation may take more time depending on the user configuration. 

Resolution: Use the CLI command Storage> snapshot destroy <snapshot_name> <fs_name> instead of the Symantec FileStore Management Console (GUI). 

Etrack: 3058933

Symptom: Special permission bits (setuid and setgid attributes) of files are not 
transmitted to the destination cluster by Symantec FileStore Replication. 

Description: On SLES10 SP3, changing ownership of files clears the setuid bit 
of the file. The Posix documentation notes the following about "chown" 

"Unless chown is invoked by a process with appropriate privileges, the set-user-
ID and set-group-ID bits of a regular file will be cleared upon successful
completion; the set-user-ID and set-group-ID bits of other file types may be 

Since Symantec FileStore Replication runs using root privileges, it needs to preserve 
these special permissions on the destination cluster.  At the time of applying 
the metadata attributes (for example, permissions, owner), Symantec FileStore 
Replication needs to follow an order. Currently, Symantec FileStore Replication
sets the permission of the file first, and then tries to set the owner of the 
file. Setting ownership after applying permissions will reset the setuid bit, 
and Symantec FileStore Replication should first set the ownership of the file and then 
apply permissions on the destination files.

Resolution: The Symantec FileStore 5.6 RP1P5 release will contain the required fix. 
Please upgrade to Symantec FileStore 5.6 RP1P5.

Etrack: 3060268

Symptom: The Symantec FileStore Management Console (GUI) may not update data immediately after an operation.

Description: Start an operation from the Symantec FileStore GUI.  The updated data may not be reflected in the
Symantec FileStore GUI after displaying a success message. The Symantec FileStore GUI may not reflect the data generated 
by the Symantec FileStore CLI immediately.

Resolution:  Wait for a while and then refresh the page by pressing the "F5" key. If the update does not appear, 
click the Refresh link provided in the Symantec FileStore GUI.

Etrack: 3060306

Symptom: The "Fullspace" option is missing from the Symantec FileStore Management Console (GUI) File Systems > File Systems > More > Set Alert dialog.

Description: When using the Symantec FileStore Management Console (GUI), the "Fullspace" option is missing from the File Systems > File Systems > More > Set Alert dialog.

Resolution: Use the Storage> fs alert set fullspace option in the Symantec FileStore CLI for setting this option.

Etrack: 3052313  

Symptom: The NFS client, which is specified when creating an NFS share, may not be able to access NFS after a long time continuous load.

Description: While exporting an NFS share to a specific client by IP, after a long time continuous load, the NFS client may not be able to access the NFS share.

Resolution: This is very likely an NFS known issue. A Symantec FileStore representative is following up with Novell/Linux-NFS. The workaround is to restart the NFS service from the Symantec FileStore CLI.

Etrack: 3036067  

Symptom: Storage tier schedule will be removed after importing the configuration.

Description: If you save a system configuration by running "system config export local" and the system has a tier schedule, the schedule may be lost after importing it later.

Resolution: Login using the support user and go to the directory /opt/VRTSnasgw/conf/backup that holds the saved configuration file, for example: 
Cluster7_01:/opt/VRTSnasgw/conf/backup # ls

Uncompress the test.cfg file, and you will see a new directory cfsfiler.config within cfsfiler.config/storage_schedules. There is a file storage_sched_conf storing the storage schedule. 
You can find the lost tier schedules here, and then add them manually to the crontab.

Etrack: 3035544  

Symptom: After `storage fs set fullspace 85` exceeded 85% full, both NFS/CIFS shares were not changed to read-only.

Description: For fullspace protection, the file system size is checked every five minutes.  During this five-minute interval, if the usage of the file system grows to more than the fullspace limit, the NFS/CIFS shares are changed to read-only.  Note that if the file system is a small size and I/O from CIFS/NFS fills the file system fast, then the file system usage can be bigger than the threshold (or even to 100% if I/O was 
really fast) before being changed to read-only. This is by design.

If the file system reaches more than the threshold limit, during this time period, the exported file system operates in read-write mode until the 
respective cron job is executed to set the file system to read-only mode.

Etrack: 3051906  

Symptom: When `antivirus scanaction clean delete`, scan-clean/delete failed for eicar.cab (MicroSoft CAB format).

Description: Symantec AntiVirus does not support the delete operation for some types of container files. The non-supported container file types for the delete operation are the following extensions: 
.arj, .cab, .rar, and .bzip2. Since the .cab file type is not a supported container file for the scanaction delete operation, this is expected behavior. 

Resolution: Avoid setting the delete operation as the second action when you want to scan such container files. The alternative is to use the quarantine as a secondary action policy. SAV always quarantines the infected files no matter what the file type.

Etrack: 3067744
Symptom: Bond devices do not work with 802.3ad mode.

Description: The SUSE Linux Enterprise Server 10 (SLES10) operating system cannot provide the correct status information for NIC bonding with mode 4(802.3ad). Veritas Cluster Server (VCS) always marks the NIC as ONLINE, which results in the VIP not failing over, even if the network cables are pulled.

Resolution: This is an operating system issue; upgrade to Symantec FileStore 5.7, which is using the SUSE Linux Enterprise Server 11 (SLES11) operating system. This issue is fixed in the SLES11 operating system.


Read and accept Terms of Service