From owner-freebsd-scsi@freebsd.org Sun Jul 15 20:29:46 2018 Return-Path: Delivered-To: freebsd-scsi@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id F19D0102742B for ; Sun, 15 Jul 2018 20:29:45 +0000 (UTC) (envelope-from marck@rinet.ru) Received: from woozle.rinet.ru (woozle.rinet.ru [195.54.192.68]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 69378969F3 for ; Sun, 15 Jul 2018 20:29:42 +0000 (UTC) (envelope-from marck@rinet.ru) Received: from localhost (localhost [127.0.0.1]) by woozle.rinet.ru (8.14.5/8.14.5) with ESMTP id w6FKRBwv044129 for ; Sun, 15 Jul 2018 23:27:12 +0300 (MSK) (envelope-from marck@rinet.ru) Date: Sun, 15 Jul 2018 23:27:11 +0300 (MSK) From: Dmitry Morozovsky To: freebsd-scsi@FreeBSD.org Subject: mfi troubles (Unexpected Sense) Message-ID: User-Agent: Alpine 2.00 (BSF 1167 2008-08-23) X-NCC-RegID: ru.rinet X-OpenPGP-Key-ID: 6B691B03 MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.4.3 (woozle.rinet.ru [0.0.0.0]); Sun, 15 Jul 2018 23:27:12 +0300 (MSK) X-BeenThere: freebsd-scsi@freebsd.org X-Mailman-Version: 2.1.27 Precedence: list List-Id: SCSI subsystem List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 15 Jul 2018 20:29:46 -0000 Colleagues, one of my servers start to expose unexpected delays possibly related to disk subsystems. It's Supemicro with mfi, ZFS on set of RAID0 (yes, I know we've missed the right controller, but this is out of question at least for the current time) Now kernel log is filled with messages like mfi0: 60006 (585001405s/0x0002/info) - Unexpected sense: PD 0e(e0x08/s5) Path 500304800021bf31, CDB: 8f 00 00 00 00 00 14 77 5c 1e 00 00 10 00 00 00, Sense: 3/11/00 every few seconds I tried to find the place in the source which produce these lines but failed :( Hard reboot, including full power off, was tried, but did not help. Any hints to diagnose this further? Ah, and this is stable/10 from Nov 2017 please keep me CC:d as I'm not subscribed to -scsi@ Thanks! -- Sincerely, D.Marck [DM5020, MCK-RIPE, DM3-RIPN] [ FreeBSD committer: marck@FreeBSD.org ] ------------------------------------------------------------------------ *** Dmitry Morozovsky --- D.Marck --- Wild Woozle --- marck@rinet.ru *** ------------------------------------------------------------------------