[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: ext3 inode_ratio
- To: luci-discuss@luci.org
- Subject: Re: ext3 inode_ratio
- From: Danny Sauer <danny@dannysauer.com>
- Date: Sat, 12 Jul 2008 08:43:55 -0500
- DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from :user-agent:mime-version:to:subject:references:in-reply-to :content-type:content-transfer-encoding:sender; bh=l6/2vLcnsFN+pPzpSgsJoi9+jkOJisrmjcDy5npgfFI=; b=Rv9ncIy+57L88k3ZYHvjC3z98PKPskKSKbLl5qDq1bBPmgKshDGeQqa6oP7gxwVT5z 5RDyoMv3O+zIML9xVFONoISFictCh4IiaD/8iBGj8VRtC60DzExS4zaa6+8G+tT9K3Gu rNtEeg7aL2KQER8uAnUvXgcdHkyUY414GyQH8=
- DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:user-agent:mime-version:to:subject:references :in-reply-to:content-type:content-transfer-encoding:sender; b=im1/trhHPaqo5wXslmNgGbJ9/Hx+b5qSAjprB38lBrc6DrRpEOHhq2D2DVzVGMYMrH hoSD98btCSHxuu4hY1+QZ9s4bCeKJBziPhTnFfHqMP92ekwDFrKNCKDKFeIXj3L8oDb/ MS4dQNWtrlA9AmenbZlBbESUaSFATSyOtrnV0=
- In-Reply-To: <2ee47fc10807070602m61f081a0n8dccd4dadd398c0b@mail.gmail.com>
- Organization: Linux Users of Central Illinois
- References: <2ee47fc10807070602m61f081a0n8dccd4dadd398c0b@mail.gmail.com>
- Reply-To: luci-discuss@luci.org
- Sender: luci-discuss-owner@luci.org
- User-Agent: Thunderbird 2.0.0.9 (X11/20071031)
damacus wrote:
> In /etc/mke2fs.conf on Ubuntu 8.04, the defaults are:
> base_features = sparse_super,filetype,resize_inode,dir_index,ext_attr
> blocksize = 4096
> inode_size = 128
> inode_ratio = 16384
>
> But if you set -T largefile on mke2fs, it changes inode_ratio to 1048576.
>
> Google hasn't been very helpful. Does anyone know what inode_ratio is
> a ratio of and its effects?
From the mkfs.ext3 man page... :)
*-i*/ bytes-per-inode/
Specify the bytes/inode ratio. *mke2fs* creates an inode for every
/bytes-per-inode/ bytes of space on the disk. The larger the
/bytes-per-inode/ ratio, the fewer inodes will be created. This
value generally shouldn't be smaller than the blocksize of the
filesystem, since then too many inodes will be made.
That parameter, IIRC, is fed to mkfs.ext3 as -i's argument.
Specifically, -T largefile is a shortcut for using one inode per MB. 1
MB is 1024 KB. 1024*1024 is 1048576 bytes.
The effect of changing that is that you either get more space used for
inodes, allowing a lot of small files, or fewer inodes which use less
space, but only allowing a few very large files.
Using something like reiserfs or xfs avoids that whole silly problem. ;)
--Danny
-
To unsubscribe, send email to majordomo@luci.org with
"unsubscribe luci-discuss" in the body.