From owner-freebsd-current@FreeBSD.ORG Thu Mar 6 00:11:04 2008 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 23E85106567C for ; Thu, 6 Mar 2008 00:11:04 +0000 (UTC) (envelope-from peter@wemm.org) Received: from wr-out-0506.google.com (wr-out-0506.google.com [64.233.184.232]) by mx1.freebsd.org (Postfix) with ESMTP id A79518FC26 for ; Thu, 6 Mar 2008 00:11:03 +0000 (UTC) (envelope-from peter@wemm.org) Received: by wr-out-0506.google.com with SMTP id c49so2229728wra.19 for ; Wed, 05 Mar 2008 16:11:02 -0800 (PST) Received: by 10.101.66.14 with SMTP id t14mr8273325ank.69.1204762262318; Wed, 05 Mar 2008 16:11:02 -0800 (PST) Received: by 10.100.8.6 with HTTP; Wed, 5 Mar 2008 16:11:02 -0800 (PST) Message-ID: Date: Wed, 5 Mar 2008 16:11:02 -0800 From: "Peter Wemm" To: "David Wolfskill" In-Reply-To: <20080305131802.GC53010@bunrab.catwhisker.org> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <47CE4FED.2000800@freebsd.org> <20080305131802.GC53010@bunrab.catwhisker.org> Cc: FreeBSD Current , David Xu Subject: Re: cvs [update aborted]: received broken pipe signal X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 06 Mar 2008 00:11:04 -0000 On Wed, Mar 5, 2008 at 5:18 AM, David Wolfskill wrote: > On Wed, Mar 05, 2008 at 03:46:53PM +0800, David Xu wrote: > > What's wrong with our cvs server? I can not receive updates: > > > > cvs update: Updating . > > cvs update: Updating alpha > > ... > > > cvs update: Updating amd64/conf > > cvs update: Updating amd64/ia32 > > cvs update: Updating amd64/includeRead from remote host > > ncvs.freebsd.org: Connection reset by peer > > > > cvs [update aborted]: end of file from server (consult above messages if > > any) > > You might need to take a look at the server, but I think I recall seeing > similar symptoms when I created /tmp as a swap-backed md-resident file > system with the default inode density and /tmp didn't actually become > "full," but ran out of inodes during a period of heavy (for that > environment) usage. > > Adjusting the tmpmfs_flags specification in /etc/rc.conf (for the CVS > server) to say 'tmpmfs_flags="-i1024 -o async -S"', then re-creating > /tmp alleviated the pain. In this case, repoman's /tmp is far from full: Filesystem 1K-blocks Used Avail Capacity Mounted on /dev/da0s1e 7858549 65 7229801 0% /tmp There's nothing in dmesg about cvs crashing, nor log messages anywhere obvious that I can find that might give a clue as to what is going on. I tested a cvs update myself, and it worked for me. The best guess I can come up with is that the local checkout is corrupt somehow. -- Peter Wemm - peter@wemm.org; peter@FreeBSD.org; peter@yahoo-inc.com "All of this is for nothing if we don't go to the stars" - JMS/B5 "If Java had true garbage collection, most programs would delete themselves upon execution." -- Robert Sewell