* different defaults in mke2fs.conf vs. the code itself?
@ 2006-10-04 17:37 Eric Sandeen
0 siblings, 0 replies; only message in thread
From: Eric Sandeen @ 2006-10-04 17:37 UTC (permalink / raw)
To: ext4 development
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
^ permalink raw reply [flat|nested] only message in thread
only message in thread, other threads:[~2006-10-04 17:37 UTC | newest]
Thread overview: (only message) (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2006-10-04 17:37 different defaults in mke2fs.conf vs. the code itself? Eric Sandeen
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.