<?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 /var inode problem in Operating System - HP-UX</title>
    <link>https://community.hpe.com/t5/operating-system-hp-ux/var-inode-problem/m-p/2569920#M30396</link>
    <description>Can anything be done to fix the inode problem listed below?   We have Online JFS.&lt;BR /&gt;Aug 24 10:54:56 hplogin1 vmunix: vxfs: mesg 016: vx_ilisterr - /var file system error reading inode 19670&lt;BR /&gt;Aug 24 10:54:56 hplogin1 vmunix: vxfs: mesg 016: vx_ilisterr - /var file system error reading inode 19670&lt;BR /&gt;</description>
    <pubDate>Fri, 24 Aug 2001 14:55:07 GMT</pubDate>
    <dc:creator>Eileen Millen</dc:creator>
    <dc:date>2001-08-24T14:55:07Z</dc:date>
    <item>
      <title>/var inode problem</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/var-inode-problem/m-p/2569920#M30396</link>
      <description>Can anything be done to fix the inode problem listed below?   We have Online JFS.&lt;BR /&gt;Aug 24 10:54:56 hplogin1 vmunix: vxfs: mesg 016: vx_ilisterr - /var file system error reading inode 19670&lt;BR /&gt;Aug 24 10:54:56 hplogin1 vmunix: vxfs: mesg 016: vx_ilisterr - /var file system error reading inode 19670&lt;BR /&gt;</description>
      <pubDate>Fri, 24 Aug 2001 14:55:07 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/var-inode-problem/m-p/2569920#M30396</guid>
      <dc:creator>Eileen Millen</dc:creator>
      <dc:date>2001-08-24T14:55:07Z</dc:date>
    </item>
    <item>
      <title>Re: /var inode problem</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/var-inode-problem/m-p/2569921#M30397</link>
      <description>Eileen-&lt;BR /&gt;&lt;BR /&gt;I'd start with running fsck on the filesystem.  normally, that will identify the inode problem and fix it.  You might need to drop down to single user mode to run it (I'm not sure with Online JFS if you have to or not).  If you reboot after running fsck (and it finds problems), remember to use the reboot -n command.&lt;BR /&gt;&lt;BR /&gt;Mark</description>
      <pubDate>Fri, 24 Aug 2001 15:00:04 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/var-inode-problem/m-p/2569921#M30397</guid>
      <dc:creator>Mark Vollmers</dc:creator>
      <dc:date>2001-08-24T15:00:04Z</dc:date>
    </item>
    <item>
      <title>Re: /var inode problem</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/var-inode-problem/m-p/2569922#M30398</link>
      <description>This could be a hard disk problem or corrupted file system. Boot into Single user mode and run an fsck on the file system.&lt;BR /&gt;&lt;BR /&gt;Before that try doing an ncheck /dev/vg00/var_lvol &amp;gt; /tmp/varnlist and see what file this inode correponds to.&lt;BR /&gt;&lt;BR /&gt;-Sri</description>
      <pubDate>Fri, 24 Aug 2001 15:03:55 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/var-inode-problem/m-p/2569922#M30398</guid>
      <dc:creator>Sridhar Bhaskarla</dc:creator>
      <dc:date>2001-08-24T15:03:55Z</dc:date>
    </item>
    <item>
      <title>Re: /var inode problem</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/var-inode-problem/m-p/2569923#M30399</link>
      <description>Sridhar:&lt;BR /&gt;Thanks, I didn't know about the ncheck command.&lt;BR /&gt;The ncheck  gets&lt;BR /&gt;read failed for block 4288 / IO error&lt;BR /&gt;&lt;BR /&gt;Does that mean the disk is no good?</description>
      <pubDate>Fri, 24 Aug 2001 15:10:43 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/var-inode-problem/m-p/2569923#M30399</guid>
      <dc:creator>Eileen Millen</dc:creator>
      <dc:date>2001-08-24T15:10:43Z</dc:date>
    </item>
    <item>
      <title>Re: /var inode problem</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/var-inode-problem/m-p/2569924#M30400</link>
      <description>Hi Eileen,&lt;BR /&gt;&lt;BR /&gt;Boot into single user mode and run&lt;BR /&gt;fsck -F vxfs -o full,nolog -y /dev/vg00/lvol_var&lt;BR /&gt;&lt;BR /&gt;But if you keep getting these errors repeatedly inspite of doing fsck, it could indicate disk going bad.&lt;BR /&gt;&lt;BR /&gt;-HTH&lt;BR /&gt;Ramesh</description>
      <pubDate>Fri, 24 Aug 2001 15:12:35 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/var-inode-problem/m-p/2569924#M30400</guid>
      <dc:creator>linuxfan</dc:creator>
      <dc:date>2001-08-24T15:12:35Z</dc:date>
    </item>
    <item>
      <title>Re: /var inode problem</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/var-inode-problem/m-p/2569925#M30401</link>
      <description>I would say it as the physical problem with the disk if my fsck fails. So, you need to fsck it while bringing down the server in single user mode. If it keeps saying cannot read blk#, then you may have to replace the disk.&lt;BR /&gt;&lt;BR /&gt;And, before doing so, since you have the system up and running now, it will be a good idea to prepare a make_recovery tape, verify it and also take a full backup of the system.&lt;BR /&gt;So,do not bring down the system unless you have a good make_recovery tape with you.&lt;BR /&gt;&lt;BR /&gt;-Sri</description>
      <pubDate>Fri, 24 Aug 2001 15:18:01 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/var-inode-problem/m-p/2569925#M30401</guid>
      <dc:creator>Sridhar Bhaskarla</dc:creator>
      <dc:date>2001-08-24T15:18:01Z</dc:date>
    </item>
  </channel>
</rss>

