| Title: | RAID Software for OpenVMS |
| Notice: | READ IMPORTANT NOTE IN 3.15, V2.4 SSB Kit in 3.17 6 |
| Moderator: | COOKIE::FROEHLIN |
| Created: | Fri Dec 03 1993 |
| Last Modified: | Fri Jun 06 1997 |
| Last Successful Update: | Fri Jun 06 1997 |
| Number of topics: | 341 |
| Total number of notes: | 1378 |
Hi
Customer question :
He created a controlller based raid 0 set (disk striping).
INITialized the raid-set and noticed that INDEXF.SYS is relatively small,
less than 300 blocks. He did :
$ init/head=<very big number>
but the file size did not grow significantly.
$ sho dev/full
shows max files 500000.
Isn't the files size too small. We are afraid it will be too fragmented in the
future.
Thanks
Zvi
| T.R | Title | User | Personal Name | Date | Lines |
|---|---|---|---|---|---|
| 334.1 | COOKIE::FROEHLIN | VMS...riding into the setting sun! | Thu Apr 24 1997 15:55 | 4 | |
Do you have a complete "SHOW DEVICE/FULL" output? The /HEADER= should
have done the trick. Somehing else is wrong.
Guenther
| |||||
| 334.2 | show dev/full ... | TAV02::ZVI_P | Here we are | Sun Apr 27 1997 02:59 | 26 |
Disk $7$DKA600: (TAVOR), device type HSZ20, is online, mounted,
file-oriented device, shareable, available to cluster, error logging is enabled.
Error count 0 Operations completed 25748332
Owner process "" Owner UIC [SYSTEM]
Owner process ID 00000000 Dev Prot S:RWPL,O:RWPL,G:R,W
Reference count 450 Default buffer size 512
Total blocks 25134084 Sectors per track 113
Total cylinders 11122 Tracks per cylinder 20
Allocation class 1
Volume label "USER600" Relative volume number 0
Cluster size 25 Transaction count 450
Free blocks 10362750 Maximum files allowed 483347
Extend quantity 5 Mount count 1
Mount status System Cache name "_$1$DKA0:XQPCACHE"
Extent cache size 64 Maximum blocks in extent cache 1036275
File ID cache size 64 Blocks currently in extent cache 877800
Quota cache size 0 Maximum buffers in FCP cache 2874
Volume owner UIC [300,2] Vol Prot S:RWCD,O:RWCD,G:RWCD,W:RWCD
Volume Status: subject to mount verification, file high-water marking,
write-back caching enabled.
Thanks
Zvi
| |||||
| 334.3 | CSC64::BLAYLOCK | If at first you doubt,doubt again. | Mon Apr 28 1997 11:01 | 9 | |
The question really belongs in VAXAXP::VMSNotes but... If you are getting a default size of 300 on the size of INDEXF.SYS, then the system is taking your /HEADERS qualifier. What does a DUMP /HEADER /BLOCK=COUNT=0 $7$DKA600:[000000]INDEXF.SYS show? Are you actually seeing the EOF value of INDEXF.SYS or its allocated value? | |||||
| 334.4 | After disk population INDEXF.SYS is ~72800/72800 | TAV02::ZVI_P | Here we are | Tue Apr 29 1997 00:43 | 8 |
As it is a production system, he couldn't wait and he populated the disk. Now INDEXF.SYS has 5 extents the 5th has size of 72500 blocks. DUMP /HEADER /BLOCK=COUNT=0 $7$DKA600:[000000]INDEXF.SYS shows that End of file block and Allocated blocks are the same and over 72500 blocks. Zvi | |||||
| 334.5 | COOKIE::FROEHLIN | VMS...riding into the setting sun! | Tue Apr 29 1997 09:52 | 5 | |
>Now INDEXF.SYS has 5 extents the 5th has size of 72500 blocks.
Is 72500 the number used with /HEADER?
Guenther
| |||||
| 334.6 | TAV02::ZVI_P | Here we are | Wed Apr 30 1997 00:30 | 7 | |
>Is 72500 the number used with /HEADER? No. For /headers they used some big number that reflects the maximun number of headers they ever expect to have in indexf.sys, several 100K's I assume. Zvi | |||||