<?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 resyncing aggr plex in ONTAP Discussions</title>
    <link>https://community.netapp.com/t5/ONTAP-Discussions/resyncing-aggr-plex/m-p/70624#M16468</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;What happens when you loose the loop to the good plex (connection between controller and shelf that has the latest up-to-date WAFL file system) during a aggr resync ?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Thu, 05 Jun 2025 06:46:54 GMT</pubDate>
    <dc:creator>gdefevere</dc:creator>
    <dc:date>2025-06-05T06:46:54Z</dc:date>
    <item>
      <title>resyncing aggr plex</title>
      <link>https://community.netapp.com/t5/ONTAP-Discussions/resyncing-aggr-plex/m-p/70624#M16468</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;What happens when you loose the loop to the good plex (connection between controller and shelf that has the latest up-to-date WAFL file system) during a aggr resync ?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 05 Jun 2025 06:46:54 GMT</pubDate>
      <guid>https://community.netapp.com/t5/ONTAP-Discussions/resyncing-aggr-plex/m-p/70624#M16468</guid>
      <dc:creator>gdefevere</dc:creator>
      <dc:date>2025-06-05T06:46:54Z</dc:date>
    </item>
    <item>
      <title>resyncing aggr plex</title>
      <link>https://community.netapp.com/t5/ONTAP-Discussions/resyncing-aggr-plex/m-p/70628#M16471</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;The same as if you loose the access to disks in a configuration without syncmirror -&amp;gt; downtime. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;What exactly the damage will be depends on the scenario.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 05 Sep 2011 05:39:32 GMT</pubDate>
      <guid>https://community.netapp.com/t5/ONTAP-Discussions/resyncing-aggr-plex/m-p/70628#M16471</guid>
      <dc:creator>pascalduk</dc:creator>
      <dc:date>2011-09-05T05:39:32Z</dc:date>
    </item>
    <item>
      <title>resyncing aggr plex</title>
      <link>https://community.netapp.com/t5/ONTAP-Discussions/resyncing-aggr-plex/m-p/70632#M16474</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt; I'm not convinced about the downtime. But maybe I didn't explain the circumstances very well:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;1. Both plexes are fine, syncmirror between both shelf loops works fine (we have only one loop to each plex).&lt;/P&gt;&lt;P&gt;2. One loop interrupted, no syncmirror between both plexes. But no downtime, since other plex is fine&lt;/P&gt;&lt;P&gt;3. Loop recoverd, syncmirror resync's latest data to the not up-to-data plex. &lt;/P&gt;&lt;P&gt;4. Other loop interrupted, no syncmirror anymore (process interrupted) between both plexes. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;=&amp;gt; WE STILL HAVE ONE PLEX HOWEVER, SO YOU SHOULD EXPECT NO DOWNTIME, BUT THIS PLEX DOESN'T HAVE AN UP-TO-DATE WAFL (since resync wasn't finished yet). &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;QUESTION: what would happen here !?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 05 Sep 2011 08:52:33 GMT</pubDate>
      <guid>https://community.netapp.com/t5/ONTAP-Discussions/resyncing-aggr-plex/m-p/70632#M16474</guid>
      <dc:creator>gdefevere</dc:creator>
      <dc:date>2011-09-05T08:52:33Z</dc:date>
    </item>
    <item>
      <title>Re: resyncing aggr plex</title>
      <link>https://community.netapp.com/t5/ONTAP-Discussions/resyncing-aggr-plex/m-p/70636#M16477</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I would expect Data ONTAP to panic due to multiple disk failures in aggregate. The second plex cannot be used because it is stale. So you suddenly lost your aggregate.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;P.S. just tested in simulator and it panics indeed. I would be &lt;STRONG&gt;greatly&lt;/STRONG&gt; surprised if anything else happened &lt;SPAN __jive_emoticon_name="happy" __jive_macro_name="emoticon" class="jive_macro jive_emote" src="https://community.netapp.com/4.5.5/images/emoticons/happy.gif"&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 05 Sep 2011 13:10:41 GMT</pubDate>
      <guid>https://community.netapp.com/t5/ONTAP-Discussions/resyncing-aggr-plex/m-p/70636#M16477</guid>
      <dc:creator>aborzenkov</dc:creator>
      <dc:date>2011-09-05T13:10:41Z</dc:date>
    </item>
    <item>
      <title>Re: resyncing aggr plex</title>
      <link>https://community.netapp.com/t5/ONTAP-Discussions/resyncing-aggr-plex/m-p/70643#M16482</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;PRE __jive_macro_name="quote" class="jive_text_macro jive_macro_quote"&gt;&lt;P&gt;aborzenkov wrote:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I would expect Data ONTAP to panic due to multiple disk failures in aggregate. The second plex cannot be used because it is stale. So you suddenly lost your aggregate.&lt;/P&gt;&lt;/PRE&gt;&lt;P&gt;&lt;BR /&gt;I can confirm this behaviour. The filer won't use a plex that is out of sync.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 06 Sep 2011 07:13:05 GMT</pubDate>
      <guid>https://community.netapp.com/t5/ONTAP-Discussions/resyncing-aggr-plex/m-p/70643#M16482</guid>
      <dc:creator>jonathon_lanzon</dc:creator>
      <dc:date>2011-09-06T07:13:05Z</dc:date>
    </item>
    <item>
      <title>Re: resyncing aggr plex</title>
      <link>https://community.netapp.com/t5/ONTAP-Discussions/resyncing-aggr-plex/m-p/70647#M16484</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Thanks for the feedback so far ! &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Taking it a little further: so in this scenario if you have a HA config or Metrocluster, it would failover to the ohter node and then go further with the resync operation from there ? &lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 06 Sep 2011 07:23:21 GMT</pubDate>
      <guid>https://community.netapp.com/t5/ONTAP-Discussions/resyncing-aggr-plex/m-p/70647#M16484</guid>
      <dc:creator>gdefevere</dc:creator>
      <dc:date>2011-09-06T07:23:21Z</dc:date>
    </item>
    <item>
      <title>Re: resyncing aggr plex</title>
      <link>https://community.netapp.com/t5/ONTAP-Discussions/resyncing-aggr-plex/m-p/70651#M16486</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Yes, as long as partner has access to both plexes.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 06 Sep 2011 07:25:07 GMT</pubDate>
      <guid>https://community.netapp.com/t5/ONTAP-Discussions/resyncing-aggr-plex/m-p/70651#M16486</guid>
      <dc:creator>aborzenkov</dc:creator>
      <dc:date>2011-09-06T07:25:07Z</dc:date>
    </item>
  </channel>
</rss>

