<?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: Huge flat directories in HPUX 11i in Operating System - HP-UX</title>
    <link>https://community.hpe.com/t5/operating-system-hp-ux/huge-flat-directories-in-hpux-11i/m-p/3021176#M130477</link>
    <description>Massive flat directories is a system design flaw, not an HP-UX problem. It's not an outrageous problem, it's a msunderstanding of how the shell works. For instance, consider these two commands:&lt;BR /&gt;&lt;BR /&gt;ls&lt;BR /&gt;ls *&lt;BR /&gt;&lt;BR /&gt;They seem to perform the same task, yet the first works just fine with millions of file names, but the second fails with an arg list too long message. The key is understanding what * means. It is NOT interpreted by the ls command! The shell sees the * and automatically translates * into the names of every visible file in the current directory and that is passed to the ls command. As you might expect, the resultant command line may be millions of characters long. &lt;BR /&gt;&lt;BR /&gt;Now there was a patch to extend the maximum command line (known as ARG_MAX) from about 20,000 chars to over 2 million. One could argue that ARG_MAX should be billions, but the reality is that it is simply impractical to continue extending the maximum line length for a command. Besides, that's why the xargs command was created.&lt;BR /&gt;&lt;BR /&gt;As every Unix system administrator has discovered, flat filesystems with thousands of files are a nightmare to manage and users must be taught how to work with this unusual configuration. Every task that requires looking at every filename (like ls and ll and find, etc) will take a long time to process, and most important: lots of directory (system) overhead which affects other programs on the system.</description>
    <pubDate>Fri, 11 Jul 2003 10:54:38 GMT</pubDate>
    <dc:creator>Bill Hassell</dc:creator>
    <dc:date>2003-07-11T10:54:38Z</dc:date>
    <item>
      <title>Huge flat directories in HPUX 11i</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/huge-flat-directories-in-hpux-11i/m-p/3021174#M130475</link>
      <description>&lt;BR /&gt;I understand that HP-UX has troubles with *really* *big* directories that containing 100,000 files which is limit by the maximum arguments size that the shell will handle. &lt;BR /&gt;&lt;BR /&gt;I heard that there are some patches released that fixed this outrageous problem. &lt;BR /&gt;&lt;BR /&gt;Does anyone know what these patches number for HPUX 11i and if it is effective in fixing the problem.&lt;BR /&gt;&lt;BR /&gt;</description>
      <pubDate>Fri, 11 Jul 2003 08:59:54 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/huge-flat-directories-in-hpux-11i/m-p/3021174#M130475</guid>
      <dc:creator>YLTan</dc:creator>
      <dc:date>2003-07-11T08:59:54Z</dc:date>
    </item>
    <item>
      <title>Re: Huge flat directories in HPUX 11i</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/huge-flat-directories-in-hpux-11i/m-p/3021175#M130476</link>
      <description>HPUX doesnt have a problem with really big directories. Its all a matter of tuning your filesystem if you do have really big dirs with a lot of files. There have been comments on this forum from customers with millions of files in a dir without problems. &lt;BR /&gt;&lt;BR /&gt;Read these threads;&lt;BR /&gt;&lt;BR /&gt;&lt;A href="http://forums.itrc.hp.com/cm/QuestionAnswer/1,,0xe87a42308663d611abdb0090277a778c,00.html" target="_blank"&gt;http://forums.itrc.hp.com/cm/QuestionAnswer/1,,0xe87a42308663d611abdb0090277a778c,00.html&lt;/A&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;A href="http://forums.itrc.hp.com/cm/QuestionAnswer/1,,0xe87a42308663d611abdb0090277a778c,00.html" target="_blank"&gt;http://forums.itrc.hp.com/cm/QuestionAnswer/1,,0xe87a42308663d611abdb0090277a778c,00.html&lt;/A&gt;&lt;BR /&gt;&lt;BR /&gt;As long as you have the latest VXFS/JFS/LVM patches and take note of some tuning options as in the threads above you will be fine.&lt;BR /&gt;</description>
      <pubDate>Fri, 11 Jul 2003 09:21:46 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/huge-flat-directories-in-hpux-11i/m-p/3021175#M130476</guid>
      <dc:creator>Stefan Farrelly</dc:creator>
      <dc:date>2003-07-11T09:21:46Z</dc:date>
    </item>
    <item>
      <title>Re: Huge flat directories in HPUX 11i</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/huge-flat-directories-in-hpux-11i/m-p/3021176#M130477</link>
      <description>Massive flat directories is a system design flaw, not an HP-UX problem. It's not an outrageous problem, it's a msunderstanding of how the shell works. For instance, consider these two commands:&lt;BR /&gt;&lt;BR /&gt;ls&lt;BR /&gt;ls *&lt;BR /&gt;&lt;BR /&gt;They seem to perform the same task, yet the first works just fine with millions of file names, but the second fails with an arg list too long message. The key is understanding what * means. It is NOT interpreted by the ls command! The shell sees the * and automatically translates * into the names of every visible file in the current directory and that is passed to the ls command. As you might expect, the resultant command line may be millions of characters long. &lt;BR /&gt;&lt;BR /&gt;Now there was a patch to extend the maximum command line (known as ARG_MAX) from about 20,000 chars to over 2 million. One could argue that ARG_MAX should be billions, but the reality is that it is simply impractical to continue extending the maximum line length for a command. Besides, that's why the xargs command was created.&lt;BR /&gt;&lt;BR /&gt;As every Unix system administrator has discovered, flat filesystems with thousands of files are a nightmare to manage and users must be taught how to work with this unusual configuration. Every task that requires looking at every filename (like ls and ll and find, etc) will take a long time to process, and most important: lots of directory (system) overhead which affects other programs on the system.</description>
      <pubDate>Fri, 11 Jul 2003 10:54:38 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/huge-flat-directories-in-hpux-11i/m-p/3021176#M130477</guid>
      <dc:creator>Bill Hassell</dc:creator>
      <dc:date>2003-07-11T10:54:38Z</dc:date>
    </item>
    <item>
      <title>Re: Huge flat directories in HPUX 11i</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/huge-flat-directories-in-hpux-11i/m-p/3021177#M130478</link>
      <description>1) Keep up with any JFS/vxfs patches.&lt;BR /&gt;&lt;BR /&gt;2) This is a management problem.  There is a reason why there is a command mkdir.  Its to make subdirectories.  These huge directories should be reorganized in some logical way.&lt;BR /&gt;&lt;BR /&gt;SEP</description>
      <pubDate>Fri, 11 Jul 2003 11:14:56 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/huge-flat-directories-in-hpux-11i/m-p/3021177#M130478</guid>
      <dc:creator>Steven E. Protter</dc:creator>
      <dc:date>2003-07-11T11:14:56Z</dc:date>
    </item>
  </channel>
</rss>

