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:39:11 -0700	[thread overview]
Message-ID: <20111212143911.GP3810@syscon4.inet> (raw)
In-Reply-To: <4EE5E268.9090404@admin-box.com>

Quick googling around indicates that JFS, or XFS don't have these limitation.
-----quote--------
Many computer programs used by system administrators in UNIX operating systems often designate files with inode numbers. Examples include popular disk 
integrity checking utilities such as the fsck or pfiles. Thus, the need naturally arises to translate inode numbers to file pathnames and vice versa. This can 
be accomplished using the file finding utility find with the -inum option, or the ls command with the proper option (-i on POSIX compliant platforms).

It is possible to use up a device's set of inodes. When this happens, new files cannot be created on the device, even though there may be free space 
available. For example, a mail server may have many small files that don't fill up the disk, but use many inodes to point to the numerous files.

Filesystems (such as JFS, or XFS) escape this limitation with extents and/or dynamic inode allocation, which can 'grow' the filesystem and/or increase the 
number of inodes.
----end quote------

-- 
Joseph



  parent reply	other threads:[~2011-12-12 14:38 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
2011-12-12 14:54   ` Alex Schuster
2011-12-12 15:44     ` Daniel Troeder
2011-12-12 14:39 ` Joseph [this message]
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=20111212143911.GP3810@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