Block Storage

 View Only

  • 1.  unmap size when using vsp5000 and esx

    Posted 05-20-2022 08:58
    Edited by System 10-17-2025 15:02

    as per this article https://kb.vmware.com/s/article/2057513 vmware suggest to ask storage vendor what should be the ideal --reclaim-unit=number .. can you please provide that ? please see below lines in this KB : VMware recommends that you consult with your storage array providers on the best value or best practices when manually defining a --reclaim-unit value.



    ------------------------------
    Chintan Patel
    ------------------------------


  • 2.  RE: unmap size when using vsp5000 and esx

    Posted 06-15-2022 07:17
    Edited by System 10-17-2025 15:02
    Hello

    I've replied to this probably more than once already. But the moderation team seems to be really slow.

    I believe you could use 42. Since Dynamic provisioned volumes use 42MB pages. I've posted links to the manual for this but I think that's what making the post get moderated.

    ------------------------------
    William Jansen van Nieuwenhuizen
    Hitachi Vantara
    ------------------------------



  • 3.  RE: unmap size when using vsp5000 and esx

    Posted 06-15-2022 14:24
    Edited by System 10-17-2025 15:02
    Hello Chintan

    This is just my personal opinion. But I believe the answer is 42! Dynamic pools work with 42MB pages. So setting it to the same should hopefully align on the volume which would then hopefully free up the same chunks.

    https://knowledge.hitachivantara.com/Documents/Management_Software/SVOS/9.8.2/Volume_Management_-_VSP_5000_Series/Provisioning/01_About_Dynamic_Provisioning


    ------------------------------
    William Jansen van Nieuwenhuizen
    Hitachi Vantara
    ------------------------------