<?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: Volume and Qtree name changed with Letter case sentive in ONTAP Hardware</title>
    <link>https://community.netapp.com/t5/ONTAP-Hardware/Volume-and-Qtree-name-changed-with-Letter-case-sentive/m-p/161760#M10542</link>
    <description>&lt;P&gt;Hello,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;File names are case-sensitive for NFS clients and case-insensitive but case-preserving for CIFS clients.&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;&lt;P class="p"&gt;For example, if a CIFS client creates&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;SPAN class="ph filepath"&gt;Spec.txt&lt;/SPAN&gt;, both CIFS and NFS clients display the file name as&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;SPAN class="ph filepath"&gt;Spec.txt&lt;/SPAN&gt;. However, if a CIFS user later tries to create&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;SPAN class="ph filepath"&gt;spec.txt&lt;/SPAN&gt;, the name is not allowed because, to the CIFS client, that name currently exists. If an NFS user later creates a file named&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;SPAN class="ph filepath"&gt;spec.txt&lt;/SPAN&gt;, NFS and CIFS clients display the file name differently, as follows:&lt;/P&gt;&lt;UL class="ul"&gt;&lt;LI&gt;On NFS clients, you see both file names as they were created,&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;SPAN class="ph filepath"&gt;Spec.txt&lt;/SPAN&gt;&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;and&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;SPAN class="ph filepath"&gt;spec.txt&lt;/SPAN&gt;, because file names are case-sensitive.&lt;/LI&gt;&lt;LI&gt;&lt;P class="p"&gt;On CIFS clients, you see&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;SPAN class="ph filepath"&gt;Spec.txt&lt;/SPAN&gt;&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;and&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;SPAN class="ph filepath"&gt;Spec~1.txt&lt;/SPAN&gt;.&lt;/P&gt;&lt;P class="p"&gt;Data ONTAP creates the&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;SPAN class="ph filepath"&gt;Spec~1.txt&lt;/SPAN&gt;&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;file name to differentiate the two files.&lt;/P&gt;&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;Was the name change done manually? Can you provide more details on the issue that you are facing..&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thanks&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Fri, 04 Dec 2020 06:59:17 GMT</pubDate>
    <dc:creator>hmoubara</dc:creator>
    <dc:date>2020-12-04T06:59:17Z</dc:date>
    <item>
      <title>Volume and Qtree name changed with Letter case sentive</title>
      <link>https://community.netapp.com/t5/ONTAP-Hardware/Volume-and-Qtree-name-changed-with-Letter-case-sentive/m-p/161736#M10539</link>
      <description>&lt;P&gt;Hi All,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;We have one device running the data Ontap 8.2.4P2 and we had a request on creating the volume and qtree for NFS request.&lt;/P&gt;&lt;P&gt;I have successfully done and even mapped to the Red hat Linux server that this was around June 2020. We had an issue last week in Nov 2020 that name change (Only one letter in that volume and qtree change from Upper case to Lower case). The main issue is we do not have support from Netapp as client migrating the environment from Netapp to EMC.&lt;/P&gt;&lt;P&gt;I requesting your help on this.&lt;/P&gt;&lt;P&gt;Hence I was looking for the Bugs but unable to find that.&lt;/P&gt;</description>
      <pubDate>Wed, 04 Jun 2025 10:43:02 GMT</pubDate>
      <guid>https://community.netapp.com/t5/ONTAP-Hardware/Volume-and-Qtree-name-changed-with-Letter-case-sentive/m-p/161736#M10539</guid>
      <dc:creator>Rama-Krishna</dc:creator>
      <dc:date>2025-06-04T10:43:02Z</dc:date>
    </item>
    <item>
      <title>Re: Volume and Qtree name changed with Letter case sentive</title>
      <link>https://community.netapp.com/t5/ONTAP-Hardware/Volume-and-Qtree-name-changed-with-Letter-case-sentive/m-p/161760#M10542</link>
      <description>&lt;P&gt;Hello,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;File names are case-sensitive for NFS clients and case-insensitive but case-preserving for CIFS clients.&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;&lt;P class="p"&gt;For example, if a CIFS client creates&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;SPAN class="ph filepath"&gt;Spec.txt&lt;/SPAN&gt;, both CIFS and NFS clients display the file name as&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;SPAN class="ph filepath"&gt;Spec.txt&lt;/SPAN&gt;. However, if a CIFS user later tries to create&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;SPAN class="ph filepath"&gt;spec.txt&lt;/SPAN&gt;, the name is not allowed because, to the CIFS client, that name currently exists. If an NFS user later creates a file named&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;SPAN class="ph filepath"&gt;spec.txt&lt;/SPAN&gt;, NFS and CIFS clients display the file name differently, as follows:&lt;/P&gt;&lt;UL class="ul"&gt;&lt;LI&gt;On NFS clients, you see both file names as they were created,&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;SPAN class="ph filepath"&gt;Spec.txt&lt;/SPAN&gt;&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;and&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;SPAN class="ph filepath"&gt;spec.txt&lt;/SPAN&gt;, because file names are case-sensitive.&lt;/LI&gt;&lt;LI&gt;&lt;P class="p"&gt;On CIFS clients, you see&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;SPAN class="ph filepath"&gt;Spec.txt&lt;/SPAN&gt;&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;and&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;SPAN class="ph filepath"&gt;Spec~1.txt&lt;/SPAN&gt;.&lt;/P&gt;&lt;P class="p"&gt;Data ONTAP creates the&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;SPAN class="ph filepath"&gt;Spec~1.txt&lt;/SPAN&gt;&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;file name to differentiate the two files.&lt;/P&gt;&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;Was the name change done manually? Can you provide more details on the issue that you are facing..&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thanks&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Fri, 04 Dec 2020 06:59:17 GMT</pubDate>
      <guid>https://community.netapp.com/t5/ONTAP-Hardware/Volume-and-Qtree-name-changed-with-Letter-case-sentive/m-p/161760#M10542</guid>
      <dc:creator>hmoubara</dc:creator>
      <dc:date>2020-12-04T06:59:17Z</dc:date>
    </item>
    <item>
      <title>Re: Volume and Qtree name changed with Letter case sentive</title>
      <link>https://community.netapp.com/t5/ONTAP-Hardware/Volume-and-Qtree-name-changed-with-Letter-case-sentive/m-p/162136#M10566</link>
      <description>&lt;P&gt;Did you mean that the name changed by itself? or you had problem accessing data after manually changed the name?&lt;/P&gt;</description>
      <pubDate>Tue, 15 Dec 2020 08:45:54 GMT</pubDate>
      <guid>https://community.netapp.com/t5/ONTAP-Hardware/Volume-and-Qtree-name-changed-with-Letter-case-sentive/m-p/162136#M10566</guid>
      <dc:creator>Mjizzini</dc:creator>
      <dc:date>2020-12-15T08:45:54Z</dc:date>
    </item>
  </channel>
</rss>

