[Pacemaker] iscsi migration to slow (disk errors) what to do ...

Florian Haas florian.haas at linbit.com
Tue Jun 14 13:48:05 UTC 2011


On 2011-06-14 15:41, Jelle de Jong wrote:
> On 14-06-11 15:22, Florian Haas wrote:
>> On 2011-06-10 17:28, Jelle de Jong wrote:
>>> The problem is most of my kvm guest file-systems get corrupted when
>>> migrating my iscsi target on heavy disk load on the kvm guests.
>> Have you tried setting DefaultTime2Retain like I suggested on Feb 24?
> 
> Yes I did I use: DefaultTime2Retain=60 DefaultTime2Wait=5
> 
> Can't find much info about the options in combination with tgt.
> 
> primitive iscsi0_target ocf:heartbeat:iSCSITarget \
> 	params implementation="tgt"
> iqn="iqn.2011-04.nl.powercraft:storage.iscsi0" tid="1"
> allowed_initiators="192.168.24.1 192.168.24.17 192.168.24.18"
> additional_parameters="DefaultTime2Retain=60 DefaultTime2Wait=5" \
> 	op stop interval="0" timeout="30s" \
> 	op monitor interval="10s"
> 
> # root at godfrey:~# crm configure show
> http://paste.debian.net/119798/

DefaultTime2Retain is a parameter that is being negotiated between the
target and the initiator, and the _minimum_ of proposed
DefaultTime2Retain values wins. The default DefaultTime2Retain for
open-iscsi is 0, thus if the initiator proposes 0 and the target 60, 0 wins.

You'll have to set this on the initiator and the target.

Florian

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 262 bytes
Desc: OpenPGP digital signature
URL: <https://lists.clusterlabs.org/pipermail/pacemaker/attachments/20110614/f3ee2f37/attachment-0004.sig>


More information about the Pacemaker mailing list