From owner-freebsd-stable@FreeBSD.ORG  Tue Dec  9 20:21:07 2003
Return-Path: <owner-freebsd-stable@FreeBSD.ORG>
Delivered-To: freebsd-stable@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id CFD8516A4CE
	for <freebsd-stable@FreeBSD.ORG>;
	Tue,  9 Dec 2003 20:21:07 -0800 (PST)
Received: from ns1.itga.com.au (ns1.itga.com.au [202.53.40.214])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 899C943D2B
	for <freebsd-stable@FreeBSD.ORG>;
	Tue,  9 Dec 2003 20:21:05 -0800 (PST)	(envelope-from gnb@itga.com.au)
Received: from lightning.itga.com.au (lightning.itga.com.au [192.168.71.20])
	by ns1.itga.com.au (8.12.9/8.12.9) with ESMTP id hBA4KsR5054569;
	Wed, 10 Dec 2003 15:20:54 +1100 (EST)
	(envelope-from gnb@itga.com.au)
Received: from lightning.itga.com.au (localhost [127.0.0.1])
	by lightning.itga.com.au (8.9.3/8.9.3) with ESMTP id PAA05574;
	Wed, 10 Dec 2003 15:20:54 +1100 (EST)
Message-Id: <200312100420.PAA05574@lightning.itga.com.au>
X-Mailer: exmh version 2.4 05/15/2001 with nmh-1.0.4
From: Gregory Bond <gnb@itga.com.au>
To: pirat <pirat@access.inet.co.th>
In-reply-to: Your message of Wed, 10 Dec 2003 11:08:57 +0700.
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Wed, 10 Dec 2003 15:20:54 +1100
Sender: gnb@itga.com.au
cc: freebsd-stable@FreeBSD.ORG
Subject: Re: newfs for insufficient inodes file system 
X-BeenThere: freebsd-stable@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: Production branch of FreeBSD source code
	<freebsd-stable.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
	<mailto:freebsd-stable-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-stable>
List-Post: <mailto:freebsd-stable@freebsd.org>
List-Help: <mailto:freebsd-stable-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
	<mailto:freebsd-stable-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Wed, 10 Dec 2003 04:21:07 -0000


Urk, running newfs on /usr (or /) is major-league, heavy-duty,
potential-foot-shooting time.  Be VERY VERY careful. In fact, if you have to
ask how, there is a pretty good chance you'll wind up hopping and bleeding.

First step is to run "df -i" and see what the current space/inode usage is.
Then check if the standard newfs params look OK (i.e. /usr currently has
substantially fewer than the 5x21504 inodes newfs would create in use.) 

Overall the best bet is probably to back up all the data and re-install, using 
adjusted newfs parameters if necessary.