A level 2 engineer had to make a threshold adjustment from 75% to 85% at the service root level for each shared folder. I was informed that although not a bug per se, at this point any new thin enabled shared folders I create and then migrate data to will need this adjustment made by a tech or engineer. This is because that after the migration, a very large amount of files are read during the first pass of the dedupe, as described above.  One alternative would be to not use the thin enabled function on the shared folder.
I've got a VNXe 3100 running 2.2.0.17384 that is currently being tested prior to going in to production. So far I've only set up two CIFS Shared folders with deduplication enabled. Share_A is thin enabled, 600GB size. There is 270.8 GB allocated, 197.6 GB Used and Maximum is 1.5TB. Share_B is thin enabled, 300GB size. There is 108.8 GB allocated, 79.5 GB Used and Maximum is 1.2TB. Both reside on the same performance pool that has a total space of 1.426 TB and it has 496.7 GB Allocated and 963.9 GB Remaining.  In the Alerts, I am seeing "Deduplication scan 27 failed due to a lack of space or other system resource issue." and "Deduplication scan 25 failed due to a lack of space or other system resource issue." The Problem Information pane shows "There is insufficient space available to complete deduplication. You need to allocate additional space.". The log shows it as: Source:Server_DEDUPE, User: , Event ID:13:1094002, Description:Deduplication scan 27 failed due to a lack of space or other system resource issue.   Both shared folder details show the Files Deduplicated at 0% and Saved 0%. I don't understand how much more (or where) the space needs to be allocated or increased. What am I missing here?  Thank you in advance for any clarification on this.  Edit: Additional info - On the Powerlink Knowledge base, I found ID:emc263729 where it states "You must increase the amount of available storage space or protection space to complete the deduplication operation."  Looking at the protection size, here is what I have:  Share_A has 514.3 GB, Current Allocation: 97.656 GB, Used 256.0 MB, and Maximum Size 15.999 TB with Auto Adjust Protection is On (checked) Share_B has 105 GB, Current Allocation: 19.5 GB, Used 256.0 MB, and Maximum Size 15.999 TB with Auto Adjust Protection is On (checked)  I don't suspect it is the protection size, as the Auto Adjust should take care of it, correct?  Also, for Share_A there is the size defined that is 3x what is used and Share_B has over 3x the amount used for the defined size. I'm at a loss as to where to add storage.  Message was edited by: Craig S
Dedupe Scan Fails; Where to Increase Space?