Hallo Fred,
-----Original Message----- From: Fred Ockert [mailto:m.ockert@bss-services.de] Sent: Tuesday, July 24, 2007 12:51 PM To: Lentes, Bernd Cc: opensuse-de@opensuse.org Subject: Re: OpenSUSE 10.2 64-bit - thread ggf. umbenennen ?
gab es nicht für jeden Block eine iNode ?
Standardmäßig wohl ein inode pro 2 Blöcke. Habe das mal auf einer ext3-Partition (SuSE 10.2) ausprobiert: pc52785:~ # dumpe2fs -h /dev/sdb2 dumpe2fs 1.39 (29-May-2006) Filesystem volume name: <none> Last mounted on: <not available> Filesystem UUID: ac91ba05-155b-4781-bd65-1fc49696f08c Filesystem magic number: 0xEF53 Filesystem revision #: 1 (dynamic) Filesystem features: has_journal ext_attr resize_inode dir_index filetype needs_recovery sparse_super large_file Default mount options: (none) Filesystem state: clean Errors behavior: Continue Filesystem OS type: Linux ==> Inode count: 13123584 ==> Block count: 26216071 !!!!! Und das kann man bei der Formatierung (und nur da) ändern. man mkfs.ext3 sagt: ----------- -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. Be warned that is not possible to expand the number of inodes on a filesystem after it is created, so be careful deciding the correct value for this parameter. ----------- Bernd -- Um die Liste abzubestellen, schicken Sie eine Mail an: opensuse-de+unsubscribe@opensuse.org Um eine Liste aller verfuegbaren Kommandos zu bekommen, schicken Sie eine Mail an: opensuse-de+help@opensuse.org