From owner-freebsd-current@FreeBSD.ORG Thu May 1 02:12:58 2003 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 682A137B401 for ; Thu, 1 May 2003 02:12:58 -0700 (PDT) Received: from critter.freebsd.dk (esplanaden.cybercity.dk [212.242.40.114]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2FAB143F3F for ; Thu, 1 May 2003 02:12:57 -0700 (PDT) (envelope-from phk@phk.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.12.9/8.12.9) with ESMTP id h419Ctas001515; Thu, 1 May 2003 11:12:55 +0200 (CEST) (envelope-from phk@phk.freebsd.dk) To: Heiko Schaefer From: "Poul-Henning Kamp" In-Reply-To: Your message of "Thu, 01 May 2003 11:07:48 +0200." <20030501105847.O32907@daneel.foundation.hs> Date: Thu, 01 May 2003 11:12:55 +0200 Message-ID: <1514.1051780375@critter.freebsd.dk> cc: freebsd-current@freebsd.org Subject: Re: poul: sorry, was: Re: still: Re: gbde data corruption? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 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, 01 May 2003 09:12:58 -0000 In message <20030501105847.O32907@daneel.foundation.hs>, Heiko Schaefer writes: >Hi Poul, > >sorry for all the fuss, you can now reattach your pulled-out hair. >and i need to find someone or something new to blame this issue on... Phew... (:-> >i have just reproduced the data-corruption on non-gbde filesystems (what >a way to start a day). so gbde is very very likely not to blame for any of >the stuff that i've been complaining about (apart from the slowness >while writing to disc, which will bugs me again after i've sorted out >the corruption :) i'll get back to you in a few weeks *g*). > >now i have the questionable pleasure to rule out pieces of hardware as >suspects, i guess. damn. sometimes cheap pc hardware really sucks. even >though i don't think it's clear if this is a hardware or a software issue. > >if anyone has suggestions on how to rule out specific causes or what >pieces of hard- and software are particularly suspect, i'd be glad to hear >about it. first of all i am planning to rule out the sis nic in the server >(onboard nics have always been suspect to me) I would suggest trying to rule networking out first: try to do the copies locally. >sorry again, poul for blaming this on you right away. No worries, the fact that I didn't dare just say "rubbish" show that you had a good case. -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence.