OC.HULVER@CU20B.COLUMBIA.EDU (Barron Hulver) (04/27/87)
HEADER FULL problem
I have not experienced the problem, before. However, I suspect it is related
to the fact that a disk pack has a maximum number of disk blocks, and also a
maximum number of files.
To see the maximum number of files allowed, enter
$ show device/full <disk device nbame>
e.g. $ show device/full dra0:
You will see in the right column the MAXIMUM_FILES value.
" Free blocks 99999999 Maximum files allowed 999999999"
If you are out of file header space (more on this in a second), then you will
have to backup the disk, INITIALIZE/MAXIMUM_FILES=n...
and restore the disk.
$ HELP INITIALIZE DEVICE /MAXI
Okay, so are you out of file header space?
$ DUMP <disk root>:[000000]INDEXF.SYS/DEC/WORD/BLOCK=(START:2,COUNT:1)
Offset 22 is the virtual block number of the file header bitmap.
Offset 32 is the size of the file header bitmap.
-------------------- EXAMPLE ------------------------------------------
$ DUMP SYSDISK:[000000]INDEXF.SYS/DEC/WORD/BLOCK=(START:2,COUNT:1)
!!!!! offset 22 is 2nd line, column 5. offset is line 3, column 8 !!!!!!!!
!!!!! 2nd line, column 5 has value 5, line 3 column 8 has value 55 !!!!!!!!
!!!!! I flagged them in the example with an asterisk * !!!!!!!!!!!!!!!!!!!!
Dump of file SYSDISK:[000000]INDEXF.SYS;1 on 27-APR-1987 09:35:52.03
File ID (1,1,0) End of file block 6075 / Allocated 6075
Virtual block number 2 (00000002), 512 (0200) bytes
1 513 6 -8924 0 767 0 1 ........$]...... 0
3 26160 6-12995 *5 4 3 2 ........=M..0f.. 16
1 1 0 0 0 0 9 *55 7............... 32
-17144-23104 3570 -512 -1536 0 0 0 .......z.~r.@%.= 48
-1 -1 -2 31072 5 775 141-19026 .5......`y~..... 64
0 0 0 0 -1 -1 -2 31072 `y~............. 80
0 0 0 0 0 0 0 0 ................ 96
0 0 0 0 0 0 0 0 ................ 112
0 0 0 0 0 0 0 0 ................ 128
0 0 0 0 0 0 0 0 ................ 144
0 0 0 0 0 0 0 0 ................ 160
0 0 0 0 0 0 0 0 ................ 176
0 0 0 0 0 0 0 0 ................ 192
0 0 0 0 0 0 0 0 ................ 208
0 0 0 0 0 0 0 0 ................ 224
0 0 0 0 0 0 0 0 ................ 240
0 0 0 0 0 0 0 0 ................ 256
0 0 0 0 0 0 0 0 ................ 272
0 0 0 0 0 0 0 0 ................ 288
0 0 0 0 0 0 0 0 ................ 304
0 0 0 0 0 0 0 0 ................ 320
0 0 0 0 0 0 0 0 ................ 336
0 0 0 0 0 0 0 0 ................ 352
0 0 0 0 0 0 0 0 ................ 368
0 0 0 0 0 0 0 0 ................ 384
0 0 0 0 0 0 0 0 ................ 400
0 0 0 0 0 0 0 0 ................ 416
0 0 0 0 0 0 0 0 ................ 432
8224 8224 0 0 0 0 0 0 ............ 448
19538 21325 22104 16726 8224 8224 8224 8224 VAXVMSRL 464
8224 8224 8224 19781 21587 22867 8224 8244 4 SYSTEM 480
10685 0 8224 16945 12613 19529 17987 17732 DECFILE11B ..=) 496
VAXC>ENDCOPY
-------------------- END EXAMPLE --------------------------------------
$ DUMP <disk root>:[000000]INDEXF.SYS/BLOCK=(START:<offset 22 value>,
COUNT:<offset 32 value>)
$ DUMP SYSDISK:[000000]INDEXF.SYS/BLOCK=(START:5,COUNT:55)
If the dump contains all x'FFFFFFFF', then you have hit
max files, because a bit is set to one if the file header is in use.
...Barron
-------
-------
-------