<?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 LUN serial NOT changed on a vol clone in ONTAP Discussions</title>
    <link>https://community.netapp.com/t5/ONTAP-Discussions/LUN-serial-NOT-changed-on-a-vol-clone/m-p/105184#M21543</link>
    <description>&lt;P&gt;Hi all.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I've just hit what I believe is a very serious bug in DOT 8.1.&lt;/P&gt;&lt;P&gt;On a vol clone operation on a LUN container, the cloned LUN kept the same serial number as the original one.&lt;/P&gt;&lt;P&gt;Of course that should never happen, since this basically means remote SAN initiators will see that LUN as just a bunch of new paths to the original LUN.&lt;/P&gt;&lt;P&gt;Experience shows it will make a VMFS datastore collapse.&amp;nbsp; &lt;span class="lia-unicode-emoji" title=":disappointed_face:"&gt;😞&lt;/span&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;DOT version used was Release 8.1.4P3 7-Mode.&lt;/P&gt;&lt;P&gt;No newer 8.1.4 patch release show such a bug as being fixed.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Has anyone experienced this before ?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Here are just a few commands exposing the problem.&lt;/P&gt;&lt;P&gt;&lt;FONT color="#008000"&gt;The first clone operation&lt;/FONT&gt; is when everything goes alright. DOT properly identifies the new LUN as a duplicate, and takes appropriate action.&lt;/P&gt;&lt;P&gt;&lt;FONT color="#FF0000"&gt;The second clone operation&lt;/FONT&gt; went bad : the LUN duplicate went unnoticed (seemingly the vol clone operation did not fully complete), and the resulting LUN has the same serial number as the original one...&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;netappb2*&amp;gt; lun serial /vol/vmfs_lan/vmfs_lan/vmfs_lan&lt;BR /&gt;Serial#: &lt;STRONG&gt;&lt;FONT color="#0000FF"&gt;2Fh5s+ClT/8T&lt;/FONT&gt;&lt;/STRONG&gt;&lt;BR /&gt;netappb2*&amp;gt;&lt;BR /&gt;netappb2*&amp;gt; &lt;FONT color="#008000"&gt;vol clone create vmfs_lan_20150517213001 -b vmfs_lan smvi__VMFS_LAN_20150517213001&lt;/FONT&gt;&lt;BR /&gt;Creation of clone volume 'vmfs_lan_20150517213001' has completed.&lt;BR /&gt;netappb2*&amp;gt; &lt;STRONG&gt;Tue May 19 01:19:50 CEST [netappb2:wafl.volume.clone.created:info]: Volume clone vmfs_lan_20150517213001 of volume vmfs_lan was created successfully.&lt;/STRONG&gt;&lt;BR /&gt;&lt;STRONG&gt;Tue May 19 01:19:50 CEST [netappb2:lun.newLocation.offline:warning]: LUN /vol/vmfs_lan_20150517213001/vmfs_lan/vmfs_lan has been taken offline to prevent map conflicts after a copy or move operation.&lt;/STRONG&gt;&lt;BR /&gt;netappb2*&amp;gt; lun serial /vol/vmfs_lan_20150517213001/vmfs_lan/vmfs_lan&lt;BR /&gt;Serial#: &lt;STRONG&gt;&lt;FONT color="#000000"&gt;2FhNd$GH-t35&lt;/FONT&gt;&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;netappb2*&amp;gt;&lt;BR /&gt;netappb2*&amp;gt; &lt;FONT color="#FF0000"&gt;vol clone create vmfs_lan_20150309213324 -b vmfs_lan smvi__VMFS_LAN_20150309213324&lt;/FONT&gt;&lt;BR /&gt;Creation of clone volume 'vmfs_lan_20150309213324' has completed.&lt;BR /&gt;netappb2*&amp;gt; lun serial /vol/vmfs_lan_20150309213324/vmfs_lan/vmfs_lan&lt;BR /&gt;Serial#: &lt;STRONG&gt;&lt;FONT color="#0000FF"&gt;2Fh5s+ClT/8T&lt;/FONT&gt;&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Thu, 05 Jun 2025 04:17:19 GMT</pubDate>
    <dc:creator>NICOLAS_MELAY</dc:creator>
    <dc:date>2025-06-05T04:17:19Z</dc:date>
    <item>
      <title>LUN serial NOT changed on a vol clone</title>
      <link>https://community.netapp.com/t5/ONTAP-Discussions/LUN-serial-NOT-changed-on-a-vol-clone/m-p/105184#M21543</link>
      <description>&lt;P&gt;Hi all.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I've just hit what I believe is a very serious bug in DOT 8.1.&lt;/P&gt;&lt;P&gt;On a vol clone operation on a LUN container, the cloned LUN kept the same serial number as the original one.&lt;/P&gt;&lt;P&gt;Of course that should never happen, since this basically means remote SAN initiators will see that LUN as just a bunch of new paths to the original LUN.&lt;/P&gt;&lt;P&gt;Experience shows it will make a VMFS datastore collapse.&amp;nbsp; &lt;span class="lia-unicode-emoji" title=":disappointed_face:"&gt;😞&lt;/span&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;DOT version used was Release 8.1.4P3 7-Mode.&lt;/P&gt;&lt;P&gt;No newer 8.1.4 patch release show such a bug as being fixed.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Has anyone experienced this before ?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Here are just a few commands exposing the problem.&lt;/P&gt;&lt;P&gt;&lt;FONT color="#008000"&gt;The first clone operation&lt;/FONT&gt; is when everything goes alright. DOT properly identifies the new LUN as a duplicate, and takes appropriate action.&lt;/P&gt;&lt;P&gt;&lt;FONT color="#FF0000"&gt;The second clone operation&lt;/FONT&gt; went bad : the LUN duplicate went unnoticed (seemingly the vol clone operation did not fully complete), and the resulting LUN has the same serial number as the original one...&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;netappb2*&amp;gt; lun serial /vol/vmfs_lan/vmfs_lan/vmfs_lan&lt;BR /&gt;Serial#: &lt;STRONG&gt;&lt;FONT color="#0000FF"&gt;2Fh5s+ClT/8T&lt;/FONT&gt;&lt;/STRONG&gt;&lt;BR /&gt;netappb2*&amp;gt;&lt;BR /&gt;netappb2*&amp;gt; &lt;FONT color="#008000"&gt;vol clone create vmfs_lan_20150517213001 -b vmfs_lan smvi__VMFS_LAN_20150517213001&lt;/FONT&gt;&lt;BR /&gt;Creation of clone volume 'vmfs_lan_20150517213001' has completed.&lt;BR /&gt;netappb2*&amp;gt; &lt;STRONG&gt;Tue May 19 01:19:50 CEST [netappb2:wafl.volume.clone.created:info]: Volume clone vmfs_lan_20150517213001 of volume vmfs_lan was created successfully.&lt;/STRONG&gt;&lt;BR /&gt;&lt;STRONG&gt;Tue May 19 01:19:50 CEST [netappb2:lun.newLocation.offline:warning]: LUN /vol/vmfs_lan_20150517213001/vmfs_lan/vmfs_lan has been taken offline to prevent map conflicts after a copy or move operation.&lt;/STRONG&gt;&lt;BR /&gt;netappb2*&amp;gt; lun serial /vol/vmfs_lan_20150517213001/vmfs_lan/vmfs_lan&lt;BR /&gt;Serial#: &lt;STRONG&gt;&lt;FONT color="#000000"&gt;2FhNd$GH-t35&lt;/FONT&gt;&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;netappb2*&amp;gt;&lt;BR /&gt;netappb2*&amp;gt; &lt;FONT color="#FF0000"&gt;vol clone create vmfs_lan_20150309213324 -b vmfs_lan smvi__VMFS_LAN_20150309213324&lt;/FONT&gt;&lt;BR /&gt;Creation of clone volume 'vmfs_lan_20150309213324' has completed.&lt;BR /&gt;netappb2*&amp;gt; lun serial /vol/vmfs_lan_20150309213324/vmfs_lan/vmfs_lan&lt;BR /&gt;Serial#: &lt;STRONG&gt;&lt;FONT color="#0000FF"&gt;2Fh5s+ClT/8T&lt;/FONT&gt;&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Thu, 05 Jun 2025 04:17:19 GMT</pubDate>
      <guid>https://community.netapp.com/t5/ONTAP-Discussions/LUN-serial-NOT-changed-on-a-vol-clone/m-p/105184#M21543</guid>
      <dc:creator>NICOLAS_MELAY</dc:creator>
      <dc:date>2025-06-05T04:17:19Z</dc:date>
    </item>
  </channel>
</rss>

