|
> Anyone know if there is a way to change the maximum # of
> files on a volume without having to init the device?
Hmm, I have my 'VMS file system internals (McCoy)' as home so this
is from memory. The maximum files is not just a number on the disk,
it is used to create a bitmap from for each possible bit in INDEXF.SYS.
I suspect that bitmap to be early in Indexf.sys itself, so the max
in place growth is probably a round up to a block full of bits. (4096).
> It would really be nice if there was a set vol/maximum_files
Nah... noone needs that except you yesterday and never again.
The default max file is really generous (and it should be considering
we are only talking about 1 bit per file.) as it corresponds with
two clusters per file where the minimum size really is 1 cluster
plus 1 block per file. I suppose, as cluster sizes are growing, the
default max files is drifting away from the absolute max max files,
but a disk filled with 1 cluster files would be fairly rare, and
supposedly, however sets up the disk knows what is going on.
I suspect, but may be wrong, that MAXIMUM_FILES is a knob which is
rarely turned and then only by folks that really know what they are
doing. (They may then move on leaving a trap for others ofcourse:-(. )
fwiw,
Hein.
|
| re .1:
> Nah... noone needs that except you yesterday and never again.
But imagine! you could easily save some valuable disk blocks within the index
file bitmap, and provide these as additional general storage to your available
disk space. Just use an artificially low maxfiles value when initializing your
disk, and raise that only when there's a real need... ;-)
-- Thilo
|