From owner-freebsd-current@FreeBSD.ORG Thu Nov 11 07:46:48 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 3885B16A4CE for ; Thu, 11 Nov 2004 07:46:48 +0000 (GMT) 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 830E743D53 for ; Thu, 11 Nov 2004 07:46:47 +0000 (GMT) (envelope-from sos@DeepCore.dk) Received: from [172.18.2.1] (axiell-gw1.novi.dk [130.225.63.24]) by spider.deepcore.dk (8.12.11/8.12.10) with ESMTP id iAB7kdZ5051166; Thu, 11 Nov 2004 08:46:45 +0100 (CET) (envelope-from sos@DeepCore.dk) Message-ID: <419318B3.8000807@DeepCore.dk> Date: Thu, 11 Nov 2004 08:45:55 +0100 From: =?ISO-8859-1?Q?S=F8ren_Schmidt?= User-Agent: Mozilla Thunderbird 0.7.2 (X11/20040802) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Frode Nordahl References: <4191CD35.9040000@DeepCore.dk> <29DB06CF-336A-11D9-B78A-000A95A9A574@nordahl.net> In-Reply-To: <29DB06CF-336A-11D9-B78A-000A95A9A574@nordahl.net> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: quoted-printable X-mail-scanned: by DeepCore Virus & Spam killer v1.4 cc: Zoltan Frombach cc: freebsd-current@freebsd.org Subject: Re: 5.3-RELEASE: WARNING - WRITE_DMA interrupt timout - what does it mean? 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, 11 Nov 2004 07:46:48 -0000 Frode Nordahl wrote: > On Nov 10, 2004, at 09:11, S=F8ren Schmidt wrote: >=20 >> Zoltan Frombach wrote: >> >>> I just upgraded to 5.3-RELEASE a few days ago. This morning this line= =20 >>> got into my system log file: >>> Nov 9 06:14:03 www kernel: ad0: WARNING - WRITE_DMA interrupt was=20 >>> seen but timeout fired LBA=3D2491143 >>> I've never seen this message before. Can someone please explain what = >>> it means? With Thanks, >> >> >> It means that the disk has processed the write request (interrupt=20 >> seen), but that the system (the bio_taskqueue) hasn't been able to get= =20 >> the result returned to the kernel. >> >> Your disk is not involved in this problem since it has done its part, = >> but the rest of the system is either busy with something else, or=20 >> there are bugs lurking that prohibits the bio_taskqueue from running. >> >> Either way its a WARNING not a FAILURE :) >=20 >=20 > This triggered my attention :-) >=20 > I have a server still running on 5.3-BETA1, with a (not very busy) MySQ= L=20 > server, and it bails out with this message when the above mentioned=20 > "warning" occurs in dmesg. >=20 > 041109 22:26:18 InnoDB: Operating system error number 5 in a file=20 > operation. > InnoDB: Starting recovery from log files... >=20 > (5 =3D=3D EIO?) I was talking 5.3R or -current.. --=20 -S=F8ren