From owner-freebsd-stable@FreeBSD.ORG Tue Aug 11 05:06:02 2009 Return-Path: Delivered-To: stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 252A71065674 for ; Tue, 11 Aug 2009 05:06:02 +0000 (UTC) (envelope-from ambrisko@ambrisko.com) Received: from mail.ambrisko.com (mail.ambrisko.com [64.174.51.43]) by mx1.freebsd.org (Postfix) with ESMTP id EB8468FC20 for ; Tue, 11 Aug 2009 05:06:01 +0000 (UTC) X-Ambrisko-Me: Yes Received: from server2.ambrisko.com (HELO www.ambrisko.com) ([192.168.1.2]) by ironport.ambrisko.com with ESMTP; 10 Aug 2009 21:38:50 -0700 Received: from ambrisko.com (localhost [127.0.0.1]) by www.ambrisko.com (8.14.3/8.14.1) with ESMTP id n7B4baot048000; Mon, 10 Aug 2009 21:37:36 -0700 (PDT) (envelope-from ambrisko@ambrisko.com) Received: (from ambrisko@localhost) by ambrisko.com (8.14.3/8.14.3/Submit) id n7B4bZFI047995; Mon, 10 Aug 2009 21:37:35 -0700 (PDT) (envelope-from ambrisko) From: Doug Ambrisko Message-Id: <200908110437.n7B4bZFI047995@ambrisko.com> In-Reply-To: <4A7F7E1C.1000708@gddsn.org.cn> To: wsk Date: Mon, 10 Aug 2009 21:37:35 -0700 (PDT) X-Mailer: ELM [version 2.4ME+ PL94b (25)] MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=US-ASCII Cc: rsmith@xs4all.nl, stable@freebsd.org Subject: Re: Monitoring tools for mfi0: ? X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 11 Aug 2009 05:06:02 -0000 wsk writes: [ Charset UTF-8 unsupported, converting... ] | On Sun, Aug 09, 2009 at 08:04:35PM +0200, V=E1clav Haisman wrote: | > Hi, | | > I have a server with the "mfi0: " controller. Are there any | > monitoring tool for this? I tried camcontrol but it doesn't even list the | > device. | =20 | Maybe sysutils/megacli does what you want? | | Roland | | some times. I got follow mesgs on my Dell PE R900. any ideas? | | mfi0: 1989 (303015600s/0x0020/info) - Patrol Read started | mfi0: 2020 (303022694s/0x0020/info) - Patrol Read complete This is normal. Patrol read scans for potential disk errors. If you want more info in real-time then you can set hw.mfi.event_class="-2" and get more detail or use MegaCli to get the full event log. | mfi0: COMMAND 0xffffff80005a7870 TIMEOUT AFTER 43 SECONDS | mfi0: COMMAND 0xffffff80005a7ed0 TIMEOUT AFTER 58 SECONDS This is usually okay and saying that some commands are taking a while. If the command never completes then that is a problem. the RAID control can decide the order of completing commands so it can take some time. | pciconf: | mfi0@pci0:25:0:0: class=0x010400 card=0x1f0c1028 chip=0x00601000 rev=0x04 hdr=0x00 | vendor = 'LSI Logic (Was: Symbios Logic, NCR)' | device = 'SAS1078 PCI-X Fusion-MPT SAS' | class = mass storage | subclass = RAID FWIW, that is a bad discription since it claims it is the SAS card and not the RAID. Doug A.