From owner-freebsd-fs@freebsd.org Tue Apr 24 05:46: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 6C56CFBC2EE for ; Tue, 24 Apr 2018 05:46:44 +0000 (UTC) (envelope-from zmey20000@yahoo.com) Received: from sonic308-39.consmr.mail.ne1.yahoo.com (sonic308-39.consmr.mail.ne1.yahoo.com [66.163.187.62]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 0818479B9E for ; Tue, 24 Apr 2018 05:46:43 +0000 (UTC) (envelope-from zmey20000@yahoo.com) X-YMail-OSG: HiVhAWAVM1ncfBdeGhTbSsrnq8_UxAfeOALA6pbVgMI6OAwb3cO6C_Osp1hr2FB OYku8M1zoDerWxgtwBoJT1sv4AbkmB2aF7Sm69nWAM6lzEWMOYIWCXaZ.r8mbnu3wkl2uPrP4Tp8 To1OkzZVJ3cp3KJS7GQfwWHeKM7oE6lQDDzrgmEnO7X_ub9f.t31Bf9Ngj.eluLK5vkl2ki.nlUr 7QvvmlGW9735YHfe2L9ewcGhfhF4BO8AUq7qHsyFkUVrGCNoNEFw0bZiov9U.N7vLHXMjQ_rT2.U kEDGjAtMs0wMGOOG1SHrYx_nhP.wQNDGjvqwrwxZnms.JnHJS8XJOPkPQ4ReWlnKqIVvtsU8wp45 UpYr8.M7APYWqs5UnUEQ8OFasOV406CANWDQivshe88DfrUWrlGUuoIu537cVK5twLVQ.fUoSGgP mM6kRn387zwxBJB9gUVBMW1PJxMBOAKL2dNlG3nUlB5DDMBfWCED9Ff.uZ7JXCthy60Zqb0hV1O6 OfHpe5gyo_ahRz.TA8_O5merWJmnXAErw56xc4XvcdaT4gYLJfxJ8.eNuhhpfWgpyNNXRgbwfntp e5qs- Received: from sonic.gate.mail.ne1.yahoo.com by sonic308.consmr.mail.ne1.yahoo.com with HTTP; Tue, 24 Apr 2018 05:46:42 +0000 Received: from athe-hcsd-peer.customers.otenet.gr (EHLO [192.168.140.13]) ([195.167.103.234]) by smtp417.mail.ne1.yahoo.com (Oath Hermes SMTP Server) with ESMTPA ID 5b02326fd0168e2da661101e424faf52; Tue, 24 Apr 2018 04:52:10 +0000 (UTC) Content-Type: text/plain; charset=utf-8 Mime-Version: 1.0 (1.0) Subject: Re: ctl_isc_lun_sync: Received conflicting HA LUN From: Mikhail Zakharov X-Mailer: iPhone Mail (15E216) In-Reply-To: <1d4a2171-d083-9e37-954c-cf58ed2c2982@sentex.net> Date: Tue, 24 Apr 2018 07:52:07 +0300 Cc: "freebsd-fs@freebsd.org" Content-Transfer-Encoding: quoted-printable Message-Id: References: <4cb4aa83-bd49-0c20-4e41-c11c682b0570@sentex.net> <1e1e7cd5-0797-c168-fbce-a36edc6a432e@sentex.net> <14CC6AF1-C1AB-48D2-925D-A46989AD7B3C@yahoo.com> <1d4a2171-d083-9e37-954c-cf58ed2c2982@sentex.net> To: Mike Tancsa X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 24 Apr 2018 05:46:44 -0000 Yes, there is misunderstanding.=20 CTL HA setup works for 2 different servers that are accessing right the same= drive. It is not like HAST. So if you need replication to a different drive= , use HAST, but if you want simultaneous access to the single drive, use CTL= HA. Best regards, Mike=20 > 23 =D0=B0=D0=BF=D1=80. 2018 =D0=B3., =D0=B2 21:54, Mike Tancsa =D0=BD=D0=B0=D0=BF=D0=B8=D1=81=D0=B0=D0=BB(=D0=B0): >=20 >> On 4/23/2018 1:41 PM, Mikhail Zakharov wrote: >>=20 >> You have different Lun0 definitions in ctl.conf: check path >> /dev/zvol/tank1/v1 vs path /dev/zvol/zroot/v1 as well as different >> device-ids. These values should describe the same =E2=80=9Cdrive=E2=80=9D= in both >> configuration, are you sure if it=E2=80=99s the same disk? :) >=20 > Hi, > I guess I am misunderstanding it. The ctl.conf is on 2 different > servers, so they are two different disks. >=20 > What I am hoping to achieve is sort of like a HAST setup. So that if > server-a dies, server-b takes over >=20 > So on server a) I did >=20 > zfs create -V 80G zroot/v1 >=20 > and on server b) I did >=20 > zfs create -V 80G tank1/v1 >=20 >=20 > However, in order for the files to be identical, I used the slower disks > on b) so that the path statement is identical. But should this matter ? >=20 >=20 > a) > # cat /etc/ctl.conf > debug 1 > portal-group pg0 { > discovery-auth-group no-authentication > listen 192.168.242.6 > listen 192.168.79.1 > } >=20 > target iqn.2018-01.ca.sentexcloud1:target0 { > auth-group no-authentication > portal-group pg0 >=20 > lun 1 { > backend block > path /dev/zvol/tank1/v2 > blocksize 4096 > device-id MULTI > serial 20180423 > } > } >=20 > b) >=20 > # cat /etc/ctl.conf > debug 1 > portal-group pg0 { > discovery-auth-group no-authentication > listen 192.168.79.2 > listen 192.168.242.11 > } >=20 > target iqn.2018-01.ca.sentexcloud1:target0 { > auth-group no-authentication > portal-group pg0 >=20 > lun 1 { > backend block > path /dev/zvol/zroot/v2 > blocksize 4096 > device-id MULTI > serial 20180423 > } > } >=20 >=20 >=20 >>=20 >> WBR, >> Mike >>=20 >> 23 =D0=B0=D0=BF=D1=80. 2018 =D0=B3., =D0=B2 20:11, Mike Tancsa > > =D0=BD=D0=B0=D0=BF=D0=B8=D1=81=D0=B0=D0=BB(=D0=B0= ): >>=20 >>>> On 4/23/2018 12:59 PM, Mikhail Zakharov wrote: >>>> Hello Mike, >>>>=20 >>>> Thank you for your interest to my paper. I appreciate it very much! >>>> Your error may be a consequence of the initial HA misconfiguration. >>>> What is in your /boot/loader.conf? Although the described config is >>>> quite simple, I can recheck the instruction in my paper in a couple >>>> of weeks only, unfortunately I=E2=80=99m on vacation right now. >>>=20 >>> Hi, >>> Config is pretty well copied from your article. Thanks for responding= , >>> and have a good holiday! >>>=20 >>> a) >>> kern.geom.label.disk_ident.enable=3D"0" >>> kern.geom.label.gptid.enable=3D"0" >>> vfs.zfs.min_auto_ashift=3D12 >>> zfs_load=3D"YES" >>> t5fw_cfg_load=3D"YES" >>> if_cxgbe_load=3D"YES" >>> vm.pmap.pti=3D0 >>> vfs.zfs.arc_max=3D22161185792 >>> ctl_load=3D"YES" >>> iscsi_load=3D"YES" >>> cfiscsi_load=3D"YES" >>> kern.cam.ctl.ha_id=3D1 >>> kern.cam.ctl.ha_mode=3D2 >>> kern.cam.ctl.ha_role=3D0 >>>=20 >>> b) >>> kern.geom.label.disk_ident.enable=3D"0" >>> kern.geom.label.gptid.enable=3D"0" >>> vfs.zfs.min_auto_ashift=3D12 >>> zfs_load=3D"YES" >>> console=3D"comconsole,vidconsole" >>> comconsole_speed=3D"115200" # Set the current serial console speed= >>> comconsole_port=3D"0x2f8" >>> ipmi_load=3D"YES" >>> ctl_load=3D"YES" >>> cfiscsi_load=3D"YES" >>> iscsi_load=3D"YES" >>> kern.cam.ctl.ha_id=3D2 >>> kern.cam.ctl.ha_mode=3D2 >>> kern.cam.ctl.ha_role=3D1 >>>=20 >>>=20 >>>=20 >>>=20 >>>=20 >>> a) >>> # cat /etc/ctl.conf >>> debug 1 >>> portal-group pg0 { >>> discovery-auth-group no-authentication >>> listen 192.168.242.6 >>> listen 192.168.79.1 >>> } >>>=20 >>> target iqn.2018-01.ca.sentexcloud1:target0 { >>> auth-group no-authentication >>> portal-group pg0 >>>=20 >>> lun 0 { >>> backend block >>> path /dev/zvol/tank1/v1 >>> blocksize 4096 >>> device-id MULTI >>> serial 20180423 >>> } >>> } >>>=20 >>> b) >>> }# cat /etc/ctl.conf >>> debug 1 >>> portal-group pg0 { >>> discovery-auth-group no-authentication >>> listen 192.168.79.2 >>> listen 192.168.242.11 >>> } >>>=20 >>> target iqn.2018-01.ca.sentexcloud1:target0 { >>> auth-group no-authentication >>> portal-group pg0 >>>=20 >>> lun 0 { >>> backend block >>> path /dev/zvol/zroot/v1 >>> blocksize 4096 >>> device-id FBSDMULTI >>> serial 20180423 >>> } >>> } >>>=20 >>> a) >>> # cat start.sh >>> sysctl -w kern.cam.ctl.ha_peer=3D"listen 192.168.79.1:7777" >>> sysctl -w kern.iscsi.fail_on_disconnection=3D1 >>> /etc/rc.d/ctld onestart >>>=20 >>> b) >>> # cat start.sh >>> sysctl -w kern.cam.ctl.ha_peer=3D"connect 192.168.79.1:7777" >>> sysctl -w kern.iscsi.fail_on_disconnection=3D1 >>> /etc/rc.d/ctld onestart >>>=20 >>>=20 >=20 >=20 > --=20 > ------------------- > Mike Tancsa, tel +1 519 651 3400 x203 > Sentex Communications, mike@sentex.net > Providing Internet services since 1994 www.sentex.net > Cambridge, Ontario Canada