Date: Fri, 22 Feb 2002 11:40:10 -0800 (PST) From: "Crist J. Clark" <crist.clark@attbi.com> To: freebsd-bugs@FreeBSD.org Subject: Re: misc/35150: FreeBSD 4.5 won't install ... out of inodes Message-ID: <200202221940.g1MJeAa72547@freefall.freebsd.org>
next in thread | raw e-mail | index | archive | help
The following reply was made to PR misc/35150; it has been noted by GNATS.
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
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-bugs" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200202221940.g1MJeAa72547>