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

[gah4]

On Tuesday, May 25, 2021 at 4:37:56 PM UTC-7, arca... at gmail.com wrote:
> 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. 

Just wondering, does it know about NFS?

I think NFS mostly gets around disk size problems, as the client OS doesn't really
need to know about it.  I do find that disk available reports sometimes do 32 bit
math, and get the wrong value, but that doesn't affect actual disk use.

A few years ago, I had a Sun3 NFS boot off a 3TB disk, which it didn't
mind at all. The last release of SunOS 4.1.1 was in 1991, so I am pretty
sure didn't know about 3TB disks.

Also, and this might apply to VMS, NFS disks tend to remove file name length
restrictions of the client OS.  Years ago, we had a version of HP-UX that had
a short (I believe 17 character) restriction on its native file system, but
not for NFS.