From owner-freebsd-current@FreeBSD.ORG Wed Nov 10 22:45:09 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 21DB816A4CE for ; Wed, 10 Nov 2004 22:45:09 +0000 (GMT) Received: from smtp1.powertech.no (smtp1.powertech.no [195.159.0.145]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0861143D1D for ; Wed, 10 Nov 2004 22:45:08 +0000 (GMT) (envelope-from frode@nordahl.net) Received: from [192.168.1.34] (ti211110a080-4342.bb.online.no [80.213.176.248]) by smtp1.powertech.no (Postfix) with ESMTP id 3E1277E68; Wed, 10 Nov 2004 23:45:06 +0100 (CET) In-Reply-To: <4191CD35.9040000@DeepCore.dk> References: <4191CD35.9040000@DeepCore.dk> Mime-Version: 1.0 (Apple Message framework v619) Content-Type: text/plain; charset=ISO-8859-1; format=flowed Message-Id: <29DB06CF-336A-11D9-B78A-000A95A9A574@nordahl.net> Content-Transfer-Encoding: quoted-printable From: Frode Nordahl Date: Wed, 10 Nov 2004 23:45:04 +0100 To: =?ISO-8859-1?Q?S=F8ren_Schmidt?= X-Mailer: Apple Mail (2.619) 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: Wed, 10 Nov 2004 22:45:09 -0000 On Nov 10, 2004, at 09:11, S=F8ren Schmidt wrote: > 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=20= >> 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,=20= > 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 :) This triggered my attention :-) I have a server still running on 5.3-BETA1, with a (not very busy)=20 MySQL server, and it bails out with this message when the above=20 mentioned "warning" occurs in dmesg. 041109 22:26:18 InnoDB: Operating system error number 5 in a file=20 operation. InnoDB: Starting recovery from log files... (5 =3D=3D EIO?) The WRITE_DMA (and the subsequent MySQL crash) ocurred when I was=20 cleaning up disk space. Basicly moving logfiles from /var to /usr, bzipping them and some other=20= logs, so not very heavy I/O. When it blew, I immediately stopped, deleted all the way too big=20 logfiles, which I never will get any use for anyway, fixed newsyslog,=20 and lived hapilly ever after :-) I'm not sure if this is an issue solved between BETA1 and RELEASE=20 (wasn't there some fixes in BETA7?) or if it's the one described here. Anyway, this "WARNING" will cause software failure in other parts of=20 the system. Hardware: The motherboard is a entry-level Intel (P4) board, probably with a ICH2 # atacontrol list ATA channel 0: Master: ad0 ATA/ATAPI revision 7 Slave: no device present ATA channel 1: Master: no device present Slave: acd0 ATA/ATAPI revision 0 Mvh, Frode Nordahl > --=20 > > -S=F8ren > > > _______________________________________________ > freebsd-current@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to=20 > "freebsd-current-unsubscribe@freebsd.org"