From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from pigeon.gentoo.org ([208.92.234.80] helo=lists.gentoo.org) by finch.gentoo.org with esmtp (Exim 4.60) (envelope-from ) id 1Ra7CX-0002gk-SP for garchives@archives.gentoo.org; Mon, 12 Dec 2011 14:49:58 +0000 Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 2F95821C156; Mon, 12 Dec 2011 14:49:39 +0000 (UTC) Received: from svr-us4.tirtonadi.com (svr-us4.tirtonadi.com [69.65.43.212]) by pigeon.gentoo.org (Postfix) with ESMTP id B2F0021C072 for ; Mon, 12 Dec 2011 14:48:09 +0000 (UTC) Received: from mail-fx0-f53.google.com ([209.85.161.53]) by svr-us4.tirtonadi.com with esmtpsa (TLSv1:RC4-SHA:128) (Exim 4.69) (envelope-from ) id 1Ra7Am-004DkO-NV for gentoo-user@lists.gentoo.org; Mon, 12 Dec 2011 21:48:08 +0700 Received: by faaa5 with SMTP id a5so1570476faa.40 for ; Mon, 12 Dec 2011 06:48:05 -0800 (PST) Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-user@lists.gentoo.org Reply-to: gentoo-user@lists.gentoo.org MIME-Version: 1.0 Received: by 10.180.104.2 with SMTP id ga2mr26975586wib.33.1323701285180; Mon, 12 Dec 2011 06:48:05 -0800 (PST) Received: by 10.223.103.70 with HTTP; Mon, 12 Dec 2011 06:48:05 -0800 (PST) Received: by 10.223.103.70 with HTTP; Mon, 12 Dec 2011 06:48:05 -0800 (PST) In-Reply-To: <20111212143911.GP3810@syscon4.inet> References: <4EE5E268.9090404@admin-box.com> <20111212143911.GP3810@syscon4.inet> Date: Mon, 12 Dec 2011 21:48:05 +0700 Message-ID: Subject: Re: [gentoo-user] ext4 inode limit reached From: Pandu Poluan To: gentoo-user@lists.gentoo.org Content-Type: multipart/alternative; boundary=f46d04182730e4559504b3e63881 X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: Primary Hostname - svr-us4.tirtonadi.com X-AntiAbuse: Original Domain - lists.gentoo.org X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12] X-AntiAbuse: Sender Address Domain - poluan.info X-Archives-Salt: ce6e017b-ff36-434a-873b-0f3a1c5af924 X-Archives-Hash: 24615f4db2bfd70efb5a7a797860139c --f46d04182730e4559504b3e63881 Content-Type: text/plain; charset=UTF-8 On Dec 12, 2011 9:39 PM, "Joseph" wrote: > > 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------ > ReiserFS also doesn't have problems with inodes because everything are kept in b*trees that can keep growing indefinitely. In fact, I think I read somewhere that ReiserFS is perfect for /var/tmp and /usr/src due to the amount of small files in those directories. Rgds, --f46d04182730e4559504b3e63881 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable


On Dec 12, 2011 9:39 PM, "Joseph" <syscon780@gmail.com> wrote:
>
> 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 ne= ed naturally arises to translate inode numbers to file pathnames and vice v= ersa. 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 compli= ant platforms).
>
> It is possible to use up a device's set of inodes. When this happe= ns, new files cannot be created on the device, even though there may be fre= e space available. For example, a mail server may have many small files tha= t 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 an= d/or increase the number of inodes.
> ----end quote------
>

ReiserFS also doesn't have problems with inodes because everything a= re kept in b*trees that can keep growing indefinitely.

In fact, I think I read somewhere that ReiserFS is perfect for /var/tmp = and /usr/src due to the amount of small files in those directories.

Rgds,

--f46d04182730e4559504b3e63881--