[Info-vax] Initializing a new disk, need some pointers for options
Toine
tdirven at volvocars.com
Fri Nov 1 19:00:34 EDT 2019
Op woensdag 30 oktober 2019 23:53:38 UTC+1 schreef cgill... at gmail.com:
> So I've been supporting a VMS machine for almost 20 years now. As all things VMS, it just sits in the corner and runs. Today, the application disk started throwing DIRALLOC errors. I ran into this like 10+ years ago, I understand why it happens.
>
> The VAX now runs in a VM, so I just need to create another disk container initialize it and go. But, there are some options I'm curious about. The documentation is accurate, it just doesn't fill in a lot of why and the nuances.
>
> The existing application shoves all of it's files in the root folder. The application has accumulated 150K files.
>
> /Headers
> According to the doc, I should pick something along the lines of the # of files
> on the disk. So, 150K?
>
> /Index = location
> Does it really matter?
>
> /Maximum_Files= nnn
> This is pretty obvious.
>
> Guidance?
>
> Thanks
I use this to init a new disk:
$ init/headers=100000/nohigh/limit/struct=5/cluster=16 DSA200: DATADISK1
//Toine
More information about the Info-vax
mailing list