Conference vaxaxp::alphanotes

78.0. "XQPERR, Error detected by file system XQP" by FORAT::PONS () Tue Apr 08 1997 14:05

	Hy,

	One important customer in Spain have a serious problem 
	with two different systems:

	- Alphaserver 8400 EV56/440
	  OpenVMS 6.2-1H3  FRONT1	
	
	- 7000-720
	  OpenVMS V6.1     FACTU2

	Since yesterday every time that from any of two systems start a
	BACKUP,to tape or disk, the system crash with the next crash:

	FRONT1:

	Module:            F11BXQP
	Offset:            00001AB8
	Always the same but with different process and image.

	FACTU2:

	Module:            F11BXQP
	Offset:            00001AC8
	Always the same but with different process and image.

	The two systems are standalone systems, and two systems have the
	next ECO installed:

	FRONT1:

ALPCLIU01_062.RELEASE_NOTES;1           ALPF11X03_070.RELEASE_NOTES;1
ALPHA_UCX033.RELEASE_NOTES;1            ALPMANA01_062.RELEASE_NOTES;1
ALPMANA02_070.RELEASE_NOTES;1           ALPMOTF07_U3012.RELEASE_NOTES;1
ALPRMS02_062.RELEASE_NOTES;1            ALPSCSI02_070.RELEASE_NOTES;1
ALPSCSI03_062.RELEASE_NOTES;1           ALPSMUP01_070.RELEASE_NOTES;1
ALPSYS02_062.RELEASE_NOTES;1            ALPSYS08_070.RELEASE_NOTES;2
ALPVERI01_071.RELEASE_NOTES;1           AMDS062.RELEASE_NOTES;1
AXPSCSI01_062.RELEASE_NOTES;1           AXPVMSU1H3_062.RELEASE_NOTES;1
CC050.RELEASE_NOTES;1                   DCPS012.RELEASE_NOTES;1
DECNET_OSI-V6_3.RELEASE_NOTES;1         DECW$MOTIFU3012.RELEASE_NOTES;1
HSZTERM010.RELEASE_NOTES;1              OSCINT021.RELEASE_NOTES;1
OSIF$032.RELEASE_NOTES;1                PATROL030.RELEASE_NOTES;1
PSDC022.RELEASE_NOTES;1                 SNALU62022.RELEASE_NOTES;1
SNATE015.RELEASE_NOTES;1                SNS_ECO01022.RELEASE_NOTES;2
TNT010.RELEASE_NOTES;1                  UCX041.RELEASE_NOTES;1
UCXECO3-041.RELEASE_NOTES;1             UCXECO4-033.RELEASE_NOTES;2
UCXECO5-041.RELEASE_NOTES;1


	FACTU2:

ALPBACK01_061.RELEASE_NOTES;1           ALPCLIU01_062.RELEASE_NOTES;1
ALPF11X03_070.RELEASE_NOTES;1           ALPHA_UCX033.RELEASE_NOTES;1
ALPLAVC01_062.RELEASE_NOTES;1           ALPMANA01_070.RELEASE_NOTES;1
ALPMANA02_070.RELEASE_NOTES;2           ALPRMS03_061.RELEASE_NOTES;2
ALPSYS08_070.RELEASE_NOTES;1            ALPSYS11_061.RELEASE_NOTES;1
ALPVERI01_071.RELEASE_NOTES;1           CC052.RELEASE_NOTES;1
DCPS012.RELEASE_NOTES;1                 DECNET_OSI-V6_2.RELEASE_NOTES;1
LPS050.RELEASE_NOTES;1                  LPS051.RELEASE_NOTES;2
OSCINT021.RELEASE_NOTES;1               PATROL030.RELEASE_NOTES;1
PSDC022.RELEASE_NOTES;1                 SNS_ECO01022.RELEASE_NOTES;1
UCXECO4-033.RELEASE_NOTES;2

	The last ECO  about F11 was installed, I hope,

	I'm waiting for a SYSDUMP.DMP file to escalate the situation, but
	in the waiting time, any suggestion!!!!!!

	Thanks in advance

	Jordi
	MCS SPAIN

    Jordi,
    
    get the CLUE files and send it to the CANASTA Mail Server as a first
    step. A quick check of the CAN_VMS_AXP_CASES.SEQ (CANASTA case db
    extract) file doesn't indicate this is a problem, which has been seen (in
    CANASTA) before.
    
    Why did it start 'yesterday' ? What has been changed ? You need to at
    least provide the instruction stream, so we can figure which code it's
    in.
    
    Then there is the 'raise an IPMT' answer (if it's a critical customer
    problem etc. etc.). And you better put this into the OpenVMS notes
    conference (VAXAXP::VMSNOTES).
    
    Volker.

	Volker,

	Start 'yesterdey' was the first surprise for me, nothing was changed
	in two systems.

	The same note was posted in VAXAXP::VMSNOTES #435, and write the
	reply .1 for put the message that was discover after eva/cond @r0
	but at the moment nobody answer.

	The dcl procedure that makes a backup is:
	
	$ set proc/prio=0
	$
	$ backup/ver/igno=interlock aplicaciones:[000000...] -
        BACKUPS:[bck]aplicaciones_19970408.bck/sav
	$ backup/ver/igno=interlock oracle_rdbms:[000000...] -
        BACKUPS:[bck]oracle_rdbms_19970408.bck/sav	
	$ backup/ver/igno=interlock SYS_DATOS_1:[000000...] -
        BACKUPS:[bck]SYS_DATOS_1_19970408.bck/sav
	$ backup/ver/igno=interlock SYS$sysdevice:[000000...] -
        BACKUPS:[bck]SYS_front1_19970408.bck/sav
	$
	$ exit

	Thanks
	Jordi
	

:                       -< Cross posted in VMSNOTES 534 >-

   Uh, that should be 435.* -- there's a discussion going on over there,
   too -- VMSNOTES is also the OpenVMS-specific notes conference.

   (Please consider don't cross-post without giving folks a day or two to
   respond to the first posting -- and if that's too long to wait, you
   should seriously consider using another reporting mechanism, such as
   an IPMT...)