From: Goswin von Brederlow <goswin-v-b@web.de>
To: Eric Sandeen <sandeen@redhat.com>
Cc: Jan Engelhardt <jengelh@medozas.de>,
linux-ext4@vger.kernel.org, kzak@redhat.com
Subject: Re: mkfs.ext4: high default -i value undocumented
Date: Mon, 09 Mar 2009 15:17:23 +0100 [thread overview]
Message-ID: <87r616vkzw.fsf@frosties.localdomain> (raw)
In-Reply-To: <49ADBB03.9070303@redhat.com> (Eric Sandeen's message of "Tue, 03 Mar 2009 17:19:31 -0600")
Eric Sandeen <sandeen@redhat.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
next prev parent reply other threads:[~2009-03-09 14:17 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-03 23:12 mkfs.ext4: high default -i value undocumented Jan Engelhardt
2009-03-03 23:19 ` Eric Sandeen
2009-03-04 0:36 ` Jan Engelhardt
2009-03-04 0:43 ` Eric Sandeen
2009-03-04 0:57 ` Jan Engelhardt
2009-03-04 2:49 ` Theodore Tso
2009-03-04 3:11 ` Jan Engelhardt
2009-03-09 14:17 ` Goswin von Brederlow [this message]
2009-03-09 15:56 ` Eric Sandeen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87r616vkzw.fsf@frosties.localdomain \
--to=goswin-v-b@web.de \
--cc=jengelh@medozas.de \
--cc=kzak@redhat.com \
--cc=linux-ext4@vger.kernel.org \
--cc=sandeen@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox