From owner-freebsd-stable Fri Aug 16 10:34:46 2002 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 C826737B400 for ; Fri, 16 Aug 2002 10:34:42 -0700 (PDT) Received: from mail2.qc.uunet.ca (mail2.qc.uunet.ca [198.168.54.17]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3756043E4A for ; Fri, 16 Aug 2002 10:34:41 -0700 (PDT) (envelope-from anarcat@anarcat.ath.cx) Received: from xtanbul (IDENT:506@[216.94.147.34]) by mail2.qc.uunet.ca (8.9.3/8.9.3) with ESMTP id NAA15521; Fri, 16 Aug 2002 13:34:08 -0400 Date: Fri, 16 Aug 2002 13:23:52 -0400 Subject: Re: "filesystem is full" during installation of 4.6.2-REL Content-Type: text/plain; charset=US-ASCII; format=flowed Mime-Version: 1.0 (Apple Message framework v482) Cc: Andrew Boothman , stable@freebsd.org To: "Scott M. Nolde" From: Antoine Beaupre In-Reply-To: <20020816031235.GA411@smnolde.com> Message-Id: Content-Transfer-Encoding: 7bit X-Mailer: Apple Mail (2.482) Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Thursday, August 15, 2002, at 11:12 PM, Scott M. Nolde wrote: > Andrew Boothman(andrew@cream.org)@2002.08.16 03:12:25 +0000: >> However, during an FTP install from ftp.uk.freebsd.org when it reaches >> 'chunk 4' the system displays a message saying "Write failure on >> transfer (wrote -1 bytes of 240260 bytes)" and "/: write failed, >> filesystem is full" >> >> VTY1 shows : >> . >> . >> bin/ls >> bin/mkdev >> bin/mv >> pid 72 (cpio), uid 0 on /: filesystem is full >> /stand/cpio: write error: No space left on drive >> /stand/gunzip: failed fwrite FWIW, I've had such problems with restarted sysinstalls. In fact, a lot of the recent uses I had of sysinstall ended up with such an error. I think it is due to sysinstall not correctly mounting the configured file systems. The behavior is quite erratic and i haven't been able to pinpoint the exact problem but restarting the install, reformating the partitions works usually ok. >> A quick /stand/df on VTY4 shows 101% capacity on /dev/md0c mounted on / >> but just 1% capacity on /dev/ad0s1a mounted on /mnt. That's odd, for sure. But md0c sure should be full or almost. And the disks should be mounted on /mnt, IIRC. >> I've never delved >> this far into a sysinstall installation before, but it sounds like it >> is >> failing on unpacking files into a memory disk? What could have caused >> this problem? I don't know. >> A reboot and going through the installation process again brought >> exactly the same failure in exactly the same place. Odd. I usually solved the issue this way. Are you sure you properly set up your partitions? > md0c is a memory disk and you're not actually writing to your hard > drive, > which would be ad0 or ad1. What happens, I think, is that since the disk is supposed to be mounted on /mnt, and it is not, the whole thing gets extracted in md0's /mnt. A. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message