From owner-freebsd-current Sun Feb 23 11:52:20 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id LAA29156 for current-outgoing; Sun, 23 Feb 1997 11:52:20 -0800 (PST) Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.50]) by freefall.freebsd.org (8.8.5/8.8.5) with SMTP id LAA29148 for ; Sun, 23 Feb 1997 11:52:14 -0800 (PST) Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id MAA23263 for current@freebsd.org; Sun, 23 Feb 1997 12:50:44 -0700 From: Terry Lambert Message-Id: <199702231950.MAA23263@phaeton.artisoft.com> Subject: Interesting CVSUP failure To: current@freebsd.org Date: Sun, 23 Feb 1997 12:50:44 -0700 (MST) X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk I just resolved an interesting cvsup failure, which I think is indicative of a "nice" boundry failure in the FFS code. During an earlier cvsup, the disk where my tree is filled up during the transfer, and an out of range block was allocated to a file. I cleaned up the disk to get (a lot) more free space, but subsequent cvsup's all failed at the point of the allocation (obviously) and cvsup kept reporting a failure (the wrong one). I finally sat down to spend some time fixing the error, and turned on my console monitor, and noticed that the disk error was occuring. Using some brute-force FS debugging tools, I located the offending file, deleted it, and the cvsup ran to completion. Is there any chance that cvsup could report a more meaningful message for SIGABRT? In any case, there's also the boudry allocation problem in FFS on a hard disk-full (as opposed to a soft one from hitting the reserve) that should be looked into. Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers.