[Info-vax] Greater than approx 16GB disk leads to UNXSIGNAL crash

[arca...@gmail.com]

I wanted a 100GB disk (using SIMH) under OpenVMS VAX V7.2.

That seems to be fine until I try to create a file. Admittedly I've only tried to create a file either using FTP or BACKUP, but as they're so disconnected, I assume that it's actually XQP (or something in the file system) that gets upset.

I backed off my disk size and even 20GB triggers the crash. 16GB seems to be OK.

Now OpenVMS beyond V5.5-2 supports single volumes of 1TB, so I'm surprised that a 16GB volume causes a crash. 

Does anyone have a real VAX with a real disk (> 16GB) successfully hanging off it? I do have some SCA-80 36GB disks but I've never successfully got them working on either a VS4000-96 or a VS4000-60, so I'm not in a position to try this out myself.

The crash is below for those who enjoy that sort of thing!

Antonio

**** Fatal BUG CHECK, version = V7.2     UNXSIGNAL, Unexpected signal name in ACP

    Crash CPU: 00        Primary CPU: 00

    Active/available CPU masks: 00000001/00000001

    Current process = UCX$FTPC_1

    Register dump

	R0 = 7FF6E0D8
	R1 = 7FF6EAFC
	R2 = 7FF6E4C0
	R3 = 7FF6E4AC
	R4 = 7FF6E4D0
	R5 = 7FF6E4A8
	R6 = 7FF6E588
	R7 = 00000000
	R8 = 00000001
	R9 = 7FF6E4C0
	R10= 7FF6E564
	R11= 00000357
	AP = 7FF6E088
	FP = 7FF6E060
	SP = 7FF6E050
	PC = 833CAABC
	PSL= 00000000

    Kernel/interrupt/boot stack

	7FF6E058  7FF6E684
	7FF6E05C  7FF6E630
	7FF6E060  00000000
	7FF6E064  243C0000
	7FF6E068  7FF6E0B4
	7FF6E06C  7FF6E09C
	7FF6E070  833CAA59
	7FF6E074  83ABE9BC
	7FF6E078  83ABE880
	7FF6E07C  00000000
	7FF6E080  000000C0
	7FF6E084  7FF6E564
	7FF6E088  00000003
	7FF6E08C  7FF6E0D8
	7FF6E090  7FF6E0C0
	7FF6E094  7FF6E098
	7FF6E098  00000000