From owner-freebsd-stable@freebsd.org Fri May 3 11:51:43 2019 Return-Path: Delivered-To: freebsd-stable@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 B51E6158D590 for ; Fri, 3 May 2019 11:51:43 +0000 (UTC) (envelope-from petefrench@ingresso.co.uk) Received: from constantine.ingresso.co.uk (constantine.ingresso.co.uk [31.24.6.74]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) server-signature RSA-PSS (4096 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 7A9656DAB6 for ; Fri, 3 May 2019 11:51:42 +0000 (UTC) (envelope-from petefrench@ingresso.co.uk) Received: from [82.47.240.30] (helo=foula.local) by constantine.ingresso.co.uk with esmtpsa (TLSv1.3:TLS_AES_128_GCM_SHA256:128) (Exim 4.92 (FreeBSD)) (envelope-from ) id 1hMWj6-0004X5-68 for freebsd-stable@freebsd.org; Fri, 03 May 2019 11:51:40 +0000 Subject: Re: ZFS... To: freebsd-stable@freebsd.org References: <30506b3d-64fb-b327-94ae-d9da522f3a48@sorbs.net> <56833732-2945-4BD3-95A6-7AF55AB87674@sorbs.net> <3d0f6436-f3d7-6fee-ed81-a24d44223f2f@netfence.it> <17B373DA-4AFC-4D25-B776-0D0DED98B320@sorbs.net> <70fac2fe3f23f85dd442d93ffea368e1@ultra-secure.de> <70C87D93-D1F9-458E-9723-19F9777E6F12@sorbs.net> <58DA896C-5312-47BC-8887-7680941A9AF2@sarenet.es> From: Pete French Message-ID: <37e71963-31d3-5d9d-02b8-88f50195afc4@ingresso.co.uk> Date: Fri, 3 May 2019 12:51:40 +0100 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.11; rv:67.0) Gecko/20100101 Thunderbird/67.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 8bit X-Rspamd-Queue-Id: 7A9656DAB6 X-Spamd-Bar: -- Authentication-Results: mx1.freebsd.org; dmarc=pass (policy=none) header.from=ingresso.co.uk; spf=pass (mx1.freebsd.org: domain of petefrench@ingresso.co.uk designates 31.24.6.74 as permitted sender) smtp.mailfrom=petefrench@ingresso.co.uk X-Spamd-Result: default: False [-2.55 / 15.00]; ARC_NA(0.00)[]; RCVD_VIA_SMTP_AUTH(0.00)[]; RCVD_COUNT_TWO(0.00)[2]; NEURAL_HAM_MEDIUM(-0.95)[-0.953,0]; FROM_HAS_DN(0.00)[]; R_SPF_ALLOW(-0.20)[+ip4:31.24.6.74]; TO_MATCH_ENVRCPT_ALL(0.00)[]; MIME_GOOD(-0.10)[text/plain]; TO_DN_NONE(0.00)[]; NEURAL_HAM_LONG(-1.00)[-0.999,0]; RCPT_COUNT_ONE(0.00)[1]; IP_SCORE(-0.30)[asn: 16082(-1.40), country: GB(-0.09)]; NEURAL_SPAM_SHORT(0.06)[0.056,0]; MX_GOOD(-0.01)[cached: us-smtp-inbound-1.mimecast.com]; DMARC_POLICY_ALLOW(-0.50)[ingresso.co.uk,none]; SUBJ_ALL_CAPS(0.45)[6]; RECEIVED_SPAMHAUS_PBL(0.00)[30.240.47.82.zen.spamhaus.org : 127.0.0.11]; R_DKIM_NA(0.00)[]; MIME_TRACE(0.00)[0:+]; ASN(0.00)[asn:16082, ipnet:31.24.0.0/21, country:GB]; MID_RHS_MATCH_FROM(0.00)[]; RCVD_TLS_ALL(0.00)[]; FROM_EQ_ENVFROM(0.00)[] X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 03 May 2019 11:51:43 -0000 > Hmm What happens when you do a “camcontrol devlist”? root@toybox:/usr/local/etc # camcontrol devlist at scbus0 target 0 lun 0 (pass0,da0) at scbus0 target 1 lun 0 (pass1,da1) at scbus0 target 2 lun 0 (pass2,da2) at scbus0 target 3 lun 0 (pass3,da3) at scbus2 target 0 lun 0 (pass4,cd0) > Camcontrol tags da0 -v? root@toybox:/usr/local/etc # camcontrol tags da0 -v (pass0:ciss0:0:0:0): dev_openings 255 (pass0:ciss0:0:0:0): dev_active 0 (pass0:ciss0:0:0:0): allocated 0 (pass0:ciss0:0:0:0): queued 0 (pass0:ciss0:0:0:0): held 0 (pass0:ciss0:0:0:0): mintags 2 (pass0:ciss0:0:0:0): maxtags 255 > How is the controller recognized by FreeBSD? For some of them it’s possible to instruct the controller to present the physical devices to CAM. Of course > you need to be careful to avoid any logical volume configuration in that case. I have been using these a long time, back to the old ones which were not ciss and ditn sit under CAM. Drives which arent configured dont show up at all, so I think the above is the best I can do. > But I would only tinker with this at system installation time, making such a change on a running system with valid data can be disastrous. Heh, yes ;-) Did you learn that the hard way ? I did! -pete.