Title: | *OLD* ALL-IN-1 (tm) Support Conference |
Notice: | Closed - See Note 4331.l to move to IOSG::ALL-IN-1 |
Moderator: | IOSG::PYE |
Created: | Thu Jan 30 1992 |
Last Modified: | Tue Jan 23 1996 |
Last Successful Update: | Fri Jun 06 1997 |
Number of topics: | 4343 |
Total number of notes: | 18308 |
Hello, We have a customer with a cluster factor of 1 on his disk, but his shared mail area files all appear to have more blocks allocated than needed. An example of size would be 1/3. Does ALL-IN-1 override the cluster size for the disk and pre-allocate a specific number of blocks?
T.R | Title | User | Personal Name | Date | Lines |
---|---|---|---|---|---|
350.1 | Not ALL-IN-1 | IOSG::DAVIS | Mark Davis | Mon Mar 30 1992 13:21 | 13 |
No, The disk cluster size is out of the control of ALL-IN-1. You are probably better off asking this question in another notes file - such as VMSDEV::VAXNOTES. There is a minimum cluster size for disks. This is calculated by (disk size in blocks)/255*4096. Your disk might have a mimimum of 3 anyway. Mark | |||||
350.2 | Only ALL-IN-1 has wrong allocation size | KAOFS::D_STREET | Mon Mar 30 1992 23:45 | 15 | |
Hello again, The problem seems to be localized to ALL-IN-1 mail files. Any files created in another way (EDT, COPY...) get a uesd/alloc with matching values. (as is to be expected with a cluster size of 1) The ALL-IN-1 mail files though, have 1/3 as their used/alloc values. Is there a preallocation aspect to the ALL-IN-1 mail? Since the user cannot modify the files, there is no chance for further extension, therefore no need to allow for the extension in a contiguous manner. I have gone over this with VMS support, and they have determined that there is no strange activity in respect to the VMS side of things. Derek. | |||||
350.3 | Allocation same as input file | IOSG::DAVIS | Mark Davis | Tue Mar 31 1992 10:00 | 10 |
I've checked the code on this. The size is preallocated to be the size of the original file. So if the user disks have a cluster size of 3 then this will be carried over to the size of the file when it is copied to the shared area. If it's any comfort to you, you are not wasting 66% of your space but only 50% as the file header requires one block. Mark |