[Search for users] [Overall Top Noters] [List of all Conferences] [Download this site]

Conference decwet::advfs_support

Title:AdvFS Support/Info/Questions Notefile
Notice:note 187 is Freq Asked Questions;note 7 is support policy
Moderator:DECWET::DADDAMIO
Created:Wed Jun 02 1993
Last Modified:Fri Jun 06 1997
Last Successful Update:Fri Jun 06 1997
Number of topics:1077
Total number of notes:4417

1066.0. "advfs-PANIC-Ver40B" by DEKVC::MOONSUCHO (MOON-SU CHO @DEK) Tue May 27 1997 00:45

    Our customer has a serious problem about advfs,
    they use Alpha 1000, Dunix ver4.0B,
    They can't mount their filesystem which is
    advfs,informix_domain#informix.
    
    #mount -t advfs informix_domain#informix /informix
    
    
      Error msg : 
    	advfs:domain informix_domain#informix not activated-inconsistency
    	detected
    	informix_domain#informix on /informix :device does not contain a
    	valid ADVFS file system
    
    
    
    
    # cat /var/adm/messages
    	.
    	.
    	vmunix: advfs EXCEPTION
    	vmunix: module=bs_sbm.c, line=292
    	vmunix: advfs internal error:dealloc_bits_page:can't clear a bit
    		twice
    	vmunix: PANIC(cpu0):advfs internal error
    
They had a similar problem usr_domain#usr file system also, so they
    reinstalled O/S.
    Is there any internal error ?
    Any idea will be welcomed.
    Thanks,
T.RTitleUserPersonal
Name		DateLines
1066.1Please submit to CANASTA and look at these notesUNIFIX::HARRISJuggling has its ups and downsTue May 27 1997 08:0616
    Please submit your crash-data file to CANASTA (see note 8919 in the
    TURRIS::UNIX_DIGITAL notes conference).
    
    If CANASTA does not come up with an existing solution to this problem,
    then please escalate this problem via an IPMT case (aka a CLD).
    
    ----
    
    Also see notes 661, 1022, 983, 1051.
    
    					Bob Harris
    
    PS.  Please follow through on the CANASTA submit because your
         crash-data file may have a different signature than previous cases
         it might appear to look like, and if it is new, then it is 
         important to find that out.
1066.2DECWET::MARTINTue May 27 1997 11:4119
Umm, Bob?  There is no crash-data.

I believe this error is due to not having the AdvFS magic-number on one or more
of the disks in informix_domain.  How that happened, I don't know.

The results of:

	# ls -alR /etc/fdmns
	# showfdmn informix_domain
	# showfsets informix_domain
	# /sbin/advfs/advscan rz0 rz1 rz2 rz6 ...

might give us some more clue(s).  Did they happen to move disks around, or
possibly add a disk to the system that could have changed the logical SCSI
number of the disk(s) that the informix_domain was on?

The advscan command should list all disks currently on the system.

--Ken
1066.3what about the "can't clear bit twice" message?UNIFIX::HARRISJuggling has its ups and downsTue May 27 1997 12:1521
    Re: .2
    
>    Umm, Bob?  There is no crash-data.
    
    I was refering to the "can't clear bit twice" message and panic that
    were shown in the 2nd part of .0's posting:
    
->    # cat /var/adm/messages
->    	.
->    	.
->    	vmunix: advfs EXCEPTION
->    	vmunix: module=bs_sbm.c, line=292
->    	vmunix: advfs internal error:dealloc_bits_page:can't clear a bit twice
->    	vmunix: PANIC(cpu0):advfs internal error
    
    Maybe this has nothing to do with the customer's problem, or maybe
    there are 2 problems mixed into one posting.
    
    Thanks for answering.  I'm sure I'll learn some of this stuff one day :-)
    
    					Bob Harris