Skip to contentSkip to conversation

different defaults in mke2fs.conf vs. the code itself?

DISCUSSION Eric Sandeen 1 participant 1 message Oct 4, 2006

lore
Share & tools
lore
#0 lore raw

from mke2fs.conf in 1.39:

[defaults]
base_features = sparse_super,filetype,resize_inode,dir_index blocksize = 4096

and yet (for example) in PRS():

if (blocksize <= 0) {
profile_get_integer(profile, "defaults", "blocksize", 0,
1024, &use_bsize);
profile_get_integer(profile, "fs_types", fs_type,
"blocksize", use_bsize, &use_bsiz

So the code itself defaults to 1k blocks, but the shipped config file defaults to 4k blocks? We noticed this when mke2fs.conf went missing from the install environment, and formatting large filesystems took a -very- long time.

Shouldn't these match? Or for that matter, why should the shipped config file be either overriding or re-stating defaults in the code itself? Seems a bit strange to me.

-Eric