<?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: / full in Operating System - HP-UX</title>
    <link>https://community.hpe.com/t5/operating-system-hp-ux/full/m-p/3468528#M211311</link>
    <description>Do a bdf. Are all your expected filesystems there. My best guess is that a filesystem is not mounted. This is not normal behavior. NNM's impact on / should be minimal. It is also possible that a symbolic link under /opt or /var that used to point to another filesystem now points only to the mountpoint under /.&lt;BR /&gt;</description>
    <pubDate>Fri, 21 Jan 2005 10:42:59 GMT</pubDate>
    <dc:creator>A. Clay Stephenson</dc:creator>
    <dc:date>2005-01-21T10:42:59Z</dc:date>
    <item>
      <title>/ full</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/full/m-p/3468525#M211308</link>
      <description>I am running a NNM install on a 11.11 machine. Everytime I run the install '/' fills up to 100%.&lt;BR /&gt;&lt;BR /&gt;I cant find the file that is doing it. I checked all '.' files and dirs. I dont see anyting,,,,anywhere in root that is doing this. Anyone seen this before?</description>
      <pubDate>Fri, 21 Jan 2005 10:36:21 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/full/m-p/3468525#M211308</guid>
      <dc:creator>Nobody's Hero</dc:creator>
      <dc:date>2005-01-21T10:36:21Z</dc:date>
    </item>
    <item>
      <title>Re: / full</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/full/m-p/3468526#M211309</link>
      <description>I found it,,,sorry. NNM was populating /etc/OV.</description>
      <pubDate>Fri, 21 Jan 2005 10:39:28 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/full/m-p/3468526#M211309</guid>
      <dc:creator>Nobody's Hero</dc:creator>
      <dc:date>2005-01-21T10:39:28Z</dc:date>
    </item>
    <item>
      <title>Re: / full</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/full/m-p/3468527#M211310</link>
      <description>do a &lt;BR /&gt;du -kx | sort -rn | head &lt;BR /&gt;or &lt;BR /&gt;find / -xdev -size +10000&lt;BR /&gt;both before and after installation, one of these commands should find it.&lt;BR /&gt;You can use diff on the results, but it should be obvious.&lt;BR /&gt;OVO also spills it's Java and other error messages into /etc/rc.log - have a look there.&lt;BR /&gt;&lt;BR /&gt;I won't ask if /tmp is a filesystem of it's own :)&lt;BR /&gt;&lt;BR /&gt;If You found the bad file, don't simply delete it, do a fuser -u on it first, only delete if it's not opened by anything.</description>
      <pubDate>Fri, 21 Jan 2005 10:42:07 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/full/m-p/3468527#M211310</guid>
      <dc:creator>Florian Heigl (new acc)</dc:creator>
      <dc:date>2005-01-21T10:42:07Z</dc:date>
    </item>
    <item>
      <title>Re: / full</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/full/m-p/3468528#M211311</link>
      <description>Do a bdf. Are all your expected filesystems there. My best guess is that a filesystem is not mounted. This is not normal behavior. NNM's impact on / should be minimal. It is also possible that a symbolic link under /opt or /var that used to point to another filesystem now points only to the mountpoint under /.&lt;BR /&gt;</description>
      <pubDate>Fri, 21 Jan 2005 10:42:59 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/full/m-p/3468528#M211311</guid>
      <dc:creator>A. Clay Stephenson</dc:creator>
      <dc:date>2005-01-21T10:42:59Z</dc:date>
    </item>
    <item>
      <title>Re: / full</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/full/m-p/3468529#M211312</link>
      <description>Hi&lt;BR /&gt;&lt;BR /&gt;After trying the above solutions ...if you still have the problem , it could be possible that some process is holding the space ... do an fuser on the / File system &lt;BR /&gt;and see who is accessing it ... if possible try killing / stoping that application / process ... or a reboot will clear the spcae , if it is process related.&lt;BR /&gt;&lt;BR /&gt;Rgds / James&lt;BR /&gt;</description>
      <pubDate>Fri, 21 Jan 2005 16:00:49 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/full/m-p/3468529#M211312</guid>
      <dc:creator>James George_1</dc:creator>
      <dc:date>2005-01-21T16:00:49Z</dc:date>
    </item>
    <item>
      <title>Re: / full</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/full/m-p/3468530#M211313</link>
      <description>if it's /etc/OV directory causing / full, one solution is to create a Symbolic link of /etc/OV and point it to a new created File-System area that has lots of space.&lt;BR /&gt;&lt;BR /&gt;for example... let's suppose /home is a file-system having lot's of Free space.&lt;BR /&gt;&lt;BR /&gt;then create:  /home/OV and link -s the /etc/OV into /home/OV.&lt;BR /&gt;&lt;BR /&gt;you might want to also do this befoe you perform the link:&lt;BR /&gt;&lt;BR /&gt;before link:&lt;BR /&gt;Stop all OV processes&lt;BR /&gt;mv /etc/OV /etc/OV.OLD&lt;BR /&gt;mkdir /home/OV&lt;BR /&gt;ln -s /home/OV /etc/OV&lt;BR /&gt;cd /etc/OV.OLD&lt;BR /&gt;find . -print |cpio -pdmuv /home/OV&lt;BR /&gt;&lt;BR /&gt;now, bring up OV, and it might be writing to /etc/OV, which now points to /home/OV.&lt;BR /&gt;&lt;BR /&gt;again, substitute:  "/home" for a file-system name or a new file-system with lot's of free space.&lt;BR /&gt;&lt;BR /&gt;as an alternative here, if it's a log file that is causing the space problems, you might want to simply link it's parent directory instead.&lt;BR /&gt;&lt;BR /&gt;bol (best of luck)&lt;BR /&gt;&lt;BR /&gt;</description>
      <pubDate>Fri, 21 Jan 2005 19:37:08 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/full/m-p/3468530#M211313</guid>
      <dc:creator>D Block 2</dc:creator>
      <dc:date>2005-01-21T19:37:08Z</dc:date>
    </item>
    <item>
      <title>Re: / full</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/full/m-p/3468531#M211314</link>
      <description>I checked - we don't have /etc/OV on our OV servers. Unfortunately, I'm not administering it, so I can't tell You what they changed to achieve that, and I'm afraid they won't remember anymore.</description>
      <pubDate>Fri, 21 Jan 2005 23:03:30 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/full/m-p/3468531#M211314</guid>
      <dc:creator>Florian Heigl (new acc)</dc:creator>
      <dc:date>2005-01-21T23:03:30Z</dc:date>
    </item>
  </channel>
</rss>

