From nobody@FreeBSD.org  Wed Feb 20 10:20:13 2002
Return-Path: <nobody@FreeBSD.org>
Received: from freefall.freebsd.org (freefall.FreeBSD.org [216.136.204.21])
	by hub.freebsd.org (Postfix) with ESMTP id D753237B419
	for <freebsd-gnats-submit@FreeBSD.org>; Wed, 20 Feb 2002 10:20:12 -0800 (PST)
Received: (from nobody@localhost)
	by freefall.freebsd.org (8.11.6/8.11.6) id g1KIKCJ14506;
	Wed, 20 Feb 2002 10:20:12 -0800 (PST)
	(envelope-from nobody)
Message-Id: <200202201820.g1KIKCJ14506@freefall.freebsd.org>
Date: Wed, 20 Feb 2002 10:20:12 -0800 (PST)
From: Rex Buddenberg <budden@nps.navy.mil>
To: freebsd-gnats-submit@FreeBSD.org
Subject: FreeBSD 4.5 won't install ... out of inodes
X-Send-Pr-Version: www-1.0

>Number:         35150
>Category:       misc
>Synopsis:       FreeBSD 4.5 won't install ... out of inodes
>Confidential:   no
>Severity:       critical
>Priority:       medium
>Responsible:    freebsd-bugs
>State:          closed
>Quarter:        
>Keywords:       
>Date-Required:  
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Wed Feb 20 10:30:01 PST 2002
>Closed-Date:    Fri Aug 09 09:33:01 PDT 2002
>Last-Modified:  Fri Aug 09 09:33:01 PDT 2002
>Originator:     Rex Buddenberg
>Release:        4.5-stable
>Organization:
Naval Postgraduate School
>Environment:
TI TravelMate, Intel 133MHz CPU, 24M RAM, IBM DPRA-21215 hard drive (1.2 G capacity)
>Description:
Installation (over ftp) crashes partway through.  Screen complaint is inability to make symbolic links, out of inodes.  

The disk is only about half full, no slices pushing available capacity. 

Problem recurred on two different disk drives, same machine.


I did not get this problem with a 4.5 installation on a Keynote laptop with 8G drive ... that installation was normal.

FreeBSD 4.4 installation works normally on the above-described setup (am finishing that up right now).  

Therefore, appears to be a directory layout problem in 4.5

>How-To-Repeat:
ftp install on the machines
>Fix:

>Release-Note:
>Audit-Trail:

From: "Bill McNAMARA" <wimac@tidhom1g.grenoble.hp.com>
To: <freebsd-gnats-submit@FreeBSD.org>, <budden@nps.navy.mil>
Cc:  
Subject: Re: misc/35150: FreeBSD 4.5 won't install ... out of inodes
Date: Fri, 22 Feb 2002 09:58:00 +0100

 I've come across exactly the same problem on a 2G disk drive Auto FS layout.
 
 I resolve it by changing the newfs options on install.. well rather removing
 all options.
 ie: just leave the newfs (and not -b 16k -...)
 
 Defaults should be changed.
 
 Later,
 Bill
 --
 William McNAMARA
 mailto:wimac@tidhom1g.grenoble.hp.com
 B1N2H1
 

From: "Crist J. Clark" <cjc@FreeBSD.ORG>
To: Rex Buddenberg <budden@nps.navy.mil>
Cc: freebsd-gnats-submit@FreeBSD.ORG
Subject: Re: misc/35150: FreeBSD 4.5 won't install ... out of inodes
Date: Fri, 22 Feb 2002 06:04:32 -0800

 Is it possible to get the 'df -i' output for the partitions on the
 drive?
 -- 
 Crist J. Clark                     |     cjclark@alum.mit.edu
                                    |     cjclark@jhu.edu
 http://people.freebsd.org/~cjc/    |     cjc@freebsd.org

From: "Crist J. Clark" <crist.clark@attbi.com>
To: "Buddenberg, Rex" <budden@nps.navy.mil>
Cc: "'Bill McNAMARA'" <wimac@tidhom1g.grenoble.hp.com>,
	bug-followup@freebsd.org
Subject: Re: misc/35150: FreeBSD 4.5 won't install ... out of inodes
Date: Fri, 22 Feb 2002 11:39:06 -0800

 On Fri, Feb 22, 2002 at 10:30:42AM -0800, Buddenberg, Rex wrote:
 > Bill, Christ,
 > 
 > We're pretty close to the smoking gun ... here's what I squeezed out of the
 > drive:
 > 
 > 
 > Filesystem  1K-blocks     Used    Avail Capacity iused   ifree  %iused
 > Mounted on
 > /dev/ad0s1a	257980	62800	   174544	26%	1276	14978	8%
 > /
 > 
 > Note that /usr doesn't show up on the troubled drive at all (and vfstab is
 > entirely
 > missing from /etc). I manually mounted /dev/ad0s1f to /usr where it belongs
 > and
 > got this:
 > /dev/ad0s1f	515996	124	   474596	0%	3	32507	0%
 > /usr
 
 Yep. Looks like 16K blocks in each.
 
 > 
 > On a normal FreeBSD 4.4 installation (similar sized disk), I got this:
 > 
 > /dev/ad0s1a     99183    32339    58910    35%    1498   23588     6%   /
 > /dev/ad0s1f    964359   642238   244973    72%   82806  159240    34%   /usr
 > /dev/ad0s1e     19815     1777    16453    10%     286    4768     6%   /var
 > procfs              4        4        0   100%      42     490     8%
 > /proc
 
 Those are 4K blocks? I would expect 8K from newfs(8)'s source.
 
 >  I used all the default settings on installation ... no tweaks whatsoever.
 > Since I can boot up in single user mode, the problem appears to show up
 > wholly
 > in /usr.
 
 No, it just that there are that many more files in /usr that you ran
 out of inodes in /usr. The default 8K to 16K was changed in revision
 1.30.2.8 of newfs.c.
 
 A 500 MB partition is tiny by today's standards. Sometime you have to
 make the choice, do you focus support the few using _really_ old stuff
 or the majority on much newer hardware. Of course, the other
 possibility is to make sysinstall(8) smarter about this kind of thing
 (and about partition sizing, and about...), but someone can always
 figure out a situation where any simple rules break down and the
 discussions tend to bikeshed.
 
 So, I don't really think the bug is in newfs(8). newfs(8) does not
 really need to be too smart. I think if there is a bug here at all, it
 would be sysinstall(8) not being smart enough to tell newfs(8) how to
 do things better.
 -- 
 Crist J. Clark                     |     cjclark@alum.mit.edu
                                    |     cjclark@jhu.edu
 http://people.freebsd.org/~cjc/    |     cjc@freebsd.org

From: "Buddenberg, Rex" <budden@nps.navy.mil>
To: "'cjclark@alum.mit.edu'" <cjclark@alum.mit.edu>,
	"Buddenberg, Rex" <budden@nps.navy.mil>
Cc: 'Bill McNAMARA' <wimac@tidhom1g.grenoble.hp.com>,
	bug-followup@freebsd.org
Subject: RE: misc/35150: FreeBSD 4.5 won't install ... out of inodes
Date: Fri, 22 Feb 2002 13:03:03 -0800

 I think i follow the analysis, Crist.  Thanks.
 
 And yes, smartening up Sysinstall would be the right approach.  Perhaps a
 better one would be to smarten up the documentation so dummies like me know
 what overrides make sense.
 
 So ... what should I do at installation time to make 4.5 run properly on
 these beasts?
 
 Thanks again.
 
 > -----Original Message-----
 > From: Crist J. Clark [mailto:crist.clark@attbi.com]
 > Sent: Friday, February 22, 2002 11:39 AM
 > To: Buddenberg, Rex
 > Cc: 'Bill McNAMARA'; bug-followup@freebsd.org
 > Subject: Re: misc/35150: FreeBSD 4.5 won't install ... out of inodes
 > 
 > 
 > On Fri, Feb 22, 2002 at 10:30:42AM -0800, Buddenberg, Rex wrote:
 > > Bill, Christ,
 > > 
 > > We're pretty close to the smoking gun ... here's what I 
 > squeezed out of the
 > > drive:
 > > 
 > > 
 > > Filesystem  1K-blocks     Used    Avail Capacity iused   
 > ifree  %iused
 > > Mounted on
 > > /dev/ad0s1a	257980	62800	   174544	26%	1276	
 > 14978	8%
 > > /
 > > 
 > > Note that /usr doesn't show up on the troubled drive at all 
 > (and vfstab is
 > > entirely
 > > missing from /etc). I manually mounted /dev/ad0s1f to /usr 
 > where it belongs
 > > and
 > > got this:
 > > /dev/ad0s1f	515996	124	   474596	0%	3	
 > 32507	0%
 > > /usr
 > 
 > Yep. Looks like 16K blocks in each.
 > 
 > > 
 > > On a normal FreeBSD 4.4 installation (similar sized disk), 
 > I got this:
 > > 
 > > /dev/ad0s1a     99183    32339    58910    35%    1498   
 > 23588     6%   /
 > > /dev/ad0s1f    964359   642238   244973    72%   82806  
 > 159240    34%   /usr
 > > /dev/ad0s1e     19815     1777    16453    10%     286    
 > 4768     6%   /var
 > > procfs              4        4        0   100%      42     
 > 490     8%
 > > /proc
 > 
 > Those are 4K blocks? I would expect 8K from newfs(8)'s source.
 > 
 > >  I used all the default settings on installation ... no 
 > tweaks whatsoever.
 > > Since I can boot up in single user mode, the problem 
 > appears to show up
 > > wholly
 > > in /usr.
 > 
 > No, it just that there are that many more files in /usr that you ran
 > out of inodes in /usr. The default 8K to 16K was changed in revision
 > 1.30.2.8 of newfs.c.
 > 
 > A 500 MB partition is tiny by today's standards. Sometime you have to
 > make the choice, do you focus support the few using _really_ old stuff
 > or the majority on much newer hardware. Of course, the other
 > possibility is to make sysinstall(8) smarter about this kind of thing
 > (and about partition sizing, and about...), but someone can always
 > figure out a situation where any simple rules break down and the
 > discussions tend to bikeshed.
 > 
 > So, I don't really think the bug is in newfs(8). newfs(8) does not
 > really need to be too smart. I think if there is a bug here at all, it
 > would be sysinstall(8) not being smart enough to tell newfs(8) how to
 > do things better.
 > -- 
 > Crist J. Clark                     |     cjclark@alum.mit.edu
 >                                    |     cjclark@jhu.edu
 > http://people.freebsd.org/~cjc/    |     cjc@freebsd.org
 > 

From: Tarjei.Jensen@kvaerner.com
To: freebsd-gnats-submit@FreeBSD.org, budden@nps.navy.mil
Cc:  
Subject: Re: misc/35150: FreeBSD 4.5 won't install ... out of inodes
Date: Mon, 18 Mar 2002 12:29:44 -0000

 I had the same problem, just so nobody think the original poster is alone
 with the problem.
 
 Just re-iterate the problem:
 I just tried to install FreeBSD 4.5 on a 1,2GB harddisk. I tried to install
 user, ports and Linux support.
 
 How I fixed it:
 Since the install failed because the system ran out of inodes on the /usr
 partition during the Linux support install, I changed the inode size to 2K
 by adding "-i 2048" to the newfs parameter list in the options page in
 sysinstall.
 
 Perhaps the install program should be a bit smarter with regards to inode
 sizes on the various partitions? Or perhaps the install program should let
 newfs decide on its own how big the various parameters should be?
 
 Perhaps this is such a showstopper that a new iso should be issued?
 
 
 greetings,
 
 
State-Changed-From-To: open->closed 
State-Changed-By: schweikh 
State-Changed-When: Fri Aug 9 09:30:17 PDT 2002 
State-Changed-Why:  
It is unlikely that anyone will beat the dead horse (sysinstall) 
to be smarter about the case of small disks. The workaround, as 
people have noted, is to modify the newf -i option value. 

http://www.freebsd.org/cgi/query-pr.cgi?pr=35150 
>Unformatted:
