Hi Dave,
We just went through an escalation to the higher floors of NetApp. Professional Services came on-site and gathered data. We ran a storage vmotion to re-create the :s and perfstat-ed the whole event. After further analysis, the PSE claims to have found a "bug" related to the :s and the model of controller, FAS3160. We are awaiting their report. The "snowquester" here in DC has delayed that report.
If you have a case open, have your case owner check into case 2003994303.
On Mar 6, 2013, at 10:49 AM, dave.withers dave.withers@gnomefoo.com wrote:
Subscribed.
We run 3240's in HA 7-mode on 8.1.2 and we have been battling issues similar to the OP and going back and forth with netapp for the last 3 months on resolution. We have moved hotspots that netapp identified from 24/7 perfstat logs to SAS off SATA and have basically removed virtually all write heavy IO applications from the SATA aggregate but we will still see the :s cp type and all of the sudden experience latency spikes across all protocols. I think we have gone through 3 upgrades based on 'bugs' netapp claimed to have found/fixed. We are definitely in a better place, but the latency issue is still too common to feel comfortable about. Definitely would liek to be added to an escalation and would be happy to provide logs/stats/etc that may help get this issue noticed by netapp.
-- View this message in context: http://network-appliance-toasters.10978.n7.nabble.com/wafl-cp-slovol-warning... Sent from the Network Appliance - Toasters mailing list archive at Nabble.com. _______________________________________________ Toasters mailing list Toasters@teaparty.net http://www.teaparty.net/mailman/listinfo/toasters