<?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: filesystems with 100% in Operating System - HP-UX</title>
    <link>https://community.hpe.com/t5/operating-system-hp-ux/filesystems-with-100/m-p/3924070#M286435</link>
    <description>Look close. sometimes there is a .filename or dir. that holds a lot of bytes, sometimes. like a .mozilla&lt;BR /&gt;&lt;BR /&gt;Just a thought.</description>
    <pubDate>Wed, 10 Jan 2007 13:41:18 GMT</pubDate>
    <dc:creator>Nobody's Hero</dc:creator>
    <dc:date>2007-01-10T13:41:18Z</dc:date>
    <item>
      <title>filesystems with 100%</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/filesystems-with-100/m-p/3924068#M286433</link>
      <description>Hi,&lt;BR /&gt;&lt;BR /&gt;This morning I had one filesystem with 64728 Kbytes available space:&lt;BR /&gt;&lt;BR /&gt;/dev/vgPRD/sapdata3 28262400 28197168   64728  100%  24  2024  1% /oracle/PRD/sapdata3&lt;BR /&gt;&lt;BR /&gt;but now is with 0 kbytes&lt;BR /&gt;&lt;BR /&gt;Filesystem          kbytes    used   avail %used Mounted on&lt;BR /&gt;/dev/vgPRD/sapdata3 28262400 28262400 0 100% /oracle/PRD/sapdata3&lt;BR /&gt;&lt;BR /&gt;In this filesystem there are only sap files:&lt;BR /&gt;&lt;BR /&gt;-rw-rw----   1 oraprd     dba        8388616192 Jan 10 17:14 ./prd_3/prd.data3&lt;BR /&gt;-rw-rw----   1 oraprd     dba        8388616192 Jan 10 17:14 ./prd_7/prd.data7&lt;BR /&gt;-rw-rw----   1 oraprd     dba        2097160192 Jan 10 17:13 ./prd_11/prd.data11&lt;BR /&gt;-rw-rw----   1 oraprd     dba        3221233664 Jan 10 17:14 ./prd46c_3/prd46c.data3&lt;BR /&gt;-rw-rw----   1 oraprd     dba        4194312192 Jan 10 14:06 ./temp_1/temp.data1&lt;BR /&gt;-rw-rw----   1 oraprd     dba        2044723200 Jan 10 17:14 ./prd_15/prd.data15&lt;BR /&gt;-rw-rw----   1 oraprd     dba        2044723200 Jan 10 17:14 ./prd_35/prd.data35&lt;BR /&gt;-rw-rw----   1 oraprd     dba        1258283008 Jan 10 17:09 ./prd_38/prd.data38&lt;BR /&gt;-rw-rw----   1 oraprd     dba        650117120 Jan 10 17:09 ./prd_39/prd.data39&lt;BR /&gt;&lt;BR /&gt;and are the same and with the same space that this morning.&lt;BR /&gt;&lt;BR /&gt;I have only this question. What there are in this filesytem that this morning was with 64728 Kbytes available and now it has 0 Kbytes available?&lt;BR /&gt;&lt;BR /&gt;Thanks a lot of!&lt;BR /&gt;Carmen.&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;</description>
      <pubDate>Wed, 10 Jan 2007 11:27:53 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/filesystems-with-100/m-p/3924068#M286433</guid>
      <dc:creator>Carme Torca</dc:creator>
      <dc:date>2007-01-10T11:27:53Z</dc:date>
    </item>
    <item>
      <title>Re: filesystems with 100%</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/filesystems-with-100/m-p/3924069#M286434</link>
      <description>You will have to comb through that filesystem and look for something out of the ordinary .... unusually huge files, or many files that aren't like the others.  You can do an "ls -ltr" on the directory to find the most recent files.  I have also attached a script (that I got from this forum) that I use for this type of thing all the time.  It will tell you exactly how big each directory within a filesystem is and helps you to narrow down the problem.&lt;BR /&gt;&lt;BR /&gt;HTH,&lt;BR /&gt;Sally</description>
      <pubDate>Wed, 10 Jan 2007 11:35:04 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/filesystems-with-100/m-p/3924069#M286434</guid>
      <dc:creator>Coolmar</dc:creator>
      <dc:date>2007-01-10T11:35:04Z</dc:date>
    </item>
    <item>
      <title>Re: filesystems with 100%</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/filesystems-with-100/m-p/3924070#M286435</link>
      <description>Look close. sometimes there is a .filename or dir. that holds a lot of bytes, sometimes. like a .mozilla&lt;BR /&gt;&lt;BR /&gt;Just a thought.</description>
      <pubDate>Wed, 10 Jan 2007 13:41:18 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/filesystems-with-100/m-p/3924070#M286435</guid>
      <dc:creator>Nobody's Hero</dc:creator>
      <dc:date>2007-01-10T13:41:18Z</dc:date>
    </item>
    <item>
      <title>Re: filesystems with 100%</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/filesystems-with-100/m-p/3924071#M286436</link>
      <description>This is a 28 Gb directory so 64 megs is a VERY small part of the directory. I am assuming that the above listing is all there is in the directory. Now two things could have happened:&lt;BR /&gt; &lt;BR /&gt;1. Your application opened one of the files nad made it slightly larger.  &lt;BR /&gt; &lt;BR /&gt;2. The files are for your database and were created as sparse files. This means that there are undefined records and no space is required for these undefined records. However, the database added new records inside the file and additional space was required. This is the most likely scenario.&lt;BR /&gt; &lt;BR /&gt;The fact that the space available is exactly 0 probably means that your application had an error when it ran out of space. The bottom line is that you need a *LOT* more free space than 64 megs. Extend the lvol to 29 or 30 Gb and watch for growth.</description>
      <pubDate>Wed, 10 Jan 2007 14:25:06 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/filesystems-with-100/m-p/3924071#M286436</guid>
      <dc:creator>Bill Hassell</dc:creator>
      <dc:date>2007-01-10T14:25:06Z</dc:date>
    </item>
    <item>
      <title>Re: filesystems with 100%</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/filesystems-with-100/m-p/3924072#M286437</link>
      <description>Hola Carmen COmo estas..&lt;BR /&gt;&lt;BR /&gt;May I suggest the following:&lt;BR /&gt;Find out the content of the directories using the DU command or perhaps the FIND command a follows&lt;BR /&gt;&lt;BR /&gt;du &lt;DIR_PATHNAME&gt;     (in 512K blocks)&lt;BR /&gt;du -k &lt;DIR_PATHNAME&gt;  (in kilobytes)&lt;BR /&gt;&lt;BR /&gt;find &lt;MOUNT-POINT&gt; -size +&lt;MINIMUMSIZE&gt;&lt;/MINIMUMSIZE&gt;-exec ll {} \;&lt;BR /&gt;&lt;BR /&gt;(notic e the "c" at the end  and that I have split the command in two lines with a "\")&lt;BR /&gt;&lt;BR /&gt;This will enable to identify large files and then you could ask your DBA to tell you what kind of data it is.&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;Espero que esto le ayude.. :-)&lt;/MOUNT-POINT&gt;&lt;/DIR_PATHNAME&gt;&lt;/DIR_PATHNAME&gt;</description>
      <pubDate>Wed, 10 Jan 2007 23:25:30 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/filesystems-with-100/m-p/3924072#M286437</guid>
      <dc:creator>Roboz</dc:creator>
      <dc:date>2007-01-10T23:25:30Z</dc:date>
    </item>
  </channel>
</rss>

