FIle and Block size relationships ...

[Ben Duncan]

It's not that bad, really. Disk space is cheap these days.
What I am trying to do is figure out the BEST Buffer/cache/page
based upon OS level stuff.

I have been reviewing how to do "variable" length keys in a
NODE, and that's ONE HECK OF A HAIRBALL.

I think I will go with fixed size keys (60 Bytes) in the nodes.
I will have multiple ROOT blocks, one for the MASTER key (it will
be unique) and then 31 more for the the up to 31 secondary keys
the system can have (they will allow duplicates). Since it
seems that Interior nodes are just a road map to get to the
leaf nodes that take you to the DATA record, I think that
will work.

Anyone got any pointers or comments on the above ?

Thanks ...



Mike Reinehr wrote:
> 
> 
> Ben,
> 
> I'm afraid so. Here's an excerpt from man mke2fs:
> 
> 
>>-b block-size 
>>Specify the size of blocks in bytes. Valid block size vales are 1024, 2048
>>and 4096 bytes per block. If omitted, mke2fs block-size is heuristically
>>determined by the file system size and the expected usage of the filesystem
>>(see the -T option). If block-size is negative, then mke2fs will use
>>heuristics to determine the appropriate block size, with the constraint that
>>the block size will be at least block-size bytes. This is useful for certain
>>hardware devices which require that the blocksize be a multiple of 2k.
> 
> 
> You can use 'stat -f /dev/hd... ' to check your file system specifications.
> 
> Cheers!
> 
> cmr
> 

-- 
Ben Duncan   - Business Network Solutions, Inc. 336 Elton Road  Jackson MS, 39212
"Never attribute to malice, that which can be adequately explained by stupidity"
        - Hanlon's Razor