Re: out of inodes... new install

[Matthew Dillon <dillon@xxxxxxxxxxxxxxxxxxxx>]

:> Filesystem  1K-blocks    Used  Avail Capacity iused  ifree %iused  Mounted on
:> /dev/ad0s2a    254063   63277 170461    27%    1849  61893    3%   /
:> /dev/ad0s2d    254063     556 233182     0%     192  63550    0%   /var
:> /dev/ad0s2e    254063       3 233735     0%       3  63739    0%   /tmp
:> /dev/ad0s2f   3120908 2122892 748344    74%  195809     29  100%   /usr
:> /dev/ad0s2g    952771  443491 433059    51%   39039 200319   16%   /home
:> procfs              4       4      0   100%      22   6142    0%   /proc
:> 
:> ...all out ..for what it's worth...

    I don't know why so few inodes were created for that filesystem.  I
    tried simulating a disk of that size with VN and what I got was:
 
dhcp62# newfs -U /dev/vn0d
	...
dhcp62# mount /dev/vn0d /mnt
dhcp62# df -i /mnt
Filesystem 1K-blocks Used   Avail Capacity iused  ifree %iused  Mounted on
/dev/vn0d    3072218    2 2826440     0%       1 384765    0%   /mnt

dhcp62# newfs -U -f 1024 -b 8192 /dev/vn0d
	...
dhcp62# mount /dev/vn0d /mnt
dhcp62# df -i /mnt
Filesystem 1K-blocks Used   Avail Capacity iused  ifree %iused  Mounted on
/dev/vn0d    3025130    1 2783119     0%       1 757117    0%   /mnt

    By default newfs uses 2K/16K for the fragment and block size.  I
    tried both the default and also manually setting it to 1K/8K.

    Maybe there is a geometry issue here that we don't know about.  Could
    you post the output of 'disklabel ad0s2' ?

						-Matt