Date: Tue, 4 Nov 2003 23:12:51 +0100 From: Bernd Walter <ticso@cicely12.cicely.de> To: Kris Kennaway <kris@obsecurity.org> Cc: ticso@cicely.de Subject: Re: New alpha 5.x bug Message-ID: <20031104221251.GJ42463@cicely12.cicely.de> In-Reply-To: <20031104175552.GA70699@rot13.obsecurity.org> References: <20031101103955.GA42891@rot13.obsecurity.org> <20031104031740.GA67484@rot13.obsecurity.org> <20031104124826.GH42463@cicely12.cicely.de> <20031104175552.GA70699@rot13.obsecurity.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, Nov 04, 2003 at 09:55:52AM -0800, Kris Kennaway wrote: > On Tue, Nov 04, 2003 at 01:48:27PM +0100, Bernd Walter wrote: > > I can't speak for this problem yet, because my test systems are a bit > > older, but speaking for the pipe corruption: > > I did a lots of bzip1, tar, scp, nfs(client) without noticing any > > sign of problem. > > What is so special with the port cluster? > > I have no clue about it's design. > > It does lots of parallel package builds (untar, pkg_add, compile, tar) and NFS copying. Any special NFS options? tcp, udp, v2, v3, IPv4, IPv6? Just to get the picture complete. The build is local and the package is then copied to a NFS server on which t has a corrupted CRC? Is the bzip2 CRC wrong, or the tar CRC (does tar have a CRC?), or both? Can you say how likely such a corruption is? Are other packages compiled during copying a package file to the server? Are the building machines memory stressed while creating the bz file or while copying it? Really - it's hard to believe that pipe itself is the problem. I do lots of buildworlds with CFLAGS=-pipe and a corruption would very likely stop building. -- B.Walter BWCT http://www.bwct.de ticso@bwct.de info@bwct.de
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20031104221251.GJ42463>