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

[chris]

On 05/28/21 09:04, gah4 wrote:
> 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.
>

Sun 3 SunOs was 32 bit and a signed number described the partition
block count. For a boot partition, the limit was 1 Gbyte, from
memory.

The way we used to get round disk sizes for RT11, was to declare a
set of logical drives across a single drive, which worked very well.
I would think vms would have similar facilities...

of logical drives, which