User documentation

Available user documentation:

Release Notes 2.2.8

  • Release Date: May-23-2016 

Availability of hot upgrade

  • From 2.2.x to 2.2.8
  • From 2.0.x to 2.2.8

Availability of host software products

See the Host Software section on this website.

INFINIDAT Software Compatibility

See the software compatibility section on this website.

What's New in this release (2.2.8)

Improved granularity of NAS performance counters

This release includes an overhaul of the performance counter infrastructure, starting with NAS (SAN to follow), adding a wider performance monitoring functionality:

  • Filesystem and pool-level on top of the already existing system-level
  • Improved Add Graph workflow
  • New graph types (top and histograms) allowing better analysis and troubleshooting

Secured LDAP communication

This release introduces support for LDAP over SSL (LDAPS) for communication with Active directory. Supported TLS versions: 1.1, 1.2.

Local user locking

The system admin can prohibit local users from accessing the InfiniBox system. A locked user cannot log into the system. The user is still listed in the system, and it can be unlocked. Locking all local users allows organizations to centrally manage their users and passwords through LDAP / Active Directory.

Support for HTTP -> HTTPS redirect 

Support for forcing HTTPS only management traffic, and redirecting HTTP requests to HTTPS. When this option is selected, HTTP initiated requests are redirected to HTTPS.

Login sessions 

The management API is enhanced with login sessions support, where cookies are used instead of user credentials on every request.

What's new in last major release (2.2) 

Introducing NAS filesystems

InfiniBox features support for filesystems in addition to the already existing support for volumes. Filesystems and volumes share the backend storage and can co-exist within the same storage pool. This release includes support for NFS protocol version 3 and a lot of the storage capabilities of volumes (e.g. Snapshots, clones, Flash Cache).   

Consistency groups

A consistency group is a group of volumes that maintain write-order fidelity.

The consistency group allows to take snapshots of all of its volumes at the same point-in-time, thus ensuring a consistent image of the volumes at that time. The consistency group is typically used when a single application spans multiple volumes and there is a need to create a point-in-time copy of these volumes. From the application perspective, point-in-time backups of the entire application are crucial for maintaining data integrity.

Encryption of data-at-rest

INFINIDAT utilizes encryption of data-at-rest for regulatory compliance, security audit readiness and other purposes.

Disk encryption-at-rest allows for data protection across all scenarios in which data that is stored in the disks is compromised due to disks removal from the site. With data encryption using Self-Encrypting Drives (SED) and the ability to securely erase a disk, the risk of data exposure is eliminated. 

The InfiniBox storage system can be set to run either with data-at-rest protection or without it. InfiniBox encryption-at-rest uses the standard method of encrypting data, so there is no performance penalty.
This feature is supported only on systems equipped with self-encrypting disks.


The Infinispares feature enables the InfiniBox system to keep running even in a situation where dozens of disks have failed across a long period of time. In such a situation, where all of the system spare disks space is consumed, an additional disk failure will cause the system to activate the InfiniSpares feature. 

When the feature is engaged, InfiniBox utilizes unused parts of the remaining drives as spares. At any given time, InfiniBox ensures that the system has an enough spare capacity to hold 2 additional disks failures.

Replication improvements


The RPO (Recovery Point Objective) is a user-defined maximum lag time between the source and target sites of the replica. This lag is measured as the time that has passed since the current image on the target existed on the source. The RPO state is either OK or Lagging.

Sync now

InfiniBox allows for an extra-curricular synchronization of a replica. The sync now task synchronizes a replicated dataset (volume, or a consistency group) on demand, regardless on the scheduled replica cycle.

Throughput reporting

Querying for the replica now reports on the current replica throughput.

Capacity counters

The capacity that is dedicated for replica staging area. This field is available on both source and target. On the target system it is called staging area size.

Replicating consistency groups

InfiniBox allows to replicate consistency group members while maintaining a consistent replica on the target system.

The consistency group is replicated as a whole. The replica is comprised of a source consistency group and a target consistency group. All of the consistency group's members are replicated, and the replica state of the consistency group abides all of its members.

Replicating to up to 16 systems

This release supports replicating to up to 16 InfiniBox systems (each volume goes to only one InfiniBox system).

Increased flash cache

This release supports up to 86TB of flash cache.

Increased number of snapshots and clones per dataset 

InfiniBox 2.2.x introduces an increase in the number of dataset descendants (snapshots and clones). The increase is as follows:

  • Volume family members: 1000
  • Filesystem family members: 250

Performance improvements (in comparison to 2.0.x release)

  • An increase to system maximum IOPS to 900K 
  • A 40% increase in system read from cache.
  • A 25% decrease in write latency
  • A 50% improvement in Rebuild 1 and Rebuild 2 times
  • Latency reduction for I/O of 512KB and above

Issues resolved in this release

The table lists issues along with their priority. The issue priority is indicated by column 'P' with icons as follows:

  •  Critical
  •  Major
  •  Minor
  •  Trivial

P Key fixed in version release notes title release notes description
Blocker INFINIBOX-22133 2.2.8 Potential node failure during drive scrubbing

The scrub process may fail the node in a rare scenario when encountering a drive error.

Critical INFINIBOX-21555 2.2.8 NAS service may fail when using very large files (Over 16TB)
Critical INFINIBOX-20795 2.2.8 Soft Targets creation at large scale fails

When creating the maximum number of soft targets on two switches at the same time, the operation may time-out and leave orphan soft targets that are not available in the fabric.
Workaround: configure one switch at a time, with at least a few seconds delay in between.

Critical INFINIBOX-20409 2.2.8 Sending a very large metadata set request may cause the management service to fail

A single metadata update request containing over 100 entities, may cause the management service to fail

Critical INFINIBOX-19354 2.2.8 When soft targets are in use and a FC link jitters, the FC port resets

Upon link up, the driver restarts. This leads to a temporary path unavailability.

Major INFINIBOX-20708 2.2.8 FC soft target path loss

Upon a migration of a soft target (virtual FC port) from one FC port to another, the new initiator connections may fail to see their LUNs. This error might occur after thousands of soft targets redistributions, following previous incorrect fabric zoning.

Major INFINIBOX-20885 2.2.8 Removing rate-limit from network space does not take effect

When a rate limit is set on a network space, removing the rate limit does not take effect.

Major INFINIBOX-20549 2.2.8 FC driver failure on soft targets redistribution

When redistributing soft targets (virtual FC target ports) due to node/port activation/deactivation, the FC driver may become unavailable, and respawn. This leads to a temporary loss of access to all of the soft targets that were assigned to the relevant FC port.

Major INFINIBOX-20384 2.2.8 Changing the role of a replicated dataset from source to target fails if the dataset is mapped

Workaround: unmap the dataset and retry to operation.

Major INFINIBOX-19984 2.2.8 NAS: File truncation may not reclaim space immediately

When a file system space is exhausted and it becomes "locked", truncating a file may not free up the space from the file system until the next file delete/truncate on the file system.

Major INFINIBOX-20048 2.2.8 Creating multiple replicas may impact the system performance during the initial sync

Once the initial sync is complete, the performance is no longer impacted.

Major INFINIBOX-19866 2.2.8 Remove restriction regarding upgrading of pre-2.2.0 systems that have replicas

Upgrading a pre-2.2.0 system that has replicas to code level 2.2.0 onward entailed deleting the replicas and recreating them. This limitation is now removed.

Major INFINIBOX-16746 2.2.8 LDAP users that log into InfiniBox with their primary group are successfully logged in, but have no InfiniBox role.

Workaround - Select from the following options:

  • Set another group as the primary group for the user (LDAP administrator)
  • Configure another group that is not the primary group (Storage administrator) and make the user a member of this group
Major INFINIBOX-20501 2.2.8 System may not poweroff nodes following system shutdown

A rare race condition may cause the management service to stall during shutdown and prevent poweroff of nodes

Minor INFINIBOX-20800 2.2.8 Performance improvement for large I/O

Latency reduction for I/O of 512KB and above

Critical INFINIBOX-21546 2.2.4 NAS service failure when using very large files

The NAS service may fail when a client reads a file which is larger than 16TB.

Critical INFINIBOX-21090 2.2.3 NAS service fails in case of a large configuration over UDP transport

When the NAS configuration is large enough to make the size of the output of 'showmount' larger than 64KB, and the client uses UDP as transport, the NAS service becomes non-responsive and requires a restart.

Critical INFINIBOX-21091 2.2.3 Volume clones allocate more physical space than actually used

On systems that were upgraded to version 2.2.x while having existing volume clones, those clones may occupy more physical space than what is actually used.

Critical INFINIBOX-20745 2.2.2 Management service fails upon an unsupported configuration request

A request to update an immutable field of Replication Link entity may cause a failure of the management service, leading to the unavailability of the system management API.

Critical INFINIBOX-20742 2.2.2 SAS cables mis-behaviour is detected as a drive error

Fixed a case in which a hardware test where SAS cables were disconnected resulted in a massive drive error that could lead to a system emergency shutdown.

Critical INFINIBOX-20721 2.2.2 Pool space accounting error

Following an upgrade of a system with snapshots from version 2.0.x to version 2.2.0/2.2.1, the subsequent deletion of snapshots causes an error in pool space allocation counters. This could lead to a premature locking of pools and volumes becoming write-protected.

Major INFINIBOX-20609 2.2.2 NFS - Root access permission issue

When the 'execute' permission is removed from a directory from all of {owner, group, others}, root user loses access to it.

Critical INFINIBOX-21003 2.2.11 Provisioning the replica defaults to 9000 MTU may lead to network issues in environments with a lower MTU

Setting a new MTU on a replication network space does not set the management IP MTU.

Major INFINIBOX-20533 2.2.1 A case of a total system unavailability is theoretically possible when performing a remote replication

There is a theoretical risk for a total system unavailability when replicating an idle volume and a process gets stuck on one of the nodes. The fix eliminates this risk.

Major INFINIBOX-20565 2.2.1 A replica manual synchronization stops the automatic synchronization schedule

When a replica is manually synchronized (using the replica 'sync now' command), the next sync job (scheduled by the replica sync interval) does not take place, thus the replica is no longer progressing.

Major INFINIBOX-20544 2.2.1 A NAS service failure occurs when there is no permission to the root of a filesystem

When a user removes the 'execute' permission bit on a root directory of an exported filesystem, the next time the NAS service comes up after shutdown/restart, it fails to activate.

Major INFINIBOX-20534 2.2.1 A sub-directory of an exported directory cannot be mounted

A sub-directory of an exported directory cannot be mounted by an NFS client. Only exported directories can be mounted.

Major INFINIBOX-18631 2.2.0 A change to the network space rate limit is not reflected on the replication it services

After setting rate limit on a network space, consequent modification to the rate limit do not take effect. (Removal of the limit and re-setting a limit is required.)

Major INFINIBOX-17303 2.2.0 Logging into InfiniBox takes too long in an environment that has over 100 Active Directory servers

When InfiniBox is configured with a large LDAP domain, logging in may take up to 2 minutes.

Major INFINIBOX-15383 2.2.0 The replica source system is not updated upon remote pool and volume name changes.

This issue does not affect the replication itself. It only affects the visibility of the pool and volume names on the UI.

Major INFINIBOX-16933 2.2.0 Upon a node failure, some of the services are shown as Active, while they are actually Degraded.
Major INFINIBOX-16817 2.2.0 A user with Pool Admin role cannot perform replication operations

A user with a Pool Admin role cannot perform operations that involve the remote system (such as replica operations).

Minor INFINIBOX-18727 2.2.0 The system does not allow SMTP user address that ends with '.trust'

The fix includes support for .trust and other new top-level-domains.

Minor INFINIBOX-18732 2.2.0 Email event notifications may have their content added as an attachment instead of part of the message body

On some SMTP servers, event notifications are sent with their content stripped out from the body of the email message and added as an attachment.

Minor INFINIBOX-17498 2.2.0 Resizing a pool generates incorrect events

When the change in capacity is lower than the granularity of capacity display, the event description does not show the change.

Minor INFINIBOX-18282 2.2.0 AIX ODM fails to distinguish controller device from disk

The fix adds "CTRL" in the INQUIRY vendor specific bytes of controller device (LUN 0).

Critical CLI-1762 InfiniShell 2.2.2 Redundant warnings in builtin CLI When using the builtin infinishell within the system's GUI, warning messages appear before the prompt shows up.
37 issues

Known issues for this release

The table lists issues along with their priority. The issue priority is indicated by column 'P' with icons as follows:

  •  Critical
  •  Major
  •  Minor
  •  Trivial

P Key release notes title release notes description
Critical INFINIBOX-20628 In a rare scenario following a redistribution of soft-targets, hosts may lose paths connected to soft-targets
Critical INFINIBOX-21003 Provisioning the replica defaults to 9000 MTU may lead to network issues in environments with a lower MTU

Setting a new MTU on a replication network space does not set the management IP MTU.

Critical INFINIBOX-21811 Node failure on CPU soft lockup

Due to a very rare kernel bug, one of the node's CPU may lock up, leading to a node failure.

Critical INFINIBOX-22178 Node unavailability due to a flapping drive

When an enclosure drive is reported missing, and it is rediscovered shortly after the initial handling of the failure, a core node may become unavailable.

Critical INFINIBOX-22229 During an emergency shutdown event, one node may not complete the shutdown process

On a system with maximal SSD cache configuration, in a rare scenario, a node may not successfully complete the emergency shutdown process.

Critical INFINIBOX-22489 In a very rare case, a node failure leads to temporary system unavailability

A node failure during replication may lead, in a very rare case, to system unavailability.

Major INFINIBOX-14604 Link down on the master node may fail the replica management link

When the replication link fails on the system's master node, the data connections failover to the other nodes. The management connection, however, does not failover and becomes unavailable until the link is up again. During this time, although the replication keeps working as usual, the replica state may not be reported correctly and replication provisioning operations cannot be performed.

Major INFINIBOX-16813 In scenarios with large SAN fabric or long initiator latency the system average latency counter may be inflated
Major INFINIBOX-20434 InfiniBox incorrectly reports the AIX hosts supported reservation types

Although SCSI reservations are supported on AIX hosts, InfiniBox LUNs reserve_policy is incorrectly reported as limited to 'no_reserve' value only.

Major INFINIBOX-21295 Network configuration changes may fail when executed while a node is inactive

Workaround: carry out the network configuration changes only when all nodes are active.

Major INFINIBOX-21968 Soft targets may not come up on system restart

When soft targets are deployed (using NPIV), in some conditions, restarting the system may not bring up the soft targets.
Work-around: Disable and re-enable one of the ports.

Major INFINIBOX-22412 Temporary unavailability of the management service following creation of metadata objects in total excessive size

Creating metadata objects in an accumulative size of above 512MB may lead to failure of the management service

12 issues

Events that have changed since release 2.2.0

Events that are new in this release 

(Events that belong to new features are not listed here)


Events that were changed in this release 

  • USER_CREATED level is now Warning.


Was this article helpful?
0 out of 0 found this helpful

0 out of 0 found this helpful