From owner-freebsd-fs@freebsd.org Tue Jan 22 12:10:40 2019 Return-Path: Delivered-To: freebsd-fs@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 05E4F14BACF5 for ; Tue, 22 Jan 2019 12:10:40 +0000 (UTC) (envelope-from borjam@sarenet.es) Received: from cu01176b.smtpx.saremail.com (cu01176b.smtpx.saremail.com [195.16.151.151]) (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 B6CFB89436 for ; Tue, 22 Jan 2019 12:10:38 +0000 (UTC) (envelope-from borjam@sarenet.es) Received: from [172.16.8.5] (unknown [192.148.167.11]) by proxypop01.sare.net (Postfix) with ESMTPA id A904F9DD7E0; Tue, 22 Jan 2019 13:10:35 +0100 (CET) Content-Type: text/plain; charset=utf-8 Mime-Version: 1.0 (Mac OS X Mail 12.2 \(3445.102.3\)) Subject: Re: ZFS on Hardware RAID From: Borja Marcos In-Reply-To: Date: Tue, 22 Jan 2019 13:10:34 +0100 Cc: Steven Hartland , freebsd-fs Content-Transfer-Encoding: quoted-printable Message-Id: References: <1180280695.63420.1547910313494.JavaMail.zimbra@gausus.net> <92646202.63422.1547910433715.JavaMail.zimbra@gausus.net> <1691666278.63816.1547976245836.JavaMail.zimbra@gausus.net> <92746659-4B3F-415C-BB6A-6C99837AFAF2@sarenet.es> <335e44ec-7c76-8dbd-f587-46e6a9266efc@multiplay.co.uk> To: Borja Marcos X-Mailer: Apple Mail (2.3445.102.3) X-Rspamd-Queue-Id: B6CFB89436 X-Spamd-Bar: -- Authentication-Results: mx1.freebsd.org; spf=pass (mx1.freebsd.org: domain of borjam@sarenet.es designates 195.16.151.151 as permitted sender) smtp.mailfrom=borjam@sarenet.es X-Spamd-Result: default: False [-2.34 / 15.00]; ARC_NA(0.00)[]; RCVD_VIA_SMTP_AUTH(0.00)[]; NEURAL_HAM_MEDIUM(-0.80)[-0.801,0]; FROM_HAS_DN(0.00)[]; RCPT_COUNT_THREE(0.00)[3]; R_SPF_ALLOW(-0.20)[+ip4:195.16.150.0/23]; MV_CASE(0.50)[]; MIME_GOOD(-0.10)[text/plain]; RCVD_TLS_LAST(0.00)[]; DMARC_NA(0.00)[sarenet.es]; NEURAL_HAM_LONG(-0.99)[-0.989,0]; TO_MATCH_ENVRCPT_SOME(0.00)[]; TO_DN_ALL(0.00)[]; MX_GOOD(-0.01)[cached: smtp.sarenet.es]; NEURAL_HAM_SHORT(-0.75)[-0.749,0]; RCVD_IN_DNSWL_NONE(0.00)[151.151.16.195.list.dnswl.org : 127.0.10.0]; IP_SCORE(0.01)[country: ES(0.05)]; FROM_EQ_ENVFROM(0.00)[]; R_DKIM_NA(0.00)[]; MIME_TRACE(0.00)[0:+]; ASN(0.00)[asn:3262, ipnet:195.16.128.0/19, country:ES]; MID_RHS_MATCH_FROM(0.00)[]; RCVD_COUNT_TWO(0.00)[2] X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 22 Jan 2019 12:10:40 -0000 > On 22 Jan 2019, at 12:52, Borja Marcos wrote: >=20 > HBA mode: when the card is in IT mode *or* it does expose the actual = targets to the CAM layer. In the past I did it > by manually patching the drivers and I=E2=80=99ve kept systems running = smoothly for many years despite using IR cards.=20 > Currently you can use hw.mfi.allow_cam_disk_passthrough tunable to = achieve the same effect without ugly tinkering.=20 This is what I did long ago to have IR cards expose the targets to the = CAM layer. It was a suggestion from Scott Long. I first did it with AAC cards, later with MFI ones.=20 = https://lists.freebsd.org/pipermail/freebsd-scsi/2007-October/003223.html Some years ago the =E2=80=9Crecipe=E2=80=9D was made official (although = not encouraged) by adding the=20 hw.mfi.allow_cam_disk_passthrough tunable. Doing this I didn=E2=80=99t need to create volumes or anything. Just = plug the disks and avoid to configure anything for them on the RAID controller. The disks appeared as =E2=80=9Cd= a=E2=80=9D devices and I could hot plug them and use the CAM commands without any issues.=20 Borja.