linux-ext4 - Re: mkfs.ext4: high default -i value undocumented

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Mon, 09 Mar 2009 15:17:23 +0100
From:	Goswin von Brederlow <goswin-v-b@....de>
To:	Eric Sandeen <sandeen@...hat.com>
Cc:	Jan Engelhardt <jengelh@...ozas.de>, linux-ext4@...r.kernel.org,
	kzak@...hat.com
Subject: Re: mkfs.ext4: high default -i value undocumented

Eric Sandeen <sandeen@...hat.com> writes:

> Jan Engelhardt wrote:
>> Hi,
>> 
>> 
>> Creating an ext4 filesystem on a 4 GB image file (to be loop-mounted 
>> later) gives me 256K inodes. Choosing -i 4096 instead gives 1M, which 
>> would mean the default for -i is 16384. 
>
> That's right, look in /etc/mke2fs.conf:
>
> [defaults]
>         base_features =
> sparse_super,filetype,resize_inode,dir_index,ext_attr
>         blocksize = 4096
>         inode_size = 256
>         inode_ratio = 16384
>
>> Besides me finding 16384 a 
>> little unreasonable (XFS offers 2M inodes by default), 
>
> XFS is a totally different beast, because it dynamically allocates
> inodes.  It doesn't really offer *anything* by default.
>
> Which part of a 16384-data-bytes-to-inode-count ratio do you find
> unreasonable?  Do you find it unreasonably high, or unreasonably low?

Too high for 4G, to low for 6 TiB.

MfG
        Goswin
--
To unsubscribe from this list: send the line "unsubscribe linux-ext4" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html