Installation guide

Acopia Networks, Inc.
show reports command. Clients experience degraded performance in these volumes until the upgrades are
completed.
After the upgrade, any directory with “~” in its name is accessible to NFS clients only. If your CIFS clients
require access to one or more of these directories, run sync files for each of them. The sync files utility
checks the volume’s back-end filers for any FGNs that collide with the directory name(s), and it clears the
NFS-only status if no collision is found.
For a Redundant Pair: Additional Reload after the Upgrade
In a redundant pair of ARXes, the above upgrade process only runs if both peers are running 2.5.0+ on
startup. This is a safeguard to protect a software rollback: if the automatic-upgrade process changed all of
the metadata to the 2.5.0+ format while the peer was running 2.4.3, a reversion to 2.4.3 would be
impossible. Additionally, there are other irreversible 2.5.0+ features that only activate when both peers are
running 2.5.x. Therefore, you must reboot the active peer after both peers are fully upgraded to 2.7.0. The
CLI Maintenance Guide describes the full software-upgrade procedure. This causes a brief service outage
while the processes fail over.
Problems Corrected
In This Release
• CIFS clients in a tree domain may be unable to authenticate to a VIP in another domain, even though
the parents of the two domains have a valid two-way trust relationship. (27887)
• If a file-placement rule receives an excessive number of inline notifications (i.e., notifications of client
changes), volume software may restart. (28770)
• If the same share name is used in multiple volumes, the nsck … report commands cannot always find
the desired share. (28769)
• A sync shares operation can cause multiple ARX reboots if applied to a disabled volume with enabled
shares. (29302)
• In rare cases, nsck … report inconsistencies fails to report some found directories (marked as “FD” in
the inconsistencies report) until after a client renames or deletes them. (28708)
• When a CIFS client copies large directories into an ARX volume, the copy operation occasionally
fails. (28735)
• In a presentation (or “direct”) volume with an attach point to a managed volume, NFS clients hang
when they attempt to create a hard link within the attached managed volume. (29106)
• In a presentation (or “direct”) volume with an attach point to a managed volume, some CIFS directory
listings get an incorrect directory path from the ARX volume. (29104)
• NFS3 UDP clients occasionally get incomplete directory listings from ls. (28668)
• If a directory in one CIFS share (for example, “longnameddirectory”) has an alternate ‘8.3’ name (e.g.,
“LONGNA~1”) that collides with a directory in another CIFS share (with an actual name of
“LONGNA~1”), the sync files command mistakenly assumes that all of the files in the first directory
8