Hi, May be you Lon have an idea about this... Thanks in advance Brem 2010/1/7 brem belguebli <brem.belguebli@xxxxxxxxx>: > Hi All, > > Any idea about that ? > > Regards > > 2009/12/30 brem belguebli <brem.belguebli@xxxxxxxxx>: >> Hi, >> >> It looks like the quorumd max_error_cycles parameter it not taken into account. >> >> Here's the test I'm doing: >> >> A 3 nodes cluster (RHEL 5.4) with a iscsi qdisk lun from a RHEL 5.4 >> target server. >> >> All 3 cluster nodes have the following cqdisk configuration: >> >> <quorumd device="/dev/iscsi/storage.quorum" interval="1" >> log_facility="local5" log_level="7" tko="10" votes="1" >> max_error_cycles="10"> >> >> When I block access from the 3 nodes to the target server (iptables >> rule that prevents all ip flows from the 3 nodes to the target >> server), I see the Quorum disk go offline but qdisk never gets stopped >> and keeps on retrying the qdisk device despite the fact that I >> instructed it to abort after 10 cycles (max_error_cycles=10). >> >> Am I misunderstanding the max_error_cycles definition in the qdisk man page ? >> >> Regards >> >> PS: As consequence of not being killed after this max-error_cycles, >> qdisk keeps on growing (memory usage virtual size) and if the >> situation lasts too long OOM killer gets involved..... >> > -- Linux-cluster mailing list Linux-cluster@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/linux-cluster
