{"id":391,"date":"2019-01-05T20:08:05","date_gmt":"2019-01-05T20:08:05","guid":{"rendered":"http:\/\/labiol.xyz\/?p=391"},"modified":"2019-02-05T20:48:08","modified_gmt":"2019-02-05T20:48:08","slug":"unmap-nie-dziala-na-macierzy-ontap","status":"publish","type":"post","link":"https:\/\/www.labiol.xyz\/index.php\/2019\/01\/05\/unmap-nie-dziala-na-macierzy-ontap\/","title":{"rendered":"UNMAP nie dzia\u0142a na macierzy ONTAP"},"content":{"rendered":"\n

Delete status (unmap) unsupported – studium przypadku \ud83d\ude42<\/p>\n\n\n\n

Sytuacja zwi\u0105zana z macierz\u0105 NetApp AFF, Ontap 9.3<\/p>\n\n\n\n

Macierz ma domy\u015bln\u0105 konfiguracj\u0119, luny s\u0105 wystawiane bez zb\u0119dnych dodatkowych \u201cudziwnie\u0144\u201d.<\/p>\n\n\n\n

Na ho\u015bcie ESXi (wersja 6.0) sytuacja wygl\u0105da w nast\u0119puj\u0105cy spos\u00f3b:<\/p>\n\n\n\n

esxcli storage core device vaai status get -d naa.
\nVAAI Plugin Name: VMW_VAAIP_NETAPP
\n ATS Status: supported
\n Clone Status: supported
\n Zero Status: supported
\n Delete Status: unsupported <\/p>\n\n\n\n

esxcli system settings advanced list -o \/VMFS3\/EnableBlockDelete
\n Path: \/VMFS3\/EnableBlockDelete
\n Type: integer
\n Int Value: 1
\n Default Int Value: 0
\n Min Value: 0
\n Max Value: 1
\n String Value:
\n Default String Value:
\n Valid Characters:
\n Description: Enable VMFS block delete when UNMAP is issued from guest OS <\/p>\n\n\n\n

Fragment zwracaj\u0105cy uwag\u0119 to unsupported dla opcji \u201cdelete status\u201d.<\/p>\n\n\n\n

Dalsza analiza wykaza\u0142a, \u017ce na jednym ho\u015bcie wy\u0142\u0105czona by\u0142a opcja HardwareAcceleratedInit.<\/p>\n\n\n\n

Opcje te mo\u017cna \u0142atwo sprawdzi\u0107 za pomoc\u0105 powercli:<\/p>\n\n\n\n

get-cluster CLUSTER_NAME | Get-VMHost | select name, @{N=”DataMover”; E={ $_ | Get-AdvancedSetting -Name DataMover.HardwareAcceleratedMove }}
get-cluster CLUSTER_NAME | Get-VMHost | select name, @{N=”DataInit”; E={ $_ | Get-AdvancedSetting -Name DataMover.HardwareAcceleratedInit }}<\/p><\/blockquote>\n\n\n\n

Wynik zapytania dla ka\u017cdego hosta w klastrze powinien zwr\u00f3ci\u0107 powinien zwr\u00f3ci\u0107 warto\u015b\u0107 \u201c1\u201d. <\/p>\n\n\n\n

hostname DataMover.HardwareAcceleratedMove:1
hostname DataMover.HardwareAcceleratedInit:1<\/p><\/blockquote>\n\n\n\n

Po zmianie warto\u015bci dla jednego z host\u00f3w i jego restarcie warto\u015b\u0107 Delete Status: unsupported nie zmieni\u0142a si\u0119.
\nZatem dalsze kroki zale\u017c\u0105 od macierzy.
\nPo analizie okaza\u0142o si\u0119, \u017ce NetApp domy\u015blnie prezentuje LUN-y bez w\u0142\u0105czonej opcji space-allocation. Wynika to z faktu, \u017ce domy\u015blnie wiele system\u00f3w operacyjnych (w\u0142\u0105cznie ze starszymi ni\u017c 6.7 wersjami ESXi) nie wykorzystuje UNMAP.<\/p>\n\n\n\n

Procedura zmiany tego na macierzy NetApp wygl\u0105da nast\u0119puj\u0105co:<\/p>\n\n\n\n

  1. Lun offline <\/li>
  2. lun show -vserver vserver_name -volume volume_name -lun lun_name \u2013fields space-allocation lun modify -vserver vserver_name -volume volume_name -lun lun_name – space-allocation enabled<\/li>
  3. Lun online<\/li><\/ol>\n\n\n\n

    Co prawda procedura dzia\u0142a bez prze\u0142\u0105czania lun offline\/online – ale nie jest to zalecany spos\u00f3b przez producenta macierzy.<\/p>\n\n\n\n

    https:\/\/kb.netapp.com\/app\/answers\/answer_view\/a_id\/1001100<\/a>
    http:\/\/buildvirtual.net\/administer-hardware-acceleration-for-vaai\/<\/a>
    http:\/\/www.bloggerbaru.com\/enabledisable-vmware-vaai-functionality-esxiesx\/<\/a><\/p>\n","protected":false},"excerpt":{"rendered":"

    Delete status (unmap) unsupported – studium przypadku \ud83d\ude42 Sytuacja zwi\u0105zana z macierz\u0105 NetApp AFF, Ontap 9.3 Macierz ma domy\u015bln\u0105 konfiguracj\u0119, luny s\u0105 wystawiane bez zb\u0119dnych dodatkowych \u201cudziwnie\u0144\u201d. Na ho\u015bcie ESXi (wersja 6.0) sytuacja wygl\u0105da w nast\u0119puj\u0105cy spos\u00f3b: esxcli storage core device vaai status get -d naa. VAAI Plugin Name: VMW_VAAIP_NETAPP … <\/p>\n","protected":false},"author":1,"featured_media":393,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[2],"tags":[],"class_list":["post-391","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-vmware"],"_links":{"self":[{"href":"https:\/\/www.labiol.xyz\/index.php\/wp-json\/wp\/v2\/posts\/391","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.labiol.xyz\/index.php\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.labiol.xyz\/index.php\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.labiol.xyz\/index.php\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.labiol.xyz\/index.php\/wp-json\/wp\/v2\/comments?post=391"}],"version-history":[{"count":3,"href":"https:\/\/www.labiol.xyz\/index.php\/wp-json\/wp\/v2\/posts\/391\/revisions"}],"predecessor-version":[{"id":395,"href":"https:\/\/www.labiol.xyz\/index.php\/wp-json\/wp\/v2\/posts\/391\/revisions\/395"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.labiol.xyz\/index.php\/wp-json\/wp\/v2\/media\/393"}],"wp:attachment":[{"href":"https:\/\/www.labiol.xyz\/index.php\/wp-json\/wp\/v2\/media?parent=391"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.labiol.xyz\/index.php\/wp-json\/wp\/v2\/categories?post=391"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.labiol.xyz\/index.php\/wp-json\/wp\/v2\/tags?post=391"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}