From owner-freebsd-questions@FreeBSD.ORG Sun Mar 30 05:48:31 2003 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 640E237B404 for ; Sun, 30 Mar 2003 05:48:31 -0800 (PST) Received: from mail.airnet.com.au (mail.airnet.com.au [202.174.32.5]) by mx1.FreeBSD.org (Postfix) with SMTP id D02D243FBD for ; Sun, 30 Mar 2003 05:48:29 -0800 (PST) (envelope-from ws@senet.com.au) Received: (qmail 9505 invoked from network); 30 Mar 2003 13:48:26 -0000 Received: from dsl2-81.gw1.adl1.airnet.com.au (HELO predatorii) (202.174.37.81) by mail.airnet.com.au with SMTP; 30 Mar 2003 13:48:26 -0000 Message-ID: <025701c2f6c3$db623fe0$0264a8c0@regional.net.au> From: "W. Sierke" To: "Jason End" , References: <20030330131221.3273.qmail@web80407.mail.yahoo.com> Date: Sun, 30 Mar 2003 23:24:17 +0930 Organization: OVirt Technologies MIME-Version: 1.0 Content-Type: text/plain; charset="Windows-1252" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2800.1106 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106 Subject: Re: write failed, disk is full 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: Sun, 30 Mar 2003 13:48:33 -0000 From: "Jason End" > Installing 4.7 through ftp, I get a series of errors > that say things like: > / write failed. disk is full > failed to create /usr/src disk is full > > The disk is new, and certainly isn't full, so I'm > thinking it could be a problem of where I've place the > partitions on the disk. > The disk is a new 120Gb WD1200JB and the relevant > partitions are as such (in this order): > 10gb ntfs > 3gb freebsd (/) > 800mb freebsd (swap) > 55gb freebsd (/usr) I had a similar experience, albeit on a much smaller partition. Just to be sure, check that you haven't run out of inodes somewhere (assuming you can boot into a console): df -i I recently talked with someone on IRC who had just had a similar experience. I'm wondering if there might be an "issue" here in that perhaps the default block/fragment size being used during new installations is too small? Wayne