From owner-freebsd-fs@freebsd.org Mon Dec 17 08:44:44 2018 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 BAF701335A1B for ; Mon, 17 Dec 2018 08:44:44 +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 A1EE88A256; Mon, 17 Dec 2018 08:44:43 +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 005709DC8C7; Mon, 17 Dec 2018 09:44:32 +0100 (CET) Content-Type: text/plain; charset=utf-8 Mime-Version: 1.0 (Mac OS X Mail 12.2 \(3445.102.3\)) Subject: Re: Dell R710 with PERC H310. GPT issues and hardware raid or ZFS? From: Borja Marcos In-Reply-To: <1372904516.1427.4.camel@localhost> Date: Mon, 17 Dec 2018 09:44:32 +0100 Cc: Steven Hartland , freebsd-fs@freebsd.org Content-Transfer-Encoding: quoted-printable Message-Id: References: <51C5B4EE.3010601@growveg.net> <81EDE2A7D67241DAB985C38662DA57DD@multiplay.co.uk> <51C5EAB0.7040009@growveg.net> <20130622191619.GA73246@icarus.home.lan> <12FB82C142E74924B27F4DBB642D0D1F@multiplay.co.uk> <1372904516.1427.4.camel@localhost> To: sbruno@freebsd.org X-Mailer: Apple Mail (2.3445.102.3) X-Rspamd-Queue-Id: A1EE88A256 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 [1.63 / 15.00]; ARC_NA(0.00)[]; RCVD_VIA_SMTP_AUTH(0.00)[]; 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]; MIME_TRACE(0.00)[0:+]; DMARC_NA(0.00)[sarenet.es]; TO_DN_SOME(0.00)[]; NEURAL_SPAM_MEDIUM(0.31)[0.310,0]; TO_MATCH_ENVRCPT_SOME(0.00)[]; MX_GOOD(-0.01)[smtp.sarenet.es,smtp.sarenet.es,smtp.sarenet.es]; NEURAL_SPAM_LONG(0.49)[0.490,0]; RCVD_IN_DNSWL_NONE(0.00)[151.151.16.195.list.dnswl.org : 127.0.10.0]; NEURAL_HAM_SHORT(-0.38)[-0.376,0]; RCVD_TLS_LAST(0.00)[]; FROM_EQ_ENVFROM(0.00)[]; R_DKIM_NA(0.00)[]; SUBJECT_ENDS_QUESTION(1.00)[]; ASN(0.00)[asn:3262, ipnet:195.16.128.0/19, country:ES]; MID_RHS_MATCH_FROM(0.00)[]; IP_SCORE(0.01)[country: ES(0.06)]; 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: Mon, 17 Dec 2018 08:44:44 -0000 > On 4 Jul 2013, at 04:21, Sean Bruno wrote: >=20 >> Some mfi controllers actually have a JBOD option, if it does you'll >> be able to this controller if not watch out as using the RAID 0 = option >> will almost certainly cause you pain. >>=20 >> mps as Jeremy has said is better option. >>=20 >> Regards >> Steve >=20 > I note that the H310 in a test R420 that I have does indeed have a = JBOD > option. This presents a disk as /dev/mfisyspdX which is totally > befuddling. In my opinion the best option is not to create any kind of volumes (a = JBOD =E2=80=9Cmfisyspd=E2=80=9D is still equivalent to creating a =E2=80=9CRAID 0=E2=80=9D volume per = disk) and rely on the hw.mfi.allow_cam_disk_passthrough tunable instead. The "mfisyspd=E2=80=9D pseudo devices are not CAM devices.=20 At least in my case it has worked perfectly for many years. Before that = tunable was available I made a change suggested by Scott Long.=20 Borja.