Hello All
My original Message is below.
Thank you to Tom Blinn and Oisin McGuinness for their replies.
They both advised that the problem is an ADVFS one and suggested that I
carry out a verify on all domains. I have done this and Identified that
there is a problem with the root domain. Verify was unable to fix the
problem, so I believe my only option is to dump and restore the root_domain.
As for the problem not occuring when the system is manually restarted. I
have investigated this further and have discovered the following.
The advfsd process is what is causing the panic. As soon as this is started
the system panics.
When you run init 3 from run level 2 the script in rc3.d that starts this
does nothing.
This occurs because there is an if statement in this script that checks the
previous runlevel and only starts advfsd if the previous run level was S.
This does leave one question. What are the issues with not having advfsd
running.
Cheers
Adrian Morin
-----Original Message-----
From: Adrian Morin [mailto:amorin_at_dbtech.com.au]
Sent: Monday, 12 April 1999 16:47
To: tru64-unix-managers_at_ornl.gov
Subject: panic : bfs_access: can't get get tag info
Hello All
We are experiencing system panics during boot up on a DEC 4100 running 4.0d.
The message is :
panic (cpu 1): bfs_access: can't get tag info
N1 = -1035
This occurs whenever we do an automatic reboot of the machine. However if we
take the machine up manually through the run levels it is fine.
Some investigation of the crash dumps and logs shows that the bfs_access
function is found in
../../../../src/kernel/msfs/bs/bs_bitfile_sets.c
The machine has been operating fine for the last 6 months, during which it
has rebooted a number of times successfully. No patches or changes have been
made that I am aware of.
Does any anybody know what could be causing this? or what the bfs_access
function is used for?
Thank you in anticipation of your assistance
Adrian Morin
Received on Wed Apr 14 1999 - 21:25:14 NZST