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 <gentoo-user+bounces-132370-garchives=archives.gentoo.org@lists.gentoo.org>) id 1Ra71J-0007Xj-N6 for garchives@archives.gentoo.org; Mon, 12 Dec 2011 14:38:21 +0000 Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 737CB21C136; Mon, 12 Dec 2011 14:38:12 +0000 (UTC) Received: from mail.shawcable.com (shawmail.shawcable.com [64.59.128.220]) by pigeon.gentoo.org (Postfix) with ESMTP id 3F89D21C05A for <gentoo-user@lists.gentoo.org>; Mon, 12 Dec 2011 14:37:17 +0000 (UTC) Received: from bpd2mi5no-svcs.prod.shawcable.com ([10.0.184.160]) by bpd2mo2no-ssvc.prod.shawcable.com with ESMTP; 12 Dec 2011 07:37:16 -0700 X-Cloudmark-SP-Filtered: true X-Cloudmark-SP-Result: v=1.1 cv=t+ZAJ7mrPn0ghCTQRrYVa3vbw5sbuRhC9KBpKnc45f0= c=1 sm=1 a=wom5GMh1gUkA:10 a=2aS7xn65_L4A:10 a=nDghuxUhq_wA:10 a=BLceEmwcHowA:10 a=8nJEP1OIZ-IA:10 a=dgx804EzjhD8CRYpIFkhZA==:17 a=V6Obo-0Tz-n4ipgZC-UA:9 a=wPNLvfGTeEIA:10 a=HpAAvcLHHh0Zw7uRqdWCyQ==:117 X-IronPort-AV: E=Sophos;i="4.71,339,1320649200"; d="scan'208";a="350063196" Received: from unknown (HELO bpd2mi5no-cmts.prod.shawcable.com) ([192.168.183.160]) by bpd2mi5no-cmts.prod.shawcable.com with ESMTP; 12 Dec 2011 07:37:16 -0700 X-reinject: true Received: from unknown (HELO syscon4.localdomain) ([68.148.245.78]) by bpd2mi5no-dmz.prod.shawcable.com with ESMTP; 12 Dec 2011 07:37:16 -0700 Received: by syscon4.localdomain (Postfix, from userid 1000) id 5FE3A1CD191; Mon, 12 Dec 2011 07:39:11 -0700 (MST) Date: Mon, 12 Dec 2011 07:39:11 -0700 From: Joseph <syscon780@gmail.com> To: gentoo-user@lists.gentoo.org Subject: Re: [gentoo-user] ext4 inode limit reached Message-ID: <20111212143911.GP3810@syscon4.inet> References: <4EE5E268.9090404@admin-box.com> Precedence: bulk List-Post: <mailto:gentoo-user@lists.gentoo.org> List-Help: <mailto:gentoo-user+help@lists.gentoo.org> List-Unsubscribe: <mailto:gentoo-user+unsubscribe@lists.gentoo.org> List-Subscribe: <mailto:gentoo-user+subscribe@lists.gentoo.org> List-Id: Gentoo Linux mail <gentoo-user.gentoo.org> X-BeenThere: gentoo-user@lists.gentoo.org Reply-to: gentoo-user@lists.gentoo.org MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1; format=flowed Content-Disposition: inline In-Reply-To: <4EE5E268.9090404@admin-box.com> User-Agent: Mutt/1.5.21 (2010-09-15) X-Archives-Salt: 5c42aeac-d851-4fec-a631-29a8eea9cb7a X-Archives-Hash: a180371214b8e42a4a7d4b1269d51a7d 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