public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Joseph <syscon780@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] ext4 inode limit reached
Date: Mon, 12 Dec 2011 07:31:28 -0700	[thread overview]
Message-ID: <20111212143128.GO3810@syscon4.inet> (raw)
In-Reply-To: <4EE5E268.9090404@admin-box.com>

On 12/12/11 12:15, Daniel Troeder wrote:
>Hello :)
>
>I have an ext4-filesystem that contains /usr/src, the /usr/portage and
>/var/cache/edb. It previously also contained /var/db/pkg, but I had to
>move that some weeks ago, because the fs was "full". Now it's "full"
>again, though it has free blocks. But no inodes are left:
>
>$ fsck -vf /dev/sda5
>[..]
>  655360 inodes used (100.00%)
>[..]
>
>$ find /gentoo -xdev | wc -l
>655338
>
>That's really disappointing. I was using reiser3fs and XFS before, and
>they didn't have that kind of limitation... Uhm... not meant as a rant -
>I like ext4 - that's why I'm moving (almost?) everything to it...
>
>Is there any way to raise the number of inodes without using
>$ mkfs.ext4 -N BIGNUM
>
>Thank you,
>Daniel

That is scary. I just install new HD with 2TB capacity and ext4 that is 2% full and:
$ find /home/joseph/ -xdev | wc -l 
shows: 169977  that is 26% full.

So will run out of inodes before I run out of hard disk space :-/ that is not good.
If other filesystems don't have these kind of limitation I'll be switching.

-- 
Joseph



  parent reply	other threads:[~2011-12-12 14:30 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-12-12 11:15 [gentoo-user] ext4 inode limit reached Daniel Troeder
2011-12-12 12:00 ` Alex Schuster
2011-12-12 14:31 ` Joseph [this message]
2011-12-12 14:54   ` Alex Schuster
2011-12-12 15:44     ` Daniel Troeder
2011-12-12 14:39 ` Joseph
2011-12-12 14:48   ` Pandu Poluan
2011-12-13  0:44 ` Frank Steinmetzger
2011-12-13 10:07   ` Daniel Troeder
2011-12-13  5:24 ` Michael Orlitzky

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=20111212143128.GO3810@syscon4.inet \
    --to=syscon780@gmail.com \
    --cc=gentoo-user@lists.gentoo.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