Date: Tue, 24 Apr 2018 07:52:07 +0300 From: Mikhail Zakharov <zmey20000@yahoo.com> To: Mike Tancsa <mike@sentex.net> Cc: "freebsd-fs@freebsd.org" <freebsd-fs@freebsd.org> Subject: Re: ctl_isc_lun_sync: Received conflicting HA LUN Message-ID: <AE0954E7-CE37-49F8-8EA2-3DEDA578C6E8@yahoo.com> In-Reply-To: <1d4a2171-d083-9e37-954c-cf58ed2c2982@sentex.net> References: <4cb4aa83-bd49-0c20-4e41-c11c682b0570@sentex.net> <F908B78A-DD9B-4204-BA1E-24CE38059ACF@yahoo.com> <1e1e7cd5-0797-c168-fbce-a36edc6a432e@sentex.net> <14CC6AF1-C1AB-48D2-925D-A46989AD7B3C@yahoo.com> <1d4a2171-d083-9e37-954c-cf58ed2c2982@sentex.net>
next in thread | previous in thread | raw e-mail | index | archive | help
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 <mike@sente=
x.net> =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 <mike@sent=
ex.net
>> <mailto:mike@sentex.net>> =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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?AE0954E7-CE37-49F8-8EA2-3DEDA578C6E8>