<?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: file system full in Operating System - HP-UX</title>
    <link>https://community.hpe.com/t5/operating-system-hp-ux/file-system-full/m-p/3686121#M246209</link>
    <description>Generally this happens when a process creates temporary files, unlinks them, and when this process dies the files close and the space is freed. When you ran the df command all was well; if you had run df just before the errors were logged the filesystem would have been almost full.</description>
    <pubDate>Tue, 06 Dec 2005 20:35:22 GMT</pubDate>
    <dc:creator>A. Clay Stephenson</dc:creator>
    <dc:date>2005-12-06T20:35:22Z</dc:date>
    <item>
      <title>file system full</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/file-system-full/m-p/3686120#M246208</link>
      <description>Strangily, Idon't understand why does lvol have sufficient space  looks like full?&lt;BR /&gt;/dev/vg01/lvol2    8929280 7051484 1761050   80% /var/opt/OV&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt; Dec  6 23:04:02 imis_sms vmunix: msgcnt 254569 vxfs: mesg 001: vx_nospace - /dev/vg01/lvol2 file system full (8 block extent)&lt;BR /&gt;Dec  6 23:04:08 imis_sms vmunix: msgcnt 254571 vxfs: mesg 001: vx_nospace - /dev/vg01/lvol2 file system full (8 block extent)&lt;BR /&gt;</description>
      <pubDate>Tue, 06 Dec 2005 20:16:12 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/file-system-full/m-p/3686120#M246208</guid>
      <dc:creator>???_185</dc:creator>
      <dc:date>2005-12-06T20:16:12Z</dc:date>
    </item>
    <item>
      <title>Re: file system full</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/file-system-full/m-p/3686121#M246209</link>
      <description>Generally this happens when a process creates temporary files, unlinks them, and when this process dies the files close and the space is freed. When you ran the df command all was well; if you had run df just before the errors were logged the filesystem would have been almost full.</description>
      <pubDate>Tue, 06 Dec 2005 20:35:22 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/file-system-full/m-p/3686121#M246209</guid>
      <dc:creator>A. Clay Stephenson</dc:creator>
      <dc:date>2005-12-06T20:35:22Z</dc:date>
    </item>
    <item>
      <title>Re: file system full</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/file-system-full/m-p/3686122#M246210</link>
      <description>Dear Zungwon,&lt;BR /&gt;&lt;BR /&gt;As Clay said, every process reserves/locks some space in disk while it is running. This will be freed up once the process dies and the reserved space may not be shown in bdf also.Thats the reason you bdf shows free space and still you get the nospace error.&lt;BR /&gt;&lt;BR /&gt;With Regards,&lt;BR /&gt;&lt;BR /&gt;Siva</description>
      <pubDate>Tue, 06 Dec 2005 23:22:00 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/file-system-full/m-p/3686122#M246210</guid>
      <dc:creator>Sivakumar TS</dc:creator>
      <dc:date>2005-12-06T23:22:00Z</dc:date>
    </item>
    <item>
      <title>Re: file system full</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/file-system-full/m-p/3686123#M246211</link>
      <description>hi,&lt;BR /&gt;&lt;BR /&gt;it might also be time to purge your old log files from /var.&lt;BR /&gt;&lt;BR /&gt;kind regards&lt;BR /&gt;yogeeraj</description>
      <pubDate>Tue, 06 Dec 2005 23:41:11 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/file-system-full/m-p/3686123#M246211</guid>
      <dc:creator>Yogeeraj_1</dc:creator>
      <dc:date>2005-12-06T23:41:11Z</dc:date>
    </item>
    <item>
      <title>Re: file system full</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/file-system-full/m-p/3686124#M246212</link>
      <description>Also - if you deleted files that were open - well - that space won't be reclaimed until the process goes away...&lt;BR /&gt;&lt;BR /&gt;Rgds...Geoff</description>
      <pubDate>Tue, 06 Dec 2005 23:43:37 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/file-system-full/m-p/3686124#M246212</guid>
      <dc:creator>Geoff Wild</dc:creator>
      <dc:date>2005-12-06T23:43:37Z</dc:date>
    </item>
    <item>
      <title>Re: file system full</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/file-system-full/m-p/3686125#M246213</link>
      <description>BDF is current capacity.</description>
      <pubDate>Wed, 07 Dec 2005 03:01:08 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/file-system-full/m-p/3686125#M246213</guid>
      <dc:creator>leaon_1</dc:creator>
      <dc:date>2005-12-07T03:01:08Z</dc:date>
    </item>
    <item>
      <title>Re: file system full</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/file-system-full/m-p/3686126#M246214</link>
      <description>"bdf" and "du -s" display different size: space process bound DocId: TBRIXKBRC00001367   Updated: 4/16/04 11:20:00 AM &lt;BR /&gt;&lt;BR /&gt;PROBLEM&lt;BR /&gt;The filesystem has filled up, so action was taken to delete 800MB of logfiles.&lt;BR /&gt;&lt;BR /&gt;The command:&lt;BR /&gt;"du -s" &lt;BR /&gt;&lt;BR /&gt;shows the space as 'freed' but "bdf" doesn't. How can that  be?                          &lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;CONFIGURATION&lt;BR /&gt;hpux 10.x 10.20 11.x s700&lt;BR /&gt;s800&lt;BR /&gt;RESOLUTION&lt;BR /&gt;&lt;BR /&gt;Obviously there is a difference in how du and bdf behave.&lt;BR /&gt;This may occur if we touch open files.&lt;BR /&gt;&lt;BR /&gt;"du" shows output in a positive view: it shows the number of currently allocated&lt;BR /&gt;blocks and counts the blocks you've just deleted as free.&lt;BR /&gt;"bdf" has a more negative perspective: it shows the free disk space available.&lt;BR /&gt;&lt;BR /&gt;The difference is here: if a still-active process has allocated blocks (such as&lt;BR /&gt;for a logfile that you've just deleted), "bdf" counts these as still occupied.&lt;BR /&gt;This won't change until the process closes the file ("deallocates the blocks")&lt;BR /&gt;as it usually happens when the process terminates.  &lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;ALT KEYWORDS&lt;BR /&gt;fs vxfs jfs hfs space display difference delete remove free&lt;BR /&gt;up&lt;BR /&gt;&lt;BR /&gt;Good Luck,</description>
      <pubDate>Wed, 07 Dec 2005 04:58:05 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/file-system-full/m-p/3686126#M246214</guid>
      <dc:creator>Cem Tugrul</dc:creator>
      <dc:date>2005-12-07T04:58:05Z</dc:date>
    </item>
  </channel>
</rss>

