Last updated on FEBRUARY 14, 2014
Applies to:Sun Storage 7410 Unified Storage System - Version All Versions and later
Sun Storage 7310 Unified Storage System - Version All Versions and later
7000 Appliance OS (Fishworks)
The history so far shows several nfs outages, performance degradation ending in clients loosing their connections. Customer's workaround is to failover the cluster until symptoms are showing on that head as well.
A failback will then again restore NFS availability for an unknown time.
Customer suspects that this is related to the update performed 4 weeks ago. There are two additional SR's open, one is performance related, the other dealt with a failed cluster failover.
BUI becomes unresponsive or inaccessible, CLI might either still working or not.
The configured readzilla also goes 'offline':
So it seems that B is waiting on D. C & D are waiting on A.
All the stacks seem to be network related. But I am unable to determine what A is waiting on.
It has been confirmed that bugs 15805888, 16748459 and 16697917 represent the same issue with the nv_sata driver on ZFSSA.
The current working hypothesis is that this issue happens if one ZFSSA head runs only one readzilla. Adding a second readzilla drive (or even physically removing all readzillas) may workaround this problem.
The hypothesis also states that this issue may be reproducible by forcing nv_power_reset on the readzilla drive.
16697917 - Primary head in 7410 cluster panicked 3 times in one day.
16748459 - 7410 nv_sata port in NV_RESTORE state/cache disk REMOVED (latest 2011.1.5.0 IDR)
15805888 - nv_sata hangs when there is only one drive configured and power reset occurs
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
Million Knowledge Articles and hundreds of Community platforms