<?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: &amp;quot;no locks available&amp;quot; issue with HP 11.0 in Operating System - HP-UX</title>
    <link>https://community.hpe.com/t5/operating-system-hp-ux/quot-no-locks-available-quot-issue-with-hp-11-0/m-p/3190399#M164576</link>
    <description>If sounds as though nflocks is too small. You will need to increase it and gen a new kernel.&lt;BR /&gt;</description>
    <pubDate>Thu, 12 Feb 2004 10:16:04 GMT</pubDate>
    <dc:creator>A. Clay Stephenson</dc:creator>
    <dc:date>2004-02-12T10:16:04Z</dc:date>
    <item>
      <title>"no locks available" issue with HP 11.0</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/quot-no-locks-available-quot-issue-with-hp-11-0/m-p/3190398#M164575</link>
      <description>I have a server which is expoeriencing frequent situations where jobs/commands fail with error messages relating to file locks.  Some examples are:&lt;BR /&gt;when running bdf I get "bdf: Cannot open /etc/mnttab: No locks available" and when running kmtune "kmtune: Cannot establish mutual exclusive lock".  This si a system-wide problem that occurs for all users.  Has anyone experienced this?&lt;BR /&gt;&lt;BR /&gt;Dave Knoch&lt;BR /&gt;Borders Group Inc</description>
      <pubDate>Thu, 12 Feb 2004 10:11:34 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/quot-no-locks-available-quot-issue-with-hp-11-0/m-p/3190398#M164575</guid>
      <dc:creator>Dave_375</dc:creator>
      <dc:date>2004-02-12T10:11:34Z</dc:date>
    </item>
    <item>
      <title>Re: "no locks available" issue with HP 11.0</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/quot-no-locks-available-quot-issue-with-hp-11-0/m-p/3190399#M164576</link>
      <description>If sounds as though nflocks is too small. You will need to increase it and gen a new kernel.&lt;BR /&gt;</description>
      <pubDate>Thu, 12 Feb 2004 10:16:04 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/quot-no-locks-available-quot-issue-with-hp-11-0/m-p/3190399#M164576</guid>
      <dc:creator>A. Clay Stephenson</dc:creator>
      <dc:date>2004-02-12T10:16:04Z</dc:date>
    </item>
    <item>
      <title>Re: "no locks available" issue with HP 11.0</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/quot-no-locks-available-quot-issue-with-hp-11-0/m-p/3190400#M164577</link>
      <description>I too believe you nflocks kernel parm is the culprit here.&lt;BR /&gt;&lt;BR /&gt;Rgds,&lt;BR /&gt;Jeff</description>
      <pubDate>Thu, 12 Feb 2004 10:18:05 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/quot-no-locks-available-quot-issue-with-hp-11-0/m-p/3190400#M164577</guid>
      <dc:creator>Jeff Schussele</dc:creator>
      <dc:date>2004-02-12T10:18:05Z</dc:date>
    </item>
    <item>
      <title>Re: "no locks available" issue with HP 11.0</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/quot-no-locks-available-quot-issue-with-hp-11-0/m-p/3190401#M164578</link>
      <description>This will be a Kernel parameter issue as pointed out. Check tunable parameters values and increase it to a desired limit and regenerate a new kernel (from SAM). Check these parameters:&lt;BR /&gt;&lt;BR /&gt;nflocks&lt;BR /&gt;nproc&lt;BR /&gt;nfile&lt;BR /&gt;ninode</description>
      <pubDate>Thu, 12 Feb 2004 10:24:57 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/quot-no-locks-available-quot-issue-with-hp-11-0/m-p/3190401#M164578</guid>
      <dc:creator>Helen French</dc:creator>
      <dc:date>2004-02-12T10:24:57Z</dc:date>
    </item>
  </channel>
</rss>

