<?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: / filesystem almost full in Operating System - HP-UX</title>
    <link>https://community.hpe.com/t5/operating-system-hp-ux/filesystem-almost-full/m-p/2496542#M830320</link>
    <description>A quick place to look is in the /dev directory.  It's not unusual to see a situation where an application attempts to write to a non-existant device but instead starts filling up a file.</description>
    <pubDate>Wed, 21 Feb 2001 06:34:04 GMT</pubDate>
    <dc:creator>Tim Malnati</dc:creator>
    <dc:date>2001-02-21T06:34:04Z</dc:date>
    <item>
      <title>/ filesystem almost full</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/filesystem-almost-full/m-p/2496540#M830318</link>
      <description>my /filesystem is 140MB...how can I find out what is taking out the space.. I can find any big file under / filesystem</description>
      <pubDate>Wed, 21 Feb 2001 04:07:43 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/filesystem-almost-full/m-p/2496540#M830318</guid>
      <dc:creator>kholikt</dc:creator>
      <dc:date>2001-02-21T04:07:43Z</dc:date>
    </item>
    <item>
      <title>Re: / filesystem almost full</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/filesystem-almost-full/m-p/2496541#M830319</link>
      <description>Hi,&lt;BR /&gt;&lt;BR /&gt;To find files larger than, say, 100000 bytes in the root filesystem, try&lt;BR /&gt;&lt;BR /&gt;find / -xdev -type f -size +100000c | xargs ls -l&lt;BR /&gt;&lt;BR /&gt;The ls command will show you the date the files were last modified.&lt;BR /&gt;&lt;BR /&gt;--Bruce</description>
      <pubDate>Wed, 21 Feb 2001 04:18:45 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/filesystem-almost-full/m-p/2496541#M830319</guid>
      <dc:creator>Bruce Regittko_1</dc:creator>
      <dc:date>2001-02-21T04:18:45Z</dc:date>
    </item>
    <item>
      <title>Re: / filesystem almost full</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/filesystem-almost-full/m-p/2496542#M830320</link>
      <description>A quick place to look is in the /dev directory.  It's not unusual to see a situation where an application attempts to write to a non-existant device but instead starts filling up a file.</description>
      <pubDate>Wed, 21 Feb 2001 06:34:04 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/filesystem-almost-full/m-p/2496542#M830320</guid>
      <dc:creator>Tim Malnati</dc:creator>
      <dc:date>2001-02-21T06:34:04Z</dc:date>
    </item>
    <item>
      <title>Re: / filesystem almost full</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/filesystem-almost-full/m-p/2496543#M830321</link>
      <description>Hi,&lt;BR /&gt;To find out which directory is eating up the most space, you can start a search from root using:&lt;BR /&gt;&lt;BR /&gt;cd /&lt;BR /&gt;du -s * |sort -nk1&lt;BR /&gt;&lt;BR /&gt;The last line will be the directory/file eating up the biggest space of your hardisk.&lt;BR /&gt;&lt;BR /&gt;cd to that particular directory and repeat the du -s * command &lt;BR /&gt;&lt;BR /&gt;regards</description>
      <pubDate>Wed, 21 Feb 2001 06:40:22 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/filesystem-almost-full/m-p/2496543#M830321</guid>
      <dc:creator>mooi-kuan</dc:creator>
      <dc:date>2001-02-21T06:40:22Z</dc:date>
    </item>
    <item>
      <title>Re: / filesystem almost full</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/filesystem-almost-full/m-p/2496544#M830322</link>
      <description>Hi,&lt;BR /&gt;&lt;BR /&gt;You also need to be careful of open files which are "invisible" to du but "visible" to bdf. In this case, your du and bdf results will not tally ie. du will report a smaller usage than bdf.&lt;BR /&gt;&lt;BR /&gt;To identify open files, you can perform an lsof on /. If the open file listed does not exist as a physical file, terminate the process that is holding on to the open file.&lt;BR /&gt;&lt;BR /&gt;This happens especially to logging processes whereby the log file grew too large and was deleted without restarting the process properly, resulting in the process still holding on to the opened log file.&lt;BR /&gt;&lt;BR /&gt;Hope this helps. Regards.&lt;BR /&gt;&lt;BR /&gt;Steven Sim Kok Leong&lt;BR /&gt;Brainbench MVP for Unix Admin&lt;BR /&gt;&lt;A href="http://www.brainbench.com" target="_blank"&gt;http://www.brainbench.com&lt;/A&gt;</description>
      <pubDate>Wed, 21 Feb 2001 06:48:43 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/filesystem-almost-full/m-p/2496544#M830322</guid>
      <dc:creator>Steven Sim Kok Leong</dc:creator>
      <dc:date>2001-02-21T06:48:43Z</dc:date>
    </item>
  </channel>
</rss>

