<?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 resize isn't always reported to iSCSI clients in ONTAP Discussions</title>
    <link>https://community.netapp.com/t5/ONTAP-Discussions/LUN-resize-isn-t-always-reported-to-iSCSI-clients/m-p/123811#M26528</link>
    <description>&lt;P&gt;We've been debugging this issue a bit more.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;OL&gt;&lt;LI&gt;We found out that the multipath issue is related to &lt;A href="https://bugs.debian.org/580972" target="_self"&gt;https://bugs.debian.org/580972&lt;/A&gt; which is solved in multipath-tools/0.5.0+git0.770e6d0d-3.&lt;/LI&gt;&lt;LI&gt;By tcpdumping we've been able to confirm that the FAS2552 device is sending the "2A 09 CAPACITY DATA HAS CHANGED" message (SCSI Response (Check Condition) LUN:0x00 - Additional Sense Code+Qualifier: Unknown (0x2a09)). It might be an issue in the Linux kernel, Debian 3.16.36-1+deb8u1 in this case. This could already have been solved in later versions of th Linux kernel. We'll report back to this forum post when we upgrade to Debian 9 (Stretch) and the issue is still there and bothering us.&lt;/LI&gt;&lt;/OL&gt;</description>
    <pubDate>Tue, 04 Oct 2016 12:14:42 GMT</pubDate>
    <dc:creator>Pommi</dc:creator>
    <dc:date>2016-10-04T12:14:42Z</dc:date>
    <item>
      <title>LUN resize isn't always reported to iSCSI clients</title>
      <link>https://community.netapp.com/t5/ONTAP-Discussions/LUN-resize-isn-t-always-reported-to-iSCSI-clients/m-p/123700#M26503</link>
      <description>&lt;P&gt;I'm trying to debug something related to iSCSI LUN resizing.&lt;BR /&gt;&lt;BR /&gt;In our setup we use Debian Linux 8 (jessie) with Open-iSCSI and multipath-tools connected to a FAS2552 (ONTAP 8.3.2RC2) device.&lt;BR /&gt;When we resized our LUN from 6 TiB to 14 TiB yesterday some of the paths got in a weird state.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;We noticed that the iSCSI clients (the Debian machines) detect the resize:&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;PRE&gt;kernel: [5606835.845712] sd 1:0:0:0: Capacity data has changed
kernel: [5606842.329394] sd 2:0:0:1: Capacity data has changed&lt;/PRE&gt;&lt;P&gt;This is detected because the FAS2552 device is reporting this via iSCSI ("2A 09 CAPACITY DATA HAS CHANGED").&lt;BR /&gt;&lt;BR /&gt;For some reason we got in this situation:&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;PRE&gt;$ multipath -l
...
size=14T features='4 queue_if_no_path pg_init_retries 50 retain_attached_hw_handle' hwhandler='1 alua' wp=rw
|-+- policy='service-time 0' prio=0 status=active
| `- 3:0:0:0 sdc 8:32 active undef running
`-+- policy='service-time 0' prio=0 status=enabled
  `- #:#:#:# -   #:#  active undef running&lt;/PRE&gt;&lt;P&gt;I'm trying to reproduce this issue by creating a new 50G LUN and resizing the LUN, but the "Capacity data has changed" logline doesn't appear in our logs when we execute the resize.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;In which case does a FAS2552 device report a resize of a LUN exactly? Or in other words, why doen't it report the resize on my 2nd LUN as it did on my 1st yesterday?&lt;/P&gt;</description>
      <pubDate>Wed, 04 Jun 2025 18:51:28 GMT</pubDate>
      <guid>https://community.netapp.com/t5/ONTAP-Discussions/LUN-resize-isn-t-always-reported-to-iSCSI-clients/m-p/123700#M26503</guid>
      <dc:creator>Pommi</dc:creator>
      <dc:date>2025-06-04T18:51:28Z</dc:date>
    </item>
    <item>
      <title>Re: LUN resize isn't always reported to iSCSI clients</title>
      <link>https://community.netapp.com/t5/ONTAP-Discussions/LUN-resize-isn-t-always-reported-to-iSCSI-clients/m-p/123811#M26528</link>
      <description>&lt;P&gt;We've been debugging this issue a bit more.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;OL&gt;&lt;LI&gt;We found out that the multipath issue is related to &lt;A href="https://bugs.debian.org/580972" target="_self"&gt;https://bugs.debian.org/580972&lt;/A&gt; which is solved in multipath-tools/0.5.0+git0.770e6d0d-3.&lt;/LI&gt;&lt;LI&gt;By tcpdumping we've been able to confirm that the FAS2552 device is sending the "2A 09 CAPACITY DATA HAS CHANGED" message (SCSI Response (Check Condition) LUN:0x00 - Additional Sense Code+Qualifier: Unknown (0x2a09)). It might be an issue in the Linux kernel, Debian 3.16.36-1+deb8u1 in this case. This could already have been solved in later versions of th Linux kernel. We'll report back to this forum post when we upgrade to Debian 9 (Stretch) and the issue is still there and bothering us.&lt;/LI&gt;&lt;/OL&gt;</description>
      <pubDate>Tue, 04 Oct 2016 12:14:42 GMT</pubDate>
      <guid>https://community.netapp.com/t5/ONTAP-Discussions/LUN-resize-isn-t-always-reported-to-iSCSI-clients/m-p/123811#M26528</guid>
      <dc:creator>Pommi</dc:creator>
      <dc:date>2016-10-04T12:14:42Z</dc:date>
    </item>
  </channel>
</rss>

