I currently have a 520 problem-child that occasionally reboots during the weekly dump. (we use scripts running from cron on the Solaris adminhost) At this time, we are running on release 5.2.2P1D4 and I've heard that Network Appliance is recommending that all customers migrate to 5.2.3 OS. Before I upgrade the filer (which will require a firmware upgrade and a disk promcode upgrade), I want to get some feedback from anyone running 5.2.3. (especially on a 520)
Linda Walton; UNIX System Administrator Reasoning, Inc.
Linda Walton wrote:
I currently have a 520 problem-child that occasionally reboots during the weekly dump. (we use scripts running from cron on the Solaris adminhost) At this time, we are running on release 5.2.2P1D4 and I've heard that Network Appliance is recommending that all customers migrate to 5.2.3 OS. Before I upgrade the filer (which will require a firmware upgrade and a disk promcode upgrade), I want to get some feedback from anyone running 5.2.3. (especially on a 520)
Linda Walton; UNIX System Administrator Reasoning, Inc.
Problems we've had with 5.2.3:
The nosnapdir option is turned to "off" for the duration of any NDMP session. The "df" output changed so that snap reserve is no longer reported unless nosnapdir is off. The "show_therm" command went away. (minor complaint since it is not supported). One system crashed twice in a month with a "cifs admin" core dump.
Other than the one system it's been very stable. We have it running on 15 systems, two of which are F520s.
All of these problems are fixed in 5.2.3D1. The "cifs admin" one is difficult to verify, but so far, so good.
Graham
-
Graham C. Knight -
Linda Walton