HPE Community read-only access December 15, 2018
This is a maintenance upgrade. You will be able to read articles and posts, but not post or reply.
Hours:
Dec 15, 4:00 am to 10:00 am UTC
Dec 14, 10:00 pm CST to Dec 15, 4:00 am CST
Dec 14, 8:00 pm PST to Dec 15, 2:00 am PST
Operating System - OpenVMS
cancel
Showing results for 
Search instead for 
Did you mean: 

Backup or Copy causing VMS 5.5-2H4 Bugcheck

 
SOLVED
Go to solution
Ayya
Frequent Advisor

Backup or Copy causing VMS 5.5-2H4 Bugcheck

I have two systems running VAX VMS 5.5-2H4.
VAX 4000-50 and VAX-4000-600.
I think I have applied all patches that I can think of.
Both systems BUGCHECK during COPY or BACKUP of a specific file.
Happens when the file is newly created using
BACKUP/Ignore=interlock/Newversion.

Any ideas?
Thanks
Sini
15 REPLIES
Volker Halle
Honored Contributor

Re: Backup or Copy causing VMS 5.5-2H4 Bugcheck

Sini,

OpenVMS VAX V5.5-2H4 does not include the CLUE utility, which does provide an ASCII readable crash summary file (so-called CLUE file).

To find out a bit more about the crash, please provide the following information:

$ ANAL/CRASH SYS$SYSTEM
SDA> SHOW CRASH
SDA> SHOW STACK
SDA> SHOW PROC/CHAN

Volker.
Arch_Muthiah
Honored Contributor

Re: Backup or Copy causing VMS 5.5-2H4 Bugcheck

Sini,

from your Forum Profile:


I have assigned points to 5 of 17 responses to my questions.


Maybe you can find some time to do some assigning?

Mind, I do NOT say you necessarily need to give lots of points. It is fully up to _YOU_ to decide how many. If you consider an answer is not deserving any points, you can also assign 0 ( = zero ) points, and then that answer will no longer be counted as unassigned.
Consider, that every poster took at least the trouble of posting for you!

To easily find your streams with unassigned points, click your own name somewhere.
This will bring up your profile.
Near the bottom of that page, under the caption â  My Question(s)â  you will find â  questions or topics with unassigned points â  Clicking that will give all, and only, your questions that still have unassigned postings.

Thanks on behalf of your Forum colleagues.

PS. â  nothing personal in this. I try to post it to everyone with this kind of assignment ratio in this forum. If you have received a posting like this before â  please do not take offence â  none is intended!
Regards
Archie
Hein van den Heuvel
Honored Contributor

Re: Backup or Copy causing VMS 5.5-2H4 Bugcheck


What is the BUGCHECKFATAL setting on your system? This could be an rms problem turned fatal if it is set to 1. Unlikey though, as copy and backup use little or no RMS. Still, check out:
$ mcr sysgen show bugcheck

You say it is a specific file.
Could it be with the output, or the input sde as implied?
Anyway, tell us more. What might be special about the file? At least share DIR/FULL output, but probably you should reply with an attached text file with the output from DUMP/HEAD/BLOCK=COUNT=0
How about the disk structure in general?
Be sure to check out ANAL/DISK for the device holding the specific file.

Finally some free advice: If you can do a simple COPY of the file, then why not use a simple BACKUP vs BACKUP/IGNORE=INTERLOCK.
IMHO using BACKUP/IGNORE=INTERLOCK is a really bad habbit to get into. It has its place, but it should not be the normal command to use.

Hope this helps,
Hein.
Ayya
Frequent Advisor

Re: Backup or Copy causing VMS 5.5-2H4 Bugcheck

Sorry folks. I am not able to go to the customer site to get the BUGCHECK information that is needed. Hopefully within the next few days I will be able to get the information.

Thanks

Sini
Ayya
Frequent Advisor

Re: Backup or Copy causing VMS 5.5-2H4 Bugcheck

Thanks all for the replys. I finally was able to get the information asked.

BUGCHECKFATAL = 0 (is set to 0)

I have attached the crash information.
The practice of BACKUP/interlock etc is being reviewed.
I need to figure out why the crash and what fix there is.

Sini
Volker Halle
Honored Contributor
Solution

Re: Backup or Copy causing VMS 5.5-2H4 Bugcheck

Sini,

it's an INVEXCEPTN crash in IO_ROUTINES+033E5, ACCVIO, failing Virtual Address is 0000000B. Process context, BACKUP is current image. DKDRIVER is on the stack and BACKUP is busy on DKA100:

To determine the instruction stream, please provide the following data:

SDA> EXA/INS 809717E5-20;30

Note you may need to change the -20 to -21 or similar to find the beginning of a valid instruction stream.

Volker.

Volker Halle
Honored Contributor

Re: Backup or Copy causing VMS 5.5-2H4 Bugcheck

Sini,

according to the old patch pages of the CSC in Sidney, the most recent DKDRIVER for V5.5-2H4 seems to be from VAXSCSI03_061 (Link Date 12-APR-1995 X-18A7A7A4).

Most recent IO_ROUTINES are from VAXSHAD09_U2055 (Link Date 22-OCT-1995 V552R05).

If you don't have those 2 files/patches installed, try them first.

Volker.
Ayya
Frequent Advisor

Re: Backup or Copy causing VMS 5.5-2H4 Bugcheck

I have applied both patches.
Any harm reapplying them?

SDA> EXA/INS 809717E5-20;30
%SDA-W-INSKIPPED, unreasonable instruction stream - 1 bytes skipped
IO_ROUTINES+033C6: DECL R3
IO_ROUTINES+033C8: BLEQ IO_ROUTINES+033D5
IO_ROUTINES+033CA: MOVZWL (R4)+,R3
IO_ROUTINES+033CD: CMPL R1,(R4)
IO_ROUTINES+033D0: BNEQ IO_ROUTINES+033D5
IO_ROUTINES+033D2: ADDL2 R3,R8
IO_ROUTINES+033D5: EXTZV #00,#18,R0,R1
IO_ROUTINES+033DA: EXTZV #18,#08,R0,R0
IO_ROUTINES+033DF: BEQL IO_ROUTINES+033F2
IO_ROUTINES+033E1: MOVL 1C(R2),R6
IO_ROUTINES+033E5: CMPB R0,0B(R6)
IO_ROUTINES+033E9: BGTRU IO_ROUTINES+0342E
IO_ROUTINES+033EB: MOVL 40(R6)[R0],R5
IO_ROUTINES+033F0: BEQL IO_ROUTINES+0342E
IO_ROUTINES+033F2: BBS #02,0B(R2),IO_ROUTINES+0343A
IO_ROUTINES+033F7: BBS #05,3C(R5),IO_ROUTINES+0343A
Ayya
Frequent Advisor

Re: Backup or Copy causing VMS 5.5-2H4 Bugcheck

Directory SYS$COMMON:[SYS$LDR]

IO_ROUTINES.EXE;4 22-OCT-1995 19:56:55.00

Total of 1 file.
$ dir/date dkdriver.exe

Directory SYS$COMMON:[SYS$LDR]

DKDRIVER.EXE;5 12-APR-1995 19:17:32.00

Total of 1 file.
Volker Halle
Honored Contributor

Re: Backup or Copy causing VMS 5.5-2H4 Bugcheck

Sini,

makes non sense to re-apply those patches. This is OpenVMS, not ;-)

The crash happens due to R6 = 0 (loaded from 1C(R2) in routine IOC$MAPVBLK).

R2 is the WCB (Window Control Block) of the file being mapped, i.e. DKA100:(12948,2,0). You can verify that this is the 'suspect' file by doing a DIR/FULL of that specific file and checking the File ID.

Unfortunately WCB$L_RVT(R2) does contain 0, which causes the ACCVIO (and crash).

Let's have a look at that WCB:

SDA> READ SYS$SYSTEM:SYSDEF
SDA> FORMAT @R2/TYPE=WCB

Did you run ANAL/DISK on DKA100: ?

Are you running the most recent XQP (from VAXF11X06_U2055 1-JUN-1998 XQP V5.5-2010 or 1-DEC-1999) ?

Volker.
Volker Halle
Honored Contributor

Re: Backup or Copy causing VMS 5.5-2H4 Bugcheck

Sini,

what's the size of the disk DKA100: ?

SDA> SHOW DEV DKA100
SDA> EXA UCB+UCB$L_MAXBLOCK

MAXBLOCK may NOT be larger than 00FFFFFF

Note that there is a 8.5 GB disk size limit in OpenVMS V5.*

Volker.
Ayya
Frequent Advisor

Re: Backup or Copy causing VMS 5.5-2H4 Bugcheck

Customer changed the drive from 4.5gb to a 9.1 GB drive.

That must be it then.

Can the customer bind 2 or more volumes to exceed 8.5GB ?

Thanks a lot.
Hein van den Heuvel
Honored Contributor

Re: Backup or Copy causing VMS 5.5-2H4 Bugcheck

This is an OpenVMS FAQ question.

>> Can the customer bind 2 or more volumes to exceed 8.5GB ?

Yes. The 24 bit limit is per volume withing the set.

See also:

http://groups.google.com/group/comp.os.vms/browse_thread/thread/dc83ba86afc1f486/5dbec206a1c51325%235dbec206a1c51325?sa=X&oi=groupsr&start=1&num=3
(Glenn Eveerhart explaining how to use the VDdriveer to workaroudn this issue)

and

http://groups.google.com/group/comp.os.vms/browse_thread/thread/4f1306f567eef734/4045c3d2918f3e61%234045c3d2918f3e61?sa=X&oi=groupsr&start=0&num=3

and

...


Hth,
Hein.
Ayya
Frequent Advisor

Re: Backup or Copy causing VMS 5.5-2H4 Bugcheck

I had already applied the XQP patch.
DKA100 got corrupted yesterday and I had the customer run anal/disk yesterday. After realizing the 8.5 GB limit customer quickly moved to a 4.3GB drive. So I don't have access to the old disk to check the file ID.
Thank you Volker and Hein for your very valuable and informative help.

Regards,
Sini
Ayya
Frequent Advisor

Re: Backup or Copy causing VMS 5.5-2H4 Bugcheck

A 9.1GB disk was being used causing the problem.
VMS 5.5 does not support disk > 8.5GB
Thanks for the invaluable help.