Correction To The Availability Of Flexclone Files And Flexclone Luns In Vfiler Contexts; Capacity Information For 3-Tb Disks; Use Flexshare With Hdds Only; Incorrect Cross-Reference To Maximum Volume Size Information - IBM N Series Manual

Correction to the availability of FlexClone files and FlexClone LUNs in
vfiler contexts
The topic "How MultiStore works with FlexClone files and FlexClone LUNs"
incorrectly states that FlexClone files and LUN commands are available in
default and non-default vfiler contexts.
The corrected information is as follows: MultiStore supports FlexClone files
and FlexClone LUNs only in vfiler0 context. You cannot run FlexClone file
and LUN commands in any other vfiler context.

Capacity information for 3-TB disks

The topic titled "Available disk capacity by disk size" does not include
information for 3-TB SATA disks.
The 3-TB SATA disks have a right-sized capacity of 2,538 GB (where GB =
1,000*1,024*1,024), and 5,198,943,744 available blocks (sectors). They are used
in SAS storage expansion units.

Use FlexShare with HDDs only

Use FlexShare with storage systems that have hard disk drives (HDDs) only.
FlexShare is not designed for use with storage systems that have solid-state
drives (SSDs). Enabling FlexShare on a storage system that has SSDs can
result in decreased throughput to SSD-based volumes.

Incorrect cross-reference to maximum volume size information

The cross-reference in the section "Deduplication and volume SnapMirror"
incorrectly references the section "Maximum volume size with deduplication."

Maximum volume size for deduplication

Starting in Data ONTAP 8.0.1 and in later releases, you can enable and run
deduplication on volumes with a maximum size of up to 16 TB for all
supported platforms. This information is missing in Data ONTAP 8.0 7-Mode
Storage Management Guide.

Maximum number of mirrored aggregates per system

You should not create more than 64 mirrored aggregates per storage system.
Data ONTAP does not prevent you from exceeding this limit, but doing so
could cause plex synchronization problems after some types of failures.

ACP example output shows incorrect IP addresses

The IP addresses shown in the example showing the output of the storage
show acp command shows ACP configured to use public IP addresses. This is
incorrect; you should use private IP addresses when configuring ACP.
The example should read as follows:
Example
Changes to published documentation
129