<?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: How do we get the (former) owner of a failed disk from 8.3 or higher? in Software Development Kit (SDK) and API Discussions</title>
    <link>https://community.netapp.com/t5/Software-Development-Kit-SDK-and-API-Discussions/How-do-we-get-the-former-owner-of-a-failed-disk-from-8-3-or-higher/m-p/109689#M1610</link>
    <description>&lt;P&gt;You have a few options, if you are running a Linux system try disk show -v | egrep -v "xxxx|yyyy" (xxxx = controller A disk serial number, yyyy = contoller B disk serial number) or put the output from the disk show -v to a file and delete out the valid disk serial numbers, what is left you find what you need or just eye ball it.&lt;/P&gt;</description>
    <pubDate>Fri, 11 Sep 2015 03:01:36 GMT</pubDate>
    <dc:creator>JH</dc:creator>
    <dc:date>2015-09-11T03:01:36Z</dc:date>
    <item>
      <title>How do we get the (former) owner of a failed disk from 8.3 or higher?</title>
      <link>https://community.netapp.com/t5/Software-Development-Kit-SDK-and-API-Discussions/How-do-we-get-the-former-owner-of-a-failed-disk-from-8-3-or-higher/m-p/109162#M1586</link>
      <description>&lt;P&gt;After upgrading some of our filers to 8.3, the scripts we use to monitor failed disks stopped working. &amp;nbsp;Looking into this &amp;nbsp;a bit further, I determined that the &amp;nbsp;{'attributes-list'}{'storage-disk-info'}{'disk-name'} parameter format has been changed. &amp;nbsp;In previous versions the api would return '&amp;lt;node-owner&amp;gt;:&amp;lt;disk_id&amp;gt;' but now only returns '&amp;lt;disk_id&amp;gt;'.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;The problem with this is, that if the disk is failed,&amp;nbsp;&lt;SPAN&gt;{'attributes-list'}{'storage-disk-info'}{'disk-ownership-info'} does not include any data for 'home-node-name' or 'owner-node-name'. &amp;nbsp;As far as I can tell, there is no way to identify who is (was) the owning node of the failed disk.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;Thanks in advance.&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Wed, 04 Jun 2025 23:25:54 GMT</pubDate>
      <guid>https://community.netapp.com/t5/Software-Development-Kit-SDK-and-API-Discussions/How-do-we-get-the-former-owner-of-a-failed-disk-from-8-3-or-higher/m-p/109162#M1586</guid>
      <dc:creator>pbolin</dc:creator>
      <dc:date>2025-06-04T23:25:54Z</dc:date>
    </item>
    <item>
      <title>Re: How do we get the (former) owner of a failed disk from 8.3 or higher?</title>
      <link>https://community.netapp.com/t5/Software-Development-Kit-SDK-and-API-Discussions/How-do-we-get-the-former-owner-of-a-failed-disk-from-8-3-or-higher/m-p/109689#M1610</link>
      <description>&lt;P&gt;You have a few options, if you are running a Linux system try disk show -v | egrep -v "xxxx|yyyy" (xxxx = controller A disk serial number, yyyy = contoller B disk serial number) or put the output from the disk show -v to a file and delete out the valid disk serial numbers, what is left you find what you need or just eye ball it.&lt;/P&gt;</description>
      <pubDate>Fri, 11 Sep 2015 03:01:36 GMT</pubDate>
      <guid>https://community.netapp.com/t5/Software-Development-Kit-SDK-and-API-Discussions/How-do-we-get-the-former-owner-of-a-failed-disk-from-8-3-or-higher/m-p/109689#M1610</guid>
      <dc:creator>JH</dc:creator>
      <dc:date>2015-09-11T03:01:36Z</dc:date>
    </item>
  </channel>
</rss>

