Advertisement
Miscellaneous
1. The total number of NAS shares is limited to 10000.
2. UID range for local user is from 1001 to 100000.
3. UID range for local group is from 1001 to 100000.
4. NDMP backup is not supported in this release.
5. NT Backup is not supported for iSCSI tape.
6. Seen only one time: Unidentified network conditions caused a hard kernel panic
requiring the iTX device to be rebooted manually. This has been identified as coming
from the IP stack of the Linux kernel itself, and is not otherwise caused by the iTX
hardware or software. (Bug 7082)
7. For NAS SAR pair creation, on remote side ( Passive Box ) volumes should NOT be
present. Based on the remote side volume name input, SAR pair creation will create
the remote side volumes and NAS SAR pair also. If volumes present, return "Volume
already exists" error code.
Snapshot
1. To disable the snapshot schedule for a volume, set its time interval to 0.
2. Apple Share access for a NAS Read Only Snapshot is not supported (using AFP) and
will not work. Alternative is to use CIFS access from MAC Clients.
3. If a writeable snapshot is activated as Read-only, then it will not accept any write
IO. In order to perform write on writeable snapshot, it has to be activated as Read-
Write, i.e. with the –w switch.
4. As a best practice measure, it is recommended that 20% of container capacity be
reserved (left free) for snapshots.
5. Folder permissions (ACL) cannot be set for NAS Read only snapshots.
6. With replication pairs, the secondary/remote volume still requires manual
configuration for SAN scheduled snapshots. If not configured, the snapshots will get
taken on the primary volume's schedule, but the maximum set for the number of
snapshots for the volume will be the default of 254.
Volume
1. Containers can be created only with a 64KB chunk size. The RAID Stripe size should
also be of 64KB minimum.
2. If the container runs out of space and any volumes which have not been pre-allocated
space (Thin-Provisioned volumes) require additional space, you might get an out of
space error when new writes happen to the volume. Note that the writes will fail
ONLY if new territory needs to be allocated. If space (territory) has already been
allocated, the writes will not fail.
Solution: Configure alerts (email or snmp) and when thus notified, add new storage
capacity to the container by expanding it before it runs out of space.
3. Event entries are not supported for SAN volumes since iTX does not host the file
system. However, capacity events for containers associated with the SAN volumes do
get logged.
iTX Open Bugs:
5524 – Sev3 - Shares of volumes/containers that have been deleted do not get
automatically deleted sometimes.
5865 – Sev3 - LTP test suite returns some failures.
6521 – Sev3 - cli commands performance degradation with iometer running.
6524 – Sev3 - If you repeatedly add/remove non-existent isns servers, the isns service
gets stopped.
6600 – Sev3 - Need warning message when user wants to rollback to snapshot of a volume
that is in a rep pair.
6601 – Sev3 - SAR: if you expand the Active volume, the Passive volume continues to
Advertisement
