From: Eric Sandeen <sandeen@redhat.com>
To: cy6erGn0m <cy6ergn0m@gmail.com>
Cc: tytso@mit.edu, linux-ext4@vger.kernel.org
Subject: Re: No space left on device after many files creation
Date: Tue, 13 Apr 2010 10:34:15 -0500 [thread overview]
Message-ID: <4BC48EF7.5030702@redhat.com> (raw)
In-Reply-To: <4BC410AB.1030607@gmail.com>
On 04/13/2010 01:35 AM, cy6erGn0m wrote:
> I know that filesystems is not targeted for this usecase, but inodes
> limit looks strange.. why they are can't be allocated dinamically? Can I
ext2/3/4 don't allocate dynamically; there was some talk of trying to
find a way to do this but it's not really very high on the list at all.
xfs does do this, not sure about other filesystems.
> enlarge this limit on the fly?
No, but since you know your usecase, you can change it at mkfs time to
match what you need.
-Eric
next prev parent reply other threads:[~2010-04-13 15:34 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
2010-04-13 6:35 ` cy6erGn0m
2010-04-13 15:34 ` Eric Sandeen [this message]
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=4BC48EF7.5030702@redhat.com \
--to=sandeen@redhat.com \
--cc=cy6ergn0m@gmail.com \
--cc=linux-ext4@vger.kernel.org \
--cc=tytso@mit.edu \
/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 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.