Hello OSF-managers,
My original question was;
--------------------------------------------------------------------------------
One of our servers (DEC 3000,DU3.2c,Pathworks5.0feco2) when
rebooted comes up with the message:
Sep 3 19:24:40 moe vmunix: WARNING: iget, dinode no. 1543 changed
This has occurred since June 15 on every reboot.
What does this mean? And what are the consequences of not doing anything about
it?
Last night, an upgrade of Pathworks was attempted. It was unsuccessful when
rebuilding the kernel. Could there be any correlation?
Your comments and advice would be greatly appreciated,
David Shaw
--------------------------------------------------------------------------------
Thanks to chandrasek_at_odixie.enet.dec.com for his reply:
Sometime ago, there was a reply to this question from Amy. I have
included her reply here. I think this answers your question.
Regards, Kris.
Using find / -i 1543, I found out that 1543 is the inode for /dev/null on my
machine. On the tech's advice, I rm'd /dev/null and created a new one, using
# mknod null c 2 2
and rebooted. The vmunix warning was gone upon reboot. Unfortunately
I don't know if the warning was a symptom of something greater or not.
If you choose to remove and rebuild /dev/null, don't forget to set the
permissions correctly. Write access is a good thing.
I would be happy to hear from others who have upgraded to V3.2, especially
on 3000/300's, so I can ferret out any other problems before I upgrade
the other machines here.
We now return you to your regularly scheduled inode.
-amy
--------------------------------------------------------------------------------
I followed these instructions, also running the "file /dev/null"
command. It was interesting to note that instead of the usual "character
special (2,2)" response, it came back with "Ascii text".
Upon reboot, the warnings had gone.
David Shaw
System Administrator
United Energy
bcn_at_ue.com.au
Received on Mon Sep 09 1996 - 03:03:32 NZST