Date: Thu, 11 Nov 2004 08:45:55 +0100 From: =?ISO-8859-1?Q?S=F8ren_Schmidt?= <sos@DeepCore.dk> To: Frode Nordahl <frode@nordahl.net> Cc: freebsd-current@freebsd.org Subject: Re: 5.3-RELEASE: WARNING - WRITE_DMA interrupt timout - what does it mean? Message-ID: <419318B3.8000807@DeepCore.dk> In-Reply-To: <29DB06CF-336A-11D9-B78A-000A95A9A574@nordahl.net> References: <BAY2-DAV13Gz1iD0CWl00009b23@hotmail.com> <4191CD35.9040000@DeepCore.dk> <29DB06CF-336A-11D9-B78A-000A95A9A574@nordahl.net>
index | next in thread | previous in thread | raw e-mail
Frode Nordahl wrote: > On Nov 10, 2004, at 09:11, Søren Schmidt wrote: > >> Zoltan Frombach wrote: >> >>> I just upgraded to 5.3-RELEASE a few days ago. This morning this line >>> got into my system log file: >>> Nov 9 06:14:03 www kernel: ad0: WARNING - WRITE_DMA interrupt was >>> seen but timeout fired LBA=2491143 >>> 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 >> seen), but that the system (the bio_taskqueue) hasn't been able to get >> 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 >> 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) MySQL > server, and it bails out with this message when the above mentioned > "warning" occurs in dmesg. > > 041109 22:26:18 InnoDB: Operating system error number 5 in a file > operation. > InnoDB: Starting recovery from log files... > > (5 == EIO?) I was talking 5.3R or -current.. -- -Sørenhelp
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?419318B3.8000807>