From owner-freebsd-fs@freebsd.org Sun Feb 14 12:59:50 2016 Return-Path: Delivered-To: freebsd-fs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 7878FAA063B; Sun, 14 Feb 2016 12:59:50 +0000 (UTC) (envelope-from tinkr@openmailbox.org) Received: from mail2.openmailbox.org (mail2.openmailbox.org [62.4.1.33]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 3B4D6125A; Sun, 14 Feb 2016 12:59:49 +0000 (UTC) (envelope-from tinkr@openmailbox.org) Received: by mail2.openmailbox.org (Postfix, from userid 1004) id B72812AC23D8; Sun, 14 Feb 2016 13:59:40 +0100 (CET) DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=openmailbox.org; s=openmailbox; t=1455454780; bh=svkyVb8OHK6GP+S1g1xbl/EC9JMRQzemiJAwu9H+ovU=; h=Date:From:To:Subject:From; b=UEIko6W7oaPLdp7a4SQDtKMWjvb17/05HsTeWmJR8Spg1keMqy558StagN4nSXg++ sFxbIOJt4V6kRncsQqSeDrhpvixzSkzp+hTM6qDfh9z0U8/qVKhbjTET3eeMgYPLyE eB163YufhMQpBYKTdtocYZF6i7x3hDhInbNjkt58= X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on openmailbox-b2 X-Spam-Level: X-Spam-Status: No, score=0.6 required=5.0 tests=ALL_TRUSTED,BAYES_50, DKIM_ADSP_ALL,URIBL_BLOCKED autolearn=no autolearn_force=no version=3.4.0 Received: from www.openmailbox.org (openmailbox-b1 [10.91.69.218]) by mail2.openmailbox.org (Postfix) with ESMTP id 97C902AC3C0E; Sun, 14 Feb 2016 13:59:30 +0100 (CET) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII; format=flowed Content-Transfer-Encoding: 7bit Date: Sun, 14 Feb 2016 19:59:30 +0700 From: Tinker To: freebsd-stable@freebsd.org, freebsd-scsi@freebsd.org, freebsd-fs@freebsd.org Subject: MRSAS driver/LSI MegaRaid 92XX-93XX admin question: When one of the Raid's physical drives break, how is it reported in the =?UTF-8?Q?logs=3F?= Message-ID: <6a648d421b6d611b4f6f411b66303017@openmailbox.org> X-Sender: tinkr@openmailbox.org User-Agent: Roundcube Webmail/1.0.6 X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 14 Feb 2016 12:59:50 -0000 ( ** Extremely sorry for crossposting! Was unclear where this RAID adapter question belongs, please clarify and I'll keep to one single list! Posted to all of stable@, scsi@ and fs@ .) Hi, When you run one of the MRSAS drives such as a Avatogech LSI MegaRaid 9361 or 9266, and then eventually one of the physical RaidDrives or a CacheCade drives breaks, how is this reported to the FreeBSD host's dmesg or syslog? I don't have the hardware in place so that I would be able to check. On the other hand someone among you may have extremely deep experience, in particular because this card is so common, so this is why I ask you here. I understand that if at least one underlying copy of the data is accessible, the RAID card will optimize all access to that one, so when it comes to keeping IO working without interruption, the LSI card does a great job. At some point, an SSD or HDD will break down, either completely (it won't connect and its SMART interface says the drive is consumed) or more discretely, through taking tons of time for its operations. My best understanding is that the Raid card automatically will take those drives out of use, transparently. Now to the main point: As admin, it's great to be informed when this happens i.e. an underlying physical Raid disk or a CacheCade disk is taken out of use or otherwise malfunctions. Does the MrSas driver output this into the dmesg or syslog somehow? Reading https://svnweb.freebsd.org/base/stable/10/sys/dev/mrsas/mrsas.c?revision=284267&view=markup , the card seems to have an "event log" that the driver downloads from the card in plaintext (??), but I don't understand from the sourcecode where that information is channeled. And also of course I can't see what that event log would contain in those cases. (The "mfiutil" has a "show events" argument, though mfiutil is only for the related "mfi" driver which does not work for both 92XX and 93XX cards. Also in this case still I'd be interested to know how it reports a broken drive) http://www.cisco.com/c/dam/en/us/td/docs/unified_computing/ucs/3rd-party/lsi/mrsas/userguide/LSI_MR_SAS_SW_UG.pdf on page 305, that is section "A.2 Event Messages" - I don't know for what LGI chip this document is, but, it does not list particular event message very clearly for when an individual underlying disk would have broken, I don't even see any event for when a hot spare would be taken in use! You who have the experience, can you clarify please? Thanks :D Tinker