From owner-freebsd-questions@FreeBSD.ORG Sun Feb 23 02:21:59 2014 Return-Path: Delivered-To: questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 52BCF4F6; Sun, 23 Feb 2014 02:21:59 +0000 (UTC) Received: from mx1.fisglobal.com (mx1.fisglobal.com [199.200.24.190]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 13C4C16FC; Sun, 23 Feb 2014 02:21:58 +0000 (UTC) Received: from smarthost.fisglobal.com ([10.132.206.191]) by ltcfislmsgpa04.fnfis.com (8.14.5/8.14.5) with ESMTP id s1N2J5nQ032354 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT); Sat, 22 Feb 2014 20:19:05 -0600 Received: from THEMADHATTER (10.242.181.54) by smarthost.fisglobal.com (10.132.206.191) with Microsoft SMTP Server id 14.3.174.1; Sat, 22 Feb 2014 20:19:02 -0600 From: Sender: Devin Teske To: References: <0fdd01cf2d29$dca0aba0$95e202e0$@FreeBSD.org> <4e4aa28301cedd61cb5693e79a90d0ab@dweimer.net> <0fdf01cf2d34$65d9de00$318d9a00$@FreeBSD.org> <87679f0a7789f01ad66b3c2ae55e3006@dweimer.net> <101101cf2d97$d708e630$851ab290$@FreeBSD.org> <101701cf2da1$8f47ddb0$add79910$@FreeBSD.org> In-Reply-To: Subject: RE: ZFS on Hardware RAID controller Date: Sat, 22 Feb 2014 18:18:54 -0800 Message-ID: <125601cf303d$9b4851a0$d1d8f4e0$@FreeBSD.org> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Mailer: Microsoft Outlook 15.0 Thread-Index: AQLZ7+7/ieFjnRxrw7xfyVSgmKX96wLfKSMrAmxEjEMCYeNcAwLaiwfuAoMsxjQB418jsAKoN686AfZonAACK13MjwJf9BfnAhyG5LeX2vQJsA== Content-Language: en-us X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:5.11.87, 1.0.14, 0.0.0000 definitions=2014-02-22_03:2014-02-21,2014-02-22,1970-01-01 signatures=0 X-Mailman-Approved-At: Sun, 23 Feb 2014 02:40:27 +0000 Cc: daver@vicor.com, questions@freebsd.org, owner-freebsd-questions@freebsd.org, 'Devin Teske' , dteske@FreeBSD.org X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 23 Feb 2014 02:21:59 -0000 > -----Original Message----- > From: freebsd@fongaboo.com [mailto:freebsd@fongaboo.com] > Sent: Saturday, February 22, 2014 12:19 PM > To: dteske@FreeBSD.org > Cc: dweimer@dweimer.net; questions@freebsd.org; owner-freebsd- > questions@freebsd.org; daver@vicor.com; 'Devin Teske' > Subject: RE: ZFS on Hardware RAID controller > > > So I think it's fair to say that there is some ambiguous information out there > about the definition of JBOD. > > So, without worrying about settling the discrepency over nomenclature, is it fair > to say that... > > If I am planning to use ZFS on a machine where the drive controller happens to > be one that can be configured for some combination of HARDWARE RAID... > > I should configure it so that it does not concatenate/span/combine the drives in > any way at the hardware level. > > I need to configure it as if it wasn't even a RAID controller, but rather in a > configuration where the motherboard/filesystem/OS will initially see each > physical drive as its own volume. > > TRUTH? > > You got it. -- Devin > On Wed, 19 Feb 2014, dteske@FreeBSD.org wrote: > > > Re: JBOD... > > > > I think it's very telling that when Google gives you the description > > of JBOD, it actually comes from the Wikipedia, but ... it doesn't > > include the [misleading] statement about the [optional] act of joining > > the disks. > > > > Google's Definition: > > Just a Bunch Of Disks. A collection of hard disks that aren't > > configured according to RAID; A hard disk enclosure for several disks, > > especially one lacking a RAID controller > > Source: > > https://urldefense.proofpoint.com/v1/url?u=http://en.wiktionary.org/wi > > > ki/JBOD&k=%2FbkpAUdJWZuiTILCq%2FFnQg%3D%3D%0A&r=Mrjs6vR4%2Faj2N > s9%2Fss > > > HJjg%3D%3D%0A&m=WjPSdoY1BxcTeoacI96NBULuvXxAWYL0OSOJgg9ME5k%3 > D%0A&s=70 > > e753addb455acc6a895f1405837f3ccf4e507dae203a1a658aa518c12c167f > > > > Definition from > > JBOD (abbreviated from "just a bunch of disks") is an architecture > > using multiple hard drives, but not in a RAID configuration, thus > > providing neither redundancy nor performance improvements. Hard drives > > *may be* handled independently as separate logical volumes, or they > > *may be* combined into a single logical volume using a volume manager > > like LVM; such [optionally combined] volumes are usually called > > "spanned".[2] > > > > I added the *'s around "may be" and also added the "[optionally > > combined]" texts to help clarify that for you. And I would go on to > > further say that the LVM volume manager used to combine the > > JBOD-access devices is not part of nor has any relation to said JBOD > > access. JBOD is a means of exporting the disks to the volume manager > > whose use is optional. > > -- > > Devin > > > > _____________ > > The information contained in this message is proprietary and/or confidential. > If you are not the intended recipient, please: (i) delete the message and all > copies; (ii) do not disclose, distribute or use the message in any manner; and > (iii) notify the sender immediately. In addition, please be aware that any > message addressed to our domain is subject to archiving and review by persons > other than the intended recipient. Thank you. > > _____________ The information contained in this message is proprietary and/or confidential. If you are not the intended recipient, please: (i) delete the message and all copies; (ii) do not disclose, distribute or use the message in any manner; and (iii) notify the sender immediately. In addition, please be aware that any message addressed to our domain is subject to archiving and review by persons other than the intended recipient. Thank you.