Operating System - OpenVMS
1753510 Members
5220 Online
108795 Solutions
New Discussion юеВ

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

 
SOLVED
Go to solution
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.