morrie_morrie wrote:
HPE have told us that they haven't seen this before in 3.3.1 and have escalated it to their Engineering team to determine what went wrong and hopefully for all of us, provide a fix to prevent it from happening again..
That's a stock answer with 3PAR support you know ... we had that same answer for a full crash on 3.2.2EMU2 code, and also for an issue with high latency ... everything is all a surprise to level 1 support .. get to the level 4 guys and you get the real honest, non-polically correct answers (which I much prefer!)
Why are you running 3.3.1 code by the way ? Our local HPE engineer says it isn't GA yet and only installed to customers who want the latest bells and whistles (and to be guinea pigs) .. I know I'm not going there on the arrays I look after until it is GA + 6 months + the release notes for fixes need to stop mentioning "unexpected node restarts" ... oh and I'd like updatevv to work properly as well as dedupe and compression working would be good too