<?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: exportfs -a causes VCS panic in ONTAP Discussions</title>
    <link>https://community.netapp.com/t5/ONTAP-Discussions/exportfs-a-causes-VCS-panic/m-p/17067#M3997</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Because these kind of problems in the past I never use exportfs -a, but only use exportfs for the volumes/qtrees that changed.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;And even though exportfs -a does not unexport unchanged entries and the manuals say it is safe, the access cache for all entries is flushed just like running exportfs -f. This is bad because all host lookups need to be re-looked up and, depending on the workload, this can cause permission denied problems.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Therefore you should change your way of working and only re-export changed entries only on at a time.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Wed, 17 Jun 2009 06:17:16 GMT</pubDate>
    <dc:creator>pascalduk</dc:creator>
    <dc:date>2009-06-17T06:17:16Z</dc:date>
    <item>
      <title>exportfs -a causes VCS panic</title>
      <link>https://community.netapp.com/t5/ONTAP-Discussions/exportfs-a-causes-VCS-panic/m-p/17053#M3989</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Has anyone seen this?&amp;nbsp; I create new volumes on the appliance, modify the exports file and then do an "exportfs -a".&amp;nbsp; At that point Veritas Cluster Services log an error&amp;nbsp; &lt;!--[if gte mso 10]&gt;&lt;style&gt; /* Style Definitions */ table.MsoNormalTable {mso-style-name:"Table Normal"; mso-tstyle-rowband-size:0; mso-tstyle-colband-size:0; mso-style-noshow:yes; mso-style-priority:99; mso-style-qformat:yes; mso-style-parent:""; mso-padding-alt:0in 5.4pt 0in 5.4pt; mso-para-margin:0in; mso-para-margin-bottom:.0001pt; mso-pagination:widow-orphan; font-size:11.0pt; font-family:"Calibri","sans-serif"; mso-ascii-font-family:Calibri; mso-ascii-theme-font:minor-latin; mso-fareast-font-family:"Times New Roman"; mso-fareast-theme-font:minor-fareast; mso-hansi-font-family:Calibri; mso-hansi-theme-font:minor-latin;}&lt;/style&gt;&lt;![endif]--&gt;&lt;SPAN style="font-size: 11pt; font-family: &amp;amp;quot;Calibri&amp;amp;quot;,&amp;amp;quot;sans-serif&amp;amp;quot;;"&gt;"5 06:39:00 [host name] nfs: [ID 897781 kern.notice] NFS write error on host [filer name]: Permission denied."&amp;nbsp; At this point the database crashes and fails over to another host.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;This doesn't seem like it should be happening.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;System: FAS3140c&lt;/P&gt;&lt;P&gt;OnTap: 7.3.1&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 05 Jun 2025 07:28:28 GMT</pubDate>
      <guid>https://community.netapp.com/t5/ONTAP-Discussions/exportfs-a-causes-VCS-panic/m-p/17053#M3989</guid>
      <dc:creator>seno</dc:creator>
      <dc:date>2025-06-05T07:28:28Z</dc:date>
    </item>
    <item>
      <title>Re: exportfs -a causes VCS panic</title>
      <link>https://community.netapp.com/t5/ONTAP-Discussions/exportfs-a-causes-VCS-panic/m-p/17058#M3991</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;What are the mount options on the host side? If you use "exportfs -av" what is the output shown?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 05 May 2009 16:49:59 GMT</pubDate>
      <guid>https://community.netapp.com/t5/ONTAP-Discussions/exportfs-a-causes-VCS-panic/m-p/17058#M3991</guid>
      <dc:creator>chriskranz</dc:creator>
      <dc:date>2009-05-05T16:49:59Z</dc:date>
    </item>
    <item>
      <title>Re: exportfs -a causes VCS panic</title>
      <link>https://community.netapp.com/t5/ONTAP-Discussions/exportfs-a-causes-VCS-panic/m-p/17063#M3994</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;What does your exports file entry look like for the volume/qtree in question?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 16 Jun 2009 17:28:19 GMT</pubDate>
      <guid>https://community.netapp.com/t5/ONTAP-Discussions/exportfs-a-causes-VCS-panic/m-p/17063#M3994</guid>
      <dc:creator>byakimowicz</dc:creator>
      <dc:date>2009-06-16T17:28:19Z</dc:date>
    </item>
    <item>
      <title>Re: exportfs -a causes VCS panic</title>
      <link>https://community.netapp.com/t5/ONTAP-Discussions/exportfs-a-causes-VCS-panic/m-p/17067#M3997</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Because these kind of problems in the past I never use exportfs -a, but only use exportfs for the volumes/qtrees that changed.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;And even though exportfs -a does not unexport unchanged entries and the manuals say it is safe, the access cache for all entries is flushed just like running exportfs -f. This is bad because all host lookups need to be re-looked up and, depending on the workload, this can cause permission denied problems.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Therefore you should change your way of working and only re-export changed entries only on at a time.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 17 Jun 2009 06:17:16 GMT</pubDate>
      <guid>https://community.netapp.com/t5/ONTAP-Discussions/exportfs-a-causes-VCS-panic/m-p/17067#M3997</guid>
      <dc:creator>pascalduk</dc:creator>
      <dc:date>2009-06-17T06:17:16Z</dc:date>
    </item>
    <item>
      <title>Re: exportfs -a causes VCS panic</title>
      <link>https://community.netapp.com/t5/ONTAP-Discussions/exportfs-a-causes-VCS-panic/m-p/17073#M4000</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Thanks Pascal.&amp;nbsp; This is the method we decided on, as we can't have our production VCS cluster going down.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 17 Jun 2009 10:49:51 GMT</pubDate>
      <guid>https://community.netapp.com/t5/ONTAP-Discussions/exportfs-a-causes-VCS-panic/m-p/17073#M4000</guid>
      <dc:creator>seno</dc:creator>
      <dc:date>2009-06-17T10:49:51Z</dc:date>
    </item>
    <item>
      <title>Re: exportfs -a causes VCS panic</title>
      <link>https://community.netapp.com/t5/ONTAP-Discussions/exportfs-a-causes-VCS-panic/m-p/17078#M4003</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Not sure if this helps or not, but we found this bug which is supposedly fixed, but we see almost the exact same behavior.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;bugid - 155052&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;We have seen this specific issue about 8 times in the past few years.&amp;nbsp; It has caused some substantial outages.&amp;nbsp; The most recent was last week.&amp;nbsp; We are only exporting specifc qtrees now.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 23 Jun 2009 14:17:35 GMT</pubDate>
      <guid>https://community.netapp.com/t5/ONTAP-Discussions/exportfs-a-causes-VCS-panic/m-p/17078#M4003</guid>
      <dc:creator>byakimowicz</dc:creator>
      <dc:date>2009-06-23T14:17:35Z</dc:date>
    </item>
  </channel>
</rss>

