Skip site navigation (1)Skip section navigation (2)
Date:      Mon, 17 Dec 2018 09:44:32 +0100
From:      Borja Marcos <borjam@sarenet.es>
To:        sbruno@freebsd.org
Cc:        Steven Hartland <killing@multiplay.co.uk>, freebsd-fs@freebsd.org
Subject:   Re: Dell R710 with PERC H310. GPT issues and hardware raid or ZFS?
Message-ID:  <E5B9E724-5210-432C-98B9-6D33E2C81834@sarenet.es>
In-Reply-To: <1372904516.1427.4.camel@localhost>
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>

next in thread | previous in thread | raw e-mail | index | archive | help


> On 4 Jul 2013, at 04:21, Sean Bruno <sean_bruno@yahoo.com> 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.




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?E5B9E724-5210-432C-98B9-6D33E2C81834>