From: tytso@mit.edu
To: Eric Sandeen <sandeen@redhat.com>
Cc: cy6erGn0m <cy6ergn0m@gmail.com>, linux-ext4@vger.kernel.org
Subject: Re: No space left on device after many files creation
Date: Mon, 12 Apr 2010 18:44:29 -0400 [thread overview]
Message-ID: <20100412224429.GN1849@thunk.org> (raw)
In-Reply-To: <4BC39805.7090807@redhat.com>
On Mon, Apr 12, 2010 at 05:00:37PM -0500, Eric Sandeen wrote:
> cy6erGn0m wrote:
> > In the past I have done the same test for ext3 and it was created ~10M
> > files in one firectory at working filesystem (/home) and it was no
> > issues reached.
> >
> > On ext4 i found inodes max size is limited as you wrote:
> > [root@cgmachine sandbox]# df -i /e4
> > Файловая система Инодов Испол Своб Исп % смонтирована на
> > (file system/inodes/used/free/used%/mounted on)
> > /dev/sda4 1,8M 1,8M 0 100% /e4
> > [root@cgmachine sandbox]#
> >
> > Why inodes count limit is so small by default? Is it depends on
> > partition size?
>
> it does depend on partition size; the inode_ratio = 16384 in mke2fs.conf
> says 1 inode per 16k of filesystem space.
1.8 million inodes is hardly small..... most people complain that
we're reserving too much space for inodes.
Cy6erGn0m, What is your use case where the average file size for your
20G partition is smaller that 16k?
- Ted
--
To unsubscribe from this list: send the line "unsubscribe linux-ext4" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2010-04-12 23:56 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-12 21:20 No space left on device after many files creation cy6erGn0m
2010-04-12 21:28 ` Eric Sandeen
2010-04-12 21:57 ` cy6erGn0m
2010-04-12 22:00 ` Eric Sandeen
2010-04-12 22:44 ` tytso [this message]
2010-04-13 6:35 ` cy6erGn0m
2010-04-13 15:34 ` Eric Sandeen
2010-04-15 15:14 ` Andi Kleen
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=20100412224429.GN1849@thunk.org \
--to=tytso@mit.edu \
--cc=cy6ergn0m@gmail.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;
as well as URLs for NNTP newsgroup(s).