FLASH - Tivoli SANergy Version 3.3.6

Updates for adding HSM SAMFS support to windows. 2 new registry configurations are present
HSMWaitDelay – Default value 7000 milliseconds

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\mcfsrdr\Parameters\HSMWaitDelay

HSMWaitRetries – Default value 0. If the value is 0 never timeout.

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\mcfsrdr\Parameters\HSMWaitRetries

APARS closed in Build 3.3.4.0 – FixPack 4
IC54113 BSOD during MDC file extension on Win 2003 (same as defect 905 below).

APARS closed in Build 3.3.3.0 – FixPack 3
None

APARS closed in Build 3.3.2.0 – FixPack 2
None

APARS closed in Build 3.3.1.0 – FixPack 1
None

APARS closed in Build 3.3.0.0 – Release
None

APARS closed in Build 3.2.13.0 – FixPack 13
None

APARS closed in Build 3.2.12.0 – FixPack 12
None

APARS closed in Build 3.2.11.0 – FixPack 11
IC48481 – Fixed SANergy ftp write to a fused volume corruption problem.
IC48663 – Fixed SANergy MDC memory leak.

APARS closed in Build 3.2.10.0 – FixPack 10
None.

APARS closed in Build 3.2.9.0 – FixPack 9
None.

APARS closed in Build 3.2.8.0 – FixPack 8
None.

APARS closed in Build 3.2.7.0 – FixPack 7
None.

APARS closed in Build 3.2.6.0 – FixPack 6
IC43779– Fixed the SANergy race condition with simultaneous open caused file limit to be reached.
IC43780 – Fixed the multi-thread write defect allowing SANergy to now read the file back correctly.
IC43781 – Fixed the uninitialized memory read errors in sanergyd.

APARS FIXED IN THIS PTF (Build 3.2.5.3 – FixPack 5)
IC43148 - Fixed the truncation of a read-only file when SANergy closes it.

APARS closed in Build 3.2.4.0 – FixPack 4
None.

APARS closed in Build 3.2.3.0 – FixPack 3
IC36783 - STOP 0x7F while using SANergy/NAV on network drive.
IC37049- SANergy does not give sufficient errors when disk runs out of space.
IC37983 – SANergy bluescreen failed allocation of paged pool.
IC38077- Windows 2000 system blue screen while booting.
IC38149- SANergy MSCS errors if regional options are set to something other than English (United States). Workaround: Install using English (United States), after install and setup is complete, change the locale back to its original setting.

APARS closed in Build 3.2.2.0 – FixPack 2
IC35523 - SANergy MDC QFS hang.

APAR’s closed in Build 3.2.1.0 – FixPack 1
IC34766 – SANergy MSCS does not install from CD.
This has been fixed in the new SANergy MSCS FixPack, version 3.2.1.1 and up.


BUG Fixes
Bug Fixes – FixPack 2 (3.3.6.0)
None

Bug Fixes – FixPack 2 (3.3.5.0)
None

Bug Fixes – FixPack 2 (3.3.4.0)
None

Bug Fixes – FixPack 2 (3.3.3.0)
905 - BSOD during MDC file extension on Win 2003 (same as APAR IC54113 above).

911 - Registry key added for Win 2K for 905. Default is 1 for Win 2003, set to 0 for Win 2K. HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\mcfs\Parameters\UseSetFileVDL

Bug Fixes – FixPack 2 (3.3.2.0)
None

Bug Fixes – FixPack 1 (3.3.1.0)
None

Bug Fixes – Release (3.3.0.0)
None

Bug Fixes – FixPack 13 (3.2.13.0)
None

Bug Fixes – FixPack 12 (3.2.12.0)
None

Bug Fixes – FixPack 11 (3.2.11.0)
857 – Can not enter large values in SANergyconfig options panel.
861 - Delete file to simplify message file build
862 - Simplify message file builds
863 - Windows: Cached FTP reads from a fused volume cause corruption.

Bug Fixes – FixPack 10 (3.2.10.0)
-none-

Bug Fixes – FixPack 9 (3.2.9.0)
-none-

Bug Fixes – FixPack 8 (3.2.8.0)
822 - Update the lease start time when appending a map.

Bug Fixes – FixPack 7 (3.2.7.0)
-none-

Bug Fixes – FixPack 6 (3.2.6.0)
-none-

Bug Fixes – FixPack 5 (3.2.5.3)
You must set the dirty file Boolean to true prior to closing with DirtyFileSize.

Bug Fixes – FixPack 4
SANergy has been improved to work better with virtual IP software.

Bug Fixes – FixPack 3
Fixed the Cluster Share Resource Offline (disk access deadlock) problem.
Fixed the Incorrect filesize problem. The incorrect filesize may be returned to the application from query file information, info class FileAllInformation.

Bug Fixes - FixPack 2
When a user opened NT's Performance Monitor and selected Physical Disk and Disk Bytes/sec, the performance results would be twice as large as those reported in the SANergy Setup Tool Performance Tester Tab. This double count has to do with an error in NT's reporting, the data is not going to the drive twice. Even though the problem primarily has to do with NT and not SANergy, the code has been modified so that the results in Performance Monitor and SANergy now share the same accuracy. Change the following registry key:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\mcfsrdr\Parameters\SubstPartDevices to 1 and reboot.


Known Issues
Windows Hyper-Extension problem with MS Word and Excel files Document properties displays the file size as 100MB for a short length of time, then updates the properties to the correct size. File is OK.

Releasing Ownership SANergy may stop responding when releasing multiple volumes simultaneously.

Compressed Files SANergy does not fuse files compressed by the operating system. All compressed files will be defaulted to go over the LAN.

Avid-NT Systems SANergy does not work with Avid-NT systems due to Avid's inability to work with network mapped volumes.

Windows 2000 mount point issues Windows 2000 hosts do not assume that all directories under a given share are always on the same drive as in Windows NT 4.0. Windows 2000 mount points can cause major corruption. If a Windows 2000 directory is shared out and there is another mount point inside of it, then a host can get a map for any of the files under that mount point. However, it will use that map as if it is on the same drive the share is on. This will cause SANergy to access the wrong drive.

Windows 2000 HSM Feature SANergy does not work with the HSM feature of Windows 2000.

Volume Sets (Windows) You may use Windows volume set capability only if you are using all Windows computers on the SAN. Macintosh and UNIX hosts do not correctly deal with volume set volumes.

Parity SANergy does not support RAID 5, which is parity based software striping. SANergy does support RAID 0.

Mirroring SANergy does not support RAID 1, which is software mirroring. SANergy does support RAID 0.

Sparse Files SANergy does not support sparse files in a Windows 2000 environment.

Delete Volume Attempt (Intermittent) SANergy only allows you to delete a volume if you are the Device Owner, although Disk Administrator may remove the drive letter and its share name if you try to delete the volume when you are not the owner.

Dynamic Volumes (Windows 2000 Striping) SANergy does not support dynamic volumes in a Windows environment.

Removing Drive Letters (Windows Host Systems) If you need to remove or change drive letters on your host systems, you must make the drive letter change and then reboot the system.

Unmanaging a Bus Tivoli SANergy provides the unmarker.exe program (in the Tivoli SANergy install directory) to stop management of the bus. To use unmarker.exe, open a command prompt window to unmark a bus. See the Administrator's Guide for information on using unmarker.exe.

Windows and copy To provide optimum performance, you should consider using the SCOPY binary or alter the caching options on the host. The cache-line-size value should be increased dramatically (from the default of 64 KB to possibly 512 KB or 1 MB). At the same time, the maximum cache size should also be adjusted dramatically upwards (from the default of 4 MB to possibly 20 MB or higher). Tivoli SANergy takes the cache memory from non-paged-pool. You must be careful not to set this value higher than the amount of non-paged-pool you can afford. For a rough estimate, assume that the size of your non-paged-pool is roughly 1/5th-1/10th of your system RAM. The reason for these adjustments has to do with how NT issues I/O when it considers a device to be a LAN device. This causes a conflict with various Tivoli SANergy optimization caching logic. This results in degraded storage performance. Therefore, it is better to reduce the number of times the cache-lines are paged.

Restriping/Partitioning It is important to closely follow the instructions in the Administrator's Guide when you restripe or repartition the storage. Typically this means rebooting any host system before you attempt to access the changed storage elements. See Chapter 5, Managing SANergy.

Renaming Volumes It is important to follow the information in the Administrator's Guide when you rename volumes that reside on the SAN. Reboot any host system before the host attempts to access the changed storage elements. See Chapter 5, Managing SANergy.

Relinquishing MDC Ownership Before relinquishing MDC ownership of a volume, you must first disconnect all network users of that volume, including UNIX, Windows hosts. Failure to do so can result in uncoordinated access to the storage volumes and possible data loss.

Administrator's Guide – MSCS updates
The information in this document detail changes to Appendix B, MSCS Configuration in the Administrator's Guide.

Setup, Installing, and Configuring SANergy with MSCS
The following steps outline how to setup, install, and configure MSCS and SANergy. For more detailed steps, refer to Appendix B in the SANergy Administrator’s Guide and the SANergy Redbook.

MSCS Initial Setup
Verify that all attached storage hardware is MSCS approved by Microsoft.

Delete the physical disk resources that correspond to the volumes you want to share via SANergy. These will later be redefined as SANergy Volume resources.

Prior to setting up a Microsoft cluster, all shared SCSI or Fiber Channel storage must be installed and configured on each node of the cluster, one machine at a time, while the other is powered off.
Only BASIC disks are supported and must be formatted with NTFS.
Disk drive partition letters must match between each node of a cluster.
The Quorum disk resource must be between 20–100 megabytes in size and an entire physical disk or logical volume if using a hardware raid controller, not just a partition. This is a SANergy restriction.

Prior to starting the MSCS setup, format and label the Quorum volume and all shared SAN volumes as you will select the Quorum volume during the Cluster Service installation. You will later need the volume serial numbers to create the new MSCS Resource called a SANergy Volume, so for each volume run dir in a command prompt window and record the volume label and serial number.

Setting up MSCS ( MSCS is already installed on 2003 )
Install the cluster service from Control Panel by selecting Add/Remove Programs or Add/Remove Windows Components if running Windows 2000 Advanced Server if not already installed.

The first cluster node wizard prompts you to select which disks are to be managed by the cluster.

Select all disk volumes EXCEPT for the QUORUM volume and move them from the managed column (right) to the unmanaged column (left).

WARNING: Be sure that the QUORUM volume remains in the MANAGED column as it’s the only volume that is controlled by the Cluster Service. The remaining disks are managed by SANergy and SANergy MSCS as SANergy volumes.

Install SANergy
New Install. Install SANergy on each node in the cluster as documented in Chapter 3 of the SANergy Administrator’s Guide. Use special names for assigning volumes to their MDCs. When defining the MSCS quorum disk, use the special name ?FREE for the MDC. When defining the volumes to be shared via SANergy, use the special name ?CLUS to denote they are not owned by any specific machine, but rather the cluster.

Previously installed. If SANergy is presently installed when setting up the first cluster node, make sure this node owns all SAN volumes and the Quorum volume. Use the Volume Ownership tab to do this. This allows the MDC or node full access to the volume labels and serial numbers which are needed during cluster setup and when creating SANergy volumes. Use the command line to get all needed serial numbers, Example: (X:\dir). Once you have all the volume serial numbers, write them down or save them in a text file. Another way to get the serial numbers and volume labels of the volumes is to run the sanergyfs /i command from a command prompt in the c:\program files\sanergy\sanergyfs directory.

NOTE: Be sure to REMOVE the hyphen when entering a volume serial number (serial numbers are not case sensitive). Once you have the volume serial numbers and the cluster service has started successfully on the first node, you may now install SANergy MSCS. The first cluster node installation only installs the drivers and exits.

Before starting installation on the second Cluster node, assign the Quorum and any SANergy MSCS volumes with special names for failover to work properly with SANergy. The Quorum volume ownership tab must be assigned ?FREE and all SANergy MSCS volumes must be assigned with ?CLUS. After completion, the Active Cluster Node has direct access to the Quorum and the soon to be created SANergy MSCS resource Volumes.

NOTE: Any other SAN volumes (not Clustered) simply remain assigned with the appropriate MDC name. These will function as normal SANergy volumes.

Bring the second Cluster node online. Install the MS Cluster Service and choose “second node”; The MS Cluster wizard prompts you to enter the NAME of the existing Cluster that is already online. If necessary you can try the name of the other node. Once the cluster is joined and both are online, you must install SANergy MSCS.

INSTALL SANERGY-MSCS SOFTWARE
The installer asks which system in the cluster you are currently installing. Ensure that you properly answer that question, because a different set of files gets installed for the last system installed in a cluster. The cluster server must be running prior to this step.
Note: Be sure to specify the same installation location on ALL machines in the cluster. That is, if you choose to install them on C:\program files\SANergy\SANergy MSCS\ on one machine, you must install to that location on the remaining systems. This is a restriction of MSCS.

Install the SANergy-MSCS layer on each system.
Note: Before installing on the last cluster node, bring up Cluster Administrator or the install may fail after login.

Install on the final cluster node. When installing on the final cluster node, select Final Cluster Node Setup.
Note: The Final Cluster Node system displays an additional installation window after the reboot and login window.

Click Install to complete the installation.

Click Exit.

Click Finish to restart the system.

Now the SANergy MSCS Resource is registered into the Cluster. When complete you should be able to run the Cluster Administrator and create the new SANergy Volume resource. If the SANergy Volume resource is not available it means that it is registered. To manually register the resource open a command prompt window and go to the c:\progarm files\sanergy\sanergy mscs directory and run smscsinstall i c:\progarm files\sanergy\sanergy mscs and click install. You may get a FTXW404 warning, just click OK and then Exit.

Note: You will now need your 8 character Volume Serial numbers, remember to drop the hyphen and also note they are NOT case sensitive.


Create SANergy Disk Resources

You told SANergy which disks to ignore, and let another program manage them; now you need to tell MSCS which disks SANergy will manage. It is possible that some of the disks that you want SANergy to manage are configured to be managed by MSCS. If so, delete those disk resources. Then, create new disk resources and select the SANergy Volume Resource as the manager.

Disks that you configure in this manner are special. The MDC for that disk will be whatever cluster member is currently in control of the disk (provided the ?CLUS SANergy owner tag is in place). If a cluster failover take place, this disk will be automatically mounted on the new member and will automatically become the SANergy MDC. That is, when the volume is brought online by cluster server (or interactively), then the volume will be mounted and available to that node (as a SANergy MDC volume).

All disk resources and share resources must be created under the Cluster Group in order for SANergy to work. When creating the SANergy volume resources, you must enter the serial number of the volume.

Note: Be sure to remove the hyphen from the serial number before entering.

Select Start->Programs->Administrative Tools->Cluster Administrator. The Cluster Administrator window appears.

From the Groups folder, open Cluster Group.

Right-mouse click on Cluster Group and select New/Resource. The New Resource window appears.

From the Name field, type the SANergy volume name.

(Optional) Type in a volume description.

From the Resource Type field, click on the down arrow key and select the SANergy volume.

Note: If the “SANergy Volume” type is not in the list you must do the following: In a command Prompt window go to the c:\Program Files\SANergy\SANergy MSCS directory and run smscsinstall i “c:\Program Files\SANergy\SANergy MSCS”. Then retry.

From the Group field, select Cluster Group.

Click Next. The Possible Owners window appears. Be sure all SANergy systems are in the possible owners field.

Click Next. The Dependencies window appears. Ignore this as there are no dependencies for SANergy volumes.

Click Next. The SANergy Volume Parameters window appears.

From the Volume Label field, type the volume name.

From the Serial Number field, type the volume serial number (excluding the hyphen).

Click Finish. The new volume appears in the Cluster Administrator window. The default value is offline.

Right-mouse click on Cluster Group and select Bring on-line.

Set up Sharing for this volume by creating CIFS disk shares or NFS exports.

Note: The disk share or NFS exports must be created within the Cluster Administrator as a cluster resource, not just from “my computer” for normal non-clustered disk shares. Also the disk share must be created for SANergy volumes before the SAN can fail over and fail back properly.

Repeat the above procedure for all remaining SANergy volumes.

You may test the Cluster fail over by right-clicking on the Cluster Group and selecting “Move Group”. All Cluster Resources should promptly move from node to node.

Solving Common Problems Setting up SANergy in MSCS and Zoned Environments
To prevent Microsoft Windows from allowing multiple machines to mount the same NTFS volume, SANergy by default will mark any unmarked volumes with the name of the machine that first mounts them.

This behavior is automatic.

Once a volume is marked with an owner, any machine that SANergy is installed on will not be allowed to mount the volume unless it is the owner of the volume.

Because of this, there are situations that you can get into when setting up SANergy in a complex clustered or zoned environment that will not make it easy for you to assign SANergy volume ownership in the proper way.

Below details some common problems and points out which methods will help you resolve them. Find the problem that matches your situation and follow the instructions.

Problems:
Problem 1: Cannot start Microsoft Cluster Service on any of the cluster nodes when SANergy is installed.

One cause of this could be that SANergy has marked the volume that is on the cluster's quorum disk with the name of a machine that is not part of the cluster. To determine which machine that SANergy thinks currently owns a volume can be difficult because on the cluster machines, clusdisk.sys may be preventing the SANergy Setup Tool from accessing the volume. Likewise, SANergy may be preventing the Microsoft Cluster Server from properly seeing the volume.

(Non-cluster nodes, if there are any) In this case, only the machines that are not cluster nodes may be able use the SANergy Setup Tool to assign ownership to any of the volumes. If you have this type of machine on your SAN, then you should be able to run the SANergy Setup Tool and assign the appropriate owner to the volume. If you cannot find a machine that can determine the volumes current owner, then it may be that the machine was renamed or that the SAN was re-zoned without removing SANergy ownership of the volume. It this is the case, follow the instructions in the "Disabling the SANergy driver responsible for protecting disks" in the Techniques section on one of the cluster nodes.

When you reboot, you should be able to bring the cluster node online and run the SANergy Setup Tool to see the current volume owner. You can then relinquish ownership by making the name of the volume owner blank, that is, change the volume owner and do not specify any name in the owner field.

Once the SANergy volume ownership is relinquished, you are free to make it whatever it should be for your cluster:

When you are done, make sure you follow the instructions in "Re-enabling the SANergy driver responsible for protecting disks" in the Techniques section, otherwise the node will not function as a SANergy client or MDC.

Problem 2: One of the Microsoft Cluster server nodes can be started, but the others cannot.

You can get into this situation by neglecting to change the ownership of the quorum resource to ?FREE. To fix this, go to the cluster node that can be started and run the SANergy Setup Tool. Then, assign the owner of the volume that is on the quorum disk to a value of ?FREE. You should now be able to start the cluster on all the cluster nodes.

Problem 3: The cluster starts up and the quorum disk comes online, but other Physical Disk resources do not come online on any of the cluster nodes while SANergy is installed.

This typically means that the volume on the Physical Disk resource is owned by a machine other than those that are members of the cluster. In order for SANergy to allow the cluster access to these volumes, the volumes that are managed by the Microsoft Physical Disk resource must be marked with the owner ?FREE. To do this, follow the instructions in the "Disabling the SANergy driver responsible for protecting disks" section.

When you reboot, you should be able to run the SANergy Setup Tool and see the current volume owner. You can now relinquish ownership by changing the name of the volume owner to blank, that is, change the volume owner and do not specify any name in the owner field.

Once SANergy volume ownership is relinquished, you are free to set its value to ?FREE.

When you are done, make sure you follow the instructions in "Re-enabling the SANergy driver responsible for protecting disks" otherwise the node will not function as a SANergy client or MDC.

Problem 4: You get the message "FTX375W and you are not allowed to remove xxxxxxx as an owner while that system is active."

The most desirable option for fixing this problem is to run the SANergy Setup Tool from machine xxxxxxx and remove the volume ownership from there. But this may not be possible because the machine xxxxxxx may no longer have access to these disks due to zoning or the operations of Microsoft Cluster server.

If you are certain that the machine mentioned in the message (xxxxxxx in this example) no longer has the volume mentioned, then you have a couple of options for getting around this:

1. You can shutdown the machine (xxxxxxx) and try to remove the owner again. If you are unable to shutdown the machine, then you can use the next option.

2. You can follow the instructions in "Fooling SANergy Setup Tool into thinking that the current machine is the current owner of the disk".

Problem 5: All the volumes on disks managed by Microsoft's Physical Disk resource are set to ?FREE, but you still cannot bring the cluster online

When a disk is marked ?FREE, SANergy will protect it only if it detects a free device manager. The free device manager is detected by attempting to open the device mentioned in the following registry key:

\HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\mcfs\Parameters\FreeDeviceManager.

The default for the key is \Device\ClusDisk0

Historically MSCS has used this device name, but if SANergy can no longer open it reliably or the name is changed, then it will prevent access to disk marked ?FREE.

SANergy assumes the role of protecting the disks marked ?FREE from access if it cannot detect that the device \Device\ClusDisk0 is present.

If you want to make sure that SANergy never prevents access to disk marked ?FREE, then make this value an empty string.

Techniques:
1. Disabling the SANergy driver responsible for protecting disks.
cd %WINDIR%\system32\drivers
move mcfs.sys mcfs.sys.backup
Reboot...

2. Re-enabling the SANergy driver responsible for protecting disks.
Start a command prompt (Start -> Programs -> Accessories -> Command Prompt)
cd %WINDIR%\system32\drivers
move mcfs.sys.backup mcfs.sys
Reboot...

3. Fooling SANergy Setup Tool into thinking that the current machine is the current owner of the disk.
Do this only when you know for certain that the machine that’s used to own the disk no longer has the disks mounted.
Start a command prompt (Start -> Programs -> Accessories -> Command Prompt)
cd "C:\program files\sanergy\sanergyfs"
set _CLUSTER_NETWORK_NAME_=currentowner
(to verify that this setting is working, execute the hostname command and the currentowner will be printed on the console).
sanergyconfig

Now when the SANergy Setup Tool calls GetComputerName, windows will return the value that _CLUSTER_NETWORK_NAME_ is set to. This means that SANergy Setup Tool will allow you to remove ownership of the volume by setting its name to blank. (i.e. entering no text in the space where the owner will be entered). Normally, it would not allow this unless you are the current owner of the volume.
After relinquishing ownership you can then set the ownership to be the name of the current machine; ?CLUS ; or ?FREE depending on how you need your cluster set up.

4. Running chkdsk safely on a SANergy managed volume.
a. Shut down the clients that have access to the disk
b. Stop SANergy on the MDC that owns the disk, rename the SANergy driver ( see number 1 above), and reboot the system
c. Run 'chkdsk' on the disk
d. Rename the SANergy driver back, reboot ( see number 2 above)
e. Restart the clients, mount the disk, etc.


For additional information and instructions on using the SANergy Setup Tool, refer to the SANergy Adminsitrator’s Guide.


-----------------------------------
Unix Updates

FixPack Installation
To install this FixPack on Unix systems, be sure that your system presently has a Tivoli SANergy version of 2.2 or higher. Do the following:
1. Close all fused windows.
2. Open a new terminal window.
3. Install the FixPack software.

Solaris Shared Memory update prior to SANergy Installation
Before installing SANergy, ensure that your maximum shared memory is set to a minimum of 12 MB. To change it, do the following:
Open the file /etc/system.
Add and save this line: set shmsys:shminfo_shmmax=0xE00000
Restart the computer: reboot

General Updates
Linux and Mozilla version 1.6 SANergy now supports Mozilla to display the GUI. To manually update the config script, do the following:
1. Open the sanergy config script.
2. Add the lines below before the ‘else’ statement.

then
/opt/NSCPcom/netscape "/tmp/SANergyConfig.html&panel=checkLicense" &
elif [ -f /usr/local/mozilla/mozilla ]
then
/usr/local/mozilla/mozilla "/tmp/SANergyConfig.html&panel=checkLicense" &

APAR Fixes
APARS FIXED IN THIS PTF (Build 3.3.6.0 – FixPack 6)
SANergyFSF (Special K)

APARS FIXED IN THIS PTF (Build 3.3.5.0 – FixPack 5)
SANergyFSF (Special K)
IC55721 Added support for block sizes other then 512.
IC55690 SANergy PIO command is not available for AIX 5.3 and above.

APARS FIXED IN THIS PTF (Build 3.3.4.0 – FixPack 4)
SANergyFSF (Special K)
IC54751 SANergy Unix MDCs unable to convert Korean characters.
IC55621 AIX invalid file pointer not to raw lun caused crash

SANergy
IC54116 SANergy does not properly work with the tar command.
IC54115 Same as Defect 902 below

APARS FIXED IN THIS PTF (Build 3.3.3.0 – FixPack 3)
SANergyFSF (Special K)
IC53790 Linux 64 bit offset not handled correctly when running in 32 bit mode.

APARS FIXED IN THIS PTF (Build 3.3.2.0 – FixPack 2)
SANergyFSF (Special K)
IC52629 I/O ERROR -61 on Unix hosts when using small files and SANergy cache

APARS FIXED IN THIS PTF (Build 3.3.1.0 – FixPack 1)

APARS FIXED IN THIS PTF (Build 3.3.0.0 - Release)
SANergy
IC51058 SANergy prevents direct I/O on non fused qfs mounts.

APARS FIXED IN THIS PTF (Build 3.2.13.0 – FixPack 13)
SANergy
IC49958 Solaris dtksh shell crashes under user mode SANergy.

APARS FIXED IN THIS PTF (Build 3.2.12.0 – FixPack 12)
SANergy
IC49008 SANergy user mode not finding the full path correctly.
SANergyFSF (Special K)
IC49301 SANergy copy of offline files causing IO errors.

APARS FIXED IN THIS PTF (Build 3.2.11.0 – FixPack 11)
IC48481 (Special K) Data corruption when using small buffers with large payload.

APARS FIXED IN THIS PTF (Build 3.2.10.0 – FixPack 10)
IC47747 (Special K) SANergy AIX panis when the volume definition is too large.
APARS FIXED IN THIS PTF (Build 3.2.9.0 – FixPack 9)
IC46679 (Special K) When using SANergy NFS mount should be mounted with the following options
–o actimeo=0 acregmin=0 acregmax=0 on some systems –o noac can be used.
IC46914 (Special K) AIX System hangs during multiple cp or mv commands.
IC46915 (Special K) Solaris 10. During a copy on a fused mount point, SANergy may cause a kernel panic.

APARS FIXED IN THIS PTF (Build 3.2.8.0 – FixPack 8)
IC45943 (Special K) SANergy panics when using named pipes on an NFS mount.
IC46200 (Special K) SANergy can hang when importing SANergyconfig.txt at startup.
IC46442 (SANergy) SANergy Linux mdc incorrectly sets the allocation size of file larger then 4GB.

APARS FIXED IN THIS PTF (Build 3.2.7.0 – FixPack 7)
IC45565 (SANergy) - When running SANergy 3.2.5.4 and QFS 4.2.2, bouncing the MDC sanergyd causes write() to fail with EIO. Subsequent write attempts to the open file descriptor will now fail, rather than sent via NFS.
IC44063 (Special K, AIX) – Fixed the SANergy MDC so that it writes to the correct area on the disk when AIX moves a file.
IC45305 (Special K) - You can now remove a file from a sanergy nfs mounted filesystem.
IC44690 (Special K) - The SANergy debug messages no longer fill the /var/adm/messages file.
IC44866 (Special K) – Fixed the unfuse filesystem data overrun.
IC44482 (Special K) – Fixed the attempt to fuse multiple mount points fails.
IC45033 (SANergy) – Fixed the simultaneous OPEN() causes failures.

APARS FIXED IN THIS PTF (Build 3.2.6.0 – FixPack 6)
IC43579 (Special K, AIX) - Fixed the owner command core dump during installation.
IC43779 (SANergy) – Fixed the SANergy race condition with simultaneous open caused file limit to be reached.
IC43780 (SANergy) – Fixed the multi-thread write defect allowing SANergy to now read the file back correctly.
IC43781 (SANergy) – Fixed the uninitialized memory read errors in sanergyd.
IC43346 (SANergy) – Fixed the shell script hang with SANergy preload set.
IC43427 (SANergy) – Fixed the file size defect when writing a file.

APARS FIXED IN THIS PTF (Build 3.2.5.3 – FixPack 5)
IC43346 - Fixed the SANergy preload set so that the shell script doesn’t hang on the SAN.
IC43427 – Fixed the file size result when SANergy is fused for writing.

APARS closed in Build 3.2.4.0 – FixPack 4
IC41199 - Fuse of volumes takes a long time. (AIX, Special-K software)
IC41186 - Unpredictable results when Fortran compiled to a SANergy managed disk. (AIX, Special-K software)
IC41205 - Cannot fuse with non-root users due to compress and gzip problems . (SGI, SANergy software)

APARS closed in Build 3.2.3.0 – FixPack 3
IC39008 - Exclude function causes SANergy to fail (Special-K software).
IC39026 - Using the unfuse command may result in a system call error (Special-K software).
IC38141 - Accessing a null pointer may cause core dump.
IC38857 - Added an NFS Mounting option (Mount –noac) to the SANergy Special K Instructions.

APARS closed in Build 3.2.2.0 – FixPack 2
IC35811 - Read behind write function causes performance degradation in a SANergy environment with QFS.
IC35854 - FOPEN failures may occur when opening files on a fused volume.
IC35855 - LSTAT call may hang when accessing fused volume.
IC36039 - In SANergy environment FPRINTF interprets "%" as format conversion specifiers.
IC37253 - SANergy device owner list display
IC35231 - SANergy PMserver set libpath libc.a
IC35706 - SGI applications that call fscanf may result in a core dump.
IC36244 - onfail option added to SANergy.

APAR’s closed in Build 3.2.1.0 – FixPack 1
None.

BUG Fixes
Bug Fixes – Build 3.3.6.0
923 Solaris amd64
924 Solaris amd64 part 2
927 Port user mode to AIX.
928 Updated error messages for going over LAN vs Erroring.
929 Fixed AIX striping algorithm on the client side.

Special K FSF
925 Solaris x86_64 / amd64 port.
926 Suse Sles 10 SP1 and SP2 port
929 Fixed AIX striping algorithm on the client side.
930 Can not set the owner on Linux MDCs
931 Linux update
932 Suse 9 32 Bit build issues.
933 Linux 2.6 depicated raw devices. Uses O_DIRECT on block device
934 Suse 9 MDC data corruption / sparse file issue.
935 Added support for NFS mounts that includes an extra "/"
936 Linux Redhat release 5.1 and 5.2 support updates
937 Update to "exclude" command in SANergyconfig tool.

Bug Fixes – Build 3.3.5.0

Added support for 64 Bit linux client only

Special K FSF
Inode hash list utility can cause a crash
Shortened the Linux Kernel version installation file name
Added correct mmap locking around user mmap calls from kernel
32 Bit Linux Port

Bug Fixes – Build 3.3.4.0

Special K FSF
914 Added method to AIX rc.sanergy to enable/disable GPFS support.
915 nFixed hyper exclusion list.
916 AIX mdc not reporting a corrupted lun correctly.
917 Update for header file changes in AIX 6.1

Bug Fixes – Build 3.3.3.0

Special K FSF
Solaris 10 UFS MDC added.
Unicode problem with Unix MDC
Updates for AIX 5.4/6.1
Redhat 2.6 kernel 32 bit Liunx updates.
Suse build error.


Bug Fixes – Build 3.3.2.0

Special K FSF
900 Looping forever when EOF is reached during read.
904 Updated make process for Linux 2.6.x

SANergy
901 Build issues for RedHat AS 3 2.4.21.47ELsmp
902 Sanergy not respecting BASEDIR during Solaris Liveupdate
903 Hang in close during failover.
906 Older 2.4 Linux / gcc does not except the -m32 flag

Bug Fixes – Build 3.3.1.0

Special K FSF
884 Solaris 10 support added for all MDCs.
885 Support QFS file holes during fused reads of a growing non-fused file.
887 Added robust logging to linux raw device creation section for debugging.
888 Memory overrun detection added
889 Added Power PC to the list of systems for Linux mdc.
890 Solaris 10 not able to fuse non-solaris partitions.
891 Make the logging value get set correctly within SANergyconfig.
892 SuSE 10 ppc64 and RedHat 4 update 4 x86_64 bit ports
893 HPUX crashing on exit from SANergy
894 Linux 2.6 32 Bit issues
895 Changed AIX loader to only allow the kernel module to load once

SANergy
886 Solaris 10 user mode sanergy mackerel update for customer


Bug Fixes – Build 3.3.0.0
880 Added ITLM to all of SANergy.

Special K FSF
878 Added support for Suse 9, Added HSM delay timeout parameter.

Bug Fixes – Build 3.2.13.0
- none -

Bug Fixes – Build 3.2.12.0
Special K FSF
864 Renamed the installation package for aix 5.x to 5L.
865 Change HP raw device open parameters to include O_NDELAY.
866 Double free when fuse fails panics AIX.
867 Solaris daemon startup
868 MDC: Put in a check for a valid library before calling get volume information.
869 Moved SANergy start to the end of the inittab on AIX.
870 Added check on HP so sanergy will only touch fused mount points.

SANergy
873 Sanergy returning IO errors during HSM delay. May be due to SAMFS change.
874 Fixed messages dealing with shared memory and increased the default value for # of volumes.

Bug Fixes – Build 3.2.11.0
Special K FSF
855 Clenauup of SP -1 return codes.
856 Hyper export not the correct syntax during SANergyconfig export
858 Solaris not truncating files properly during ftruncate/truncate commands.
859 Added test for truncate to perf.
SANergy
- none -

Bug Fixes – Build 3.2.10.0
Special K FSF
Customer reports offline files lock the system during retrieval.
Hyper values not exporting correctly
Set up AIX to use non-sanmem memory.
Stop the UFS mdc from getting volume information for a QFS volume.
854 Display error if aix mdc is asked about an unknown fs type.

SANergy
Stop the UFS mdc from getting volume information for a QFS volume.

Bug Fixes – Build 3.2.9.0
Special K FSF
835 AIX datagram size must be less then 64k.
836 Check the SMBPATH env var before searching for the smb.conf file.
837 Removed an optimization for reading up against the end of a file in fsf_directio_prim. An error -61 is
generate when the code tries to read passed the map extents for a file.
838 Duplicate of IC46915
839 Append not starting at the end of file on AIX
840 Fix SYSTEM file creation on AIX in the /usr/SANergy directory.
841 Stripeio not checking for thread creation errors. AIX 5.3
842 Configuration problems.
843 Close holes for unfusing while files are in proccess.
844 Customers complain of vstats crashes.
845 Sun message cleanup.

SANergy
846 SANergyconfig "sanmem|off" causes sanmap to fail.
847 Release cleanup.

Bug Fixes – Build 3.2.8.0
Special K FSF
814 "unfuse" on AIX does not de-reference the raw devices.
815 Minor configuration changes.
816 Solaris 10 NFS 4 support added.
817 More Solaris 10 updates. VFS hook.
818 Solaris FSF panics when using named pipes.
820 SANergy AIX fsf hangs when failing over to LAN.
823 Cleanup -1 errors being returned to applications from kernel mode.
825 Hyper not displaying properly in vstats.
826 AIX not handling hard linked file properly on close.
828 AIX log time does not match local time.
827 In setsize messages for lease updates the write lease value is always used.
829 Linux mdc does not report the correct allocation size for files.
830 AIX log permissions set so "Other" can write but not read.
831 Set Sun log level in sanergyfs when global logging is set.
834 Solaris device names truncated during initialization when using Qlogic HBA’s.

SANergy
811 Added a maxUnalignedXfer parameter to sanergy to handle large io cases that end up with very large canonical maps. This relates to error -7 being returned from blockio.
821 Added support for handling "//" and "//...." in the full name builder.
824 sanergyd needs to start after the import of sanergyconfig.txt in the init startup scripts.

Bug Fixes – Build 3.2.7.0
Special K FSF
(AIX) Fixed the SANergy MDC crash when the volume description is too large.
(AIX) Fixed the extra prints in AIX.
(AIX) You can now fuse multiple NFS mount points simultaneously.
(AIX) Fortran Open - Write - Close sequence results in file corruption. Turns out a truncate is being called by the exe before the first write. Fixed truncate to not allow fused files to go over NFS.
Fixed the clean-up when running perf.
Fixed the print version to the log at the startup of the daemon.
(MDC All platforms) Removed extra logging statements.

SANergy
Fixed lease default time during setsize call inside of the write call.
Fixed onfail error condition that could cause IO to LAN during error setting.
libSANergy is now compiled position-independent.
Fixed sanlog panic kill to just kill the process that it is in.
Fixed the race condition on attaching to shared memory segment.

Bug Fixes – Build 3.2.6.0
Special K – (AIX) Fixed the install so that SANergy doesn’t chmod everything 777 including /usr.
Special K – (AIX) Fixed the client I/O call, it now returns the correct number of bytes.
SANergy – Fixed the clean-up of remaining reference to non-mt calls.

Bug Fixes – Build 3.2.5.3
Special K FSF
(AIX) Fixed "fuse -> unfuse -> sanergy stop" issue.
Added Lun blocking for all devices listed in a specified text file. Controlled by the SANergyconfig "blockluns" command.
Added Lun blocking to FSF for hp-ux, solaris, and aix. If devices.txt is present and "SANergyconfig blockluns on" is set, then all luns listed in devices.txt will be blocked.
The Solaris Makefile now updates to use a common sol_sanmem.c
Fixed compiling errors for Solaris platforms.
AIX SANergy fsf crashes if:
1. fuse a nfs volume (hook)
2. Unfuse
3. /etc/rc.sanergy stop
Fixed the AIX client i/o call so that it returns correct number of bytes.
Fixed the AIX install so that it doesn’t chmod everything 777 including /usr.

SANergy
Fixed the memory errors/SEGVs in SANergy.

Bug Fixes – FixPack 5
Reports of Segv Faults in DGRAM. User mode SANergy was not using the proper reentrant gethostbyname.

Changed to use getipnodebyname.

Bug Fixes – FixPack 4
The MAX_STRIPES size is now increased from 96 to 512. This allows SANergy to handle up to 512 LUNs in the volume definition. Side effect is a rise in the amount of shared memory needed by SANergy. Shared memory max for systems must be set to at least 12MB.

Allow fbuf to change on the fly per file. The memory manager that SANergy uses is now configurable.
"sanmem|off" uses the systems malloc.
"sanmem|on" uses SANergy's memory manager (default).

Added configuration for how the raw device file descriptors are tracked.
"rawopenid|on" SANergy opens the raw devices for every thread in a process.
"rawopenid|off" SANergy only opens the raw devices once per process (default).

Configuration for deferred open of raw devices.
"deferfd|on" SANergy opens the raw device during the first IO to a file. (default)
"deferfd|off" SANergy opens the raw device during the open of a file.

Under stress, the mdc may fail to send a map during a "getRealMap" call during a write operation which causes a core dump. SANergy now includes proper error checking for this condition.

Corrected handling of multiple retries when ONFAIL is set to ERR. Originally SANergy would unfuse the file, which resulted in no more IO for that file. SANergy now respects the retries from the app and returns the errno from the IO that SANergy is attempting. Added a "-l" parameter to sanergyd. The value is passed directly to the backlog parameter of the listen command in the fd server. (default is 512) (see man -s 3XNET listen on Solaris). This takes care of ECONNREFUSED on the client side during multiple opens.
Reports of SIGHUP killing sanergyd on Solaris systems. Added nohup to init startup of sanergyd.
Fixed problems with compress and gzip.

Bug Fixes – FixPack 3
Special K - Fixed a cache problem on Linux.
Special K - Increased MAXSTRIPES on AIX.

Bug Fixes – FixPack 2
Removed the threadcreate in fifoserver.c. This is now single threaded.
Added delayed retries for volume cookie mismatch errors in getInitalMap call. When an MDC / NFS server fails over, it can take a number of seconds for the new machine to fail over.
Fixed use of env var SANFOLLOW for creating files.
sanergyd now opens and creates the log file for users. The log file will always be set at 0600.
Fixed sun ssd driver issues in sanergyd. The raw device name could be truncated by sanergyd when a non-root user attempts to open it.
The permissions on SANergy files now match the request.
Added command "SECURELOG" to SANergyconfig.
SECURELOG|ON or SECURELOG|OFF (default)
ON - The log in the SANergy directory will always have permissions 0600
OFF - permissions 0644
If ONFAIL|ERR set Open will return an EIO (errno 5) on getInitialMap failures to the application. Prior to this it would always failover to nfs.
Enhanced the duplicate message handler on the mdc side to handle heavy loads.
Added env var MAX_TRACKED_MESSAGES to allow the duplicate message cache to be increased. The default value is 100. The size of each message could be 64K. To manipulate the value, set the env var and restart sanergyd.
Added a signal handler to sanergyd for sigpipe, which fixed sanergyd die issues.
Fixed POSIX compliance issues with write, pread and pwrite.
Fixed a problem in the SANergy mmap that was found when using the file command on large files.
AIX - added llseek to the SANergy lib.
Added the command, "MAXRAWIO" to SANergyconfig.
SGI has a default value of 4MB for a raw IO request and for SUN it is 32MB.
SGI - Two parameters that set the raw IO max size include; systune maxdmasz and sysconf PAGESIZE
max raw IO = (maxdmasz -1)*PAGESIZE
One page is reserved for the kernel.
Added env var for the socket name used in SANergy's client / sanergyd communication. To change the name set SANERGYFIFO to the complete path that you want: "/tmp/sanergy.fifo") and restart sanergyd. All the clients will also need to run with the env var set, so that non-root access to the raw devices will be available.


Known Issues
AIX 5.3
The pio command is not support on AIX 5.3 and above.

Linux 2.6 MDC
Important Notes:
The Linux volume must be EXT3 type.
The Linux partition must NOT start on cylinder 0 of the LUN.

Method to create SANergy friendly volumes on Linux.
Select the LUN that is to be used as a SANergy volume on the MDC ( Ex: /dev/sdb )
Using sfdisk setup the volumes similar to below:

venus:~ # sfdisk /dev/sdb
Checking that no-one is using this disk right now ...
OK

Disk /dev/sdb: 8683 cylinders, 64 heads, 32 sectors/track
Old situation:
Units = cylinders of 1048576 bytes, blocks of 1024 bytes, counting from 0

Device Boot Start End #cyls #blocks Id System
/dev/sdb1 0+ 0 1- 1023+ 83 Linux
/dev/sdb2 1 8682 8682 8890368 83 Linux
/dev/sdb3 0 - 0 0 0 Empty
/dev/sdb4 0 - 0 0 0 Empty
Input in the following format; absent fields get a default value.
<start> <size> <type [E,S,L,X,hex]> <bootable [-,*]> <c,h,s> <c,h,s>
Usually you only need to specify <start> and <size> (and perhaps <type>).

/dev/sdb1 :0 1
/dev/sdb1 0+ 0 1- 1023+ 83 Linux
/dev/sdb2 :1
/dev/sdb2 1 8682 8682 8890368 83 Linux
/dev/sdb3 :
/dev/sdb3 0 - 0 0 0 Empty
/dev/sdb4 :
/dev/sdb4 0 - 0 0 0 Empty
New situation:
Units = cylinders of 1048576 bytes, blocks of 1024 bytes, counting from 0

Notice that the first partition on the LUN extends from cylinder 0 to 1. This LUN can not be used as a volume on the MDC or any other machine on the SAN.

The next step is to make the EXT3 volume on the other partitions.

venus:~ # mke2fs -j /dev/sdb2
mke2fs 1.38 (30-Jun-2005)
Filesystem label=
OS type: Linux
Block size=4096 (log=2)
Fragment size=4096 (log=2)
1111936 inodes, 2222592 blocks
111129 blocks (5.00%) reserved for the super user
First data block=0
68 block groups
32768 blocks per group, 32768 fragments per group
16352 inodes per group
Superblock backups stored on blocks:
32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632

Writing inode tables: done
Creating journal (32768 blocks): done
Writing superblocks and filesystem accounting information: done

Other interesting points:
Beginning with Linux kernel 2.6 raw devices that coincide with mounted EXT volumes can not be created and therefore accessed by the machine they are mounted on. The consequences of having no raw device for the LUN are the MDC can not use the self fuse test and can not use the owner command to set the ownership tag on the LUN.

Solaris 10
SANergy presently does not support the UFS MDC on Solaris 10.

Solaris EFI Labels SANergy UFS MDC does not support EFI type partition labels. EFI can be used with SANergy QFS/SAMFS MDCs. Solaris SANergy clients can not “fuse” to SANergy MDCs using EFI labels. All other Unix and Windows SANergy clients can “fuse” to EFI partition labels. If the SANergy Solaris UFS MDC is to be used the partition type must be SMI and the size must be less then 1TB.

Linux Device Ownership panel You cannot assign owners to devices using the GUI device ownership panel in user mode SANergy, you must use the SANergy command Line tool. To assign device owners from the command line, type: owner|device|systemname|
To remove a device owner, put a - in the systemname or tag field.

Linux install/uninstall problem (intermittent) Intermittently, the system may freeze during the install or uninstall process. The uninstalled freeze is due to running the uninstaller from an nfs mount point.

Drag and Drop Copy The drag-and-drop file copy command using a GUI File Manager may not be accelerated on some Unix platforms.

sh (Bourne Shell) You can now define the environment variable SANPWD to be 1. This allows SANergy to use the system call getcwd() to determine the working directory. Some old applications (such as diff) intermittently may have difficulty if getcwd() is called by file system routines.
Mounting on the MDC The filesystem mount point of the shared NFS volume on the MDC must be a unique path. It is possible to use the same mount point for 2 different filesystem types, SANergy may not find the correct filesystem to get information from and will return an invalid filesystem error.

Mounting NFS on the SANergy client (Also see Mount the NFS Volumes ) The SANergy client must include the leading “/” in the share name of the NFS mount command. The following mount options must be used to ensure the NFS filesystems is kept up to date –o actimeo=0 acregmin=0 acregmax=0 or on some operating systems –o noac can be used.
Ex: mount –o noac hostname:/sharename

AIX 5L: SANergy does not handle several large maps. We have discovered that on some AIX systems, the default IP/UDP parameters are not set large enough for SANergy. The following two lines must be added to the /etc/rc.net file or the root /.profile file.

no -o udp_recvspace=65536
no -o udp_sendspace=65536

Systems Disk view vary (Hetero SANs) It is possible that not all SAN members will have the same information about the size of various storage elements. Tests show cases where NT sees a disk at 9 GB, but a Solaris host sees a disk as 8.44 GB. The space above 8.44 will be inaccessible to the Solaris host and results in read and write errors. There is no real control over how a file system chooses blocks. Any time there is a discrepancy between sizes, it is possible for data to be stored in inaccessible regions. We recommend that you verify that all computers have the same view of the storage. On Solaris, use the format command to determine what Solaris displays as the size of the disk (do not format or label this volume). If there is a size difference, partition the storage element so that the partition is entirely visible by all members. Check the SANergy log file for errors any time the system behaves in a strange manner.

Log Files (Operating System and Tivoli SANergy) Check the operating system and Tivoli SANergy log files continuously, especially if you experience errors or the system behaves in a strange manner.

Accessing Raw Disks You must have root privileges to access the raw disks.

UNIX MDCs and Samba You might need to run the Samba server with "oplock=no" in your smb.conf file. This is analogous to NFS users mounting with the "-o acregmin=0..." options specified in this manual. Samba can cache certain information on file attributes (such as size) that can sometimes confuse applications that simultaneously open the same file from different machines through SANergy. The need to set this or other Samba options depends on the access patterns of customer applications.

Managing Devices The Device Panel might not be protecting applications from accessing the raw disk. You should be careful when running various system maintenance tools. You do not want to manipulate storage elements that are being managed by another SANergy MDC system. That is, do not relabel, format, or run newfs on any disk from a system that is not the proper MDC.

SDD on AIX If you are using SDD, you must ensure that you create a /usr/SANergy/devices.txt file. This file shows the correct devices listed as /dev/rvpath*.

National Language Version Operating Systems
AIX 5.1 / Japanese OS / Netscape Character Settings Netscape does not display the SANergy graphical user interface properly. In order to start the SANergy graphical setup tool in Japanese environment (this will launch Netscape), you must specify the following Language Environment:
AIX 5.1 Locale (Ja_JP)
MOZILLA_NLSHELPPATH=/usr/lpp/X11/lib/X11/Ja_JP/communicator
MOZILLA_NLSPATH=/usr/lpp/X11/lib/X11/Ja_JP/communicator
XENVIRONMENT=/usr/lpp/X11/lib/X11/Ja_JP/communicator/Netscape

AIX 5.1 Locale (ja_JP)
MOZILLA_NLSHELPPATH=/usr/lpp/X11/lib/X11/ja_JP/communicator
MOZILLA_NLSPATH=/usr/lpp/X11/lib/X11/ja_JP/communicator
XENVIRONMENT=/usr/lpp/X11/lib/X11/ja_JP/communicator/Netscape

If you continue to have problems with the display of SANergy, we recommend that you use the SANergyconfig program. This program is the command line interface that lets you control SANergy.

-----------------------------------
Tivoli Sanergy, Special-K Software (AIX, SuSE, Solaris, and HP-UX Systems)

Overview of the SANergy Special-K (SANergyFSF) Software
Special-K is SANergy’s new architecture on some UNIX systems. The overall product concept and the wire protocol are identical letting you mix new and/or old versions of SANergy on the same SAN.

The Special-K software has moved most of the SANergy logic into a kernel driver. From a user perspective, this indicates:
No more LD_PRELOAD (or LIBPATH on AIX)
No more application sensitivity to the SANergy implementation of libc
Higher transparency to applications
Redirection and shell applications work well.

-----------------------------------
Using The SANergy Special-K Software

UNIX Installation and Configuration

Note: Refer to the SANergy Administrator’s Guide and README file located on your SANergy CD for detailed instructions on how to configure your systems before you install.

You might have to configure several computers to share storage in your SAN. Configure one computer at a time and build up the workgroup.

Most UNIX systems can be host computers in a SANergy network. AIX, Solaris, and Linux systems can be MDCs as well as hosts. All UNIX computers must have a direct SAN connection (for example, Fibre Channel) and they might need Windows-to-UNIX LAN networking technology, such as network file system (NFS). If you are using a Windows system on your SAN, use NFS.

To configure UNIX systems to work with SANergy, perform the following steps:
Set up and configure the MDC computers (Windows, Solaris, AIX, or Linux). See Windows MDC Setup procedure or UNIX MDC Setup procedure located in the SANergy Administrator’s Guide.
Install and configure your UNIX-to-Windows LAN software and hardware, or both, if necessary.
Install your SAN hardware and drivers on the UNIX system.
Set up partition and volume configuration. The MDC must be able to see the actual disk systems. Remember the following points:
Set up the proper volume type for the MDC OS you are going to use.
Create your volumes after the 2^nd Disk Block (Linux only).
Mount the NFS volumes. Ensure that the NFS volumes mount properly and without errors. Test the mounts for user access. If the NFS volumes do not mount properly, see your NFS documentation or your product manufacturer.
Install and configure SANergy on the UNIX system.


Device Ownership
Device ownership is only required if you are using Windows systems on your SAN. This is due to Windows performs automatic disk operations that can be destructive to non-Windows systems. MDC ownership is not necessary for Unix systems, this is due to SANergy does not force the volume to only be mounted by the registered MDC.

Note: The owner of a device is the only computer that should change the configuration of the drives.


UNIX to Windows Networking (LAN connection)
On the Windows MDCs, install the NFS server software and configure it for use by the UNIX computers. This procedure can vary. See the documentation with your networking product. You also need a physical networking connection (for example, Ethernet) between the Windows and the UNIX computer, although some Fibre Channel (FC) implementations support conventional networking such as Internet Protocol (IP) over FC.

Experiment with the networking connection to verify that it works properly. Performance will be that of a regular LAN network until SANergy is enabled. Continue only if you are sure of the NFS connectivity from the UNIX computer to the MDC. Check for read and write permissions. You must create NFS shares that match the names of the CIFS shares; otherwise they will not fuse. In addition, the UNIX MDC must start Samba from an accelerated window in order to have fused access to the volumes.


SAN Connection
Install an FC adapter and the associated drivers, wiring, and hubs. SANergy does not offer any acceleration unless it can correctly access the SAN elements. Be aware of the information that is provided by the SAN adapter manufacturer.

Once you install the adapter and verify that the UNIX computer can access the storage elements reliably, install SANergy. Run a disk exerciser that verifies performance and the integrity of the data.

Mount the NFS Volumes
SANergy works with networking products such as NFS. It accelerates network transactions by intercepting and reissuing them over the faster storage area network when possible. SANergy must be aware of the association of a network mount point and the equivalent hard mount point of the storage elements. Refer to your NFS documentation for the specifics on how to mount network volumes successfully. Verify that the NFS volumes mount properly and without errors. Test the volume mounts for correct user access. If the NFS volumes do not mount properly, see your NFS documentation or product manufacturer.

Use one of the following options for NFS mounting:

Mount -o acregmin=0,acregmax=0,actimeo=0,noac host:/share_name/mount_point /local_mount_point

Notes:
In Services for UNIX 2, if the share name is one letter, you need the slash (/) in the path. If more than one letter, do not use the / after host:
The share name and volume share names must be the same.

Installing SANergy Special-K
Mount the NFS volumes, and install the SANergy software. See your NFS and networking documentation for information on how to mount network volumes.

Note: If you are upgrading your SANergy software, the installer will uninstall before it runs the Special-K install script.

Installing SANergy Special-K
To install SANergy, perform the following steps:
Copy the .tar file to a directory.
From a UNIX shell, change to that directory.
From the directory mount point, enter:
tar xvf <filename.tar>
From the same directory mount point, enter:
./install
After installation completes, a devices.txt file can be created in the SANergy directory.
(see the “SANergy devices.txt” section below.)
NFS mount the volumes that you want to fuse.
Change directory to:
/opt/SANergy/SANergyconfig (Solaris, HP-UX, Linux) -or-
/usr/SANergy/SANergyconfig (other UNIX’s)
The Enter Command: prompt appears.
Fuse the NFS mount points, by typing: fuse local mount point
The nfs_mount_point parameter is the local mount point that was specified when you issued the NFS mount command.
Optional. Repeat Step 9 to fuse additional volumes.
Acceleration is now available on the NFS mount points that go to a SANergy MDC volume.
Be aware of any output generated by the fuse command. If it fails, acceleration does not occur.

SANergy devices.txt
The devices.txt file lists the devices SANergy will access, which can make fusing much faster and limits SANergy to just the devices that it needs to touch. The devices.txt is not required for any of the supported platforms.
The file is located in the SANergy install directory:
/opt/SANeryg for HPUX and Solaris
/usr/SANergy for all other UNIX’s
2. The devices paths must be the complete full path from the root directory followed by a return.
Typical examples of devices:
HPUX: /dev/rdsk/c22t0d0
AIX: /dev/rhdisk4
Solaris: /dev/rdsk/c1t2d0s2

UNIX MDC Setup Procedure
You might have to configure a variety of computers to share storage in your SAN. Configure one computer at a time and build up the workgroup.

Configure the MDC computers first. Do one at a time. You can set up a single MDC for all volumes, or you can spread the MDC task among several computers. If security and access control are important, configure the necessary parameters on that computer.

Presently, you can mix MDC types on a given SAN. However, on a per-disk basis, the entire disk must be one file system format or the other (either Windows or UNIX).

If you are going to include Windows computers as hosts with your UNIX MDCs, install Samba, a CIFS package, on your MDCs to create shares.

UNIX MDCs (Solaris, Linux and AIX) and Samba. It is possible that you need to run the Samba server with
oplock = no in its smb.conf file. This is the same as NFS users mounting with the -o acregmin=0... options. Samba can cache certain information regarding file attributes (such as size) that can sometimes confuse applications that simultaneously open the same file from different machines via SANergy. Setting this or other Samba options depends on the access patterns of your applications and usually is not needed.

To configure an Solaris, AIX, or Linux systems as an MDC:
Create the file systems on the shared storage. Partition and format your storage elements. Refer to your UNIX documentation for information on how to format disks.
For AIX MDCs only: Prior to mounting the volume, run the following commands to set the volume group (which is the name of volume you just created):
varyoffvg (SAN volume group name)
varyonvg -u (SAN volume group name)
Install the SANergy software. See procedure for Installing SANergy Special-K in this document.

QFS Volumes
If QFS is installed after SANergy, restart the SANergy demon. If the SANergy demon is not restarted, the system might attempt to use the UFS drivers to fuse to the QFS volumes. Install SANergy after QFS, create the following link , and restart the SANergy demon:
For 3.x: ln -s/opt/LSCsamfs/lib/libsamsanergy.so /opt/SANergy/lib/libsamsanergy.so
For 4.x: ln -s/opt/SUNWsamfs/lib/libsamsanergy.so /opt/SANergy/lib/libsamsanergy.so

Using the SANergyconfig Program
The SANergyconfig program is a command-line interface that lets you control SANergy Special-K.

Important: The settings do not persist. If you reboot your computer, you will have to reset your settings. To save these settings, you can use the “export” command to create a sanergyconfig.txt file, add the commands to the sanergyconfig.txt file manually OR create a file and boot-time script to redirect the file contents into the sanergyconfig program.

When you start the SANergyconfig program, you can use the “help” command to displays the current supported commands and syntax. If you enter a SANergy command without a parameter value, the current settings display. The following table defines the SANergy commands in alphabetical order. The commands are not case sensitive and if parameter values are available for a command, a space or a vertical bar can be used to separate the command from the parameter.

Values entered for byte range type parameters can be entered as the byte value or with a one character non case sensitive size suffix. The available size suffixes are b for bytes, k for kilobytes m for megabytes and g for gigabytes.
Example: SANergyconfig hyper on 100m 1g
The example sets hyper extend to be on, hyper1 to 100 megabytes and hyper2 to 1 gigabyte.

Table 5. SANergy Commands

>>-cache|-+-rw--+-|linesize|numlinesperfile|totalcachesize---------------><
'-off-'

Options

rw|off
Sets the cache for read write (rw), or turns the cache off (off).
linesize
Specifies the size of each cache line. The number of lines in dictated by the total size of the cache.
numlinesperfile
This is ignored for now, but a number must be entered to change the cache settings.
totalcachesize
Specifies the maximum amount of system memory that is consumed for caching.


clear
This command clears the fused read or fused write statistics.
Syntax

>>-clear---------------><

exclude
This command excludes from fusing a list of files with specific extensions.

Each list is a comma-separated, lower-case list of file extensions that are to be excluded from the action.

Special characters for the exclude command are:

- Indicates exclude nothing (an empty list).
* Indicates exclude everything. The “*” character must be in quote.
+ Indicates that a list is not be changed during the exclude command.

Examples:
1. exclude Will list the current list settings.
2. exclude - - “*” - Exclude nothing from acceleration, nothing from hyper extension, caching for all files and include no files for caching.
3. exclude .mov,.txt + + + Exclude from acceleration .mov and .txt files and leave the other lists the same.

Note: There must always be an entry for all list locations during the exclude command.

Syntax

>>-exclude|exclusion_list|hyperexcl|cacheexcl|forceinclude|---------------><

Options

Exclusion_list
Specifies which files to exclude from acceleration. This list prevents SANergy from accelerating any file with the specified extension.
Hyperexcl
Specifies which files to exclude from hyperextension. This list prevents SANergy from hyper-extending any file with the specified extension.
cacheexcl
Specifies which files to exclude from caching.
forceinclude
Forces those files to be cached even if the application opened them with no-caching specified. Not all OS's have this capability.
exit
This command exits the SANergyconfig program.
Syntax

>>-exit---------------><

export
This command exports the current SANergyconfig settings to SANergyconfig.txt. SANergyconfig.txt is located in the install directory of SANergy. See also import.
Syntax

>>-export------------><
fuse
Accelerates a SANergy-managed volume.
Note: You must be a root user to fuse volumes.
Syntax

>>-fuse-local_mount_point---------------><
or
fuse| (with no parameters displays a list of fused volumes)

Options

local_mount_point
Specifies the local mount point of the volume for accelerated access.

Example

This example connects the volume mounted at /nfs1.
fuse /nfs1


help
This command displays the SANergy help menu.
Syntax

>>-help---------------><


hsmdelay
On an HSM system, if the client tries to read/write data in a file that is not yet resident, it will delay X milliseconds and retry until the maximum retries are reach. Use HSMDELAY to set the value of X and the maximum retries.
Syntax

>>-hsmdelay-delay--retries-------------><

Options

delay
Specifies the delay value in milliseconds.
hyper
This command sets the hyper-extension values.
Syntax

>>-hyper|-+-on--+|hyper1|hyper2---------------><
'-off-'

Options

on|off
Sets the hyper-extension value to on or off.
Hyper1
The first time a file needs to grow, this amount of space will be asked for from the MDC to hold the initial part of the new data. Once this is exhausted, the next time space is needed SANergy will ask for the amount specified by the hyper2 value. Typically hyper1 should be 64k and hyper2 should be 10M or 100M.
Hyper2
Is the same as Hyper1 except that this value is used from the second hyper request and any subsequent ones for the file.

Example

This example turns hyper-extension on and sets hyper1 to 64k and hyper2 to 100M.
hyper on 64k 100m

import
This command imports configuration settings from the SANergyconfig.txt. SANergyconfig.txt is located in the install directory of SANergy. See also export.
Syntax

>>-import------------><

lan

This command sets the host-to-MDC LAN communication parameters. Use this command on the host machines.

Syntax

>>-lan|timeout|retries|port----------------><

Options

timeout
Specifies the timeout in seconds. The default is 10 seconds.
retries
Specifies the number of retries. The default is 5 retries.
port
Specifies the TCP communication port for SANergy to use. You must use the default value only.

Example

This example sets the host-to- MDC LAN communication parameters to 20 seconds and 10 retries.
comm 20 10

lease
This command sets the block-lease period. Files that are opened for read-only access need only a few seconds to completely access a file. If the time expires, then they solicit for a new lease. Increasing this value to a large number will mean fewer renewal requests for large files, but the addition of a "disconnect" request during file close (which is skipped if the remaining lease is only a few seconds). The special setting of -1 (read lease only) disables read-leases entirely, which can be useful for some streaming applications. A zero for either value triggers the system to use the default value of five seconds for read operations, and one hour for write operations.
Syntax

>>-lease-read_time-write_time---------------><

Options

Read_ time
Specifies the number in milliseconds for read operations.
write_time
Specifies the number in milliseconds for write operations.

Example

This example specifies a read time of 5000 milliseconds (5 seconds) and write lease to 3600000 milliseconds (1 hour).
lease 5000 3600000

log
This command displays and sets the logging level. This is used for internal and support purposes.
Syntax

>>-log-log_level---------------><

Options

Log log_level
Specifies the logging level. Turn logging on only when you encounter problems.
0 - Disables logging.
2 - Default setting for logging errors.
1-11 - Sets varying levels of logging.

Log file locations are:
HP-UX systems: /var/adm/syslog/syslog.log
AIX systems: /usr/SANergy/mclog0
Linux systems: /var/log/messages
Solaris system: /var/adm/messages

maps
This command displays and sets the map cache parameters.
Syntax

>>-maps-time-number_of_maps---------------><

Options

time
Specifies the time to map the cache. This time is in seconds. The default is 30 seconds.
number_of_maps
Specifies the number of maps. The default is 100 maps.

maxunalignedxfer
Any unaligned data greater than this size (in bytes) is broken down into chunks of this size and then processed.

Syntax

>>-maxunalignedxfer----------------><

Options

bytes
Specifies the size that you want to break the I/O up into.

min
This command sets the internal values for the minimum file size to fuse.
Syntax

>>-min-read_size-write_size-getmaponopen-accum-byte---------------><

Options

read_size
Specifies the minimum file size to fuse for read access. A zero value indicates to fuse all read files.
write_size
Specifies the minimum file size to fuse for write access. Do not set this value larger than a cache-line size.
getmaponopen
Specifies whether or not to get the map on open. 0=disabled, 1=enabled
accum-byte
This is a different method of controlling whether a file fuses for reads. Rather than keying off of the files static size, SANergy will instead allow up to this amount of bytes to go over the LAN before it starts accelerating. Some applications have large files on disk but might only read a very small portion and the overhead of SANergy getting a disk map is too high for such files.

mmap
This command defines how SANergy will handle mmap calls.
Syntax

>>-mmap-lan---------------><
‘-fail-’
‘-bail-’

Options

lan
When an mmap call is encountered pass the call directly over the lan.
fail
Return a failure for the mmap call. Most applications will call read or write if mmap fails.
bail
Close all references to the file on a mmap call and send the call over the lan. SANergy will not “fuse” this file again until the next open call.

neof
If a eof (end of file) is encountered during a read of a file SANergy will retry a map request after the number of eofs indicated. If the file is being read in a read behind write situation then this will allow the writer time to catch up while the reader waits.
Syntax

>>-neof -[Number of retries]-------------><
onfail
Set this to LAN if you want the fused I/O that fails to go over the LAN, set it to RETRY if you want to keep retrying the failed I/O or set it to ERROR if you want the your application to handle the I/O failure. This determines how SANergy handles a physical or communication error.
Syntax

>>-onfail-[lan, error or retry]---------------><

Options

lan
SANergy will put the transaction over the LAN and return whatever the LAN has for a status code.
error
SANergy will report back I/O Error to the application.
retry
SANergy will retry the I/O.

owner
Assigns or releases volume ownership and assigns a tag name to a device.
Also, lists all UNIX MDCs and the devices they own.

Syntax

>>-owner device-system_name -tag ----------------><
Options

device
Specifies the device to assign or release ownership, or tag.
system_name
Assigns device ownership to the specified system_name.
tag
Specifies the label to assign to the device.
no value
Release device ownership.

Example

This command displays a list of all the devices and owner information.
owner

Example

This command assigns the system Sol-01 as the owner of the device c1t0d0 and labels the device as UFS.
owner c1t0d0 Sol-01 UFS
This command assigns the system aix-03 as the owner of the device rhdisk4 and labels the device as JFS2.
owner rhdisk4 aix-01 JFS2
This command clears the owner assignment on device rhdisk4.
owner rhdisk4 - -
Note: To release ownership of a device, you must either run the command from the system that owns the device, or the system that owns the device must be offline.

pio
Settings for parallel I/O by SANergy to raw devices.
Syntax

>>-pio [on / off] [Number of threads]-----------------><

Options

mode
Set parallel I/O on or off.
Number of threads
The maximum number of threads used per I/O. The default is 10 and the maximum value is 256. This number is dependent on the size of the stripe group that the client is fusing to and amount of I/O that is taking place concurrently. The threads are kernel level and there is usually an upper limit imposed by the OS.

Note: The pio command is not support on AIX 5.3 and above.

quit
Exits the program.

Syntax

>>-quit-----------------><

renew
When a lease is about to expire this is the time value when the client begins to ask for a renewal. If the client has a 30000 ms lease and the renew is set to 10000 ms, when there is 10000 ms left on the lease the client will start asking for a renewal.
Syntax

>>-renew [value in ms]-------------><

sanmem
This command should only be used for diagnostic and support personnel purposes because it activates more aggressive memory checks and statistics that can adversely affect your system performance.
Syntax

>>-sanmem|-+-walk |----------------><
|+-stats |
|+-check |
Options

walk
Checks the heap for any errors.
Stats
Displays status|allocated memory|free memory
Check
Turns on/off runtime memory error checking. 0 turns it off. 1-4 turns on checking, 1 being least checks and 4 being most checks. Be advised that this can and probably will slow performance of the software.


stats
Displays the fused write and read statistics, cached write and read statistics, and unfused write and read statistics.
Syntax

>>-stats----------------><
Note: Stats will display fused writes statistics (first number) and fused reads statistics (second number).

syncio
Synchronize all IO through SANergy. (Default off)
Syntax

>>-syncio [on / off] -----------------><

Options

mode
Set synchronized IO on or off.
Number of threads
All IO through SANergy fsf will be synchronize / serialized for all processes.

tacitclose
If a client is about to close a file and the client’s lease on a file is within the desired milliseconds of expiring, the client will not send a close to the MDC in order to minimize LAN traffic. Use TACITCLOSE to set the value of time in milliseconds
Syntax

>>-tacitclose-time----------------><

Options

time
The desired amount of time in milliseconds
unfuse
Removes accelerated access from a SANergy managed volume.
Syntax

>>-unfuse-volume_mount_point-----------------><

Options

volume_mount_point
Specifies the volume mount point to remove accelerated access from.

Example

This example unfuses the volume at mount point /nfs1.
unfuse /nfs1
updatesize
Prior to each I/O the time since the last size update is checked. If the time since the last update has expired then a setsize command is sent to the MDC to keep the file systems file size up to date.
Syntax

>>-updatesize-time-----------------><
Options

time
The update size timeout in milliseconds.

version
Displays the SANergy Special-K version number.
Syntax

>>-version-----------------><
vstats
Displays detailed statistics and current SANergy settings.
Syntax

>>-vstats-----------------><
Example:
--- Verbose Statistics --
Fused: Read: 10485760 Write:10485760
Cache: Read: 0 Write:0 Benefited:0 FilesInUse:0 MemInUse:112
TimesSequential: 0 Not:0 TimesPunted:0
Unfused: Read: 0 Write:0
Maps: InCache:0 Hits:0
Memory: InUse:1056624 Free:0
LAN: Nmsgs:5 NcommErrs:0 NmisMatch:0 Noverflow:0
?? Sent:0 Received Resp:0
GetVolume Sent:1 Received Resp:1
InitialMap Sent:2 Received Resp:2
ExtendedMap Sent:0 Received Resp:0
SetSize Sent:0 Received Resp:0
Close Sent:2 Received Resp:2
Dump Sent:0 Received Resp:0
Number of files processed (GetInitialMaps): 2
Number of files processed with ZERO I/O 0
Times IO stalled 0 DMA stalled:0
UsrIO: 1m:20
fsfIO: 1m:20
PhysIO: 32k:6 64k:4 512k:4 1m:16
realIO:
dmaIO:
Average bytes processed per file: 10485760
Processing Density ( r+w / filesizebytes ) 20971520 / 20971520
------------- Settings -------------
Hyper1:104857600 2:104857600 ReadLease:3600000 Write:3600000
TacitClose:0 Renew:10000 UpdateSize:5000 Neofs:2
Log:2 File: HSMdelay:10000 HSMRetries:360 zfill:1
Min read:0 write:0 accum:0
LAN: timeout:15 retries:20 port:5501
Maps: GetOnOpen:1 MaxCache:0 Time:30000
IOQ: 30 ndma:16
Cache: Mode:RW LineSize:1048576 LinesPer:3 MaxMemory:10485760
OnFailure:RETRY mmap:BAIL MaxUnaligned:2097152 MultiPath:OFF
Exclude: Fuse: Hyper: Cache: ForceInclude:
parallelio: pio:ON pioThreads:10

zfill
Set to 1 so that new regions of file will be zero filled for security. Set to 0 to turn off zero filling.
Syntax

>>-zfill-[1 or 0]-----------------><
Options

1 Enables or 0 Disables zero filling.

Running SANergyconfig
You can run SANergyconfig as a text line application, or you can pass a script file into it. The following procedures describe both ways to use SANergyconfig.

SANergyconfig allows you to use script files. To use it, do one of the following:
Pass SANergyconfig a script file. This is the recommended method.
Use single commands (text line application) as command line arguments.

Passing SANergy a script file
To pass SANergy a script file, use the following steps:
Edit the SANergyconfig.txt script file for your environment to include the shared volumes that you want to fuse. To edit the script, enter the following command:
vi SANergyconfig.txt
Or open the file in a text editor.
The SANergyconfig.txt window appears. A sample FUSE command could be:
FUSE /nfs1
(Other FUSE commands for other shared volumes you want to fuse)
EXIT| (end every script file with the EXIT command)
The /nfs1 is the local mount point of a NFS volume.
Save and exit the SANergyconfig.txt script file.
Do one of the following:
For Solaris and HP-UX, type: ./opt/SANergy/SANergyconfig < SANergyconfig.txt
For AIX, type: ./usr/SANergy/SANergyconfig < SANergyconfig.txt

Using single commands
To enter a single command, perform the following steps:
Do one of the following:
For Solaris and HP-UX, type: opt/SANergy/SANergyconfig
For AIX, type: usr/SANergy/SANergyconfig
The Enter Command: prompt appears.
Type: fuse /nfs_mount_point
The nfs_mount_point parameter is the local mount point that you specified when you issued the NFS mount command.

Be aware of any output generated by the fuse command. If it fails, acceleration does not occur.

Log files
The SANergy driver writes important information to a log file that varies by platform as follows:
HP-UX systems: /var/adm/syslog/syslog.log
AIX systems: /usr/SANergy/mclog0
Solaris systems: /var/adm/messages
Linux systems: /var/log/messages

Check this file for any accumulating messages. You also can turn on the tracing information using the SANergyconfig program that writes to this file. Use this to determine how well your programs are running in the SANergy environment.

Running the built-in performance tester
Ensure that you run the command line version of the performance tester from a SANergy fused window. To run the built-in performance tester, perform the following steps:
Do one of the following:
For HP-UX and Solaris, enter the following:
cd /opt/SANergy
For all other UNIX, enter the following:
cd /usr/SANergy

Enter: ./perf or ./perf [filename to fuse] [size of record in KB] [size of file in MB]
The following help appears:

Command line usage: perf -o [r,w,wr,a] -b [] -s [] -l [] -v [] -d filename
-h Print this help message and exit
-o File mode: (Default "wr"
r - read (O_RDONLY)
w - write (O_WRONLY | O_CREAT | O_TRUNC)
wr - write then read.
a - append (O_WRONLY | O_APPEND)
-b Record size to read or write (size[k,m,g]). (Default 1m)
-s Total IO to perform (size[k,m,g]). (Default 100m)
-l Number of loops. (Default none). (-1 loop infinitely)
-d Do direct IO (0 or 1). (Default 1)
-a Do aligned IO (0 or 1). (Default 1)
-v Validate character ('-' for ramp). (Default none)
EX: perf -o wr -b 1m -s 100m -d /nfs/test
Press Enter to continue interactive setup or "q" to exit.

3. The intention of perf is to run it directly from the command line.

Example 1:
perf –o w –b 1m –s 100m –l 10 /nfs/test
Write /nfs/test 10 times in a loop with a size of 100Mb using a 1Mb buffer.

Example 2:
perf –o wr –b 1m –s 100m –l 10 –v t /nfs/test
Write and read /nfs/test in a loop and use a t as a verification character.

Limitations:
mmap()” - Not yet supported in SANergy fsf.

Uninstalling SANergy on all UNIX Computers
Note: Uninstall SANergy only if you are disconnected from the SAN network. This assures that there is no risk of data loss that is ordinarily protected by SANergy. Before uninstalling, ensure that you are not in the SANergy directory.

To uninstall SANergy on UNIX computers, perform the following steps:

Bring up the UNIX shell and log in as the superuser. Enter:
su root
Password: <root_password>
Remove all references to SANergy from the .profile and .login files, if you edited them.
Do one of the following:
From a non nfs directory run
For HP-UX, Linux and Solaris, enter the following:
/opt/SANergy/uninstall

For all other UNIX, enter the following:
/usr/SANergy/uninstall

Note: Solaris and AIX support the native installation tools also.