[mod.computers.vax] vms disk volume sets

george@VAX1.CCS.CORNELL.EDU.UUCP (07/31/86)

When initalizing disk volumes that will be part of a multi volume set,
do any of the settings apply to more than just the volume being
initialized, are any ignored, and are any of special importance when
the volume is to be the first volume in the set?

This question is motivated by the size and use of the indexf.sys files
on each of the volumes. At first I thought I had to init the first
volume with the desired values of maximum_files, headers, and
directories and that it didn't matter how the other volumes were
initialized. That's not true since the volume stopped working when I
reached the max file limit of the second volume. So I tried again,
this time splitting the values across the volumes. I like this since
it would imply that I can add another volume at any time and increase
any of the limits. Indeed, I see each volume has indexf.sys open so it
seems to be in use. BUT, why does it let me create files explicitly on
the second volume that are only visible with an explicit directory
command of that volume AND a directory command of the volume set does
not show the files? That seems to imply that the indexf.sys files are
independent of each other. Where is my logic flawed?

So I have one explicit question. If I want to have a maximum of, say,
200000 files spread across a two volume set, can I init each volume to
have a max of 100000 or must the first have a max of 200000. (As
mentioned above, i already know that the second volume must be set at
100000.)

Thanks...
-- 
George Boyce, Academic Computing, Cornell University
george@vax1.ccs.cornell.edu (128.84.252.10), george@crnlcs.bitnet