From owner-freebsd-current@FreeBSD.ORG Fri Feb 18 16:14:05 2005 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 A274116A4CE; Fri, 18 Feb 2005 16:14:05 +0000 (GMT) Received: from mx2.zhwin.ch (mx2.zhwin.ch [160.85.104.51]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0C45043D5C; Fri, 18 Feb 2005 16:14:05 +0000 (GMT) (envelope-from philipp.stutz@gmx.ch) Received: from orwell.zhwin.ch ([160.85.104.31]) by mx2.zhwin.ch with esmtp (Exim 4.44) id 1D2AlX-00023h-AX; Fri, 18 Feb 2005 17:14:03 +0100 Received: from [160.85.171.212] (Not Verified[160.85.171.212]) by orwell.zhwin.ch with NetIQ MailMarshal (v6,0,3,8) id ; Fri, 18 Feb 2005 17:13:47 +0100 Message-ID: <4216144A.5000809@gmx.ch> Date: Fri, 18 Feb 2005 17:14:02 +0100 From: Philipp Stutz User-Agent: Mozilla Thunderbird 0.6+ (Windows/20050214) MIME-Version: 1.0 To: Reid Linnemann References: <20050218152505.4B672A063E@csa.cs.okstate.edu> In-Reply-To: <20050218152505.4B672A063E@csa.cs.okstate.edu> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Mailman-Approved-At: Sat, 19 Feb 2005 13:04:22 +0000 cc: "freebsd-current@freebsd.org" cc: cperciva@freebsd.org Subject: Re: ad WRITE_DMA timing out frequently 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: Fri, 18 Feb 2005 16:14:05 -0000 Reid Linnemann wrote: > Colin Percival wrote: >> Reid Linnemann wrote: >>> ad0: TIMEOUT - WRITE_DMA retrying (2 retries left) LBA=2085599 >>> ad0: TIMEOUT - WRITE_DMA retrying (2 retries left) LBA=2085599 >>> kernel: ad0: FAILURE - WRITE_DMA timed out >>> kernel: g_vfs_done():ad0s1d[WRITE(offset=52772864, length=16384)]error = 5 >> >> Looks like a dying disk. A few weeks ago I had the same problem on two different machines but only when I synced two (mirrored) gvinum stripes/plexes. Think this was with 5.3 release. Did the sync with the old vinum (and 5.2.1) and I never again had these messages and the disk shows no defects. >>> It seems to me that a sector on the disk might be dead in the >>> ad0s1d slice (/var), but I want to be certain before I take >>> further steps that the behavior I'm experiencing is positively >>> unrelated to the migration to 6-CURRENT. >> >> Install sysutils/smartmontools from ports and use smartctl. Odds >> are that the drive has logged hundreds of errors by now. > > smartctl doesn't report any logged errors. On a hunch, I also dd'ed a > file large enough to fill /var, hoping that it would crater on > writing to that sector. It didn't. I know that's not a very useful > test, but it seems to hint to me that the disk isn't bad, but the > driver is freaking out from some event. same here philipp stutz Content Security by MailMarshal