Every 12-hrs -- "ad0: TIMEOUT - WRITE DMA"

[Duane Whitty]

Fabian Keil wrote:
> "V.I.Victor" <idmc_vivr at intgdev.com> wrote:
> 
>> For the last 4-days, our (otherwise OK) 5.4-RELEASE machine has been
>> reporting:
>>
>> Feb 12 12:08:05 : ad0: TIMEOUT - WRITE_DMA retrying (2 retries left) LBA=2701279
>> Feb 13 00:08:51 : ad0: TIMEOUT - WRITE_DMA retrying (2 retries left) LBA=2701279
>> Feb 13 12:09:38 : ad0: TIMEOUT - WRITE_DMA retrying (2 retries left) LBA=2963331
>> Feb 14 00:10:24 : ad0: TIMEOUT - WRITE_DMA retrying (2 retries left) LBA=2705947
>> Feb 14 12:11:09 : ad0: TIMEOUT - WRITE_DMA retrying (2 retries left) LBA=2706335
>> Feb 15 00:12:02 : ad0: TIMEOUT - WRITE_DMA retrying (2 retries left) LBA=2832383
>> Feb 15 12:12:57 : ad0: TIMEOUT - WRITE_DMA retrying (2 retries left) LBA=139839
>> Feb 16 00:13:50 : ad0: TIMEOUT - WRITE_DMA retrying (2 retries left) LBA=131391
>> Feb 16 12:14:36 : ad0: TIMEOUT - WRITE_DMA retrying (2 retries left) LBA=131391
>>
>> The system was created Jan 08 and, prior to the above, the ad0: timeout had
>> only been reported twice:
>>
>> Jan 25 11:43:34 : ad0: TIMEOUT - WRITE_DMA retrying (2 retries left) LBA=17920255
>> Feb 6 11:59:42 : ad0: TIMEOUT - WRITE_DMA retrying (2 retries left) LBA=2832383
> 
Hi,

I hate sending out a "me too" message but yet here 
we are.

It's not a production machine so I was going to 
let it run its course.  The messages stopped 
appearing after a couple of days.

I reviewed my logs and couldn't find anything more 
revealing and my system appeared to be functioning 
well.

Likely unrelated but my new activities at the time 
were experimenting with some new SAMBA shares and 
setting-up the CAM driver.  There is likely no 
correlation but I thought I'd mention it.


--Duane