<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Understanding disk show Command: Why Are Physical and Usable Disk Sizes the Same for AFF Models but in ONTAP Discussions</title>
    <link>https://community.netapp.com/t5/ONTAP-Discussions/Understanding-disk-show-Command-Why-Are-Physical-and-Usable-Disk-Sizes-the-Same/m-p/453890#M43764</link>
    <description>&lt;P&gt;Hello,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I’m seeking some clarification on the &lt;STRONG&gt;disk show&lt;/STRONG&gt; command in NetApp ONTAP, specifically regarding the difference between physical and usable disk sizes across different NetApp models.&lt;/P&gt;&lt;P&gt;I’ve observed that on &lt;STRONG&gt;AFF (All Flash FAS)&lt;/STRONG&gt; models, the &amp;nbsp;&lt;STRONG&gt;physical-size&lt;/STRONG&gt; and &lt;STRONG&gt;usable-size&lt;/STRONG&gt; values for disks are the same. However, on &lt;STRONG&gt;FAS (Fabric-Attached Storage)&lt;/STRONG&gt; models, these values are different. Here are the details from the &lt;STRONG&gt;disk show&lt;/STRONG&gt; command for both types of models:&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;AFF Model&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;netapp-c1::&amp;gt; disk show -fields physical-size,usable-size&lt;BR /&gt;&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;disk physical-size usable-size&lt;BR /&gt;------ ------------- -----------&lt;/P&gt;&lt;P&gt;1.0.0 1.75TB 1.75TB&lt;BR /&gt;1.0.1 1.75TB 1.75TB&lt;BR /&gt;1.0.2 1.75TB 1.75TB&lt;BR /&gt;1.0.3 1.75TB 1.75TB&lt;BR /&gt;1.0.4 1.75TB 1.75TB&lt;BR /&gt;1.0.19 1.75TB 1.75TB&lt;BR /&gt;1.0.20 1.75TB 1.75TB&lt;BR /&gt;1.0.21 1.75TB 1.75TB&lt;BR /&gt;1.0.22 1.75TB 1.75TB&lt;BR /&gt;1.0.23 1.75TB 1.75TB&lt;BR /&gt;10 entries were displayed.&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;FAS Model&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;OnTapMulti::&amp;gt; disk show -fields physical-size,usable-size&lt;BR /&gt;disk physical-size usable-size&lt;BR /&gt;-------- ------------- -----------&lt;BR /&gt;NET-1.1 2.00TB 1.97TB&lt;BR /&gt;NET-1.2 68.00GB 66.93GB&lt;BR /&gt;NET-1.3 1023GB 1023GB&lt;BR /&gt;NET-1.4 1023GB 1023GB&lt;BR /&gt;NET-1.5 1023GB 1023GB&lt;BR /&gt;NET-1.6 1023GB 1023GB&lt;BR /&gt;NET-1.7 8.00GB 7.99GB&lt;BR /&gt;NET-1.8 8.00GB 7.99GB&lt;BR /&gt;NET-1.9 8.00GB 7.99GB&lt;BR /&gt;NET-1.10 8.00GB 7.99GB&lt;BR /&gt;10 entries were displayed.&lt;/P&gt;&lt;P&gt;Why are the &amp;nbsp;&amp;nbsp;&lt;STRONG&gt;physical-size&lt;/STRONG&gt; and &lt;STRONG&gt;usable-size&lt;/STRONG&gt;&amp;nbsp;values the same for AFF model disks but different for FAS model disks?&lt;/P&gt;&lt;P&gt;Thank You !&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Thu, 11 Jul 2024 01:41:18 GMT</pubDate>
    <dc:creator>vemus</dc:creator>
    <dc:date>2024-07-11T01:41:18Z</dc:date>
    <item>
      <title>Understanding disk show Command: Why Are Physical and Usable Disk Sizes the Same for AFF Models but</title>
      <link>https://community.netapp.com/t5/ONTAP-Discussions/Understanding-disk-show-Command-Why-Are-Physical-and-Usable-Disk-Sizes-the-Same/m-p/453890#M43764</link>
      <description>&lt;P&gt;Hello,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I’m seeking some clarification on the &lt;STRONG&gt;disk show&lt;/STRONG&gt; command in NetApp ONTAP, specifically regarding the difference between physical and usable disk sizes across different NetApp models.&lt;/P&gt;&lt;P&gt;I’ve observed that on &lt;STRONG&gt;AFF (All Flash FAS)&lt;/STRONG&gt; models, the &amp;nbsp;&lt;STRONG&gt;physical-size&lt;/STRONG&gt; and &lt;STRONG&gt;usable-size&lt;/STRONG&gt; values for disks are the same. However, on &lt;STRONG&gt;FAS (Fabric-Attached Storage)&lt;/STRONG&gt; models, these values are different. Here are the details from the &lt;STRONG&gt;disk show&lt;/STRONG&gt; command for both types of models:&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;AFF Model&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;netapp-c1::&amp;gt; disk show -fields physical-size,usable-size&lt;BR /&gt;&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;disk physical-size usable-size&lt;BR /&gt;------ ------------- -----------&lt;/P&gt;&lt;P&gt;1.0.0 1.75TB 1.75TB&lt;BR /&gt;1.0.1 1.75TB 1.75TB&lt;BR /&gt;1.0.2 1.75TB 1.75TB&lt;BR /&gt;1.0.3 1.75TB 1.75TB&lt;BR /&gt;1.0.4 1.75TB 1.75TB&lt;BR /&gt;1.0.19 1.75TB 1.75TB&lt;BR /&gt;1.0.20 1.75TB 1.75TB&lt;BR /&gt;1.0.21 1.75TB 1.75TB&lt;BR /&gt;1.0.22 1.75TB 1.75TB&lt;BR /&gt;1.0.23 1.75TB 1.75TB&lt;BR /&gt;10 entries were displayed.&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;FAS Model&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;OnTapMulti::&amp;gt; disk show -fields physical-size,usable-size&lt;BR /&gt;disk physical-size usable-size&lt;BR /&gt;-------- ------------- -----------&lt;BR /&gt;NET-1.1 2.00TB 1.97TB&lt;BR /&gt;NET-1.2 68.00GB 66.93GB&lt;BR /&gt;NET-1.3 1023GB 1023GB&lt;BR /&gt;NET-1.4 1023GB 1023GB&lt;BR /&gt;NET-1.5 1023GB 1023GB&lt;BR /&gt;NET-1.6 1023GB 1023GB&lt;BR /&gt;NET-1.7 8.00GB 7.99GB&lt;BR /&gt;NET-1.8 8.00GB 7.99GB&lt;BR /&gt;NET-1.9 8.00GB 7.99GB&lt;BR /&gt;NET-1.10 8.00GB 7.99GB&lt;BR /&gt;10 entries were displayed.&lt;/P&gt;&lt;P&gt;Why are the &amp;nbsp;&amp;nbsp;&lt;STRONG&gt;physical-size&lt;/STRONG&gt; and &lt;STRONG&gt;usable-size&lt;/STRONG&gt;&amp;nbsp;values the same for AFF model disks but different for FAS model disks?&lt;/P&gt;&lt;P&gt;Thank You !&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Thu, 11 Jul 2024 01:41:18 GMT</pubDate>
      <guid>https://community.netapp.com/t5/ONTAP-Discussions/Understanding-disk-show-Command-Why-Are-Physical-and-Usable-Disk-Sizes-the-Same/m-p/453890#M43764</guid>
      <dc:creator>vemus</dc:creator>
      <dc:date>2024-07-11T01:41:18Z</dc:date>
    </item>
    <item>
      <title>Re: Understanding disk show Command: Why Are Physical and Usable Disk Sizes the Same for AFF Models</title>
      <link>https://community.netapp.com/t5/ONTAP-Discussions/Understanding-disk-show-Command-Why-Are-Physical-and-Usable-Disk-Sizes-the-Same/m-p/453991#M43773</link>
      <description>&lt;P&gt;Hello Vemus,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I don't think it is related to AFF &amp;lt;=&amp;gt; FAS.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I've checked on some of my systems:&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Cluster_AFF8080EX::&amp;gt; disk show -fields physical-size,usable-size&lt;BR /&gt;disk physical-size usable-size&lt;BR /&gt;------- ------------- -----------&lt;/P&gt;&lt;P&gt;Info: This cluster has partitioned disks. To get a complete list of spare disk capacity use "storage aggregate show-spare-disks".&lt;BR /&gt;1.10.0 372.6GB 372.4GB&lt;BR /&gt;1.10.1 372.6GB 372.4GB&lt;BR /&gt;1.10.2 372.6GB 372.4GB&lt;BR /&gt;1.10.3 372.6GB 372.4GB&lt;BR /&gt;1.10.4 372.6GB 372.4GB&lt;BR /&gt;1.10.5 372.6GB 372.4GB&lt;BR /&gt;1.10.6 372.6GB 372.4GB&lt;BR /&gt;1.10.7 372.6GB 372.4GB&lt;BR /&gt;1.10.8 372.6GB 372.4GB&lt;BR /&gt;1.10.9 372.6GB 372.4GB&lt;BR /&gt;1.10.10 372.6GB 372.4GB&lt;BR /&gt;1.10.11 372.6GB 372.4GB&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Cluster_AFF_A700::&amp;gt; disk show -fields physical-size,usable-size&lt;BR /&gt;disk physical-size usable-size&lt;BR /&gt;------ ------------- -----------&lt;BR /&gt;1.0.0 745.2GB 745.0GB&lt;BR /&gt;1.0.1 745.2GB 745.0GB&lt;BR /&gt;1.0.2 745.2GB 745.0GB&lt;BR /&gt;1.0.3 745.2GB 745.0GB&lt;BR /&gt;1.0.4 745.2GB 745.0GB&lt;BR /&gt;1.0.5 745.2GB 745.0GB&lt;BR /&gt;1.0.6 745.2GB 745.0GB&lt;BR /&gt;1.0.7 745.2GB 745.0GB&lt;BR /&gt;1.0.8 745.2GB 745.0GB&lt;BR /&gt;1.0.9 745.2GB 745.0GB&lt;BR /&gt;1.0.10 745.2GB 745.0GB&lt;BR /&gt;1.0.11 745.2GB 745.0GB&lt;BR /&gt;12 entries were displayed.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I don't have the same value.&lt;/P&gt;</description>
      <pubDate>Wed, 17 Jul 2024 07:50:20 GMT</pubDate>
      <guid>https://community.netapp.com/t5/ONTAP-Discussions/Understanding-disk-show-Command-Why-Are-Physical-and-Usable-Disk-Sizes-the-Same/m-p/453991#M43773</guid>
      <dc:creator>Gmox</dc:creator>
      <dc:date>2024-07-17T07:50:20Z</dc:date>
    </item>
  </channel>
</rss>

