From owner-freebsd-fs@freebsd.org Mon Jan 21 20:05:31 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 478F514B63AC for ; Mon, 21 Jan 2019 20:05:31 +0000 (UTC) (envelope-from killing@multiplay.co.uk) Received: from mail-ed1-x531.google.com (mail-ed1-x531.google.com [IPv6:2a00:1450:4864:20::531]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id E8AA676522 for ; Mon, 21 Jan 2019 20:05:29 +0000 (UTC) (envelope-from killing@multiplay.co.uk) Received: by mail-ed1-x531.google.com with SMTP id a20so17510371edc.8 for ; Mon, 21 Jan 2019 12:05:29 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=multiplay-co-uk.20150623.gappssmtp.com; s=20150623; h=subject:to:cc:references:from:message-id:date:user-agent :mime-version:in-reply-to:content-transfer-encoding:content-language; bh=svyxM5Edxr05G9Pr3gOmk3+k5jHvW/NhruMV3fx22JY=; b=z4rSR3PWNtbZT3+OaPmJDphVLf5mtRxRP4IdbDFUZcbOWt62BE8bSL1/o0ZTwyzTV0 IKQnd7BRF/394VT4VdfASWo3mHj/X45FS2p4E3rx8EVGrpa7tPFa1hUSRdMNY6N1o94/ TawXB00xLeLGlcxXovP7xJhwl2cLHML+qWa0ZRwARyiieUbdRLhNhLA3Iio5dAu4WtOF QS5/iYeJYacff0Mh6ImmgWudlthgOiEZReAFYTi5gcNSv4F9GkK0XEn9zbvkxyx/fOrD ys8ekW/kY8RGSdTCydwuEoK4l0U+e+EAe1jyh/t9HMAxLJFzdXzv5rnA8ikxwrxpbahY 3BZA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:cc:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-transfer-encoding :content-language; bh=svyxM5Edxr05G9Pr3gOmk3+k5jHvW/NhruMV3fx22JY=; b=KsuyHRN2UI8zVor+ncl9rCikDFr9XSHk0Yc55nQkZ7X4gjxBniXM51nx/mgbf0I1JZ RYhdVu7arkIvwqaMDE0o9OckyyvWn9pqNcfVIjM6Cui99doz8mSgEfVX8ntifI6uQAiT SqdAxBs3VuhZ8upGgDRPdFksxUbgTIXhv397qe7DuP1x2uUlAKStcEwxZod+x/q5tDdL WwA20fYrkuy8dYJTOveRL6oEGuca1eGQ5qbeq1DevFJxl5ixaT5tAihmT51NYofGFrqi dcjzLbrfYK9/62YlKurgDBgmUvsCyXUYw2DCUTkpl4vm1uJIXl+++3S8JEguByJ6ouSE Gc5A== X-Gm-Message-State: AJcUukfCWAyxcUgGXvp5I0j55HlXZrTefCOGq+79GV2MKurPsETt1Wj8 pQxP7jlyrg7+zgwCNs0HPrvSa11qo8Y= X-Google-Smtp-Source: ALg8bN4DYjMN5Q5+s8LI63ThSbWmUMCAl+THWmZcLzA/NkCuNaxy1m8tBJzswSzt8F2o/EPnwBma3A== X-Received: by 2002:a50:b559:: with SMTP id z25mr27760436edd.239.1548101127786; Mon, 21 Jan 2019 12:05:27 -0800 (PST) Received: from [10.44.128.75] ([161.12.40.153]) by smtp.gmail.com with ESMTPSA id p21sm8858861edr.67.2019.01.21.12.05.26 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Mon, 21 Jan 2019 12:05:26 -0800 (PST) Subject: Re: ZFS on Hardware RAID To: Gary Palmer , Borja Marcos Cc: freebsd-fs 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> <20190121160016.GC45377@in-addr.com> From: Steven Hartland Message-ID: Date: Mon, 21 Jan 2019 20:05:27 +0000 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:60.0) Gecko/20100101 Thunderbird/60.4.0 MIME-Version: 1.0 In-Reply-To: <20190121160016.GC45377@in-addr.com> Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit Content-Language: en-US X-Rspamd-Queue-Id: E8AA676522 X-Spamd-Bar: ------ Authentication-Results: mx1.freebsd.org; dkim=pass header.d=multiplay-co-uk.20150623.gappssmtp.com header.s=20150623 header.b=z4rSR3PW; spf=pass (mx1.freebsd.org: domain of killing@multiplay.co.uk designates 2a00:1450:4864:20::531 as permitted sender) smtp.mailfrom=killing@multiplay.co.uk X-Spamd-Result: default: False [-6.09 / 15.00]; ARC_NA(0.00)[]; RCVD_VIA_SMTP_AUTH(0.00)[]; R_DKIM_ALLOW(-0.20)[multiplay-co-uk.20150623.gappssmtp.com:s=20150623]; NEURAL_HAM_MEDIUM(-1.00)[-0.998,0]; FROM_HAS_DN(0.00)[]; RCPT_COUNT_THREE(0.00)[3]; R_SPF_ALLOW(-0.20)[+ip6:2a00:1450:4000::/36]; NEURAL_HAM_LONG(-1.00)[-1.000,0]; MIME_GOOD(-0.10)[text/plain]; PREVIOUSLY_DELIVERED(0.00)[freebsd-fs@freebsd.org]; DMARC_NA(0.00)[multiplay.co.uk]; RCVD_COUNT_THREE(0.00)[3]; TO_MATCH_ENVRCPT_SOME(0.00)[]; TO_DN_ALL(0.00)[]; DKIM_TRACE(0.00)[multiplay-co-uk.20150623.gappssmtp.com:+]; MX_GOOD(-0.01)[cached: ASPMX.L.GOOGLE.COM]; RCVD_IN_DNSWL_NONE(0.00)[1.3.5.0.0.0.0.0.0.0.0.0.0.0.0.0.0.2.0.0.4.6.8.4.0.5.4.1.0.0.a.2.list.dnswl.org : 127.0.5.0]; NEURAL_HAM_SHORT(-0.95)[-0.946,0]; IP_SCORE(-2.64)[ip: (-9.09), ipnet: 2a00:1450::/32(-2.16), asn: 15169(-1.87), country: US(-0.08)]; FROM_EQ_ENVFROM(0.00)[]; MIME_TRACE(0.00)[0:+]; RCVD_TLS_LAST(0.00)[]; ASN(0.00)[asn:15169, ipnet:2a00:1450::/32, country:US]; MID_RHS_MATCH_FROM(0.00)[] 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, 21 Jan 2019 20:05:31 -0000 On 21/01/2019 16:00, Gary Palmer wrote: > On Mon, Jan 21, 2019 at 03:17:08PM +0100, Borja Marcos wrote: >> >>> On 20 Jan 2019, at 16:33, jdelisle wrote: >>> I can say for certain that with Dell PERC 6/e RAID (SAS 8087ELP based) >>> cards, when the virtual devices are entire disks each in a RAID0 >>> configuration, the way the adapter writes data to them is effectively the >>> same as JBOD. You can take a RAID0 drive from a PERC 6/e controller and >>> use in with an HBA/ "IT Mode" JBOD controller without issue. I personally >>> migrated 14x 1TB drives off PERC 6/e (all RAID0's) to a SAS 6gbps HBA, and >>> my ZFS VDEV's and pools were totally fine. You can move back and forth no >>> problem. I can't say this is the case for ALL RAID controllers, I've only >>> done this with an old PERC 6/e. >> However a single disk RAID0 volume (what manufacturers call a JBOD) is not the same >> as a disk. With the ???virtual JBOD??? you lose direct CAM access, which means that some >> advanced options won???t be supported. >> >> For example, if you are using SSDs ZFS knows when to issue a TRIM (or, in general, >> BIO_DELETE) command. Does the ???virtual JBOD??? offer that option? >> >> The same could be said of other functionalities available when you talk directly >> to the disks. > This is a pertinent point. If I remember right, no LSI RAID controller > supports TRIM/UNMAP on SSDs. Spinning rust is OK in a RAID controller, > but if you have SSDs attached to the LSI RAID controller and plan to use > them in ZFS it is better to get a HBA instead. LSI controllers, even RAID ones, when used in JBOD mode pass this information through correctly. Even if its SATA disk, it should work after I added support to pass-through ATA command to CAM SCSI disk many years ago.     Regards     Steve