From owner-freebsd-scsi@freebsd.org Wed Nov 15 20:24:49 2017 Return-Path: Delivered-To: freebsd-scsi@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 73AEEDE66A4 for ; Wed, 15 Nov 2017 20:24:49 +0000 (UTC) (envelope-from leeb@ratnaling.org) Received: from mail-it0-x230.google.com (mail-it0-x230.google.com [IPv6:2607:f8b0:4001:c0b::230]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 3CCF17A4DB for ; Wed, 15 Nov 2017 20:24:49 +0000 (UTC) (envelope-from leeb@ratnaling.org) Received: by mail-it0-x230.google.com with SMTP id n134so3232292itg.1 for ; Wed, 15 Nov 2017 12:24:49 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ratnaling-org.20150623.gappssmtp.com; s=20150623; h=mime-version:from:date:message-id:subject:to; bh=Va5/IglhoNS/EadJ1BPj2gaabKkdaROrq+ZK1FUWpkU=; b=OxYRl3I0QebQW6Pao8LlRrR0igW1iekdMiKf7QzElqjuPyJjBhSH9zeOjWNGs1lZXG SkjjHAAUXK2xqyFOG2bY6Jqc6XVnP673Oak6J/KrH6lR/ewspBQ4cnH6o+OjuiXTMP8N wPyZl/7JUGNaRJJ2tsgsiml7SPvWO9lHEy95XFXvD4elXdZaAjjARMyw9RnrnNdlunom k+TeXpUON+jLoq2KYAGI/RCu2Yl3YxD4JhkqVl5SG2mLP6+iezDBsENM9rDA8hrxA7qF +5p9zg0nUWW2FISctK1AI1tBiU+Kep0So/mQOJS1tOkl+alcrIDOJRXg4pw+Ka54Xf+P 4VQg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=Va5/IglhoNS/EadJ1BPj2gaabKkdaROrq+ZK1FUWpkU=; b=Ds9eWg1weYSUghO0KZaDExgf/Ilot1pLlhZfjroaX4FMYjC+EZGSV4uxthjK9w9OhW 8Sl/9xNelgFWpf4+hExL2fNc277BRmr086z3GfaU3jfEJFU/UxpF7o3NnTh/Bl46YXWO TFAj2YBr6A+Bot1JuiorczVTlvOd0X3O8jD2rHeBOP0bDF49UPI1EOYYOE7a7cCmdikl Xsid3Xpwte6JVSH+yoCV/Dd+eWAzsqreG63knCfCy/NyowYTh75vclZ7bNywSoe27rTE 0ScrSGOUgNXVDxoMLdZBJAC22cawWHaeDH46XXviWuipvyRAaqUOLwaVZ30QtQkCbIxn tOqg== X-Gm-Message-State: AJaThX5Uo/cdD9HsRCveWHHpsJ7zTwG/US2u06Vfi7sNYuVJeY1JsYAi Mu2rOHMHsGB7O91dSjt+0aDKLNcotZVqLSQECyIbtg== X-Google-Smtp-Source: AGs4zMYBcVGNXonpcD69S/lS2vEsze0V9RE4+T54tyqEMRMhXeEO2r7zwjjbxwPmWjOR2nse1mHWDDbmC+KGFrXGDLM= X-Received: by 10.36.159.195 with SMTP id c186mr21950257ite.83.1510777488344; Wed, 15 Nov 2017 12:24:48 -0800 (PST) MIME-Version: 1.0 Received: by 10.79.125.79 with HTTP; Wed, 15 Nov 2017 12:24:47 -0800 (PST) From: Lee Brown Date: Wed, 15 Nov 2017 12:24:47 -0800 Message-ID: Subject: Does anybody have experience with a MD1420, mpr(4) To: freebsd-scsi@freebsd.org, freebsd-hardware@freebsd.org Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.25 X-BeenThere: freebsd-scsi@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: SCSI subsystem List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 15 Nov 2017 20:24:49 -0000 Hi, This is my for foray into DAS, so please be gentle :) Apologies if the cross-post is inappropriate, let me know. I'm looking to build a SAS array with a Dell MD1420. It will be attached via a SAS 9300-414E HBA in a Dell R330. I've verified that the server / SAS card should be fine, but just wanted to know if anybody has set this up before, or if there's any obvious reason why it wouldn't work. Dell can be a bit weird sometimes. Any information is most welcome. Thanks -- lee From owner-freebsd-scsi@freebsd.org Thu Nov 16 14:28:46 2017 Return-Path: Delivered-To: freebsd-scsi@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 E3057DDF257; Thu, 16 Nov 2017 14:28:46 +0000 (UTC) (envelope-from ken@kdm.org) Received: from mithlond.kdm.org (mithlond.kdm.org [96.89.93.250]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "A1-33714", Issuer "A1-33714" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 8D3837CA8B; Thu, 16 Nov 2017 14:28:46 +0000 (UTC) (envelope-from ken@kdm.org) Received: from mithlond.kdm.org (localhost [127.0.0.1]) by mithlond.kdm.org (8.15.2/8.14.9) with ESMTPS id vAGEShhg025924 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Thu, 16 Nov 2017 09:28:43 -0500 (EST) (envelope-from ken@mithlond.kdm.org) Received: (from ken@localhost) by mithlond.kdm.org (8.15.2/8.14.9/Submit) id vAGEShxs025923; Thu, 16 Nov 2017 09:28:43 -0500 (EST) (envelope-from ken) Date: Thu, 16 Nov 2017 09:28:43 -0500 From: "Kenneth D. Merry" To: Lee Brown Cc: freebsd-scsi@freebsd.org, freebsd-hardware@freebsd.org Subject: Re: Does anybody have experience with a MD1420, mpr(4) Message-ID: <20171116142843.GA25563@mithlond.kdm.org> References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.23 (2014-03-12) X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.4.3 (mithlond.kdm.org [127.0.0.1]); Thu, 16 Nov 2017 09:28:43 -0500 (EST) X-Spam-Status: No, score=-2.9 required=5.0 tests=ALL_TRUSTED,BAYES_00, HEADER_FROM_DIFFERENT_DOMAINS autolearn=ham autolearn_force=no version=3.4.1 X-Spam-Checker-Version: SpamAssassin 3.4.1 (2015-04-28) on mithlond.kdm.org X-BeenThere: freebsd-scsi@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: SCSI subsystem List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 16 Nov 2017 14:28:47 -0000 On Wed, Nov 15, 2017 at 12:24:47 -0800, Lee Brown wrote: > Hi, > > This is my for foray into DAS, so please be gentle :) Apologies if the > cross-post is inappropriate, let me know. > > I'm looking to build a SAS array with a Dell MD1420. It will be attached > via a SAS 9300-414E HBA in a Dell R330. > > I've verified that the server / SAS card should be fine, but just wanted to > know if anybody has set this up before, or if there's any obvious reason > why it wouldn't work. Dell can be a bit weird sometimes. > > Any information is most welcome. In theory it should be fine. I haven't used a Dell enclosure recently, but from posts here, it seems that they like to turn on Type 2 Protection Information on the drives. (Assuming you buy the drives from Dell.) If they do that, you can either reformat, or see the patch here for the mpr(4) driver to disable using protection information: https://docs.freebsd.org/cgi/getmsg.cgi?fetch=308820+0+archive/2017/freebsd-scsi/20171022.freebsd-scsi I haven't gotten around to changing things so that we detect the PI in the da(4) driver and use 32 byte CDBs when type 2 protection is enabled. (So if someone else has time and wants to do it, feel free. It will be somewhat messy because we only allocate enough space for 16 byte CDBs inside the CCB, so you'll need to allocate the CDB separately...) If you use ZFS, you'll have checksum protection on your data anyway, so PI would just be additional protection. I would also suggest that you update to the latest firmware (currently Phase 15) for the SAS controller. You can do that with LSI's sas3flash or the FreeBSD mprutil(8) utility. Ken -- Kenneth Merry ken@FreeBSD.ORG From owner-freebsd-scsi@freebsd.org Thu Nov 16 18:43:56 2017 Return-Path: Delivered-To: freebsd-scsi@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 5DBECDE5A7B for ; Thu, 16 Nov 2017 18:43:56 +0000 (UTC) (envelope-from leeb@ratnaling.org) Received: from mail-it0-x229.google.com (mail-it0-x229.google.com [IPv6:2607:f8b0:4001:c0b::229]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 32841653F4 for ; Thu, 16 Nov 2017 18:43:56 +0000 (UTC) (envelope-from leeb@ratnaling.org) Received: by mail-it0-x229.google.com with SMTP id x28so1176717ita.0 for ; Thu, 16 Nov 2017 10:43:56 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ratnaling-org.20150623.gappssmtp.com; s=20150623; h=mime-version:in-reply-to:references:from:date:message-id:subject:cc; bh=3wyTi64k1wFbQzkWV//IbUg8X3dVM81oNMUN/8zzjK4=; b=Kf3x8DJc1z5ZYVRyGrJ2F3LvUwfrInO+isPpUpz79if4hv5Cf7BKZonvKRqphUEzqw 5l8ucMjCmBmsROXeYIakKzbnNpG4TEjklAbIwzY8EH7PZXBhaq3ta4ZQDAsisOwxhcjI 2pf5bvAkQs0zMafQspGVOZjUEeiVGPTPhZEHYVqSS4eBuJkLxLhsa7P00WGKe6z8McM6 ieAp4j+ePAS8c40PhTyRtSY0qQ57pEE+ojn91EaDt3EVrNKL6HjdSxMlc4Z15UuMZQWh 43XRJeUrYYoOTjtuxwhLJbPNckGZihGMpBwb+H2XNWH8QwHCYudMvpAlMcq3ul5RHeq5 irBw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:cc; bh=3wyTi64k1wFbQzkWV//IbUg8X3dVM81oNMUN/8zzjK4=; b=gBiyfbI5r3KWv0dXaKSzlpmLcwcpo+XK3GxDFw/L8uy2yWn8uyXDJFY0d9YJdCqprS 9HLQgZT/rfhyf05SCGja8TMJRAuAonHWE4dw3eI1sfYnX2MYu3g3B1gptsfTe8n3kYco eMuU0s30dgMoZFVLqMihBkdu+UHH1q43iW/pr+sZn9gvrajcIWP6kDoSV37ZFfJTxtHU 5aFbdfXClYEuJX6UJKSYNN9oonG6fx1BjiqX2hVgUWriHlbIKryK2TrsM6wc2t2WAB5f 2nLOis7IdaW6KZpoElbAmP28a0tWXz1clZ+rsY6dsbiWrYYYoUAwh2y2J96tb3mylz43 oaSg== X-Gm-Message-State: AJaThX6l++XNvwl/wbBotufEjDBSNMkXV2nl9zS344tfMc08D92RH+v0 o9TCDeeN0syPL+BXBJvMotzxhJWqakNHzEu5j8rOQQ== X-Received: by 10.36.163.138 with SMTP id p132mt3351033ite.57.1510857833960; Thu, 16 Nov 2017 10:43:53 -0800 (PST) MIME-Version: 1.0 Received: by 10.79.125.79 with HTTP; Thu, 16 Nov 2017 10:43:53 -0800 (PST) In-Reply-To: <20171116142843.GA25563@mithlond.kdm.org> References: <20171116142843.GA25563@mithlond.kdm.org> From: Lee Brown Date: Thu, 16 Nov 2017 10:43:53 -0800 Message-ID: Subject: Re: Does anybody have experience with a MD1420, mpr(4) Cc: freebsd-scsi@freebsd.org, freebsd-hardware@freebsd.org Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.25 X-BeenThere: freebsd-scsi@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: SCSI subsystem List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 16 Nov 2017 18:43:56 -0000 On Thu, Nov 16, 2017 at 6:28 AM, Kenneth D. Merry wrote: > On Wed, Nov 15, 2017 at 12:24:47 -0800, Lee Brown wrote: > > Hi, > > > > This is my for foray into DAS, so please be gentle :) Apologies if the > > cross-post is inappropriate, let me know. > > > > I'm looking to build a SAS array with a Dell MD1420. It will be attached > > via a SAS 9300-414E HBA in a Dell R330. > > > > I've verified that the server / SAS card should be fine, but just wanted > to > > know if anybody has set this up before, or if there's any obvious reason > > why it wouldn't work. Dell can be a bit weird sometimes. > > > > Any information is most welcome. > > In theory it should be fine. I haven't used a Dell enclosure recently, but > from posts here, it seems that they like to turn on Type 2 Protection > Information on the drives. (Assuming you buy the drives from Dell.) > > If they do that, you can either reformat, or see the patch here for the > mpr(4) driver to disable using protection information: > > https://docs.freebsd.org/cgi/getmsg.cgi?fetch=308820+0+ > archive/2017/freebsd-scsi/20171022.freebsd-scsi > > I haven't gotten around to changing things so that we detect the PI in the > da(4) driver and use 32 byte CDBs when type 2 protection is enabled. (So > if someone else has time and wants to do it, feel free. It will be > somewhat messy because we only allocate enough space for 16 byte CDBs > inside > the CCB, so you'll need to allocate the CDB separately...) > > If you use ZFS, you'll have checksum protection on your data anyway, so PI > would just be additional protection. > > I would also suggest that you update to the latest firmware (currently > Phase 15) for the SAS controller. You can do that with LSI's sas3flash or > the FreeBSD mprutil(8) utility. > > Ken > -- > Kenneth Merry > ken@FreeBSD.ORG > Thanks Ken, I'm going to purchase the system. I had no idea about PI, that's a nice feature for sure. This will probably just be iSCSI and NFS4 over a 10Gb NIC (Xen cluster), so having PI detection is certainly of interest to me. I'll figure out what I can do to contribute (code/testing) when things have settled. Assuming all is well I'll get the 1420 added to the hardware compatibility list. Much appreciated -- lee From owner-freebsd-scsi@freebsd.org Sat Nov 18 05:42:49 2017 Return-Path: Delivered-To: freebsd-scsi@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 CD607DEF57E for ; Sat, 18 Nov 2017 05:42:49 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id A305B6421B for ; Sat, 18 Nov 2017 05:42:49 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id vAI5gnoX038947 for ; Sat, 18 Nov 2017 05:42:49 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-scsi@FreeBSD.org Subject: [Bug 223381] mpt driver hangs with iscsi devices and scsi drives defined in VBOX FBSD guest Date: Sat, 18 Nov 2017 05:42:49 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: 11.1-RELEASE X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: randomnoise058@gmail.com X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-scsi@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-scsi@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: SCSI subsystem List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 18 Nov 2017 05:42:49 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D223381 --- Comment #3 from Jim D. --- Update on situation (11/17/2017, 11:20pm CST) 1) created VirtualBox (VBox) SCSI controller and added VBox 3GB drive to it 2) modified FBSD-11.1 "fstab" to mount SCSI drive at boot (/SCSIhdd) 3) created shell script to run through a series of system commands on 3 iSC= SI drives, 1 zfs drive, 1 SCSI drive every 10 minutes; FBSD11 Zabbix client not running a) dd (15 times,count=3D1), fsck -Cn, zpool status b) tail /var/log/messages 4) no notable issues for several hours 5) started FBSD11 Zabbix cilent with Zabbix server active but Zabbix queries disabled 6) no notable issues 7) modified Zabbix configuration for FBSD11 client a) removed Zabbix FreeBSD template which included various file system che= cks b) left special locally developed template to perform HDD discovery, stat= us check, and other miscellaneous HDD information reporting 8) activated Zabbix server queries to FBSD11 client 9) script above continues to run without any notable issues 10) after some time, kernel WARNING messages related to iSCSI appeared kernel: WARNING: 192.168.1.19:3260 (iqn.2000-01.com.synology:ds216j.Target-7.c16e0895b7): underflow mismatch: target indicates 0, we calculated 4 11) stopped Zabbix server queries 12) modified special local Zabbix template to exclude extensive HDD status testing (ls, dd, mount, fsck, smartctl, ZFS pool status, iSCSI Target statu= s) 13) reconfigured Zabbix definition for FBSD11 client to use modified templa= te 14) re-started Zabbix server queries to FBSD11 client; above script still running 15) after 1.5 hours, no iSCSI related kernel WARNING messages have appeared Initial conclusion: something within the extensive HDD status testing is probably causing whatever to occur which results in the kernel WARNING messages. It may, or may not, be the iSCSI Target query using "iscsictl". More testing is required to further nail done the specific command(s) relat= ed to the iSCSI issue which as reported earlier which would eventually cause t= he FBSD11 client host to hang. --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-scsi@freebsd.org Sat Nov 18 05:59:04 2017 Return-Path: Delivered-To: freebsd-scsi@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 B1088DEF9A1 for ; Sat, 18 Nov 2017 05:59:04 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 9F4856474B for ; Sat, 18 Nov 2017 05:59:04 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id vAI5x4m7072008 for ; Sat, 18 Nov 2017 05:59:04 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-scsi@FreeBSD.org Subject: [Bug 223381] mpt driver hangs with iscsi devices and scsi drives defined in VBOX FBSD guest Date: Sat, 18 Nov 2017 05:59:04 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: 11.1-RELEASE X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: randomnoise058@gmail.com X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-scsi@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-scsi@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: SCSI subsystem List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 18 Nov 2017 05:59:04 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D223381 --- Comment #4 from Jim D. --- Note that the same locally developed Zabbix template for extensive HDD discovery, testing, and reporting works just fine, with OS specific modifications, on/under Solaris-10/11, CentOS-6/7, RHEL-7, OREL-7, and MacO= S X Sierra (10.12). Though the Synology SAN shows log entries of the same "underflow" warning messages for most/all of the other OS's - none of them = hang up, even when I have all 10, or so, servers and hosts up and active with Za= bbix (one physical for 3 physical hosts, one virtual for all virtual hosts). One physical host is not included in this process. --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-scsi@freebsd.org Sat Nov 18 07:24:59 2017 Return-Path: Delivered-To: freebsd-scsi@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 7F947DF0B7A for ; Sat, 18 Nov 2017 07:24:59 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 629E06661A for ; Sat, 18 Nov 2017 07:24:59 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id vAI7OxY6039487 for ; Sat, 18 Nov 2017 07:24:59 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-scsi@FreeBSD.org Subject: [Bug 223381] mpt driver hangs with iscsi devices and scsi drives defined in VBOX FBSD guest Date: Sat, 18 Nov 2017 07:24:59 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: 11.1-RELEASE X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: randomnoise058@gmail.com X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-scsi@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-scsi@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: SCSI subsystem List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 18 Nov 2017 07:24:59 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D223381 --- Comment #5 from Jim D. --- I have found the problmematical commands on the VBox FBSD-11.1 client host which invoke the previously noted "kernel WARNING/iSCSI underflow" messages: smartctl -d scsi -a -T permissive /dev/da3 smartctl -d scsi -A -T permissive /dev/da3 Same effect if "-d scsi" is not included. "smartctl --scan-open" reports da3 as "scsi" device type which is one of th= e 3 attached iSCSI Targets. Interestingly enough, the following smartctl commands from FBSD-11.1 host do NOT cause any kernel messages: smartctl -d scsi -H -T permissive /dev/da3 smartctl -d scsi -i -T permissive /dev/da3 Installed FBSD-11.1 smartmontools is at version 6.5 2016-05-07. It might be that the Synology SAN handling of the smartctl request for SAN = HDD smartmon attributes from the installed SAN hard drive is problematical, but= I don't understand why that would cause FBSD iSCSI underflow messages. =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D Results from Synology SAN same as obtained from FBSD-11.1 host =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D smartctl --scan-open /dev/hda -d ata # /dev/hda, ATA device /dev/sda -d scsi # /dev/sda, SCSI device -------------------------------- smartctl -d scsi -i -T permissive /dev/sda smartctl 6.5 (build date Oct 25 2017) [x86_64-linux-3.10.102] (local build) Copyright (C) 2002-16, Bruce Allen, Christian Franke, www.smartmontools.org =3D=3D=3D START OF INFORMATION SECTION =3D=3D=3D Vendor: WDC Product: WD6000HLHX-01JJP Revision: 04.0 User Capacity: 600,127,266,816 bytes [600 GB] Logical block size: 512 bytes LU is fully provisioned Rotation Rate: 10000 rpm Logical Unit id: 0x50014ee0ae06dfb2 Serial number: WD-WX71E71WZ063 Device type: disk Local Time is: Sat Nov 18 01:13:52 2017 CST SMART support is: Unavailable - device lacks SMART capability. -------------------------------- smartctl -d scsi -a -T permissive /dev/sda smartctl 6.5 (build date Oct 25 2017) [x86_64-linux-3.10.102] (local build) Copyright (C) 2002-16, Bruce Allen, Christian Franke, www.smartmontools.org =3D=3D=3D START OF INFORMATION SECTION =3D=3D=3D Vendor: WDC Product: WD6000HLHX-01JJP Revision: 04.0 User Capacity: 600,127,266,816 bytes [600 GB] Logical block size: 512 bytes LU is fully provisioned Rotation Rate: 10000 rpm Logical Unit id: 0x50014ee0ae06dfb2 Serial number: WD-WX71E71WZ063 Device type: disk Local Time is: Sat Nov 18 01:16:00 2017 CST SMART support is: Unavailable - device lacks SMART capability. =3D=3D=3D START OF READ SMART DATA SECTION =3D=3D=3D Current Drive Temperature: 0 C Drive Trip Temperature: 0 C Error Counter logging not supported [GLTSD (Global Logging Target Save Disable) set. Enable Save with '-S on'] Device does not support Self Test logging -------------------------------- smartctl -d scsi -A -T permissive /dev/sda;echo $? smartctl 6.5 (build date Oct 25 2017) [x86_64-linux-3.10.102] (local build) Copyright (C) 2002-16, Bruce Allen, Christian Franke, www.smartmontools.org =3D=3D=3D START OF READ SMART DATA SECTION =3D=3D=3D 255 -------------------------------- smartctl -d scsi -H -T permissive /dev/sda;echo $? smartctl 6.5 (build date Oct 25 2017) [x86_64-linux-3.10.102] (local build) Copyright (C) 2002-16, Bruce Allen, Christian Franke, www.smartmontools.org =3D=3D=3D START OF READ SMART DATA SECTION =3D=3D=3D SMART Health Status: OK 255 --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-scsi@freebsd.org Sat Nov 18 07:41:53 2017 Return-Path: Delivered-To: freebsd-scsi@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 66A61DF109B for ; Sat, 18 Nov 2017 07:41:53 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 548B066C82 for ; Sat, 18 Nov 2017 07:41:53 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id vAI7frB2076245 for ; Sat, 18 Nov 2017 07:41:53 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-scsi@FreeBSD.org Subject: [Bug 223381] mpt driver hangs with iscsi devices and scsi drives defined in VBOX FBSD guest Date: Sat, 18 Nov 2017 07:41:53 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: 11.1-RELEASE X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: randomnoise058@gmail.com X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-scsi@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-scsi@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: SCSI subsystem List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 18 Nov 2017 07:41:53 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D223381 --- Comment #6 from Jim D. --- Again - other OS's accessing the same Synology SAN using the same commands don't have any problem with the "iSCSI underflow" messages. None of them lo= ck or hang up. I don't understand enough of how the "iSCSI underflow" messages= are generated or why. --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-scsi@freebsd.org Sat Nov 18 20:49:05 2017 Return-Path: Delivered-To: freebsd-scsi@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 B6713DDBF78 for ; Sat, 18 Nov 2017 20:49:05 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id A42F47CBDC for ; Sat, 18 Nov 2017 20:49:05 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id vAIKn5Bj095606 for ; Sat, 18 Nov 2017 20:49:05 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-scsi@FreeBSD.org Subject: [Bug 223381] mpt driver hangs with iscsi devices and scsi drives defined in VBOX FBSD guest Date: Sat, 18 Nov 2017 20:49:05 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: 11.1-RELEASE X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: trasz@FreeBSD.org X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-scsi@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-scsi@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: SCSI subsystem List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 18 Nov 2017 20:49:05 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D223381 --- Comment #7 from Edward Tomasz Napierala --- The "iSCSI underflow" is a warning that the other side uses buggy iSCSI implementation. It's harmless and shouldn't cause any problems. If you do= n't want to see it, just mute it down by appending kern.iscsi.debug=3D0 to /etc/sysctl.conf. --=20 You are receiving this mail because: You are the assignee for the bug.=