From owner-freebsd-stable@FreeBSD.ORG Wed Jan 19 21:13:03 2005 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id BA7CA16A4CE for ; Wed, 19 Jan 2005 21:13:03 +0000 (GMT) Received: from FS.Denninger.Net (wsip-68-15-213-52.at.at.cox.net [68.15.213.52]) by mx1.FreeBSD.org (Postfix) with ESMTP id E311D43D3F for ; Wed, 19 Jan 2005 21:13:02 +0000 (GMT) (envelope-from karl@FS.Denninger.Net) Received: from fs.denninger.net (localhost [127.0.0.1]) by FS.Denninger.Net (8.12.10/8.12.8) with SMTP id j0JLD2qP022406 for ; Wed, 19 Jan 2005 15:13:02 -0600 (CST) (envelope-from karl@FS.Denninger.Net) Received: from fs.denninger.net [127.0.0.1] by Spamblock-sys; Wed Jan 19 15:13:02 2005 Received: (from karl@localhost) by FS.Denninger.Net (8.12.10/8.12.8/Submit) id j0JLD1Mh022402 for freebsd-stable@freebsd.org; Wed, 19 Jan 2005 15:13:01 -0600 (CST) Message-ID: <20050119151301.A22310@Denninger.Net> Date: Wed, 19 Jan 2005 15:13:01 -0600 From: Karl Denninger To: freebsd-stable@freebsd.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i Organization: Karl's Sushi and Packet Smashers X-Die-Spammers: Spammers cheerfully broiled for supper and served with ketchup! Subject: Bad disk or kernel (ATA Driver) problem? X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 19 Jan 2005 21:13:03 -0000 Hi folks; New one... I've got a 2 x SATA system here I'm playing with in preparation to move over production to 5.x. These drives have been working under 4.x for quite some time - they're 250GB Maxtor disks.... ad4: 239372MB [486344/16/63] at ata2-master SATA150 ad6: 239372MB [486344/16/63] at ata3-master SATA150 The first disk runs nice and happy. The second does too, provided that the load isn't too high. If it is, then I start to get DMA transfer errors, such as the following: ad6: FAILURE - READ_DMA status=51 error=40 LBA=543191 GEOM_MIRROR: Request failed (error=5). ad6[READ(offset=278048256, length=102400)] GEOM_MIRROR: Device m0: provider ad6 disconnected. ad6: FAILURE - READ_DMA status=51 error=40 LBA=300463 ad6: TIMEOUT - READ_DMA retrying (2 retries left) LBA=90863 ad6: FAILURE - READ_DMA timed out ad6: FAILURE - READ_DMA status=51 error=40 ad6: TIMEOUT - READ_DMA retrying (2 retries left) LBA=120663 ad6: FAILURE - READ_DMA timed out I'm having a lot of trouble believing this is an actual disk problem. Among other things, its happening at different places - not always at the same block. The above (after the first one) are all being provoked with a "dd if=/dev/ad6s1 of=/dev/null bs=100k". Anyone else seeing this with a -STABLE build from the last few days, and only on a secondary (and/or SATA) channel? Note that this disk can be reintegrated into the mirror, and it will rebuild happily. Its only when I put a real working load on it that things act up. -- -- Karl Denninger (karl@denninger.net) Internet Consultant & Kids Rights Activist http://www.denninger.net My home on the net - links to everything I do! http://scubaforum.org Your UNCENSORED place to talk about DIVING! http://www.spamcuda.net SPAM FREE mailboxes - FREE FOR A LIMITED TIME! http://genesis3.blogspot.com Musings Of A Sentient Mind