From owner-FreeBSD-users-jp@jp.FreeBSD.org Mon Apr  4 22:33:06 2005
Received: (from daemon@localhost)
	by castle.jp.FreeBSD.org (8.11.6p2+3.4W/8.11.3) id j34DX6t60137;
	Mon, 4 Apr 2005 22:33:06 +0900 (JST)
	(envelope-from owner-FreeBSD-users-jp@jp.FreeBSD.org)
Received: from smtp5.dti.ne.jp (smtp5.dti.ne.jp [202.216.228.40])
	by castle.jp.FreeBSD.org (8.11.6p2+3.4W/8.11.3) with ESMTP/inet id j34DX6X60132
	for <FreeBSD-users-jp@jp.FreeBSD.org>; Mon, 4 Apr 2005 22:33:06 +0900 (JST)
	(envelope-from maenaka@pluto.dti.ne.jp)
Received: from towerrecords.minidns.net (PPPbb124.gifu-ip.dti.ne.jp [218.225.250.124]) by smtp5.dti.ne.jp (3.10s) with ESMTP id j34DX5g2016150 for <FreeBSD-users-jp@jp.FreeBSD.org>; Mon, 4 Apr 2005 22:33:05 +0900 (JST)
Received: from [127.0.0.1] (destroy [192.168.0.1])
	by towerrecords.minidns.net (Postfix) with ESMTP id 3D570204D
	for <FreeBSD-users-jp@jp.FreeBSD.org>; Mon,  4 Apr 2005 22:33:05 +0900 (JST)
From: "UEMURA (fka. MAENAKA) Tetsuya" <maenaka@pluto.dti.ne.jp>
To: FreeBSD-users-jp@jp.FreeBSD.org
In-Reply-To: <20050404152956.3852.TSAKUMA@mycom.co.jp>
References: <20050404030540.E590A2049@towerrecords.minidns.net> <20050404152956.3852.TSAKUMA@mycom.co.jp>
MIME-Version: 1.0
Content-Type: text/plain; charset="ISO-2022-JP"
Content-Transfer-Encoding: 7bit
X-Mailer: Becky! ver. 2.12.01 [ja]
Message-Id: <20050404133305.3D570204D@towerrecords.minidns.net>
Reply-To: FreeBSD-users-jp@jp.FreeBSD.org
Precedence: list
Date: Mon, 4 Apr 2005 22:33:05 +0900
X-Sequence: FreeBSD-users-jp 83899
Subject: [FreeBSD-users-jp 83899] Re: RAID =?ISO-2022-JP?B?GyRCJE4bKEI=?=
 =?ISO-2022-JP?B?GyRCPUxCYDRGO2slRCE8JWskcjY1JCgkRiQvJEAbKEI=?=
 =?ISO-2022-JP?B?GyRCJDUkJBsoQg==?= 
Sender: owner-FreeBSD-users-jp@jp.FreeBSD.org
X-Originator: maenaka@pluto.dti.ne.jp
X-Distribute: distribute version 2.1 (Alpha) patchlevel 24e+050320

$B?"B<$G$9!#(B

Posted on Mon, 04 Apr 2005 15:52:34 +0900
by author $B:45W4V!!Bg<y(B <tsakuma@mycom.co.jp>
> For information, Scott Long has committed a patch for amr.c in current 
> yesterday which solved this problem (I've tested).
> 
> $B$3$N!"(BScott$B$5$s$N(Bamr.c$B$C$F$$$&$N$O$J$s$J$N$G$7$g$&$+!)(B
$B$=$b$=$b(BScott Long$B$5$s$N(Bfix$B$O(BPhilippe PEGON$B$5$s$N%*%j%8%J%k%]%9%H$K$"$k(B
> Starting a program which continuously polls the state of the raid array
> (amrstat, see source attached), and making a buildworld at the same time
> triggers a kernel panic. The problem is fairly easy to reproduce.
$B$KBP$9$k$b$N$@$H;W$$$^$9!#(B
http://www.freebsd.org/cgi/cvsweb.cgi/src/sys/dev/amr/amr.c
$B$N3:Ev$7$=$&$JF|IU$1$@$H(Bamr.c:1.62$B$N(B
> Fix a null pointer de-ref when passthrough ioctls are issued.  This
> involves some code shuffle to avoid locking problems.
$B$G$7$g$&$+!#(B

$B$G!":45W4V$5$s$N:G=i$N%]%9%H$G(B
> amrcontrol$B%3%^%s%I$rEjF~$9$k$H!"#12sL\$O$[$\IaDL$K>uBV$,I=<($5$l$k(B
> $B$N$G$9$,!"2?2s$+O"B3$7$FEjF~$9$k$H#1#0#0!s!"%O!<%I%&%'%"$,%j%;%C%H(B
> $B$5$l$F$7$^$$$^$9!#(B
$B$H$"$C$?$N$G!"$3$l$+$J$"$H;W$C$?$N$G$9!#(B

> $B$H$$$&(BSCSIRAID1$B$G$9$,!"F1MM$K%j%S%k%ICf$G$"$m$&$H$J$+$m$&$H(B
> degraded$B$H$7$FI=<($5$l$F$^$7$?!#(B
$B$6$i$C$H8+2s$7$?$s$G$9$1$I!"%\!<%I$+$iJV$C$FMh$?%9%F!<%?%9$r%*%&%`JV$7$7(B
$B$F$k$@$1$_$?$$$J$s$G!"$=$&$$$&$b$N$J$s$G$7$g$&$+$M!#(B

-- 
$B?"B<(B (fka. $BA0Cg(B) $BE0:H(B <maenaka@pluto.dti.ne.jp>

