Jeff is right, let it run if you can.  The option to disable it is so tempting, but you're better off just adding another shelf and running a reallocate.  

On Jun 23, 2015, at 11:55 PM, Jeffrey Mohler <jmohler@yahoo-inc.com> wrote:

This is normal, and -required- to...to simplify this, comb out the new physical to virtual block map required after a snapmirror update.

It will eventually finish, but if it never finishes, run a less intensive snapmirror schedule and let it catch up.

 

_________________________________

Jeff Mohler

Tech Yahoo, Storage Architect, Principal

(831)454-6712

TW: @PrincipalYahoo

YM: Supra89ta

On Tuesday, June 23, 2015 11:51 PM, Mike Michalakis <mike@directit.com.cy> wrote:

Hi

I have a storage system that is under stress, and as luck has it I need to added more stress by loading it with a large cifs related volume, this is a transition from a 7-Mode ontap system

 

Every time we complete the transition, the system spikes disks 100%, cpu 100%, etc. On the perfstat we see deswizzling running. This is a normal operation every time a snapmirror break-off occurs, that is the deswizzle part of the equation.. When we take this volume offline, operations go back to normal.

 

My question, what is the result of disabling deswizzle is the short term, do I look functionality, e.g. vol move?

 

To turn off deswizzle:

Nodeshell*> options wafl.deswizzle.enable off

To turn on deswizzle:

Nodeshell*> options wafl.deswizzle.enable on

 

 

Backround: FAS3210, C-Dot 8.2.3, SAS disks

 

_______________________________________________
Toasters mailing list
Toasters@teaparty.net
http://www.teaparty.net/mailman/listinfo/toasters

_______________________________________________
Toasters mailing list
Toasters@teaparty.net
http://www.teaparty.net/mailman/listinfo/toasters

_______________________________________________
Toasters mailing list
Toasters@teaparty.net
http://www.teaparty.net/mailman/listinfo/toasters