Memory leak issues in older DSS V6 builds
If you are using one of the old DSS V6 builds it is the best time to update the DSS V6 to the newest stable version.
In the DSS V6 builds earlier than b5217 we have discovered a memory leak issue which is commonly called "low space". This problem may lead to unexpected system freezes. If that situation appears, the only way to make the DSS V6 running again is to execute a hard reboot.
What's more in the really old builds like for example b4221 no errors are logged when the "low space" problem occurs. We've been working to solve the problem for quite a long time and in later builds (after b4221) some additional mechanism were introduced to log the issues and to try to avoid them. However the problem has finally been solved since DSS V6 build 5217.
Here is short DSS V6 builds history:
DSS_V6_up06_build_3535 26.07.2009
DSS_V6_up07_build_3537 31.08.2009
DSS_V6_up10_build_3719 18.11.2009
DSS_V6_up12_build_3836 08.12.2009
DSS_V6_up12_build_3927_ASR 18.12.2009
DSS_V6_up13_build_3902 09.12.2009
DSS_V6_up13_build_4023 18.01.2010
DSS_V6_up14_build_4221 02.04.2010
DSS_V6_up30_build_4362 19.04.2010
DSS_V6_up35_build_4452 17.05.2010
DSS_V6_up40_build_4550 11.06.2010
DSS_V6_up45_build_4622 27.07.2010
DSS_V6_up50_build_4786 12.01.2011
DSS_V6_up55_build_5087 12.01.2011
DSS_V6_up65_build_5217 20.05.2011 <- since that build the "low space" issue was fixed
DSS_V6_up75_build_5377 21.06.2011
DSS_V6_up80_build_5626 19.08.2011
DSS_V6_up85_build_5794 14.10.2011
DSS_V6_up90_build_5845 09.11.2011
As you can see even after we've fixed the problem a lot of new builds were released. Each build contains a lot of fixes and updates, new drivers and even some new functionality. All the changes that were added in each version can be found in the latest readme_xxxx file (e.g. readme_5845). There are lots of small fixes that are even not listed there. The latest builds has improved stability. That's why we strongly recommend to updated the older builds of DSS V6 to the newest DSS V6 build 5845.
During the DSS V6 update you won't lose any data. The new files are copied only to the bootable medium. The volume groups stay untouched. You can always boot your system to the old DSS V6 build because it remains an option in the boot menu. You also won't need to reconfigure your DSS V6 because all settings are stored on the system volume (which is located on your volume group).
If you are using DSSes configured in Failover it's important to update both of your nodes to the latest build.
1). Apply the small update to the Secondary system first using the software update functionality and reboot.
2). Once the Secondary is running again click on the start button in the Failover manager.
3). Now update the Primary system using the software update functionality and reboot.
4). Once the Primary is running go to the Secondary and click on the Sync volumes button in the Failover manager.
5). Then click on the Failback button in the Secondary system.
6). The Primary system goes back to the active mode and ready for another Failover.
For more detailed information about how to update the DSS V6 without disabling Failover see the release notes.
If you're using b4786 or older you will need to apply a small update 0756 before being able to upload the newest DSS V6.
Please download the mentioned small update from our FTP.
Small Update DSS V6 number: 0756
And apply it via the DSS webgui. Go to Maintenance -> software update and locate
the file using "System software update" frame.
Each time a small update is applied to your system, DSS V6 needs to be rebooted. After the reboot you can proceed with the system update.
There are two ways to update the DSS V6 to the newest version:
- you can use the “Update downloader”
- you can download the new release (iso) to your PC from our FTP server and User Portal and upload it to DSS through the webgui, choose Maintenance -> software update and in the “System software update” locate the ISO file on your PC and apply it. After it’s finished a reboot is needed.
