We have an OCFS2 cluster, but it is on ECKD dasd, not SAN.

This is what we have for timeouts

==Dumping header on disk /dev/dasdf1
Header version     : 2.1
UUID               : 2524f6ad-0469-4a3d-85b6-6ae6681efa7d
Number of slots    : 255
Sector size        : 4096
Timeout (watchdog) : 30
Timeout (allocate) : 2
Timeout (loop)     : 1
Timeout (msgwait)  : 60


-----Original Message-----
From: Linux on 390 Port [mailto:[email protected]] On Behalf Of Victor 
Echavarry Diaz
Sent: Friday, December 18, 2015 11:57 AM
To: [email protected]
Subject: [LINUX-390] Z/VM and Clusteirng

Our Unix team define a z/Linux cluster with db2 and other with oracle. We cap 
those servers to 25% relative share. The oracle server works fine, but the db2 
reboot losing the SAN connectivity. The Unix guy argue that the problem is the 
cap. This is the log files from the db2 server.

Dec 18 15:00:03 tepst1 sbd: [5531]: WARN: Servant for /dev/mapper/clustersbd 
outdated (age: 4)
Dec 18 15:00:03 tepst1 sbd: [5531]: WARN: Majority of devices lost - surviving 
on pacemaker
Dec 18 15:00:14 tepst1 sbd: [5531]: WARN: Servant for /dev/mapper/clustersbd 
outdated (age: 7)
Dec 18 15:00:14 tepst1 sbd: [5531]: WARN: Pacemaker state outdated (age: 5)
Dec 18 15:00:14 tepst1 sbd: [5531]: WARN: Majority of devices lost - surviving 
on pacemaker
Dec 18 15:00:19 tepst1 sbd: [5533]: WARN: Latency: 12 exceeded threshold 3 on 
disk /dev/mapper/clustersbd
Dec 18 15:00:19 tepst1 sbd: [5531]: WARN: Pacemaker state outdated (age: 4)
Dec 18 15:00:45 tepst1 sbd: [5531]: WARN: Servant for /dev/mapper/clustersbd 
outdated (age: 4)
Dec 18 15:00:45 tepst1 sbd: [5531]: WARN: Majority of devices lost - surviving 
on pacemaker
Dec 18 15:00:46 tepst1 sbd: [5533]: WARN: Latency: 5 exceeded threshold 3 on 
disk /dev/mapper/clustersbd
Dec 18 15:01:14 tepst1 sbd: [5531]: WARN: Servant for /dev/mapper/clustersbd 
outdated (age: 4)
Dec 18 15:01:14 tepst1 sbd: [5531]: WARN: Majority of devices lost - surviving 
on pacemaker
Dec 18 15:01:14 tepst1 sbd: [5533]: WARN: Latency: 5 exceeded threshold 3 on 
disk /dev/mapper/clustersbd
Dec 18 15:01:36 tepst1 sbd: [5533]: WARN: Latency: 4 exceeded threshold 3 on 
disk /dev/mapper/clustersbd
Dec 18 15:01:36 tepst1 sbd: [5531]: WARN: Pacemaker state outdated (age: 4)
Dec 18 15:01:47 tepst1 sbd: [5531]: WARN: Servant for /dev/mapper/clustersbd 
outdated (age: 6)
Dec 18 15:01:47 tepst1 sbd: [5531]: WARN: Majority of devices lost - surviving 
on pacemaker
Dec 18 15:01:47 tepst1 sbd: [5533]: WARN: Latency: 6 exceeded threshold 3 on 
disk /dev/mapper/clustersbd
Dec 18 15:01:53 tepst1 sbd: [5531]: WARN: Servant for /dev/mapper/clustersbd 
outdated (age: 4)
Dec 18 15:01:53 tepst1 sbd: [5531]: WARN: Majority of devices lost - surviving 
on pacemaker
Dec 18 15:01:53 tepst1 sbd: [5533]: WARN: Latency: 5 exceeded threshold 3 on 
disk /dev/mapper/clustersbd
Dec 18 15:02:07 tepst1 sbd: [5533]: WARN: Latency: 4 exceeded threshold 3 on 
disk /dev/mapper/clustersbd
Dec 18 15:02:16 tepst1 sbd: [5531]: WARN: Servant for /dev/mapper/clustersbd 
outdated (age: 4)
Dec 18 15:02:16 tepst1 sbd: [5531]: WARN: Majority of devices lost - surviving 
on pacemaker
Dec 18 15:02:25 tepst1 sbd: [5531]: WARN: Pacemaker state outdated (age: 4)
Dec 18 15:02:29 tepst1 sbd: [5531]: WARN: Servant for /dev/mapper/clustersbd 
outdated (age: 4)
Dec 18 15:02:29 tepst1 sbd: [5531]: WARN: Majority of devices lost - surviving 
on pacemaker


IMPORTANT:  the timeout of the SBD disk is determine with:

sbd -d /dev/mapper/clustersbd dump
==Dumping header on disk /dev/mapper/clustersbd
Header version     : 2.1
UUID               : 6272a75a-26cf-4f69-95c9-2d1db151a358
Number of slots    : 255
Sector size        : 512
Timeout (watchdog) : 15
Timeout (allocate) : 2
Timeout (loop)     : 1
Timeout (msgwait)  : 30

We have z/vm  6.3 under SSI. z/Linux version SLES 11 SP3.

Regards.

Victor Echavarry
System Programmer, EVERTEC LLC



WARNING: This email and any files transmitted with it are confidential and
intended solely for the use of the individual or entity to whom they are
addressed. If you have received this email in error please delete it 
immediately.
Please note that any views or opinions presented in this email are solely those
of the author and do not necessarily represent those of EVERTEC, Inc. or its
affiliates. Finally, the integrity and security of this message cannot be
guaranteed on the Internet, and as such EVERTEC, Inc. and its affiliates accept
no liability for any damage caused by any virus transmitted by this email.

----------------------------------------------------------------------
For LINUX-390 subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390
----------------------------------------------------------------------
For more information on Linux on System z, visit
http://wiki.linuxvm.org/

----------------------------------------------------------------------
For LINUX-390 subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390
----------------------------------------------------------------------
For more information on Linux on System z, visit
http://wiki.linuxvm.org/

Reply via email to