HP StoreAll OS 6.5.1 Upgrade Guide

ibrix_cifsconfig -t -S "ignore_writethru=1"
The SMB signing feature specifies whether clients must support SMB signing to access SMB
shares. When ignore_writethru is enabled, StoreAll software ignores writethru buffering
to improve SMB write performance on some user applications that request it. See the HP
StoreAll OS User Guide for more information about this feature.
7. Mount file systems on Linux StoreAll clients.
8. (X9720 Storage platforms) If the cluster network is configured on bond1, the 6.1.5 release
requires that the Fusion Manager VIF (Agile_Cluster_VIF) also be on bond1. To check your
system, run the ibrix_nic -l and ibrix_fm -f commands. Verify that the TYPE for
bond1 is set to Cluster and that the IP_ADDRESS for both nodes matches the subnet or
network on which your management consoles are registered. For example:
[root@ib121-121 fmt]# ibrix_nic -l
HOST IFNAME TYPE STATE IP_ADDRESS MAC_ADDRESS
BACKUP_HOST BACKUP_IF ROUTE VLAN_TAG LINKMON
----------------------------- ------- ------- ---------------------- ------------- -----------------
----------- ---------- ----- -------- -------
ib121-121 bond1 Cluster Up, LinkUp 10.10.121.121 10:1f:74:35:a1:30
No
ib121-122 bond1 Cluster Up, LinkUp 10.10.121.122 10:1f:74:35:83:c8
No
ib121-121 [Active FM Nonedit] bond1:0 Cluster Up, LinkUp (Active FM) 10.10.121.220
No
[root@ib121-121 fmt]# ibrix_fm -f
NAME IP ADDRESS
--------- ----------
ib121-121 10.10.121.121
ib121-122 10.10.121.122
If there is a mismatch on your system, you will see errors when connecting to ports 1234 and
9009. To correct this condition, see “Moving the Fusion Manager VIF to bond1” (page 47).
9. Because of a change in the inode format, files used for snapshots must either be created on
StoreAll 6.0 or later, or the pre-6.0 file system containing the files must be upgraded for
snapshots. For more information about upgrading a file system, see “Upgrading pre–6.0 file
systems for software snapshots” (page 24).
Upgrading pre–6.0 file systems for software snapshots
To support software snapshots, the inode format was changed in the StoreAll 6.0 release. The
upgrade60.sh utility upgrades a file system created on a pre–6.0 release, enabling software
snapshots to be taken on the file system.
The utility can also determine the needed conversions without actually performing the upgrade.
IMPORTANT:
• The file system must be unmounted while the utility runs.
• Segments marked as BAD are not upgraded.
• The upgrade takes place in parallel across all nodes owning segments in the file system, with
at least one thread running on each node. For a system with multiple controllers, the utility
will run a thread for each controller if possible.
• Files up to 3.8 TB in size can be upgraded. To enable snapshots on larger files, they must be
migrated after the upgrade is complete (see “Migrating large files” (page 25)).
• In general, the upgrade takes approximately three hours per TB of data. The configuration of
the system can affect this number.
Running the utility
Typically, the utility is run as follows to upgrade a file system:
upgrade60.sh file system
For example, the following command performs a full upgrade on file system fs1:
24 Cascading upgrades