Re: [Pacemaker] iscsi target mounting readonly on client
Hi Felix, Sorry for the late answer. I gave a try to your suggestions, it worked immediately with block io and the increase block timeout. I stick with iet for now as my supervisor want to stick to standard pacakges. You really save my day. Best reagards, Joseph-André GUARAGNA 2013/4/14 Joseph-Andre Guaragna joseph-an...@rdmo.com Thanks for the informations. I give it a try monday and gave you a feedback. 2013/4/12 Felix Zachlod fz.li...@sis-gmbh.info: Hello Joseph! -Ursprüngliche Nachricht-, Von: Joseph-Andre Guaragna [mailto:joseph-an...@rdmo.com] Gesendet: Freitag, 12. April 2013 17:19 An: pacemaker@oss.clusterlabs.org Betreff: [Pacemaker] iscsi target mounting readonly on client You have to make two things absolutely shure. 1. Data that has been acknowledged by you iscsi Target to your initiator has hit the device and not only the page cache! If you run your target in fileio mode you have to use write trough- cause with write back you or your cluster manager can't ever tell if the writes have completed before switching the DRBD states. That will only perform good if you have a decent raid card with BBWC! BUT YOU MUST RUN WRITE TRHOUGH or blockio (which will be write trough too) running write back in such a constellation IS NOT SAFE you might risk SERIOUS DATA CORRUPTION when switching targets. 2. On your initiator side try to rise the /sys/block/sd*/device/timeout value. That is the time the block device will wait for a command to complete before handing an i/o error tot he upper layer- which will most probably lead to your filesystem remounting r/o. 3. This is just a side note: do not use iet. We were running a production target wit iet for about 2 year which caused horrible problems to us. Consider scst or lio (I personally do not have any experiences with lio but scst is running in our production environment for years now without any problems) regards Felix ___ Pacemaker mailing list: Pacemaker@oss.clusterlabs.org http://oss.clusterlabs.org/mailman/listinfo/pacemaker Project Home: http://www.clusterlabs.org Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf Bugs: http://bugs.clusterlabs.org ___ Pacemaker mailing list: Pacemaker@oss.clusterlabs.org http://oss.clusterlabs.org/mailman/listinfo/pacemaker Project Home: http://www.clusterlabs.org Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf Bugs: http://bugs.clusterlabs.org
Re: [Pacemaker] iscsi target mounting readonly on client
Thanks for the informations. I give it a try monday and gave you a feedback. 2013/4/12 Felix Zachlod fz.li...@sis-gmbh.info: Hello Joseph! -Ursprüngliche Nachricht-, Von: Joseph-Andre Guaragna [mailto:joseph-an...@rdmo.com] Gesendet: Freitag, 12. April 2013 17:19 An: pacemaker@oss.clusterlabs.org Betreff: [Pacemaker] iscsi target mounting readonly on client You have to make two things absolutely shure. 1. Data that has been acknowledged by you iscsi Target to your initiator has hit the device and not only the page cache! If you run your target in fileio mode you have to use write trough- cause with write back you or your cluster manager can't ever tell if the writes have completed before switching the DRBD states. That will only perform good if you have a decent raid card with BBWC! BUT YOU MUST RUN WRITE TRHOUGH or blockio (which will be write trough too) running write back in such a constellation IS NOT SAFE you might risk SERIOUS DATA CORRUPTION when switching targets. 2. On your initiator side try to rise the /sys/block/sd*/device/timeout value. That is the time the block device will wait for a command to complete before handing an i/o error tot he upper layer- which will most probably lead to your filesystem remounting r/o. 3. This is just a side note: do not use iet. We were running a production target wit iet for about 2 year which caused horrible problems to us. Consider scst or lio (I personally do not have any experiences with lio but scst is running in our production environment for years now without any problems) regards Felix ___ Pacemaker mailing list: Pacemaker@oss.clusterlabs.org http://oss.clusterlabs.org/mailman/listinfo/pacemaker Project Home: http://www.clusterlabs.org Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf Bugs: http://bugs.clusterlabs.org ___ Pacemaker mailing list: Pacemaker@oss.clusterlabs.org http://oss.clusterlabs.org/mailman/listinfo/pacemaker Project Home: http://www.clusterlabs.org Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf Bugs: http://bugs.clusterlabs.org
[Pacemaker] iscsi target mounting readonly on client
Hi, I just finish to install a cluster based on pacemaker for High available ISCSI target (active/passive), everythinf work like a charm swictching between nodes, fencing rebooting and disconnecting node. the cluster runs the following properties ipaddr2, iscsi target, iscsi lun and drbd. But here comes the troubles as soon as I try too bench the iscsi and move service accross nodes, the iscsi target get remounted as read-only. I try to tweak on the client /etc/iscsi/iscsid.conf with node.conn[0].timeo.logout_timeout = 10 node.conn[0].timeo.noop_out_interval = 30 node.session.timeo.replacement_timeout = 480 I also modigy the ISCSI target provider /etc/iet/ietd.conf DefaultTime2Wait5 DefaultTime2Retain 60 On the client I get the followinfg error messages: sd 14:0:0:0: [sdk] Attached SCSI disk [ 4146.898335] EXT4-fs (sdk1): recovery complete [ 4146.900299] EXT4-fs (sdk1): mounted filesystem with ordered data mode. Opts: (null) [ 4173.975058] EXT4-fs error (device sdj1): ext4_put_super:819: Couldn't clean up the journal [ 4173.975065] EXT4-fs (sdj1): Remounting filesystem read-only [ 4182.347630] EXT4-fs error (device sdi1): ext4_put_super:819: Couldn't clean up the journal I any of you have a way to avoird the disconnection and the read-only remounting I would be glad. Joseph ___ Pacemaker mailing list: Pacemaker@oss.clusterlabs.org http://oss.clusterlabs.org/mailman/listinfo/pacemaker Project Home: http://www.clusterlabs.org Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf Bugs: http://bugs.clusterlabs.org
