<?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 Re: Re-assign shared disks FAS2520 in ONTAP Hardware</title>
    <link>https://community.netapp.com/t5/ONTAP-Hardware/Re-assign-shared-disks-FAS2520/m-p/107163#M6662</link>
    <description>&lt;P&gt;You can reassign data partitions separately if necessary. You still need root partitions for second node. Note that it is recommended to have at least one disk with full ownership (root + data partition) for the purpose of writing core.&lt;/P&gt;</description>
    <pubDate>Thu, 09 Jul 2015 09:33:58 GMT</pubDate>
    <dc:creator>aborzenkov</dc:creator>
    <dc:date>2015-07-09T09:33:58Z</dc:date>
    <item>
      <title>Re-assign shared disks FAS2520</title>
      <link>https://community.netapp.com/t5/ONTAP-Hardware/Re-assign-shared-disks-FAS2520/m-p/107159#M6660</link>
      <description>&lt;P&gt;Scenario FAS2520-HA, cDOT 8.3&lt;/P&gt;
&lt;P&gt;System Setup with internal drives and 1xextra shelf - option chosen during setup to 'manually configure disks later'&lt;/P&gt;
&lt;P&gt;Result: Storage balanced 50/50 between each node in HA pair, including the root 'partitions'.&lt;/P&gt;
&lt;P&gt;Unable to reassign 'remainder' capacity of internal drives to a single controller as message states:&amp;nbsp; Cannot remove owner of disk "1.0.x" because it is&lt;BR /&gt;shared.&lt;/P&gt;
&lt;P&gt;Please can anyone advise what is the best course of action to be able to maximise the usage of the remaining disk space on the internal drives?&lt;/P&gt;
&lt;P&gt;Is there somewhere advanced that I can dive into to reassign all partitions to a single node (I take it that this would include root partitions too?)&lt;/P&gt;
&lt;P&gt;Thanks, Garth&lt;/P&gt;</description>
      <pubDate>Mon, 13 Jul 2015 16:43:59 GMT</pubDate>
      <guid>https://community.netapp.com/t5/ONTAP-Hardware/Re-assign-shared-disks-FAS2520/m-p/107159#M6660</guid>
      <dc:creator>GLOYNSSNS</dc:creator>
      <dc:date>2015-07-13T16:43:59Z</dc:date>
    </item>
    <item>
      <title>Re: Re-assign shared disks FAS2520</title>
      <link>https://community.netapp.com/t5/ONTAP-Hardware/Re-assign-shared-disks-FAS2520/m-p/107162#M6661</link>
      <description>&lt;P&gt;Do you want the disks all handled by one controller? And the shelf handled by the other one? If so:&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Login into your clustershell&lt;/P&gt;&lt;P&gt;Switch to your nodeshell (system node run)&lt;/P&gt;&lt;P&gt;priv set advanced&lt;/P&gt;&lt;P&gt;aggr status -r to check which disks are handled by your second controller&lt;/P&gt;&lt;P&gt;switch to the nodeshell of which controller currently handles the disks you want to unown&lt;/P&gt;&lt;P&gt;again, priv set advanced&lt;/P&gt;&lt;P&gt;disk show&lt;/P&gt;&lt;P&gt;disk remove_ownership &amp;lt;disk_id&amp;gt;&lt;/P&gt;&lt;P&gt;disk show -n to list all unowned disks&lt;/P&gt;&lt;P&gt;switch to your nodeshell of your prefered controller&lt;/P&gt;&lt;P&gt;disk assign &amp;lt;disk_id&amp;gt; -o unowned -s &amp;lt;sysid&amp;gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;check again with aggr status -r that only one controller handles all disks, except the root partitions&lt;/P&gt;</description>
      <pubDate>Thu, 09 Jul 2015 09:24:22 GMT</pubDate>
      <guid>https://community.netapp.com/t5/ONTAP-Hardware/Re-assign-shared-disks-FAS2520/m-p/107162#M6661</guid>
      <dc:creator>Racoon</dc:creator>
      <dc:date>2015-07-09T09:24:22Z</dc:date>
    </item>
    <item>
      <title>Re: Re-assign shared disks FAS2520</title>
      <link>https://community.netapp.com/t5/ONTAP-Hardware/Re-assign-shared-disks-FAS2520/m-p/107163#M6662</link>
      <description>&lt;P&gt;You can reassign data partitions separately if necessary. You still need root partitions for second node. Note that it is recommended to have at least one disk with full ownership (root + data partition) for the purpose of writing core.&lt;/P&gt;</description>
      <pubDate>Thu, 09 Jul 2015 09:33:58 GMT</pubDate>
      <guid>https://community.netapp.com/t5/ONTAP-Hardware/Re-assign-shared-disks-FAS2520/m-p/107163#M6662</guid>
      <dc:creator>aborzenkov</dc:creator>
      <dc:date>2015-07-09T09:33:58Z</dc:date>
    </item>
    <item>
      <title>Re: Re-assign shared disks FAS2520</title>
      <link>https://community.netapp.com/t5/ONTAP-Hardware/Re-assign-shared-disks-FAS2520/m-p/107164#M6663</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thank you both for your feedback - in the end the answer was in the 8.3 Storage Guide from NetApp.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;In advanced mode&lt;/P&gt;&lt;P&gt;storage disk assign -force -data true -owner NEWOWNERNODE -disk 1.0.x -&amp;gt; for each drive/partition&lt;/P&gt;&lt;P&gt;Then create aggregate leaving one free partition for spare space.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thank You,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Garth&lt;/P&gt;</description>
      <pubDate>Thu, 09 Jul 2015 09:44:56 GMT</pubDate>
      <guid>https://community.netapp.com/t5/ONTAP-Hardware/Re-assign-shared-disks-FAS2520/m-p/107164#M6663</guid>
      <dc:creator>GLOYNSSNS</dc:creator>
      <dc:date>2015-07-09T09:44:56Z</dc:date>
    </item>
    <item>
      <title>Re: Re-assign shared disks FAS2520</title>
      <link>https://community.netapp.com/t5/ONTAP-Hardware/Re-assign-shared-disks-FAS2520/m-p/134554#M8395</link>
      <description>&lt;P&gt;It is helped my issue.&lt;/P&gt;&lt;P&gt;Disk was assigned to node where shelf was not connected.&lt;/P&gt;</description>
      <pubDate>Mon, 18 Sep 2017 15:36:10 GMT</pubDate>
      <guid>https://community.netapp.com/t5/ONTAP-Hardware/Re-assign-shared-disks-FAS2520/m-p/134554#M8395</guid>
      <dc:creator>eduard_abrahamyan</dc:creator>
      <dc:date>2017-09-18T15:36:10Z</dc:date>
    </item>
  </channel>
</rss>

