<?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: lsof to find worst offender of open files in Operating System - HP-UX</title>
    <link>https://community.hpe.com/t5/operating-system-hp-ux/lsof-to-find-worst-offender-of-open-files/m-p/4035951#M302105</link>
    <description>Thanks Clay.&lt;BR /&gt;&lt;BR /&gt;I pulled the lsof into excel then created a pivot table to count the occurances.  &lt;BR /&gt;&lt;BR /&gt;About the same as you suggested.&lt;BR /&gt;&lt;BR /&gt;Using the output to compare agaist some other systems not having issue to see if I can find some really large differences.&lt;BR /&gt;&lt;BR /&gt;This is a case of pulling down vx_ninode too far to save some memory has caused an issue.  8000 descriptors was enough initially but we have since grown.  I am setting vx_ninode now to NFILE to cover the contingency.&lt;BR /&gt;&lt;BR /&gt;</description>
    <pubDate>Wed, 11 Jul 2007 14:16:04 GMT</pubDate>
    <dc:creator>Tim Nelson</dc:creator>
    <dc:date>2007-07-11T14:16:04Z</dc:date>
    <item>
      <title>lsof to find worst offender of open files</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/lsof-to-find-worst-offender-of-open-files/m-p/4035947#M302101</link>
      <description>I am investigating a recent issue with vx_iget inode table overflow messages and intend on upping my vx_ninode setting this weekend but wanted to investigate who was the worst offender of open inodes.&lt;BR /&gt;&lt;BR /&gt;Looking for help to find a combination of switches in lsof that would help ID the worst offender or any other ideas as well.&lt;BR /&gt;&lt;BR /&gt;HPUX 11.11&lt;BR /&gt;&lt;BR /&gt;Thanks to all !!&lt;BR /&gt;</description>
      <pubDate>Wed, 11 Jul 2007 13:13:18 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/lsof-to-find-worst-offender-of-open-files/m-p/4035947#M302101</guid>
      <dc:creator>Tim Nelson</dc:creator>
      <dc:date>2007-07-11T13:13:18Z</dc:date>
    </item>
    <item>
      <title>Re: lsof to find worst offender of open files</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/lsof-to-find-worst-offender-of-open-files/m-p/4035948#M302102</link>
      <description>I'm not sure lsof is set up to do that?  You'll probably have to do some scripting on the output of all open files on a file system.  Create tuples of PID and file, then sort by PID.&lt;BR /&gt;&lt;BR /&gt;What would you do with that output?  Figure out who you can kill/delay until you change it?</description>
      <pubDate>Wed, 11 Jul 2007 13:19:36 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/lsof-to-find-worst-offender-of-open-files/m-p/4035948#M302102</guid>
      <dc:creator>Dennis Handly</dc:creator>
      <dc:date>2007-07-11T13:19:36Z</dc:date>
    </item>
    <item>
      <title>Re: lsof to find worst offender of open files</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/lsof-to-find-worst-offender-of-open-files/m-p/4035949#M302103</link>
      <description>That is the idea.  If I can releive the pressure until saturday's reboot it would help.&lt;BR /&gt;&lt;BR /&gt;</description>
      <pubDate>Wed, 11 Jul 2007 13:26:54 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/lsof-to-find-worst-offender-of-open-files/m-p/4035949#M302103</guid>
      <dc:creator>Tim Nelson</dc:creator>
      <dc:date>2007-07-11T13:26:54Z</dc:date>
    </item>
    <item>
      <title>Re: lsof to find worst offender of open files</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/lsof-to-find-worst-offender-of-open-files/m-p/4035950#M302104</link>
      <description>Well, here's a script that should do it:&lt;BR /&gt;&lt;BR /&gt;#!/usr/bin/sh&lt;BR /&gt;&lt;BR /&gt;lsof | awk '{if (!($0 ~ /^COMMAND/)) {print $2, $1}}' | uniq -c | sort -rn&lt;BR /&gt;&lt;BR /&gt;If my logic (and syntax) is correct this should print 1 line for each process listing the number of file descriptors, the PID, and the process name sorted in reverse order from the biggest file descriptor hog to the smallest.&lt;BR /&gt;&lt;BR /&gt;I'm willing to bet that some of the biggest file descriptor hogs are also your most critical applications.</description>
      <pubDate>Wed, 11 Jul 2007 14:09:37 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/lsof-to-find-worst-offender-of-open-files/m-p/4035950#M302104</guid>
      <dc:creator>A. Clay Stephenson</dc:creator>
      <dc:date>2007-07-11T14:09:37Z</dc:date>
    </item>
    <item>
      <title>Re: lsof to find worst offender of open files</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/lsof-to-find-worst-offender-of-open-files/m-p/4035951#M302105</link>
      <description>Thanks Clay.&lt;BR /&gt;&lt;BR /&gt;I pulled the lsof into excel then created a pivot table to count the occurances.  &lt;BR /&gt;&lt;BR /&gt;About the same as you suggested.&lt;BR /&gt;&lt;BR /&gt;Using the output to compare agaist some other systems not having issue to see if I can find some really large differences.&lt;BR /&gt;&lt;BR /&gt;This is a case of pulling down vx_ninode too far to save some memory has caused an issue.  8000 descriptors was enough initially but we have since grown.  I am setting vx_ninode now to NFILE to cover the contingency.&lt;BR /&gt;&lt;BR /&gt;</description>
      <pubDate>Wed, 11 Jul 2007 14:16:04 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/lsof-to-find-worst-offender-of-open-files/m-p/4035951#M302105</guid>
      <dc:creator>Tim Nelson</dc:creator>
      <dc:date>2007-07-11T14:16:04Z</dc:date>
    </item>
    <item>
      <title>Re: lsof to find worst offender of open files</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/lsof-to-find-worst-offender-of-open-files/m-p/4035952#M302106</link>
      <description>I'm not familiar with the UNIX excel command and pivot tables. This must be some non-standard utilty that you have developed.</description>
      <pubDate>Wed, 11 Jul 2007 14:25:07 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/lsof-to-find-worst-offender-of-open-files/m-p/4035952#M302106</guid>
      <dc:creator>A. Clay Stephenson</dc:creator>
      <dc:date>2007-07-11T14:25:07Z</dc:date>
    </item>
    <item>
      <title>Re: lsof to find worst offender of open files</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/lsof-to-find-worst-offender-of-open-files/m-p/4035953#M302107</link>
      <description>U2 Funny.&lt;BR /&gt;&lt;BR /&gt;Thanks for the tips..&lt;BR /&gt;&lt;BR /&gt;</description>
      <pubDate>Wed, 11 Jul 2007 14:35:25 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/lsof-to-find-worst-offender-of-open-files/m-p/4035953#M302107</guid>
      <dc:creator>Tim Nelson</dc:creator>
      <dc:date>2007-07-11T14:35:25Z</dc:date>
    </item>
  </channel>
</rss>

