From owner-freebsd-scsi Tue Jun 19 2:20:15 2001 Delivered-To: freebsd-scsi@freebsd.org Received: from mailout01.sul.t-online.de (mailout01.sul.t-online.com [194.25.134.80]) by hub.freebsd.org (Postfix) with ESMTP id A656D37B401 for ; Tue, 19 Jun 2001 02:20:11 -0700 (PDT) (envelope-from haribeau@gmx.de) Received: from fwd02.sul.t-online.de by mailout01.sul.t-online.de with smtp id 15CHgA-0002tP-0C; Tue, 19 Jun 2001 11:20:10 +0200 Received: from asterix.local (320080844193-0001@[217.80.84.120]) by fmrl02.sul.t-online.com with smtp id 15CHfz-0zfM0WC; Tue, 19 Jun 2001 11:19:59 +0200 Received: (qmail 537 invoked from network); 19 Jun 2001 09:19:52 -0000 Received: from homer.local (HELO homer.local.nlocal) (192.168.1.50) by 0 with SMTP; 19 Jun 2001 09:19:52 -0000 Received: (nullmailer pid 850 invoked by uid 1100); Tue, 19 Jun 2001 09:19:52 -0000 Date: Tue, 19 Jun 2001 11:19:52 +0200 From: Clemens Hermann To: Mike Smith Cc: scsi@freebsd.org Subject: Re: 'mly' driver update/bugfix snapshot available Message-ID: <20010619111952.A823@homer.local> References: <20010618130851.C1070@homer.local> <200106190508.f5J58XP05458@mass.dis.org> Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="T4sUOijqQbZv57TR" Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <200106190508.f5J58XP05458@mass.dis.org> von Mike Smith am 18.Jun.2001 um 22:08:33 (-0700) X-Mailer: Mutt 1.2.5i (FreeBSD 4.3-RELEASE i386) X-Sender: 320080844193-0001@t-dialin.net Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org --T4sUOijqQbZv57TR Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Hi, > Can you try the new version at: > > http://people.freebsd.org/~msmith/RAID/mylex/mly-20010618.tar.gz sure. It worked :). I attached the according syslog. the behaviour is the same as the old driver with Markus' patch. > I still don't think that it'll properly handle a drive going totally > offline and then coming back, but I could be wrong. I think you are :). As you might have noticed I am no expert but to me it looks like things work as they should. /ch --T4sUOijqQbZv57TR Content-Type: text/plain; charset=us-ascii Content-Disposition: attachment; filename=messages Jun 19 13:02:03 hiob /kernel: mly0: physical device 0:4 device cannot be accessed Jun 19 13:02:03 hiob /kernel: mly0: logical device 0 (da0) critical Jun 19 13:02:03 hiob /kernel: mly0: unknown event code - 61 Jun 19 13:02:03 hiob /kernel: mly0: unknown event code - 162 Jun 19 13:08:33 hiob /kernel: mly0: logical device 0 (da0) rebuild completed Jun 19 13:08:33 hiob /kernel: mly0: physical device 0:0 rebuild completed Jun 19 13:08:33 hiob /kernel: mly0: physical device 0:0 online Jun 19 13:08:33 hiob /kernel: mly0: logical device 0 (da0) online Jun 19 13:10:00 hiob /kernel: mly0: physical device 0:4 found Jun 19 13:10:00 hiob /kernel: mly0: physical device 0:4 standby --T4sUOijqQbZv57TR-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message