On Mon, Jul 30, 2012 at 5:32 PM, Bruno MACADRE
<[email protected]> wrote:
> Le 30/07/2012 04:29, Andrew Beekhof a écrit :
>> On Mon, Jul 23, 2012 at 11:56 PM, Bruno MACADRE
>> <[email protected]> wrote:
>>> Hi,
>>>
>>>          I'm working on a 2-node active/passive iSCSI storage cluster.
>>>
>>>          (I follow the guide from linbit)
>>>
>>>          All works fine, except when active server goes offline, in this 
>>> case
>>> the iSCSI target (ocf:heartbeat:iSCSITarget) can't stop and flood my
>>> syslog with this line :
>>>
>>> "lrmd: [1405]: info: RA output: (p_iSCSItarget_vm-storage:stop:stderr)
>>> Device or resource busy."
>>>
>>> The fact that the resource is busy is normal 'cause this target is in use.
>>
>> Normal but very bad.
>> Either the iSCSI stop needs to be taught how to succeed in this case,
>> or (more likely) there needs to be some additional ordering
>> constraints that ensure services using the iSCSI target are stopped
>> first.
>>
> That's impossible 'cause stopping services using iSCSI implies stopping
> all clients logged on this target. So if I must disconnect all my
> servers before switching to the other node, this solution is not HA at
> all xD !

Well it depends on whether the clients are resources or not.
In your case it sounds like "not", so the first option made the most sense.

>
> I've just found a solution, using tgt instead of iet works fine 'cause
> tgtd doesn't stop shutdown when clients are connected.
>
>
>>>
>>> I'm on Ubuntu Server 12.04 x64 using iscsitarget (iet) implementation.
>>>
>>> below my crm configure :
>>> primitive p_LUN_vm-storage_lun ocf:heartbeat:iSCSILogicalUnit \
>>>          params implementation="iet"
>>>          target_iqn="iqn.2012-07.fr.domain:storage.vms" lun="1" 
>>> path="/dev/drbd0" \
>>>          op start interval="0" timeout="10s" \
>>>          op stop interval="0" timeout="10s" \
>>>          op monitor interval="10s" timeout="10s" depth="0"
>>>
>>> primitive p_drbd_vm-storage ocf:linbit:drbd \
>>>          params drbd_resource="vm-storage" \
>>>          op monitor interval="19" role="Master" \
>>>          op monitor interval="21" role="Slave"
>>>
>>> primitive p_iSCSItarget_vm-storage ocf:heartbeat:iSCSITarget \
>>>          params implementation="iet" iqn="iqn.2012-07.fr.domain:storage.vms"
>>> additional_parameters="DefaultTime2Retain=60 DefaultTime2Wait=5" \
>>>          op monitor interval="10s" \
>>>          meta target-role="Started"
>>>
>>> primitive p_vip_internal ocf:heartbeat:IPaddr2 \
>>>          params ip="192.168.1.100" cidr_netmask="24" 
>>> broadcast="192.168.1.255"
>>> nic="bond1" iflabel="intVIP" \
>>>          op monitor interval="7s"
>>>
>>> primitive p_vip_pedago ocf:heartbeat:IPaddr2 \
>>>          params ip="10.130.162.240" cidr_netmask="24" 
>>> broadcast="10.130.162.255"
>>> nic="bond2" iflabel="pedaVIP" \
>>>          op monitor interval="5s"
>>>
>>> group g_VIPs p_vip_internal p_vip_pedago
>>>
>>> group g_vm-storage p_iSCSItarget_vm-storage p_LUN_vm-storage_lun
>>>
>>> ms ms_drbd_vm-storage p_drbd_vm-storage \
>>>          meta master-max="1" master-node-max="1" clone-max="2" clone-
>>> node-max="1" notify="true"
>>>
>>> colocation c_VIPs_on_vm-storage inf: g_VIPs g_vm-storage
>>>
>>> colocation c_vm-storage_on_drbd0 inf: g_vm-storage ms_drbd_vm-
>>> storage:Master
>>>
>>> order o_drbd0_before_vm-storage inf: ms_drbd_vm-storage:promote
>>> g_vm-storage:start
>>>
>>> order o_vm-storage_before_VIPs inf: g_vm-storage g_VIPs:start
>>>
>>> property $id="cib-bootstrap-options" \
>>>          dc-version="1.1.6-9971ebba4494012a93c03b40a2c58ec0eb60f50c" \
>>>          cluster-infrastructure="openais" \
>>>          expected-quorum-votes="2" \
>>>          stonith-enabled="false" \
>>>          no-quorum-policy="ignore" \
>>>          default-resource-stickiness="200" \
>>>          last-lrm-refresh="1343050159"
>>>
>>>          If anybody have an idea to force iSCSITarget to stop even if the
>>> resource is busy, i will appreciate.
>>>
>>>          Regards,
>>>          Bruno
>>>
>>> --
>>>
>>> Bruno MACADRE
>>> -------------------------------------------------------------------
>>>    Ingénieur Systèmes et Réseau     | Systems and Network Engineer
>>>    Département Informatique         | Department of computer science
>>>    Responsable Réseau et Téléphonie | Telecom and Network Manager
>>>    Université de Rouen              | University of Rouen
>>> -------------------------------------------------------------------
>>> Coordonnées / Contact :
>>>          Université de Rouen
>>>          Faculté des Sciences et Techniques - Madrillet
>>>          Avenue de l'Université - BP12
>>>          76801 St Etienne du Rouvray CEDEX
>>>          FRANCE
>>>
>>>          Tél : +33 (0)2-32-95-51-86
>>>          Fax : +33 (0)2-32-95-51-87
>>> -------------------------------------------------------------------
>>>
>>> _______________________________________________
>>> Linux-HA mailing list
>>> [email protected]
>>> http://lists.linux-ha.org/mailman/listinfo/linux-ha
>>> See also: http://linux-ha.org/ReportingProblems
>> _______________________________________________
>> Linux-HA mailing list
>> [email protected]
>> http://lists.linux-ha.org/mailman/listinfo/linux-ha
>> See also: http://linux-ha.org/ReportingProblems
>>
>
>
> --
>
> Bruno MACADRE
> -------------------------------------------------------------------
>   Ingénieur Systèmes et Réseau     | Systems and Network Engineer
>   Département Informatique         | Department of computer science
>   Responsable Réseau et Téléphonie | Telecom and Network Manager
>   Université de Rouen              | University of Rouen
> -------------------------------------------------------------------
> Coordonnées / Contact :
>         Université de Rouen
>         Faculté des Sciences et Techniques - Madrillet
>         Avenue de l'Université - BP12
>         76801 St Etienne du Rouvray CEDEX
>         FRANCE
>
>         Tél : +33 (0)2-32-95-51-86
>         Fax : +33 (0)2-32-95-51-87
> -------------------------------------------------------------------
>
> _______________________________________________
> Linux-HA mailing list
> [email protected]
> http://lists.linux-ha.org/mailman/listinfo/linux-ha
> See also: http://linux-ha.org/ReportingProblems
_______________________________________________
Linux-HA mailing list
[email protected]
http://lists.linux-ha.org/mailman/listinfo/linux-ha
See also: http://linux-ha.org/ReportingProblems

Reply via email to