<?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 inode error in Operating System - HP-UX</title>
    <link>https://community.hpe.com/t5/operating-system-hp-ux/filesystem-inode-error/m-p/2501073#M20907</link>
    <description>Yes, my command was shutdown -nr</description>
    <pubDate>Mon, 05 Mar 2001 17:50:05 GMT</pubDate>
    <dc:creator>nancy rippey</dc:creator>
    <dc:date>2001-03-05T17:50:05Z</dc:date>
    <item>
      <title>Filesystem inode error</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/filesystem-inode-error/m-p/2501071#M20905</link>
      <description>I am recieving an inode error under var.  I unmounted var and ran an fsck which fixed some damage, I then reran fsck and /var was clean.  When the server booted I still receive the inode error.  I have been able to track it down to a file under /var/spool/sockets/pwgr.  The file does not exist but I tried a rm -r anyway and the response was that it does not exist, as root I then tried to touch the file but recieve 'cannot create', I can touch other files no problem.&lt;BR /&gt;I have run the vsfs version of fsam for extent reorg. but am still having the problem.  Any ideas?</description>
      <pubDate>Mon, 05 Mar 2001 17:00:48 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/filesystem-inode-error/m-p/2501071#M20905</guid>
      <dc:creator>nancy rippey</dc:creator>
      <dc:date>2001-03-05T17:00:48Z</dc:date>
    </item>
    <item>
      <title>Re: Filesystem inode error</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/filesystem-inode-error/m-p/2501072#M20906</link>
      <description>when you rebooted, did you use the "reboot -n" command?  the HP manuals say that you need to to do this otherwise the changes that were made by the fsck don't get saved because the "reboot" command runs the sync command, which undo the changes.</description>
      <pubDate>Mon, 05 Mar 2001 17:07:29 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/filesystem-inode-error/m-p/2501072#M20906</guid>
      <dc:creator>Mark Vollmers</dc:creator>
      <dc:date>2001-03-05T17:07:29Z</dc:date>
    </item>
    <item>
      <title>Re: Filesystem inode error</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/filesystem-inode-error/m-p/2501073#M20907</link>
      <description>Yes, my command was shutdown -nr</description>
      <pubDate>Mon, 05 Mar 2001 17:50:05 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/filesystem-inode-error/m-p/2501073#M20907</guid>
      <dc:creator>nancy rippey</dc:creator>
      <dc:date>2001-03-05T17:50:05Z</dc:date>
    </item>
    <item>
      <title>Re: Filesystem inode error</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/filesystem-inode-error/m-p/2501074#M20908</link>
      <description>Hallo,&lt;BR /&gt;&lt;BR /&gt;I would run the fsck on the /dev/vg00/lvolXX.&lt;BR /&gt;Make sync an rerun the fsck. After that, make a normal shutdown. &lt;BR /&gt;&lt;BR /&gt;bye</description>
      <pubDate>Mon, 05 Mar 2001 18:08:25 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/filesystem-inode-error/m-p/2501074#M20908</guid>
      <dc:creator>Juergen Nagel_1</dc:creator>
      <dc:date>2001-03-05T18:08:25Z</dc:date>
    </item>
  </channel>
</rss>

