SVC + Storwize V7000 + Unified : 208 days reboot bug resolved with new firmware release (V6.3.0.2, V1.3.0.5)

A new firmware level has been released and corrects a serious bug :

  • Storwize V7000 and SVC : 6.3.0.2 (30 March 2012)
  • Storwize V7000 Unified : 1.3.0.5 (2 April 2012)

This strange bug due to a known Linux kernel issue  which result in a kernel panic (due to a internal counter overflow) after 208 days of uninterrupted time and reboot of both nodes was affecting SVC controller nodes, Storwize V7000,  and Storwize V7000 unified block node canisters.

This issue affects the following releases : 6.2.0.x (excepting V6.2.0.5), 6.3.0.x, 1.3.0.x (for unified)

For more information : http://www-01.ibm.com/support/docview.wss?uid=ssg1S1004038

Here is a part of the release note :

  APARs resolved in this release (6.3.0.2):

Critical Fixes

     There is a serious issue on 6.2.0.0 releases and higher that will result in node
     canisters rebooting after 208 days of continuous uptime since their last power cycle
     or software upgrade.  This issue is fixed in this release.  

Refer to the following flash for more information:

http://www.ibm.com/support/docview.wss?uid=ssg1S1004038

IC80846          Multiple node asserts due to receipt of a malformed SCSI request from
a backend storage controller
IC81273          All nodes assert simultaneously when a Global Mirror Change Volume is
created using the Volume ID of a Volume that had previously been a
FlashCopy target of a Volume in a remote copy relationship
IC81418          All nodes assert simultaneously when a migration of a Volume to image
mode fails

High Importance Fixes
IC79840          Node assert following issuing of chvdisk -cache none command to
thin provisioned Volume
IC80466          Configuration node unavailable after upgrade to 6.3.0.x
IC81571          1630 errors following upgrade for 6.3.0.x
IC81627          Node assert caused by internal FlashCopy notification behaviour
IC81791          Node assert during software upgrade

Suggested Fixes
IC81354          Incorrect MDisk WWPN mappings listed following upgrade to 6.2.0.x

APARs resolved in Storwize V7000 Unified File Module 1.3.0.5:

Critical Fixes
IC82264        Upgrade from 1.3.0.0 to 1.3.0.2 failed

High Importance Fixes
IC82260        Replication fails after R1.3 upgrade
IC82298        TSM backups fail after upgrade to 1.3
IC82273        Replications hang after upgrade to 1.3

 

PS : HP have the same issue with HP P4000 SAN/iQ software version 9.0 and 9.0.01 (http://h20000.www2.hp.com/bizsupport/TechSupport/Document.jsp?lang=en&cc=us&taskId=110&prodSeriesId=4118659&prodTypeId=12169&objectID=c03090774)

Print Friendly