locked
Defrag - 2012R2 - Slab Consolidation - 8MB RRS feed

 > 

  • Question

  • Question
    Sign in to vote
    1
    Sign in to vote

    Hi

    Hi

    i have looked at this article: http://blogs.technet.com/b/askcore/archive/2014/02/17/what-39-s-new-in-defrag-for-windows-server-2012-2012r2.aspx

    what can be done to resolve this error:

    Microsoft-Windows-Defrag(257 - None): The volume H (H:) was not optimized because an error was encountered: Neither Slab Consolidation nor Slab Analysis will run if slabs are less than 8 MB. (0x8900002D)

    it's a server running on Hyper-V 2012R2 , with dynamic disks.

    or is it safe to ignore this?

    Friday, October 3, 2014 10:50 AM

Answers

All replies

  • Question
    Sign in to vote
    3
    Sign in to vote
    Hi,

    There's no need to run Storage Optimizer on thin provisioned LUNs that use an allocation size (also known as slab size) of less than 8 MB.

    This is expected behavior because slab consolidation and slab analysis has been disabled on thin provisioned LUNs that have a slab size of less than 8 MB.

    For more detailed information, please refer to the article bellw:

    Storage Optimizer memory use increases when it runs on thin provisioned LUNs
    http://support2.microsoft.com/kb/2964429

    Best Regards,

    Mandy 

    We are trying to better understand customer views on social support experience, so your participation in this interview project would be greatly appreciated if you have time.
    Thanks for helping make community forums a great place.

    • Marked as answer by Mandy Ye Wednesday, October 15, 2014 2:22 AM
    Monday, October 6, 2014 8:27 AM
  • Question
    Sign in to vote
    0
    Sign in to vote

    We are seeing this on 2 out of 12 VM's on the same Hyper-V Host; these 2 disks are fixed - one having VHD the other VHDX and one is 2012 the other 2012R2.

    Can you explain why we continue to get these "error" messages from this?  The other guests are aligned with the same Config (some 2012, some 2012R2 - all fixed, etc.) and all VM's storage is on the SAME LUN...

    Any help in understanding this would be appreciated...


    • Edited by gwin99 Tuesday, December 23, 2014 1:51 PM edit :-)
    Tuesday, December 23, 2014 1:50 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    We are seeing this on 2 out of 12 VM's on the same Hyper-V Host; these 2 disks are fixed - one having VHD the other VHDX and one is 2012 the other 2012R2.

    Can you explain why we continue to get these "error" messages from this?  The other guests are aligned with the same Config (some 2012, some 2012R2 - all fixed, etc.) and all VM's storage is on the SAME LUN...

    Any help in understanding this would be appreciated...


    I would like to figure out an answer to this as well.

    Have a 2012 server vm and need to shrink the vmdk disk usage and keep getting this error.  The server shows the disk needs optimization but it doesnt work with vsphere 6.  

    Tuesday, December 22, 2015 7:37 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Nice to know what's the reason for the error, but what can be done to prevent it? I don't want to have that many Eventlog errors on all our 2012 R2 servers.

    Disable the scheduled task?
    Change it? (Remove -k switch)

    Wednesday, August 3, 2016 11:01 AM
  • Question
    Sign in to vote
    35
    Sign in to vote


    Disable the scheduled task?
    Change it? (Remove -k switch)

    Since nobody really answered this question, I figured I'd shed some light...

    You are right on the money here.  The Scheduled Task "ScheduledDefrag" is generating this error when it runs.  It's created by the system.  

    Open Scheduled Tasks > Microsoft > Windows > Defrag

    Open "ScheduledDefrag" > Actions

    Highlight "Start a program" click the "Edit..." button.

    Remove the "-k" entry from the "Add arguments" section

    Click the OK button.  Events should no longer appear, if this is the only place Defrag is run from.

    • Proposed as answer by wilspin Friday, June 16, 2017 1:06 PM
    Thursday, February 16, 2017 6:26 AM
  • Question
    Sign in to vote
    1
    Sign in to vote
    So the built in scheduled task not only causes errors, but it has multiple flags that are not documented.  And this has not been corrected in 5 years.  Great stuff Microsoft... 
    Tuesday, April 4, 2017 4:26 PM
  • Question
    Sign in to vote
    8
    Sign in to vote

    This is probably the best and most concise answer so far I've seen when I've come to social TechNet.  I mean, look at Mandy's answer above, really doesn't give you details, doesn't explain why the problem is occurring, makes you feel silly - "geez gosh darn it, why did I have to set up that stupid rule for???".

    Now Gamefanatic - gives a short but specific answer for why the error is occurring, and how to fix it.  Why can't most replies on here by this way?

    Sunday, May 21, 2017 1:12 PM
  • Question
    Sign in to vote
    1
    Sign in to vote

    This is probably the best and most concise answer so far I've seen when I've come to social TechNet.  I mean, look at Mandy's answer above, really doesn't give you details, doesn't explain why the problem is occurring, makes you feel silly - "geez gosh darn it, why did I have to set up that stupid rule for???".

    Now Gamefanatic - gives a short but specific answer for why the error is occurring, and how to fix it.  Why can't most replies on here by this way?


    I agree!
    Friday, June 16, 2017 1:06 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    An amazing confluence of events indeed.  Thanks for an actual usable, understandable, and undoublespeak answer.  

    As a followup, just in case anyone else runs into it. I started seeing these about 3 months ago but it was restricted to one particular drive. As it turns out that drive was actually a common mount point for multiple volumes. So it appears that attaching a volume in the tree rather than assigning it a drive letter may also impact things.  

    Only dead fish swim with the current.


    Sunday, August 13, 2017 3:50 PM
  • Question
    Sign in to vote
    0
    Sign in to vote
    Thanks a lot. Superfluous errors like these make troubleshooting using the EventLog so tedious, so getting rd of them is a great help.

    Jan Z

    Thursday, December 21, 2017 11:47 AM
  • Question
    Sign in to vote
    1
    Sign in to vote
    Double down on that thought. Why would Mandy Yee even think that a "robo" answer like hers should even compare to GameFanactic's true answer?  As a fellow technical support provider it shames me to think that such a lucid response actually deserves points.  Get with it people and start answering the questions!  Do not point users to abstracts or lengthy articles which don't provide actual answers unless said articles are requested by the originator. 
    Friday, August 24, 2018 5:37 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Hi

    What is the root cause or what causes this?

    I am experiencing the same issue on a SQL Cluster built on SAN storage and physical Disks not VMDKs

    What should one do to avoid this?

    Yes there is a  defrag task schedule which we have discovered.

    Friday, February 15, 2019 10:58 AM
  • Question
    Sign in to vote
    1
    Sign in to vote

    The only option which is not documented within the exe itself is the -$ option. 

    C:\Windows\System32>defrag /?

    ....

     /K      Perform slab consolidation on the specified volumes.

    ....

    Their support is crap, agreed. 

    Thursday, April 4, 2019 3:52 PM
  • Question
    Sign in to vote
    0
    Sign in to vote
    Since we moved all of our servers to an all flash storage, we finally disabled the ScheduledDefrag task and got rid of the eventlog errors in this way.
    Tuesday, July 30, 2019 8:09 AM
  • Question
    Sign in to vote
    0
    Sign in to vote
    in addition: https://docs.microsoft.com/en-us/windows-server/administration/windows-commands/defrag

    Paul Fijma

    Friday, December 20, 2019 9:06 AM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Hi there,

    So this is how I did it:

    Zero the free space

    Shut down the machine and mount the VHD/VHDX on the HyperV - then treat the disks as any other disk on the HyperV. Defrag it and Shrink it from there.

    This worked perfectly for me when I encountered this issue.

    Friday, July 31, 2020 10:25 AM