Unsolved
This post is more than 5 years old
3 Posts
0
1615
VNX5400 - Disabling LUN Deduplication Slow
Hello,
7 Days ago, I disabled deduplication on a 3 TB LUN. Today, it is still in the process of disabling (84% complete). Is this an expected timeframe for this task? Looking at the performance statistics of the LUN, it is not heavily taxed. Is something amiss here, or is this typical behavior for the size of this LUN?
sk_
104 Posts
1
October 12th, 2016 01:00
It will be slow, I think 1 TB LUN took one day to disable in our setup.
But it can also get totally stuck. Check if the numbers advance at all? If not, open SR or reboot SP, dedup process is stuck.
jupiter1890
3 Posts
0
October 12th, 2016 07:00
It has went from 84% to 96% since I posted this yesterday. The LUN is 3 TB. Does the VNX prioritize other traffic ahead of disabling dedupe?
Rainer_EMC
8.6K Posts
1
October 13th, 2016 03:00
yes host traffic has priority over dedupe
when disabling dedupe the LUN will move out of the dedupe container so quite some I/O is required
jupiter1890
3 Posts
0
October 13th, 2016 07:00
IO has been fine except for the first few hours after disabling dedupe (according to EMC monitoring/reporting utility). I was just surprised that 3 TB took over a week to completely disable. Now we are running an old version of OE, 5.33.000.5.052, so I imagine there may be improvements in newer releases.
sk_
104 Posts
1
October 13th, 2016 22:00
That is OLD code..
there has been major changes to dedupe in .119 and .155. Changes are so big that you actually need to disable dedupe completely so that dedupe container is deleted, and then start fresh if you want to use all new fixes for dedupe.