From owner-freebsd-questions@FreeBSD.ORG Sat Feb 21 10:38:17 2004 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id BEA5716A4F3 for ; Sat, 21 Feb 2004 10:38:17 -0800 (PST) Received: from rwcrmhc11.comcast.net (rwcrmhc11.comcast.net [204.127.198.35]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8B52E43D1F for ; Sat, 21 Feb 2004 10:38:17 -0800 (PST) (envelope-from freebsd-questions-local@be-well.ilk.org) Received: from be-well.no-ip.com ([66.30.196.44]) by comcast.net (rwcrmhc11) with ESMTP id <2004022118381701300datu2e>; Sat, 21 Feb 2004 18:38:17 +0000 Received: by be-well.no-ip.com (Postfix, from userid 1147) id BEC86E; Sat, 21 Feb 2004 13:38:16 -0500 (EST) Sender: lowell@be-well.ilk.org To: Dave Vollenweider References: <20040219185016.5a46068e.radioguy@uni.edu> From: Lowell Gilbert Date: 21 Feb 2004 13:38:16 -0500 In-Reply-To: <20040219185016.5a46068e.radioguy@uni.edu> Message-ID: <447jygwa5j.fsf@be-well.ilk.org> Lines: 17 User-Agent: Gnus/5.09 (Gnus v5.9.0) Emacs/21.3 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii cc: freebsd-questions@freebsd.org Subject: Re: Error when installing FreeBSD 5.2: " /mnt/usr: create symlink failed, no inode free" X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 21 Feb 2004 18:38:17 -0000 Dave Vollenweider writes: > Been trying to install FreeBSD 5.2 using the kern.flp and mfsroot.flp images on floppies and proceeding with a network install via FTP on an old Acer Aspire with a Pentium 120 MHz processor and 80 MB of RAM on a 1.6 GB hard drive (the second on the system; I have another OS on the other hard drive which shall remain nameless). > > The install goes fine until it begins to extract the files to the /usr directory, at which it then spits out this error multiple times: > > /mnt/usr: create symlink failed, no inode free > > and continues to do so whenever something is added to the hard drive during the installation. Curiously enough, though, the installation continues, even though I got that error message again and again when the base install was completed and the extra packages were being installed. I decided at that point to abort the installation. > > Is there any way for me to fix this, and if so, how can I do it? Try allocating all of the disk space to a single root partition. This will make backups a little more difficult, but not much. Alternatively, try a more minimal installation at first, and then add things later, when you can follow the inode usage more closely.