[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

1035.0. "vquotacheck panics" by MDR01::CALVINO (MCS Madrid) Mon Apr 07 1997 11:26

    Hello,
    
    I have tree panic's with panic_string:"" and ADVFS EXCEPTION Module =
    2, Line = 1657. The current process was vquotacheck. 
    The O.S. is Digital UNIX V3.2D-1 (Rev. 41).
    
    I send to the customer AdvFS Consolidated Patch, but I don't know If
    that patches will be solve the panics problem.
    
    Any help will be appreciate.
    Regards
    Ricardo
    
T.RTitleUserPersonal
Name
DateLines
1035.1please try CANASTA Mail ServerHAN::HALLEVolker Halle MCS @HAO DTN 863-5216Mon Apr 07 1997 14:428
    Ricardo,
    
    if you have the crash-data file available, please send them to the
    CANASTA Mail Server (a crashdump analysis service !).
    
    Please read note TURRIS::DIGITAL_UNIX 8919 for more info.
    
    Volker.
1035.2unknown panicMDR01::CALVINOMCS MadridTue Apr 08 1997 02:1411
    This was the asnwer from canasta:
    CANASTA was unable to find a rule matching the footprint of this
        crash.  If, in the future, a new rule is added that matches this
        crash, you will be notified via mail.
    
        This does not necessarily indicate that this is a new or unknown
        problem, but that there is currently no CANASTA rule that matches
        this case.
    
    Regards
    Ricardo.
1035.3reported before IPMT MGO102481 -> QAR 49275 ...HAN::HALLEVolker Halle MCS @HAO DTN 863-5216Tue Apr 08 1997 06:1637
    Ricardo,
    
    so you have used CANASTA (thanks !), but there was no rule match for
    your case. The FIND_SIMILAR_CASES function in the CANASTA Mail
    Server did have additional information for you:
    
    There was a list of CANASTA cases with SIMILAR (or even IDENTICAL)
    footprints and some of them were IPMT cases, e.g. like this one:
    
    MGO102481.0     OGO  bs_frag_has_stg:1665, 0xfffffc00003bd3b4] nil
    MGO102481.2     OGO  UNIDENTIFIED   USEG  17-JUL-1996 10:31:39.00 booster2
    ^^^^^^^^^<<< IPMT number		^^^^escalated to USEG !!!
    MGO102481.2     OGO  V3.2D-1  ~
    MGO102481.2     OGO  boot panic advfs_sad bs_frag_has_stg msfs_real_syscall
    			 msfs_syscall syscall _Xsyscall
    MGO102481.2     OGO  bs_frag_has_stg:1665, 0xfffffc00003bdc44] nil
    
    This has shown you, that this crash has been seen (and sent to CANASTA)
    before. Please see note SPECXN::CANASTA 239 & 244 on how to read and
    interpret the information from CAN_OSF1_CASES.SEQ
    
    When you check that IPMT, you'll see that the problem has been moved
    into the QAR database as QAR 49275. If you then check that QAR (SET
    HOST to node GORGE, enter Username: QAR_INTERNAL, select OSF_QAR db),
    you'll find it to be similar to QAR 39341 and it also seems to say,
    that it's fixed in V4.0...
    
    You can also check the UNIX or ADVFS patch readme files for any of the
    above strings: MGO102481, 49275 and 39341 to find out, if the problem
    might have been fixed.
    
    If this doesn't help your customer, you'll have to raise an IPMT ...
    
    Sorry, but that's the way it is...
    
    Volker.
    
1035.4see note 870 for a crash with the same footprintHAN::HALLEVolker Halle MCS @HAO DTN 863-5216Tue Apr 08 1997 06:261
    
1035.5That's THE explanation...BACHUS::DEVOSManu Devos DEC/SI Brussels 856-7539Tue Apr 08 1997 12:117
    Thanks, Volker
    
    for this excellent CANASTA user course and how to find our way in this
    jongle up to the patch README file ...
    
    Manu.
    
1035.6Thanks! (GRACIAS!!)MDR01::CALVINOMCS MadridThu Apr 10 1997 09:046
    Hello, Volker
    
    Thank you very much for your help 
    
    Ricardo