kern/95459: Rebooting the system while rebuilding RAID (Intel
MatrixRAID) results in data loss
Wouter de Jong
maddog2k at maddog2k.net
Mon Nov 13 10:50:10 UTC 2006
The following reply was made to PR kern/95459; it has been noted by GNATS.
From: "Wouter de Jong" <maddog2k at maddog2k.net>
To: <bug-followup at FreeBSD.org>,
<be9-ml at be9.ru>
Cc:
Subject: Re: kern/95459: Rebooting the system while rebuilding RAID (Intel MatrixRAID) results in data loss
Date: Mon, 13 Nov 2006 11:47:44 +0100
This is a multi-part message in MIME format.
------=_NextPart_000_0021_01C70719.88714550
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
I get the same error message _after_ rebuilding (and the ar0 goes back =
to status READY).
However, my data is not lost nor the RAID.
The system just 'hangs'.
This is with both ICH5 and ICH6-chipset. (different SuperMicro =
server-models).
Nov 13 10:41:16 monitoring0-1 kernel: ad4: 76319MB <WDC WD800JD-00LSA0 =
06.01D06> at ata2-master SATA150
Nov 13 10:41:37 monitoring0-1 kernel: ad4: inserted into ar0 disk0 as =
spare
Nov 13 11:34:22 monitoring0-1 kernel: ad6: WARNING - WRITE_DMA taskqueue =
timeout - completing request directly
Nov 13 11:34:22 monitoring0-1 kernel: ad4: WARNING - WRITE_DMA freeing =
taskqueue zombie request
Nov 13 11:34:22 monitoring0-1 kernel: ad6: WARNING - WRITE_DMA freeing =
taskqueue zombie request
After rebooting, it's all OK _after_ a forced fsck in single mode.
Regards,
Wouter
------=_NextPart_000_0021_01C70719.88714550
Content-Type: text/html;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; =
charset=3Diso-8859-1">
<META content=3D"MSHTML 6.00.2900.2963" name=3DGENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=3D#ffffff>
<DIV><FONT face=3DArial size=3D2>I get the same error message =
_after_=20
rebuilding (and the ar0 goes back to status READY).</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>However, my data is not lost nor=20
the RAID.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>The system just 'hangs'.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2>This is with both ICH5 and =
ICH6-chipset. (different=20
SuperMicro server-models).</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2>Nov 13 10:41:16 monitoring0-1 kernel: =
ad4: 76319MB=20
<WDC WD800JD-00LSA0 06.01D06> at ata2-master SATA150<BR>Nov 13 =
10:41:37=20
monitoring0-1 kernel: ad4: inserted into ar0 disk0 as spare<BR>Nov 13 =
11:34:22=20
monitoring0-1 kernel: ad6: WARNING - WRITE_DMA taskqueue timeout - =
completing=20
request directly<BR>Nov 13 11:34:22 monitoring0-1 kernel: ad4: WARNING - =
WRITE_DMA freeing taskqueue zombie request<BR>Nov 13 11:34:22 =
monitoring0-1=20
kernel: ad6: WARNING - WRITE_DMA freeing taskqueue zombie=20
request<BR></FONT></DIV>
<DIV><FONT face=3DArial size=3D2>After rebooting, it's all OK _after_ a =
forced fsck=20
in single mode.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2>Regards,</FONT></DIV>
<DIV><FONT face=3DArial size=3D2><BR>Wouter</DIV></FONT></BODY></HTML>
------=_NextPart_000_0021_01C70719.88714550--
More information about the freebsd-bugs
mailing list