From owner-freebsd-current@FreeBSD.ORG Mon Jul 6 21:25:01 2009 Return-Path: Delivered-To: freebsd-current@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id A53C810656A3; Mon, 6 Jul 2009 21:25:01 +0000 (UTC) (envelope-from scottl@samsco.org) Received: from pooker.samsco.org (pooker.samsco.org [168.103.85.57]) by mx1.freebsd.org (Postfix) with ESMTP id 4F84B8FC14; Mon, 6 Jul 2009 21:25:00 +0000 (UTC) (envelope-from scottl@samsco.org) Received: from pooker.samsco.home (pooker.samsco.home [192.168.254.1]) by pooker.samsco.org (8.14.2/8.14.2) with ESMTP id n66LOvUH088882; Mon, 6 Jul 2009 15:24:57 -0600 (MDT) (envelope-from scottl@samsco.org) Date: Mon, 6 Jul 2009 15:24:57 -0600 (MDT) From: Scott Long To: Mike Tancsa In-Reply-To: <200907062118.n66LIGRg043316@lava.sentex.ca> Message-ID: <20090706152351.S26418@pooker.samsco.org> References: <4A4517BE.9040504@FreeBSD.org> <200906272303.n5RN3rTi070177@lava.sentex.ca> <4A471F44.7010108@FreeBSD.org> <200907021859.n62IxghN009931@lava.sentex.ca> <4A4D0B7E.8060503@FreeBSD.org> <200907022117.n62LHrvZ010791@lava.sentex.ca> <200907031326.n63DQCGM016627@lava.sentex.ca> <4A4E0D51.3080904@FreeBSD.org> <200907031413.n63ED2jl016885@lava.sentex.ca> <4A4E1525.2040809@FreeBSD.org> <200907031430.n63EUMH1016965@lava.sentex.ca> <4A4E1A6C.3090605@FreeBSD.org> <200907031858.n63IwDIt018455@lava.sentex.ca> <4A4E5C82.9070209@FreeBSD.org> <7.1.0.9.0.20090703165005.196d3ba0@sentex.net> <200907050030.n650UkEu028408@lava.sentex.ca> <4A504B0C.2060406@FreeBSD.org> <200907062118.n66LIGRg043316@lava.sentex.ca> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Spam-Status: No, score=-4.4 required=3.8 tests=ALL_TRUSTED,BAYES_00 autolearn=ham version=3.1.8 X-Spam-Checker-Version: SpamAssassin 3.1.8 (2007-02-13) on pooker.samsco.org Cc: Alexander Motin , FreeBSD-Current , scottl@FreeBSD.org Subject: Re: RFC: ATA to CAM integration patch (INTEL DX58SO) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 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, 06 Jul 2009 21:25:02 -0000 On Mon, 6 Jul 2009, Mike Tancsa wrote: > At 02:41 AM 7/5/2009, Alexander Motin wrote: >>> Jul 4 20:25:57 ich10 kernel: ahcich2: ahci_ch_intr ERROR is 40000001 cs >>> 00000004 ss 00000000 rs 00000004 tfd 451 serr 00000000 >> >> This is AHCI driver debugging. I've removed it in latest patch. In this >> case it means that drive signals some command error. > > > Hi, > > With the latest patch (cam-ata.20090704.patch), writing to the disk with > physical errors looks like this now > > Jul 6 13:56:17 ich10 last message repeated 4 times > Jul 6 13:56:17 ich10 kernel: g_vfs_done():ada2[READ(offset=42003431424, > length=16384)]error = 5 > Jul 6 13:56:17 ich10 kernel: ahcich2: Error while READ LOG EXT > Jul 6 13:56:17 ich10 last message repeated 4 times > Jul 6 13:56:17 ich10 kernel: g_vfs_done():ada2[READ(offset=42196107264, > length=16384)]error = 5 > Jul 6 13:56:17 ich10 kernel: ahcich2: Error while READ LOG EXT > Jul 6 13:56:17 ich10 last message repeated 4 times > Jul 6 13:56:17 ich10 kernel: g_vfs_done():ada2[READ(offset=42388783104, > length=16384)]error = 5 > Jul 6 13:56:17 ich10 kernel: ahcich2: Error while READ LOG EXT > Jul 6 13:56:17 ich10 last message repeated 4 times > Jul 6 13:56:17 ich10 kernel: g_vfs_done():ada2[READ(offset=42581458944, > length=16384)]error = 5 > Jul 6 13:56:17 ich10 kernel: ahcich2: Error while READ LOG EXT > Jul 6 13:56:17 ich10 last message repeated 4 times > Jul 6 13:56:17 ich10 kernel: g_vfs_done():ada2[READ(offset=42774134784, > length=16384)]error = 5 > Jul 6 13:56:17 ich10 kernel: ahcich2: Error while READ LOG EXT > Jul 6 13:56:18 ich10 last message repeated 4 times > Jul 6 13:56:18 ich10 kernel: g_vfs_done():ada2[READ(offset=42966810624, > length=16384)]error = 5 > Jul 6 13:56:18 ich10 kernel: ahcich2: Error while READ LOG EXT > Jul 6 13:56:18 ich10 last message repeated 4 times > > Still the box does a panic when writing to the disk that has bad sectors on > it. (I do newfs it between reboots). Again, not sure if this is a "well, > dont use a bad disk", but here is the panic again in case it shows something > useful. > This is a 'don't use a bad disk' panic; FreeBSD UFS and VM simply can't handle errors on reads or writes. Scott