From owner-freebsd-current@FreeBSD.ORG Mon Mar 15 10:58:56 2004 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 3DFF016A4CE for ; Mon, 15 Mar 2004 10:58:56 -0800 (PST) Received: from spider.deepcore.dk (cpe.atm2-0-53484.0x50a6c9a6.abnxx9.customer.tele.dk [80.166.201.166]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0DE9C43D1F for ; Mon, 15 Mar 2004 10:58:55 -0800 (PST) (envelope-from sos@DeepCore.dk) Received: from DeepCore.dk (sos.deepcore.dk [194.192.25.130]) by spider.deepcore.dk (8.12.11/8.12.10) with ESMTP id i2FIw0p0094726; Mon, 15 Mar 2004 19:58:15 +0100 (CET) (envelope-from sos@DeepCore.dk) Message-ID: <4055FCB9.1040406@DeepCore.dk> Date: Mon, 15 Mar 2004 19:58:01 +0100 From: =?ISO-8859-1?Q?S=F8ren_Schmidt?= User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.6b) Gecko/20040126 Thunderbird/0.4 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Elliot Finley References: <019001c40abb$ac2a9350$32cba1cd@science1> In-Reply-To: <019001c40abb$ac2a9350$32cba1cd@science1> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 8bit X-mail-scanned: by DeepCore Virus & Spam killer v1.4 cc: freebsd-current@freebsd.org Subject: Re: reliable disk FAILURE 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: Mon, 15 Mar 2004 18:58:56 -0000 Elliot Finley wrote: > when doing a disk-to-disk backup using dump/restore, I reliably get a disk > failure. I don't think it's the disk because it happens on six different > machines. All six machines are using SATA drives. They all have an ASUS > P4P800 MB. > > None of the six machines had any problems until after the last security > patch to 5.2.1. After the patch, they all fail. If I remember correctly, > the last security patch only touched some TCP files, so the disk failures > don't make any sense to me. > > commands causing the failure, console output and dmesg are below. This is > on a test machine that I can take down or modify at any time, so if there is > anything further that I can do to help debug this - please let me know. Does it also fail if you use the Promise channels instead ? -- -Søren