From owner-freebsd-questions@FreeBSD.ORG Mon Mar 7 03:36:39 2005 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 CB1DF16A4CE for ; Mon, 7 Mar 2005 03:36:39 +0000 (GMT) Received: from rproxy.gmail.com (rproxy.gmail.com [64.233.170.202]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6EC5743D48 for ; Mon, 7 Mar 2005 03:36:39 +0000 (GMT) (envelope-from bevan.coleman@gmail.com) Received: by rproxy.gmail.com with SMTP id a41so981720rng for ; Sun, 06 Mar 2005 19:36:39 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:references; b=o6Qhc8mL/LDnZJmZVK0DvN57UEB2GDN0g2bM0PshcuLNr3McEbhjRVBmvZDAqorlH3bVFnu2LGKIybyHrnGlTBDa4uMX7yZ1iatKY/gQIvQxGNx8nDAKF2pwp2ceAkvY7z9Gs0p4+/RbPeLwhrcz4kdYXmTGUl6ZzMqqT64Tau8= Received: by 10.38.90.47 with SMTP id n47mr165988rnb; Sun, 06 Mar 2005 19:36:38 -0800 (PST) Received: by 10.38.10.6 with HTTP; Sun, 6 Mar 2005 19:36:38 -0800 (PST) Message-ID: Date: Mon, 7 Mar 2005 14:06:38 +1030 From: Bevan Coleman To: freebsd-questions@freebsd.org In-Reply-To: <1110165971l.46432l.0l@BARTON> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit References: <1110165971l.46432l.0l@BARTON> Subject: Re: bittorrent corruption problems X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: Bevan Coleman List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 07 Mar 2005 03:36:39 -0000 On Mon, 07 Mar 2005 03:26:11 +0000, Jason Henson wrote: > I have been getting this error: > > data corrupted on disk - maybe you have two copies running? > > I have looked on the net and the only causes I can see are bad ram and > bad software. I noticed this after I started using the gui, never > noticed it on the command line. I used to never get this. It has I had this a while back on one of my Linux boxes. Turned out to be bad ram. Memtest86+ should do the trick, just leave it testing over night and see what it says in the morning. -- Bevan Coleman -- What Signature?