<?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: lun Corruption in Cloud Volumes ONTAP</title>
    <link>https://community.netapp.com/t5/Cloud-Volumes-ONTAP/lun-Corruption/m-p/168880#M350</link>
    <description>&lt;P&gt;Try chkdsk or fsck depending upon the host-side filesystem - if this doesn't work, offline &amp;amp; un-map the lun and perform a 'snap restore' of particular LUNs or entire volume&amp;nbsp; from a previous known working date snap (depending upon whether it is one-2-one or one-2-many setup). After LUN restore from 'snapshot', re-map the LUN to igroup-of-the-host and try assessing things. If you have flex-clone licensed, you can choose a previous good snap and make a clone and then present those luns to the same host and if that works, split it which runs in the background. Number of options to try. (may not be that straightforward in all scenarios but do start trying).&lt;/P&gt;</description>
    <pubDate>Fri, 30 Jul 2021 10:51:33 GMT</pubDate>
    <dc:creator>Ontapforrum</dc:creator>
    <dc:date>2021-07-30T10:51:33Z</dc:date>
    <item>
      <title>lun Corruption</title>
      <link>https://community.netapp.com/t5/Cloud-Volumes-ONTAP/lun-Corruption/m-p/168875#M349</link>
      <description>&lt;P&gt;We have lun’s assigned&amp;nbsp; DB servers .&amp;nbsp; assigned disk seems to be corrupted and its reflecting as raw after&amp;nbsp;DB team&amp;nbsp; performed a cluster rebuild and&lt;/P&gt;&lt;P&gt;On other machine lun’s does not show up at all.&lt;/P&gt;&lt;P&gt;Can someone help on this ?&lt;/P&gt;</description>
      <pubDate>Wed, 04 Jun 2025 10:17:40 GMT</pubDate>
      <guid>https://community.netapp.com/t5/Cloud-Volumes-ONTAP/lun-Corruption/m-p/168875#M349</guid>
      <dc:creator>Netapp_maniac</dc:creator>
      <dc:date>2025-06-04T10:17:40Z</dc:date>
    </item>
    <item>
      <title>Re: lun Corruption</title>
      <link>https://community.netapp.com/t5/Cloud-Volumes-ONTAP/lun-Corruption/m-p/168880#M350</link>
      <description>&lt;P&gt;Try chkdsk or fsck depending upon the host-side filesystem - if this doesn't work, offline &amp;amp; un-map the lun and perform a 'snap restore' of particular LUNs or entire volume&amp;nbsp; from a previous known working date snap (depending upon whether it is one-2-one or one-2-many setup). After LUN restore from 'snapshot', re-map the LUN to igroup-of-the-host and try assessing things. If you have flex-clone licensed, you can choose a previous good snap and make a clone and then present those luns to the same host and if that works, split it which runs in the background. Number of options to try. (may not be that straightforward in all scenarios but do start trying).&lt;/P&gt;</description>
      <pubDate>Fri, 30 Jul 2021 10:51:33 GMT</pubDate>
      <guid>https://community.netapp.com/t5/Cloud-Volumes-ONTAP/lun-Corruption/m-p/168880#M350</guid>
      <dc:creator>Ontapforrum</dc:creator>
      <dc:date>2021-07-30T10:51:33Z</dc:date>
    </item>
  </channel>
</rss>

