linux-ext4.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Eric Sandeen <sandeen@redhat.com>
To: Jan Engelhardt <jengelh@medozas.de>
Cc: linux-ext4@vger.kernel.org, kzak@redhat.com
Subject: Re: mkfs.ext4: high default -i value undocumented
Date: Tue, 03 Mar 2009 18:43:39 -0600	[thread overview]
Message-ID: <49ADCEBB.6080904@redhat.com> (raw)
In-Reply-To: <alpine.LSU.2.00.0903040125410.12894@fbirervta.pbzchgretzou.qr>

Jan Engelhardt wrote:
> On Wednesday 2009-03-04 00:19, Eric Sandeen wrote:
>>> 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
> 
> Interesting - thanks for the hint.
> 
>>> 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?
> 
> I think it's a bit too high, causing the amount of usable inodes
> to be a bit too low. 

When we doubled the size of inodes by default, we halved the count.  I
also have a sneaking suspicion that it may be too low for some
scenarios, but probably ok for most.

>>> the big 
>>> point is that the mke2fs manpage (belonging to util-linux, hence Cc) 
>> not so much:
>> $ rpm -qf /usr/share/man/man8/mke2fs.8.gz
>> e2fsprogs-1.41.3-2.fc10.x86_64
> 
> Sorry, I had looked for man8/mkfs.ext2.8.gz. I am not quite sure
> what makes some developers deviate(*) from the mkfs.$name/fsck.$name
> scheme ;-)

$ rpm -qf /usr/share/man/man8/mkfs.ext2.8.gz
e2fsprogs-1.41.3-2.fc10.x86_64

:)

> (*) e2, reiser(3), dosfs
> 
>>> does not mention this 16384 default.
>>> Hope this can be addressed.
>> You could send a patch :)
> 
> parent b2ca48f40eb33bd86b8d53d4373e7fce96bced4a (v1.41.4)
> commit ca28058c4004ceaa42edeb6ba61bc2aa53d7c03d
> Author: Jan Engelhardt <jengelh@medozas.de>
> Date:   Wed Mar 4 01:36:09 2009 +0100
> 
> doc: mention default for mke2fs -i

thanks :)  (up to Ted now)

-Eric

  reply	other threads:[~2009-03-04  0:43 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 [this message]
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
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=49ADCEBB.6080904@redhat.com \
    --to=sandeen@redhat.com \
    --cc=jengelh@medozas.de \
    --cc=kzak@redhat.com \
    --cc=linux-ext4@vger.kernel.org \
    /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;
as well as URLs for NNTP newsgroup(s).