<?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 root partition full in Operating System - HP-UX</title>
    <link>https://community.hpe.com/t5/operating-system-hp-ux/root-partition-full/m-p/2572321#M873486</link>
    <description>I can't seem to find out where all the space in root went to. I was doing backups last night and root filled up around the same time - can't figure out where to start cleaning up.</description>
    <pubDate>Wed, 29 Aug 2001 17:06:42 GMT</pubDate>
    <dc:creator>Kerilyn O'Donnell</dc:creator>
    <dc:date>2001-08-29T17:06:42Z</dc:date>
    <item>
      <title>root partition full</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/root-partition-full/m-p/2572321#M873486</link>
      <description>I can't seem to find out where all the space in root went to. I was doing backups last night and root filled up around the same time - can't figure out where to start cleaning up.</description>
      <pubDate>Wed, 29 Aug 2001 17:06:42 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/root-partition-full/m-p/2572321#M873486</guid>
      <dc:creator>Kerilyn O'Donnell</dc:creator>
      <dc:date>2001-08-29T17:06:42Z</dc:date>
    </item>
    <item>
      <title>Re: root partition full</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/root-partition-full/m-p/2572322#M873487</link>
      <description>I would start by looking for core files.  Then I would look for any log files, especially ones that are MBs in size.&lt;BR /&gt;&lt;BR /&gt;Chris</description>
      <pubDate>Wed, 29 Aug 2001 17:12:43 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/root-partition-full/m-p/2572322#M873487</guid>
      <dc:creator>Christopher McCray_1</dc:creator>
      <dc:date>2001-08-29T17:12:43Z</dc:date>
    </item>
    <item>
      <title>Re: root partition full</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/root-partition-full/m-p/2572323#M873488</link>
      <description>Hi Kerilyn,&lt;BR /&gt;I am sure you mistype something in backup if this happen just after you start backup&lt;BR /&gt;&lt;BR /&gt;/dev/rmt/ has all your space.&lt;BR /&gt;Some how your backup didn't went to tape but as a file in to the /dev/rmt/c?t?d????&lt;BR /&gt;&lt;BR /&gt;Sachin</description>
      <pubDate>Wed, 29 Aug 2001 17:16:55 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/root-partition-full/m-p/2572323#M873488</guid>
      <dc:creator>Sachin Patel</dc:creator>
      <dc:date>2001-08-29T17:16:55Z</dc:date>
    </item>
    <item>
      <title>Re: root partition full</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/root-partition-full/m-p/2572324#M873489</link>
      <description>Run lsof and redirect the output &amp;gt; /tmp/lsof.out &lt;BR /&gt;Look for entries that have /dev/dsk/vg## in the last column these are processes that can still be writing even though space has been cleared up. In my case it was a glance process. An example of the lsof is &lt;BR /&gt;emsagent 1502 root 0w VREG 64,0x2 47387 1884 / (/dev/vg00/l &lt;BR /&gt;vol3) &lt;BR /&gt;where=emsagent is the process name &lt;BR /&gt;1502= is the process number &lt;BR /&gt;/ = the filesystem that is being written to &lt;BR /&gt;/dev/vg00/lvol3=gives an inidication that the problem could be there. &lt;BR /&gt;&lt;BR /&gt;By killing the process giving me problems I went from 97% full to 65%. &lt;BR /&gt;&lt;BR /&gt;Hope this helps. &lt;BR /&gt;nancy</description>
      <pubDate>Wed, 29 Aug 2001 17:20:08 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/root-partition-full/m-p/2572324#M873489</guid>
      <dc:creator>nancy rippey</dc:creator>
      <dc:date>2001-08-29T17:20:08Z</dc:date>
    </item>
    <item>
      <title>Re: root partition full</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/root-partition-full/m-p/2572325#M873490</link>
      <description>Hi Kerilyn:&lt;BR /&gt;&lt;BR /&gt;Generally, core file is the first thing to check if I were you, &lt;BR /&gt;&lt;BR /&gt;find / -name core -exec ll {} \;&lt;BR /&gt;&lt;BR /&gt;Another point: you can use search function of this forums, just put "full" as key word, I am sure you can find more useful threads.&lt;BR /&gt;&lt;BR /&gt;Good luck.&lt;BR /&gt;&lt;BR /&gt;</description>
      <pubDate>Wed, 29 Aug 2001 17:30:36 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/root-partition-full/m-p/2572325#M873490</guid>
      <dc:creator>Victor_5</dc:creator>
      <dc:date>2001-08-29T17:30:36Z</dc:date>
    </item>
    <item>
      <title>Re: root partition full</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/root-partition-full/m-p/2572326#M873491</link>
      <description>Hi Kerilyn:&lt;BR /&gt;&lt;BR /&gt;If you were doing backups when your root filesystem space disappeared, it is very likely that you mis-keyed the tape device file name, leading to the creation of a large, space-consuming file.&lt;BR /&gt;&lt;BR /&gt;A common typographical error would be substituting the letter "o" for the number "0" as in "/dev/rmt/om" instead of "/dev/rmt/0m".&lt;BR /&gt;&lt;BR /&gt;Look for regular files in the /dev/rmt directory that don't belong.  Remember that files in this directory should be character special files, not regular files, and thus should have modes that look like "crw-rw-rw-".&lt;BR /&gt;&lt;BR /&gt;Regards!&lt;BR /&gt;&lt;BR /&gt;...JRF...</description>
      <pubDate>Wed, 29 Aug 2001 17:39:37 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/root-partition-full/m-p/2572326#M873491</guid>
      <dc:creator>James R. Ferguson</dc:creator>
      <dc:date>2001-08-29T17:39:37Z</dc:date>
    </item>
    <item>
      <title>Re: root partition full</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/root-partition-full/m-p/2572327#M873492</link>
      <description>Usually when you run out of space it is one or two &lt;BR /&gt;large files.  The command &lt;BR /&gt;    du -a | sort -r -n | more&lt;BR /&gt;usually lists the problem file in the first few entries.&lt;BR /&gt;&lt;BR /&gt;As noted above if you see a file in /dev here a file &lt;BR /&gt;got lost on its way to a device.&lt;BR /&gt;&lt;BR /&gt;If space doesn't open up when you delete the file&lt;BR /&gt;check to make sure there isn't a process writting &lt;BR /&gt;to the file.  lsof is the tool of choice.</description>
      <pubDate>Wed, 29 Aug 2001 22:31:25 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/root-partition-full/m-p/2572327#M873492</guid>
      <dc:creator>Bill Thorsteinson</dc:creator>
      <dc:date>2001-08-29T22:31:25Z</dc:date>
    </item>
    <item>
      <title>Re: root partition full</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/root-partition-full/m-p/2572328#M873493</link>
      <description>Hi Kerylin,&lt;BR /&gt;try this little shell-script to find out your &lt;BR /&gt;largest files.&lt;BR /&gt;</description>
      <pubDate>Thu, 30 Aug 2001 03:04:54 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/root-partition-full/m-p/2572328#M873493</guid>
      <dc:creator>Joachim DIESTEL</dc:creator>
      <dc:date>2001-08-30T03:04:54Z</dc:date>
    </item>
  </channel>
</rss>

