<?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: files get stange names in windows in ONTAP Discussions</title>
    <link>https://community.netapp.com/t5/ONTAP-Discussions/files-get-stange-names-in-windows/m-p/118833#M25463</link>
    <description>&lt;P&gt;The reason for this is Windows.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;On Windows, you can’t have a file named &lt;STRONG&gt;file&lt;/STRONG&gt; and another file named &lt;STRONG&gt;FILE&lt;/STRONG&gt; in the same folder. The Windows file system isn’t case sensitive, so it treats these names as the same file.&lt;/P&gt;&lt;P&gt;On Linux, the file system is case sensitive. This means that you could have files named &lt;STRONG&gt;file&lt;/STRONG&gt;, &lt;STRONG&gt;File&lt;/STRONG&gt;, and &lt;STRONG&gt;FILE&lt;/STRONG&gt; in the same folder. Each file would have different contents – Linux treats capitalized letters and lower-case letters as different characters.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;This means that the wierd looking files are files that windows could handle.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Fri, 29 Apr 2016 08:39:26 GMT</pubDate>
    <dc:creator>Niclas</dc:creator>
    <dc:date>2016-04-29T08:39:26Z</dc:date>
    <item>
      <title>files get stange names in windows</title>
      <link>https://community.netapp.com/t5/ONTAP-Discussions/files-get-stange-names-in-windows/m-p/118831#M25461</link>
      <description>&lt;P&gt;On a unix style volume when it is cifs/smb mounted to a windows host some file names get a stange naming like ~AHSGT00000&lt;/P&gt;&lt;P&gt;but only some of them.&lt;/P&gt;&lt;P&gt;When you do a listing in linux all file have the correct names.&lt;/P&gt;</description>
      <pubDate>Wed, 04 Jun 2025 21:10:53 GMT</pubDate>
      <guid>https://community.netapp.com/t5/ONTAP-Discussions/files-get-stange-names-in-windows/m-p/118831#M25461</guid>
      <dc:creator>Niclas</dc:creator>
      <dc:date>2025-06-04T21:10:53Z</dc:date>
    </item>
    <item>
      <title>Re: files get stange names in windows</title>
      <link>https://community.netapp.com/t5/ONTAP-Discussions/files-get-stange-names-in-windows/m-p/118833#M25463</link>
      <description>&lt;P&gt;The reason for this is Windows.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;On Windows, you can’t have a file named &lt;STRONG&gt;file&lt;/STRONG&gt; and another file named &lt;STRONG&gt;FILE&lt;/STRONG&gt; in the same folder. The Windows file system isn’t case sensitive, so it treats these names as the same file.&lt;/P&gt;&lt;P&gt;On Linux, the file system is case sensitive. This means that you could have files named &lt;STRONG&gt;file&lt;/STRONG&gt;, &lt;STRONG&gt;File&lt;/STRONG&gt;, and &lt;STRONG&gt;FILE&lt;/STRONG&gt; in the same folder. Each file would have different contents – Linux treats capitalized letters and lower-case letters as different characters.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;This means that the wierd looking files are files that windows could handle.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Fri, 29 Apr 2016 08:39:26 GMT</pubDate>
      <guid>https://community.netapp.com/t5/ONTAP-Discussions/files-get-stange-names-in-windows/m-p/118833#M25463</guid>
      <dc:creator>Niclas</dc:creator>
      <dc:date>2016-04-29T08:39:26Z</dc:date>
    </item>
  </channel>
</rss>

