Date: 2011-01-27
OS: SLES
OS Version: 10 SP3
Symantec FileStore (previously called Veritas Storage Foundation Scalable File Server)
5.6P1 Patch Upgrade README
CONTENTS
I. Overview
II. Upgrade procedure
III. Fixes in the new patch
IV. New features
V. Known Issues
PATCH ID : N/A
PATCH NAME : FileStore-sles10_x86_64-patch-5.6P1.tar.gz
BASE PACKAGE NAME : Symantec FileStore
BASE PACKAGE VERSION : 5.6
OBSELETE PATCHES : N/A
SUPERCEDED PATCHES : N/A
INCOMPATIBLE PATCHES : N/A
SUPPORTED OS : SLES
SUPPORTED OS VERSION : SLES 10 SP3
CREATION DATE : 2011-01-25
CATEGORY : enhancement, performance issue
REBOOT REQUIRED : Yes
SUPPORTS ROLLBACK : NO
I. OVERVIEW:
------------
Symantec FileStore (previously called Veritas Storage Foundation Scalable File Server) provides a scalable clustered storage solution. This document provides release information for the patch.
Important: The Symantec version naming convention has changed for this patch. Hot Fix (HF) patches are now catalogued as Point (P) patches. Because of the new naming convention, the official name of this patch is 5.6P1 (instead of patch 5.6HF1).
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 cannot 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: 2044370, 2219806, 2219890, 2220746, 2220990, 2227298, 2227625, 2227628, 2228546, 2228910, 2230644
Errors/Problems Fixed:
2044130, 2044370 Unable to unset the quota for a user who is already deleted from database.
2219885, 2219806 Local users whose account names start with a capital letter cannot successfully map the home directory share.
2218884, 2219890 CIFS> mapuser command works for local user accounts that do not exist.
2219325, 2220746 Configuration information for a CIFS share of a DAR file system is not getting imported.
2221730, 2220990 Unable to create second rollback for a file system.
2218881, 2227298 Spelling mistakes in command prompts.
2228704, 2227625 In some cases, the ctdb_server goes offline unexpectedly.
2219888, 2227628 The snapshot restore operation cannot be executed in XML.
2229134, 2228546 Showing VCS error message when no virtual IP is online.
2226121, 2228910 CIFS> share add command accepts unsupported values for share names (such as "global" "printers" and "homes").
VI. NEW FEATURES:
-----------------
Etrack Incident: 2226842
When a CIFS home directory file system is changed, quota information for a user's home directory is migrated from the existing home directory file system to the new home directory file system.
Quota migration results are based on the following logic:
Case 1:
In the case where the existing home directory file system is NULL, you can set the new home directory file system to be multiple file systems (for example, fs1, fs2). If the multiple files systems previously had different quota values, the quota status and values from the first file system are migrated to other file systems in the new home directory. The first file system is the template. Only the user/group quota values that existed on the first file system are migrated. Other user/group quota values remain the same on the other file system.
For example, assume the following:
* The new home directory file systems are fs1 and fs2.
* user1, user2, and user3 have quota values on fs1.
* user2, user3, and user4 have quota values on fs2.
For the migration, user/group quota values for user1, user2, and user 3 are migrated from fs1 to fs2. Quota values for user4 are kept the same on fs2, and user4 has no quota values on fs1.
Case 2:
When the existing home directory file systems are already set, and you change the file systems for the home directory, the quota status and values need to be migrated from the existing home directory file systems to the new file systems. For this migration, the first file system in the existing home directory acts as the template for migrating quota status and values.
For example, if the existing home directory file systems are fs1 and fs2, and the file systems are changed to fs2, fs3, and fs4, then the user/group quota values on fs1 are migrated to fs3 and fs4. Other user/group values on fs3 and fs4 remain the same.
Etrack Incident: 2228040
The Storage> quota fs set command has a new domain_name option. This option enables you specify file system quotas for a particular domain.
Previously, the command syntax was:
Storage> quota fs set userquota|groupquota user_or_group_names [hardlimit|softlimit] [numinodes|numspace] [value] [fs_name]
The new command syntax is:
Storage> quota fs set userquota|groupquota user_or_group_names domain_name [hardlimit|softlimit] [numinodes|numspace] [value] [fs_name]
V. Known Issues:
----------------
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: 2251966
Symptom: In admin mode, you can use CIFS> local user commands to create and delete special, reserved system accounts (such as root).
Description: If you use the CIFS> local user add command to add an account with the same name as a special, reserved system account (for example, root, support, or master), you can then use the CIFS> local user delete command to delete that account from /etc/passwd.
Workaround: There is no workaround for this issue. Do not use reserved names (such as root, support, or master) when you create local user accounts.
