From vectorz3 at gmail.com  Fri Feb  1 01:20:29 2008
From: vectorz3 at gmail.com (Vectorz Sigma)
Date: Thu, 31 Jan 2008 17:20:29 -0800
Subject: [Linux-cluster] How to set node timeout when using gulm?
Message-ID: <940a2e6d0801311720m695a992bq99ec592a9644bc51@mail.gmail.com>

I'm aware of how to do this for CMAN but I'm running gulm.  I can't find
information anywhere on how to do this.

Anyone know?
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://listman.redhat.com/archives/linux-cluster/attachments/20080131/23c7c2a5/attachment.htm>

From isplist at logicore.net  Fri Feb  1 01:29:49 2008
From: isplist at logicore.net (isplist at logicore.net)
Date: Thu, 31 Jan 2008 19:29:49 -0600
Subject: [Linux-cluster] DLM Problem
In-Reply-To: <47A2529C.1040404@io-consulting.net>
Message-ID: <2008131192949.627124@leena>

> i think that's the file he sent you ;) (starting with "# /etc/udev..")

<cough><embarrassed>

>thinking about it, i think i should add to say that you need to edit
>that file for your needs (adjust the scsi id). i didn't use udev yet,
>the only place where i scsi_id etc together with dm-multipath.

I've not looked into this yet so don't know what to edit or add. 

On one node, the drive is /dev/sda, but on some nodes, it'll be sdx because 
some of the machines already have SCSI drives in them. Not hard to see, just 
have to keep it in mind since I'm assuming each machine needs this file.

I see a catch all ( sd*[!0-9] ) but don't know where I need to put say 
/dev/sda.

# /etc/udev/rules.d/69-xraid.rules
# 2008-01-18
# Brian Kroth
# Setup devices nodes for the two storage arrays based upon their unique
# scsi_id

ACTION!="add", GOTO="xraid_end"

KERNEL=="sd*[!0-9]", ENV{ID_SERIAL}=="3600039300001e6db01000000d52b0606",
SYMLINK+="xraid-c1-a1"
KERNEL=="sd*[!0-9]", ENV{ID_SERIAL}=="3600039300001e6db020000006a95fef7",
SYMLINK+="xraid-c1-a2"

KERNEL=="sd*[0-9]", ENV{ID_SERIAL}=="3600039300001e6db01000000d52b0606",
SYMLINK+="xraid-c1-a1-p%n"
KERNEL=="sd*[0-9]", ENV{ID_SERIAL}=="3600039300001e6db020000006a95fef7",
SYMLINK+="xraid-c1-a2-p%n"

LABEL="xraid_end"

>johannes





From td3201 at gmail.com  Fri Feb  1 05:10:15 2008
From: td3201 at gmail.com (Terry)
Date: Thu, 31 Jan 2008 23:10:15 -0600
Subject: [Linux-cluster] postgres cluster with RHEL5
Message-ID: <8ee061010801312110q25519afck1ba7776948cb6a44@mail.gmail.com>

Good evening,

I am trying to get an active-passive postgres cluster going.  I have a
shared storage with NFS.  I just can't get it going.  I am using luci
to configure this which, from what I have been reading, is somewhat
buggy in the postgres-8 arena.  My first question is what components
of postgres should live on the shared storage?

Here are the relevant parts of my config:

                <resources>
                        <ip address="192.168.100.207" monitor_link="1"/>
                        <fs device="/dev/sdc1" force_fsck="0"
force_unmount="1" fsid="42585" fstype="ext3" mountpoint="/db00"
name="db00" self_fence="1"/>
                        <postgres-8
config_file="/etc/postgresql/postgresql.conf" name="dssystem2"
postmaster_user="postgres" shutdown_wait="0"/>
                </resources>
           <service autostart="1" domain="failover00" exclusive="0"
name="database" recovery="relocate">
                        <postgres-8 ref="dssystem2">
                                <fs ref="db00"/>
                                <ip ref="192.168.100.207"/>
                        </postgres-8>
                </service>



From qqlka at nask.pl  Fri Feb  1 07:34:18 2008
From: qqlka at nask.pl (=?iso-8859-2?Q?Agnieszka_Kuka=B3owicz?=)
Date: Fri, 1 Feb 2008 08:34:18 +0100
Subject: [Linux-cluster] Power fencing, Xen, Virtual Services, RHCS
Message-ID: <047001c864a4$dbb58660$0777b5c2@gda07ak>

Hi,

I have problem with 2 nodes cluster runnig xen virtual machines.
The configuration is very simple. Node 1 - d1 runs vm_service1 and node
2 - d2 runs vm_service2 and have configured APC Master Switch as fence
devices.

Everything works well: starting, stopping and migrating virtual services
between nodes. But the problem occurs when I try to test crash one of
the nodes by, for example, shutting down node d2. In this case node d1
discovers node d2 failed and fences it through APC device. After node d2
is up it joins cluster and try to relocate vm_service2. But during that
I get strange logs on node d2:

Jan 31 21:18:11 d2 openais[5485]: [TOTEM] entering OPERATIONAL state.
Jan 31 21:18:11 d2 openais[5485]: [CLM  ] got nodejoin message
10.0.200.101
Jan 31 21:18:11 d2 openais[5485]: [CLM  ] got nodejoin message
10.0.200.102
Jan 31 21:18:11 d2 openais[5485]: [CPG  ] got joinlist message from node
2
Jan 31 21:18:45 d2 openais[5485]: [TOTEM] Retransmit List: 31
Jan 31 21:18:46 d2 openais[5485]: [TOTEM] Retransmit List: 31
....
Jan 31 21:19:10 d2 openais[5485]: [TOTEM] FAILED TO RECEIVE
Jan 31 21:19:11 d2 openais[5485]: [TOTEM] entering GATHER state from 6.
Jan 31 21:19:11 d2 openais[5485]: [TOTEM] Retransmit List: 31
Jan 31 21:19:11 d2 openais[5485]: [TOTEM] FAILED TO RECEIVE
Jan 31 21:19:12 d2 openais[5485]: [TOTEM] entering GATHER state from 6.
Jan 31 21:19:15 d2 openais[5485]: [TOTEM] Retransmit List: 31
Jan 31 21:19:15 d2 openais[5485]: [TOTEM] FAILED TO RECEIVE
Jan 31 21:19:16 d2 openais[5485]: [TOTEM] entering GATHER state from 6.
Jan 31 21:19:16 d2 openais[5485]: [TOTEM] Retransmit List: 31
Jan 31 21:19:16 d2 openais[5485]: [TOTEM] FAILED TO RECEIVE
Jan 31 21:19:16 d2 openais[5485]: [TOTEM] entering GATHER state from 6.
Jan 31 21:19:17 d2 openais[5485]: [TOTEM] Retransmit List: 31
Jan 31 21:19:17 d2 openais[5485]: [TOTEM] FAILED TO RECEIVE
Jan 31 21:19:18 d2 openais[5485]: [TOTEM] entering GATHER state from 6.
Jan 31 21:19:18 d2 openais[5485]: [TOTEM] Retransmit List: 31
Jan 31 21:19:18 d2 openais[5485]: [TOTEM] FAILED TO RECEIVE
Jan 31 21:19:19 d2 openais[5485]: [TOTEM] entering GATHER state from 6.
Jan 31 21:19:19 d2 openais[5485]: [TOTEM] Retransmit List: 31
Jan 31 21:19:19 d2 openais[5485]: [TOTEM] FAILED TO RECEIVE
Jan 31 21:19:20 d2 openais[5485]: [TOTEM] entering GATHER state from 6.
Jan 31 21:19:20 d2 openais[5485]: [TOTEM] Retransmit List: 31
Jan 31 21:19:20 d2 openais[5485]: [TOTEM] FAILED TO RECEIVE
Jan 31 21:19:20 d2 openais[5485]: [TOTEM] entering GATHER state from 6.
Jan 31 21:19:21 d2 openais[5485]: [TOTEM] Retransmit List: 31
Jan 31 21:19:21 d2 openais[5485]: [TOTEM] FAILED TO RECEIVE
Jan 31 21:19:21 d2 openais[5485]: [TOTEM] entering GATHER state from 6.
Jan 31 21:19:21 d2 openais[5485]: [TOTEM] Retransmit List: 31
Jan 31 21:19:21 d2 openais[5485]: [TOTEM] FAILED TO RECEIVE
Jan 31 21:19:21 d2 openais[5485]: [TOTEM] entering GATHER state from 6.
Jan 31 21:19:23 d2 openais[5485]: [TOTEM] Retransmit List: 31
Jan 31 21:19:23 d2 openais[5485]: [TOTEM] FAILED TO RECEIVE
Jan 31 21:19:23 d2 openais[5485]: [TOTEM] entering GATHER state from 6.
Jan 31 21:19:24 d2 openais[5485]: [TOTEM] Retransmit List: 31
Jan 31 21:19:24 d2 openais[5485]: [TOTEM] FAILED TO RECEIVE
Jan 31 21:19:24 d2 openais[5485]: [TOTEM] entering GATHER state from 6.
Jan 31 21:19:26 d2 openais[5485]: [TOTEM] Retransmit List: 31
Jan 31 21:19:26 d2 openais[5485]: [TOTEM] FAILED TO RECEIVE
Jan 31 21:19:26 d2 openais[5485]: [TOTEM] entering GATHER state from 6.
Jan 31 21:19:27 d2 openais[5485]: [TOTEM] Retransmit List: 31
Jan 31 21:19:27 d2 openais[5485]: [TOTEM] FAILED TO RECEIVE
Jan 31 21:19:27 d2 openais[5485]: [TOTEM] entering GATHER state from 6.
Jan 31 21:19:29 d2 openais[5485]: [TOTEM] Retransmit List: 31
Jan 31 21:19:29 d2 openais[5485]: [TOTEM] FAILED TO RECEIVE
Jan 31 21:19:29 d2 openais[5485]: [TOTEM] entering GATHER state from 6.
Jan 31 21:19:30 d2 openais[5485]: [TOTEM] Retransmit List: 31
Jan 31 21:19:30 d2 openais[5485]: [TOTEM] FAILED TO RECEIVE
Jan 31 21:19:30 d2 openais[5485]: [TOTEM] entering GATHER state from 6.
Jan 31 21:19:32 d2 openais[5485]: [TOTEM] Retransmit List: 31
Jan 31 21:19:32 d2 openais[5485]: [TOTEM] FAILED TO RECEIVE
Jan 31 21:19:32 d2 openais[5485]: [TOTEM] entering GATHER state from 6.
Jan 31 21:19:33 d2 openais[5485]: [TOTEM] Retransmit List: 31
Jan 31 21:19:33 d2 openais[5485]: [TOTEM] FAILED TO RECEIVE
Jan 31 21:19:33 d2 openais[5485]: [TOTEM] entering GATHER state from 6.
Jan 31 21:19:35 d2 openais[5485]: [TOTEM] Retransmit List: 31
Jan 31 21:19:35 d2 openais[5485]: [TOTEM] FAILED TO RECEIVE
Jan 31 21:19:35 d2 openais[5485]: [TOTEM] entering GATHER state from 6.
Jan 31 21:19:36 d2 openais[5485]: [TOTEM] Retransmit List: 31
Jan 31 21:19:36 d2 openais[5485]: [TOTEM] FAILED TO RECEIVE
Jan 31 21:19:36 d2 openais[5485]: [TOTEM] entering GATHER state from 6.
Jan 31 21:19:38 d2 openais[5485]: [TOTEM] Retransmit List: 31
Jan 31 21:19:38 d2 openais[5485]: [TOTEM] FAILED TO RECEIVE
Jan 31 21:19:38 d2 openais[5485]: [TOTEM] entering GATHER state from 6.
Jan 31 21:19:43 d2 openais[5485]: [TOTEM] entering GATHER state from 0.
Jan 31 21:20:18 d2 openais[5485]: [TOTEM] The consensus timeout expired.
Jan 31 21:20:18 d2 openais[5485]: [TOTEM] entering GATHER state from 3.
Jan 31 21:20:52 d2 openais[5485]: [TOTEM] The consensus timeout expired.
Jan 31 21:20:52 d2 openais[5485]: [TOTEM] entering GATHER state from 3.

And on node d2:
Jan 31 21:18:08 d1 openais[5467]: [CLM  ] CLM CONFIGURATION CHANGE
Jan 31 21:18:08 d1 openais[5467]: [CLM  ] New Configuration:
Jan 31 21:18:08 d1 openais[5467]: [CLM  ]       r(0) ip(10.0.200.101)
Jan 31 21:18:08 d1 openais[5467]: [CLM  ] Members Left:
Jan 31 21:18:08 d1 openais[5467]: [CLM  ] Members Joined:
Jan 31 21:18:08 d1 openais[5467]: [CLM  ] CLM CONFIGURATION CHANGE
Jan 31 21:18:08 d1 openais[5467]: [CLM  ] New Configuration:
Jan 31 21:18:09 d1 openais[5467]: [CLM  ]       r(0) ip(10.0.200.101)
Jan 31 21:18:09 d1 openais[5467]: [CLM  ]       r(0) ip(10.0.200.102)
Jan 31 21:18:09 d1 openais[5467]: [CLM  ] Members Left:
Jan 31 21:18:09 d1 openais[5467]: [CLM  ] Members Joined:
Jan 31 21:18:09 d1 openais[5467]: [CLM  ]       r(0) ip(10.0.200.102)
Jan 31 21:18:09 d1 openais[5467]: [SYNC ] This node is within the
primary component and will provide service.
Jan 31 21:18:09 d1 openais[5467]: [TOTEM] entering OPERATIONAL state.
Jan 31 21:18:09 d1 openais[5467]: [CLM  ] got nodejoin message
10.0.200.101
Jan 31 21:18:10 d1 openais[5467]: [CLM  ] got nodejoin message
10.0.200.102
Jan 31 21:18:10 d1 openais[5467]: [CPG  ] got joinlist message from node
2
Jan 31 21:18:15 d1 kernel: dlm: connecting to 1
Jan 31 21:18:15 d1 kernel: dlm: got connection from 1
Jan 31 21:19:47 d1 openais[5467]: [TOTEM] The token was lost in the
OPERATIONAL state.
Jan 31 21:19:47 d1 openais[5467]: [TOTEM] Receive multicast socket recv
buffer size (288000 bytes).
Jan 31 21:19:47 d1 openais[5467]: [TOTEM] Transmit multicast socket send
buffer size (288000 bytes).
Jan 31 21:19:47 d1 openais[5467]: [TOTEM] entering GATHER state from 2.
Jan 31 21:19:52 d1 openais[5467]: [TOTEM] entering GATHER state from 0.
Jan 31 21:19:52 d1 openais[5467]: [TOTEM] Creating commit token because
I am the rep.
Jan 31 21:19:52 d1 openais[5467]: [TOTEM] Saving state aru 30 high seq
received 31
Jan 31 21:19:52 d1 openais[5467]: [TOTEM] Storing new sequence id for
ring 4bc
Jan 31 21:19:52 d1 openais[5467]: [TOTEM] entering COMMIT state.
Jan 31 21:19:52 d1 openais[5467]: [TOTEM] entering RECOVERY state.
Jan 31 21:19:52 d1 openais[5467]: [TOTEM] position [0] member
10.0.200.101:
Jan 31 21:19:52 d1 kernel: dlm: closing connection to node 1
Jan 31 21:19:52 d1 openais[5467]: [TOTEM] previous ring seq 1208 rep
10.0.200.101
Jan 31 21:19:52 d1 openais[5467]: [TOTEM] aru 30 high delivered 30
received flag 0
Jan 31 21:19:52 d1 openais[5467]: [TOTEM] copying all old ring messages
from 31-31.
Jan 31 21:19:52 d1 openais[5467]: [TOTEM] Originated 0 messages in
RECOVERY.
Jan 31 21:19:52 d1 openais[5467]: [TOTEM] Originated for recovery:
Jan 31 21:19:52 d1 fenced[5484]: d2.local.polska.pl not a cluster member
after 0 sec post_fail_delay
Jan 31 21:19:52 d1 openais[5467]: [TOTEM] Not Originated for recovery:
31
Jan 31 21:19:52 d1 fenced[5484]: fencing node "d2"
Jan 31 21:19:52 d1 openais[5467]: [TOTEM] Sending initial ORF token
Jan 31 21:19:53 d1 fenced[5484]: fence "d2" success 

In consequence, I cannot start cluster because node d1 constantly fences
node d2. 

Making some research I find out that the problem might be in xen
networking. During staring virtual service the xen bridges are
reconfigurating (am I wrong?) and therefore there is a problem with
communication between nodes. 
But I don't know what to do with xen configuration the cluster starts
working.

Cheers
Agnieszka Kukalowicz





From mpartio at gmail.com  Fri Feb  1 07:37:23 2008
From: mpartio at gmail.com (Mikko Partio)
Date: Fri, 1 Feb 2008 09:37:23 +0200
Subject: [Linux-cluster] postgres cluster with RHEL5
In-Reply-To: <8ee061010801312110q25519afck1ba7776948cb6a44@mail.gmail.com>
References: <8ee061010801312110q25519afck1ba7776948cb6a44@mail.gmail.com>
Message-ID: <2ca799770801312337q3ce5b981l8d09e53720617b5@mail.gmail.com>

> I am trying to get an active-passive postgres cluster going.  I have a
> shared storage with NFS.  I just can't get it going.  I am using luci
> to configure this which, from what I have been reading, is somewhat
> buggy in the postgres-8 arena.  My first question is what components
> of postgres should live on the shared storage?
>


A have also implemented an active-passive cluster for postgresql, here's
what I suggest:

-Do not use nfs with postgresql. It can lead to unpredictable results when a
failure with the nfs mount occurs. For more info check the postgresql
mailing list archives.
-I don't know how the rgmanager's built-in postgresql support works, but at
least using the "script" resource works just fine.
-I am using gfs with postgresql and all but the database binaries are on the
shared storage.
-Be sure to test, test and test that your fencing is working!

Regards

Mikko
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://listman.redhat.com/archives/linux-cluster/attachments/20080201/b58ed322/attachment.htm>

From cosimo at streppone.it  Fri Feb  1 08:23:31 2008
From: cosimo at streppone.it (Cosimo Streppone)
Date: Fri, 01 Feb 2008 09:23:31 +0100
Subject: [Linux-cluster] postgres cluster with RHEL5
In-Reply-To: <8ee061010801312110q25519afck1ba7776948cb6a44@mail.gmail.com>
References: <8ee061010801312110q25519afck1ba7776948cb6a44@mail.gmail.com>
Message-ID: <47A2D703.9050008@streppone.it>

Terry wrote:
> 
> I am trying to get an active-passive postgres cluster going.  I have a
> shared storage with NFS.  I just can't get it going.  I am using luci
> to configure this which, from what I have been reading, is somewhat
> buggy in the postgres-8 arena.  My first question is what components
> of postgres should live on the shared storage?

I configured pg on RHEL4 cluster, and I put only the
database files and logs on the shared storage.
In my case was a 4Gb FC-attached SAN.
The pg binaries and config files were on both active and
passive nodes.

Probably if you put also your binaries on shared storage,
you should be sure that pg won't start if something bad
happens :-)

I also wouldn't recommend NFS, but I never
tried that myself with pg. Only had bad experiences
with NFS shares hanging up processes for long.

> <postgres-8
> config_file="/etc/postgresql/postgresql.conf" name="dssystem2"
> postmaster_user="postgres" shutdown_wait="0"/>

Also, in RHCS4 there was no "<postgres-8>" resource, but
I did that with a script resource, which is simple but
kind-of worked (after fixing the infamous init scripts bug :)

-- 
Cosimo



From devrim at gunduz.org  Fri Feb  1 08:29:03 2008
From: devrim at gunduz.org (=?iso-8859-9?Q?Devrim_G=DCND=DCZ?=)
Date: Fri, 1 Feb 2008 00:29:03 -0800 (PST)
Subject: [Linux-cluster] postgres cluster with RHEL5
In-Reply-To: <47A2D703.9050008@streppone.it>
References: <8ee061010801312110q25519afck1ba7776948cb6a44@mail.gmail.com>
	<47A2D703.9050008@streppone.it>
Message-ID: <Pine.LNX.4.64.0802010028130.21620@community1.commandprompt.com>


Hi,

On Fri, 1 Feb 2008, Cosimo Streppone wrote:

> I also wouldn't recommend NFS, but I never
> tried that myself with pg. Only had bad experiences
> with NFS shares hanging up processes for long.

See PostgreSQL archives -- NFS is considered *very* harmful for many apps, 
and also to PostgreSQL.

Never ever use NFS:)

--
Devrim G?ND?Z
RHCE		       _
ASCII ribbon campaign ( )     devrim~gunduz.org
against HTML e-mail    X      devrim~PostgreSQL.org
 		      / \     devrim.gunduz~linux.org.tr
             http://www.gunduz.org



From nhuczp at gmail.com  Fri Feb  1 08:30:28 2008
From: nhuczp at gmail.com (chenzp)
Date: Fri, 1 Feb 2008 16:30:28 +0800
Subject: [Linux-cluster] look gfs2 resource have some problem
Message-ID: <6cc6db6f0802010030u69a4ff5egc587ef8a3bea6b30@mail.gmail.com>

hi all:

I have some problem about gfs2 mds and cluster component.
The problem as follows:



Frist problem:    I want known the cluster Component how to manager GFS2
MDS.
Secondly problem: The other proble  how to sync mds.


thanks!

carry.chen
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://listman.redhat.com/archives/linux-cluster/attachments/20080201/2dfbefd3/attachment.htm>

From abhramica at gmail.com  Fri Feb  1 09:27:39 2008
From: abhramica at gmail.com (Abhra Paul)
Date: Fri, 1 Feb 2008 14:57:39 +0530
Subject: [Linux-cluster] Storage problem in Linux Cluster
Message-ID: <8e3fbac10802010127s511fa106w59302a27ec12161b@mail.gmail.com>

Respected Users

    I have a problem in cluster. One user of this cluster needs huge
amount of space. In this cluster one big partition(size 1TB) is
mounted on /data . So I provide this amount of space for his program
execution. At 1.30 PM he occupied 200GB of this storage(which is
mounted on /data). Now when I am going to check this /data , about
usage of space , using the command  du -sh * . In o/p there is no
entry for /data and courser is only blinking without showing total o/p
as well as command prompt is not coming back. Also when I am issuing
cd / same thing is happening . How I solve this problem.

                                                                With regards
                                                                 Abhra Paul



From pcaulfie at redhat.com  Fri Feb  1 09:32:35 2008
From: pcaulfie at redhat.com (Patrick Caulfeld)
Date: Fri, 01 Feb 2008 09:32:35 +0000
Subject: [Linux-cluster] DLM Problem
In-Reply-To: <200813111252.477369@leena>
References: <200813111252.477369@leena>
Message-ID: <47A2E733.4000401@redhat.com>

isplist at logicore.net wrote:
>> Can you boot a single node, without any cluster software running, then
>> do the 'netstat -tap'. Then start the cluster software and do it again.
> 
> compdev# netstat -tap
> Active Internet connections (servers and established)
> Proto Recv-Q Send-Q Local Address Foreign Address State PID/Program name
> tcp 0 0 *:amanda      *:*            LISTEN      2371/xinetd
> tcp 0 0 *:netbios-ssn *:*            LISTEN      2444/smbd
> tcp 0 0 *:718            *:*            LISTEN      2232/rpc.statd
> tcp 0 0 *:sunrpc         *:*           LISTEN      2212/portmap
> tcp 0 0 *:10000          *:*           LISTEN      2885/perl
> tcp 0 0 *:microsoft-ds *:*           LISTEN      2444/smbd
> tcp 0 0 *:http              *:*           LISTEN      2424/httpd
> tcp 0 0 *:ssh              *:*           LISTEN      2356/sshd
> tcp 0 0 *:https            *:*           LISTEN      242 /httpd
> tcp 0 0 compdev:ssh  ::ffff:192.168.1.200:2685   ESTABLISHED 3134/0


OK, so that tells me that nothing else is using the DLM port.

>> If you get the error then, say so.
> 
> I'll post the log at the end of this so as not to make it so hard to read. 
> But, it's the same error and nothing blocking that port.
>  
>> Then boot another node, using the same procedure.
> 
> This will take me a little, I'll post the results shortly.
>  
>> Post the results here along with the cluster.conf ... also make sure you
>> have the same version of EVERYTHING on both nodes ... that's software
>> AND cluster.conf
> 
> All machines are exactly the same versions of everything. I've taken nodes out 
> and left only a few nodes in place to simplify things.
>

cluster.conf looks fine too.

I don't need the LVM log. Sorry if I wasn't clear. I wanted the syslog
extracts for the DLM startup. I also wanted to see the netstat AFTER
starting the dlm on the first node (and if there were any errors), then
the same things (on both nodes) when the second node was added.

Patrick



From johannes.russek at io-consulting.net  Fri Feb  1 10:24:46 2008
From: johannes.russek at io-consulting.net (jr)
Date: Fri, 01 Feb 2008 11:24:46 +0100
Subject: [Linux-cluster] DLM Problem
In-Reply-To: <2008131192949.627124@leena>
References: <2008131192949.627124@leena>
Message-ID: <1201861486.29126.102.camel@admc.win-rar.local>

Am Donnerstag, den 31.01.2008, 19:29 -0600 schrieb isplist at logicore.net:

> I've not looked into this yet so don't know what to edit or add. 
> 
> On one node, the drive is /dev/sda, but on some nodes, it'll be sdx because 
> some of the machines already have SCSI drives in them. Not hard to see, just 
> have to keep it in mind since I'm assuming each machine needs this file.
> 
> I see a catch all ( sd*[!0-9] ) but don't know where I need to put say 
> /dev/sda.

okay, i'll try to help as far as i can with my nonexistant udev rules.
the catchall is there because you *don't* know which scsi disk it is,
wether it is sda, sdb or whatever. 
however, the DISK does have a unique serial number (even raid slices do)
or at least a WWN.
so you basically need to find out which unique number your unique disk
has (by using /sbin/scsi_id -p 0x83 -g -u -s /block/sda), tell that the
udev system and let it create a symlink you name whatever you like. this
way, every node get's a symlink with the same name for the same disk,
whatever the state of it's device enumeration is. 
oh, any udev gurus.. i suppose udev uses page 0x83 rather then 0x80, is
that correct? 
regards,
johannes





From bpkroth at wisc.edu  Fri Feb  1 13:51:35 2008
From: bpkroth at wisc.edu (Brian Kroth)
Date: Fri, 01 Feb 2008 07:51:35 -0600
Subject: [Linux-cluster] DLM Problem
In-Reply-To: <1201861486.29126.102.camel@admc.win-rar.local>
References: <2008131192949.627124@leena>
	<1201861486.29126.102.camel@admc.win-rar.local>
Message-ID: <20080201135135.GA4812@omnius.hslc.wisc.edu>

jr <johannes.russek at io-consulting.net>:
> Am Donnerstag, den 31.01.2008, 19:29 -0600 schrieb isplist at logicore.net:
> 
> > I've not looked into this yet so don't know what to edit or add. 
> > 
> > On one node, the drive is /dev/sda, but on some nodes, it'll be sdx because 
> > some of the machines already have SCSI drives in them. Not hard to see, just 
> > have to keep it in mind since I'm assuming each machine needs this file.
> > 
> > I see a catch all ( sd*[!0-9] ) but don't know where I need to put say 
> > /dev/sda.
> 
> okay, i'll try to help as far as i can with my nonexistant udev rules.
> the catchall is there because you *don't* know which scsi disk it is,
> wether it is sda, sdb or whatever. 
> however, the DISK does have a unique serial number (even raid slices do)
> or at least a WWN.
> so you basically need to find out which unique number your unique disk
> has (by using /sbin/scsi_id -p 0x83 -g -u -s /block/sda), tell that the
> udev system and let it create a symlink you name whatever you like. this
> way, every node get's a symlink with the same name for the same disk,
> whatever the state of it's device enumeration is. 

That's all correct.

> oh, any udev gurus.. i suppose udev uses page 0x83 rather then 0x80, is
> that correct? 

I'm no guru, but I've never had to specify -p before.  The rest is what
I've used:

scsi_id -g -u -s /block/sd?

Brian
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/x-pkcs7-signature
Size: 2192 bytes
Desc: not available
URL: <http://listman.redhat.com/archives/linux-cluster/attachments/20080201/7176d34f/attachment.bin>

From npf-mlists at eurotux.com  Fri Feb  1 15:34:45 2008
From: npf-mlists at eurotux.com (Nuno Fernandes)
Date: Fri, 1 Feb 2008 15:34:45 +0000
Subject: [Linux-cluster] RHEL5 CLVMD hang
In-Reply-To: <200801221707.51986.npf-mlists@eurotux.com>
References: <200801171731.26493.npf-mlists@eurotux.com>
	<4795B3D3.7030606@redhat.com>
	<200801221707.51986.npf-mlists@eurotux.com>
Message-ID: <200802011534.45693.npf-mlists@eurotux.com>

Hi,

CLVM is hung again. This time, the problem started when we restarted clvmd in 
one node (xen1).

Xen2 started to report:

Feb  1 15:26:34 xen2 kernel: dlm: recover_master_copy -53 103e7
Feb  1 15:26:34 xen2 kernel: dlm: recover_master_copy -53 10264
Feb  1 15:26:34 xen2 kernel: dlm: recover_master_copy -53 10008
Feb  1 15:26:34 xen2 kernel: dlm: recover_master_copy -53 10047
Feb  1 15:26:34 xen2 kernel: dlm: recover_master_copy -53 1020b
...

Attached i send group_tool dump.

All cluster nodes have dlm_recoverd blocked:

..
10191 ?        D<     0:00  \_ [dlm_recoverd]
..

but only xen2 is putting all that logs.


# cman_tool services
type             level name     id       state
fence            0     default  00010008 none
[1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20]
dlm              1     clvmd    00010001 none
[1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20]

# clustat
Member Status: Quorate

  Member Name                        ID   Status
  ------ ----                        ---- ------
  xen1.dc.eurotux.pt                      1 Online
  xen2.dc.eurotux.pt                      2 Online, Local
  xen3.dc.eurotux.pt                      3 Online
  xen4.dc.eurotux.pt                      4 Online
  xen5.dc.eurotux.pt                      5 Online
  xen6.dc.eurotux.pt                      6 Online
  xen7.dc.eurotux.pt                      7 Online
  xen8.dc.eurotux.pt                      8 Online
  xen9.dc.eurotux.pt                      9 Online
  xen10.dc.eurotux.pt                    10 Online
  xen11.dc.eurotux.pt                    11 Online
  xen12.dc.eurotux.pt                    12 Online
  xen13.dc.eurotux.pt                    13 Online
  xen14.dc.eurotux.pt                    14 Online
  xen17.dc.eurotux.pt                    15 Online
  xen18.dc.eurotux.pt                    16 Online
  xen19.dc.eurotux.pt                    17 Online
  xen20.dc.eurotux.pt                    18 Online
  xen21.dc.eurotux.pt                    19 Online
  xen22.dc.eurotux.pt                    20 Online

Any info on this?

Thanks
Nuno Fernandes

On Tuesday 22 January 2008 17:07:51 Nuno Fernandes wrote:
> On Tuesday 22 January 2008 09:13:55 Patrick Caulfeld wrote:
> > Nuno Fernandes wrote:
> > > On Monday 21 January 2008 15:58:38 Patrick Caulfeld wrote:
> > >> echo 255 > /sys/kernel/config/dlm/cluster/log_debug
> > >
> > > echo 255 > /sys/kernel/config/dlm/cluster/log_debug
> > > -bash: /sys/kernel/config/dlm/cluster/log_debug: Permission denied
> > >
> > > ls -la /sys/kernel/config/dlm/cluster/
> > > total 0
> > > drwxr-xr-x  4 root root 0 May 27  2007 .
> > > drwxr-xr-x  3 root root 0 May 27  2007 ..
> > > drwxr-xr-x 19 root root 0 Jan 17 16:36 comms
> > > drwxr-xr-x  3 root root 0 Nov 27 14:48 spaces
> >
> > No debug options! you need to upgrade the kernel I'm afraid. It might
> > even fix the bug ;-)
> >
> > Patrick
>
> Solved. Rebooted the whole cluster! :(
>
> Thanks
> Nuno Fernandes
>
> --
> Linux-cluster mailing list
> Linux-cluster at redhat.com
> https://www.redhat.com/mailman/listinfo/linux-cluster
-------------- next part --------------
A non-text attachment was scrubbed...
Name: group.dump.txt.gz
Type: application/x-gzip
Size: 13974 bytes
Desc: not available
URL: <http://listman.redhat.com/archives/linux-cluster/attachments/20080201/3b17a7d9/attachment.bin>

From lhh at redhat.com  Fri Feb  1 16:06:43 2008
From: lhh at redhat.com (Lon Hohberger)
Date: Fri, 01 Feb 2008 11:06:43 -0500
Subject: [Linux-cluster] How to set node timeout when using gulm?
In-Reply-To: <940a2e6d0801311720m695a992bq99ec592a9644bc51@mail.gmail.com>
References: <940a2e6d0801311720m695a992bq99ec592a9644bc51@mail.gmail.com>
Message-ID: <1201882003.1759.105.camel@ayanami.boston.devel.redhat.com>

On Thu, 2008-01-31 at 17:20 -0800, Vectorz Sigma wrote:
> I'm aware of how to do this for CMAN but I'm running gulm.  I can't
> find information anywhere on how to do this.
> 
> Anyone know?

According to the gulm.5 man page:

       heartbeat_rate
              The rate at which the heartbeats are checked by the
              server  in seconds.  Two-thirds of this time is the
              rate at which the heartbeats are sent.  Default  is
              15.

       allowed_misses
              How  many  consecutive heartbeats can be missed be-
              fore we mark the node expired.  Default is 2.

Remember that allowed_misses+1 is the "actual" node death time.  So,
with the defaults, that's 45 seconds - not 30.  (important!)

<cluster>
   ...
   <gulm heartbeat_rate="10" allowed_misses="5" />  
          <!-- (5+1)*10 second failure recovery -->
   ...
</cluster>

-- Lon



From lhh at redhat.com  Fri Feb  1 16:09:23 2008
From: lhh at redhat.com (Lon Hohberger)
Date: Fri, 01 Feb 2008 11:09:23 -0500
Subject: [Linux-cluster] postgres cluster with RHEL5
In-Reply-To: <8ee061010801312110q25519afck1ba7776948cb6a44@mail.gmail.com>
References: <8ee061010801312110q25519afck1ba7776948cb6a44@mail.gmail.com>
Message-ID: <1201882163.1759.109.camel@ayanami.boston.devel.redhat.com>

On Thu, 2008-01-31 at 23:10 -0600, Terry wrote:

>            <service autostart="1" domain="failover00" exclusive="0"
> name="database" recovery="relocate">
>                         <postgres-8 ref="dssystem2">
>                                 <fs ref="db00"/>
>                                 <ip ref="192.168.100.207"/>
>                         </postgres-8>
>                 </service>

That's not going to work; the dependencies are backwards (assuming
postgresql is trying to use the fs and ip).  Try:

    <service autostart="1" domain="failover00" exclusive="0"
             name="database" recovery="relocate">
        <fs ref="db00"/>
        <ip ref="192.168.100.207"/>
        <postgres-8 ref="dssystem2"/>
    </service>

-- Lon




From lhh at redhat.com  Fri Feb  1 16:12:59 2008
From: lhh at redhat.com (Lon Hohberger)
Date: Fri, 01 Feb 2008 11:12:59 -0500
Subject: [Linux-cluster] Storage problem in Linux Cluster
In-Reply-To: <8e3fbac10802010127s511fa106w59302a27ec12161b@mail.gmail.com>
References: <8e3fbac10802010127s511fa106w59302a27ec12161b@mail.gmail.com>
Message-ID: <1201882379.1759.111.camel@ayanami.boston.devel.redhat.com>

On Fri, 2008-02-01 at 14:57 +0530, Abhra Paul wrote:
> Respected Users
> 
>     I have a problem in cluster. One user of this cluster needs huge
> amount of space. In this cluster one big partition(size 1TB) is
> mounted on /data . So I provide this amount of space for his program
> execution. At 1.30 PM he occupied 200GB of this storage(which is
> mounted on /data). Now when I am going to check this /data , about
> usage of space , using the command  du -sh * . In o/p there is no
> entry for /data and courser is only blinking without showing total o/p
> as well as command prompt is not coming back. Also when I am issuing
> cd / same thing is happening . How I solve this problem.

Could you check: 
  cman_tool services

-- Lon





From td3201 at gmail.com  Fri Feb  1 16:30:06 2008
From: td3201 at gmail.com (Terry)
Date: Fri, 1 Feb 2008 10:30:06 -0600
Subject: [Linux-cluster] postgres cluster with RHEL5
In-Reply-To: <1201882163.1759.109.camel@ayanami.boston.devel.redhat.com>
References: <8ee061010801312110q25519afck1ba7776948cb6a44@mail.gmail.com>
	<1201882163.1759.109.camel@ayanami.boston.devel.redhat.com>
Message-ID: <8ee061010802010830k270c3deaxcd2a5bdaa5d552c1@mail.gmail.com>

On Feb 1, 2008 10:09 AM, Lon Hohberger <lhh at redhat.com> wrote:
> On Thu, 2008-01-31 at 23:10 -0600, Terry wrote:
>
> >            <service autostart="1" domain="failover00" exclusive="0"
> > name="database" recovery="relocate">
> >                         <postgres-8 ref="dssystem2">
> >                                 <fs ref="db00"/>
> >                                 <ip ref="192.168.100.207"/>
> >                         </postgres-8>
> >                 </service>
>
> That's not going to work; the dependencies are backwards (assuming
> postgresql is trying to use the fs and ip).  Try:
>
>     <service autostart="1" domain="failover00" exclusive="0"
>              name="database" recovery="relocate">
>         <fs ref="db00"/>
>         <ip ref="192.168.100.207"/>
>         <postgres-8 ref="dssystem2"/>
>     </service>
>
> -- Lon

I spoke incorrectly.  The shared storage is an iSCSI volume with ext3.
 NFS is another cluster service.  Sorry.



From isplist at logicore.net  Fri Feb  1 17:45:43 2008
From: isplist at logicore.net (isplist at logicore.net)
Date: Fri, 1 Feb 2008 11:45:43 -0600
Subject: [Linux-cluster] DLM Problem
In-Reply-To: <20080131233956.GA4485@omnius.hslc.wisc.edu>
Message-ID: <200821114543.838843@leena>

I'm still getting very long delays before access. Is there some way of testing 
this to see if it's the storage or the GFS setup? Like a test I could run with 
the storage connected raw then with GFS?

Perhaps I just kill the partition, run some test, format it as GFS again, 
mount it, test?

Mike


On Thu, 31 Jan 2008 17:39:56 -0600, Brian Kroth wrote:
> Johannes Russek <johannes.russek at io-consulting.net>:
> 
>>> 
>>> i think that's the file he sent you ;) (starting with "# /etc/udev..")
>>> johannes
>>> 
> Yes.
> 
>>> 
>>> --
>>> Linux-cluster mailing list
>>> Linux-cluster at redhat.com
>>> https://www.redhat.com/mailman/listinfo/linux-cluster
>> thinking about it, i think i should add to say that you need to edit that
>> file for your needs (adjust the scsi id). i didn't use udev yet, the only
>> place where i scsi_id etc together with dm-multipath.
>> johannes
>> 
> True, you will need to edit it.  That example is coming from a gentoo
> install, so it'll probably be different for you.
> 
> Brian






From td3201 at gmail.com  Fri Feb  1 19:14:37 2008
From: td3201 at gmail.com (Terry)
Date: Fri, 1 Feb 2008 13:14:37 -0600
Subject: [Linux-cluster] postgres cluster with RHEL5
In-Reply-To: <8ee061010802010830k270c3deaxcd2a5bdaa5d552c1@mail.gmail.com>
References: <8ee061010801312110q25519afck1ba7776948cb6a44@mail.gmail.com>
	<1201882163.1759.109.camel@ayanami.boston.devel.redhat.com>
	<8ee061010802010830k270c3deaxcd2a5bdaa5d552c1@mail.gmail.com>
Message-ID: <8ee061010802011114l11e566c4wa211c7d7da441066@mail.gmail.com>

On Feb 1, 2008 10:30 AM, Terry <td3201 at gmail.com> wrote:
> On Feb 1, 2008 10:09 AM, Lon Hohberger <lhh at redhat.com> wrote:
> > On Thu, 2008-01-31 at 23:10 -0600, Terry wrote:
> >
> > >            <service autostart="1" domain="failover00" exclusive="0"
> > > name="database" recovery="relocate">
> > >                         <postgres-8 ref="dssystem2">
> > >                                 <fs ref="db00"/>
> > >                                 <ip ref="192.168.100.207"/>
> > >                         </postgres-8>
> > >                 </service>
> >
> > That's not going to work; the dependencies are backwards (assuming
> > postgresql is trying to use the fs and ip).  Try:
> >
> >     <service autostart="1" domain="failover00" exclusive="0"
> >              name="database" recovery="relocate">
> >         <fs ref="db00"/>
> >         <ip ref="192.168.100.207"/>
> >         <postgres-8 ref="dssystem2"/>
> >     </service>
> >
> > -- Lon
>
> I spoke incorrectly.  The shared storage is an iSCSI volume with ext3.
>  NFS is another cluster service.  Sorry.
>

Thanks for all of your replies.  I think I have a catch 22 situation.
Here is my (corrected) config:
                <resources>
                        <ip address="192.168.100.206" monitor_link="1"/>
                        <fs device="/dev/sdc1" force_fsck="0"
force_unmount="1" fsid="42585" fstype="ext3" mountpoint="/db00"
name="db00" self_fence="1"/>
                        <postgres-8
config_file="/var/lib/pgsql/data/postgresql.conf" name="dssystem"
postmaster_user="postgres" shutdown_wait="0"/>
                </resources>
                <service autostart="1" domain="failover00"
exclusive="0" name="database" recovery="relocate">
                        <fs ref="db00"/>
                        <ip ref="192.168.100.207"/>
                        <postgres-8 ref="dssystem"/>
                </service>


Here is a listing of /db00:
[root at nfs00a ~]# ls /db00/
backups  data  pgstartup.log
[root at nfs00a ~]# ls /db00/data/
base    lost+found  pg_hba.conf    pg_log        pg_subtrans
pg_twophase  pg_xlog          postmaster.opts
global  pg_clog     pg_ident.conf  pg_multixact  pg_tblspc
PG_VERSION   postgresql.conf

You can see that my postgres config lives on this iscsi volume which
needs to be mounted as part of the database service.  When I attempt
to start the database service, it acts like it starts, there are no
logs but it doesn't start, nor does the /db00 volume get mounted.
What am I missing?  I want to stay as close to standard as possible
with regards to postgres and directory locations so I created a
symlink:
lrwxrwxrwx 1 root root 5 Feb  1 12:32 /var/lib/pgsql -> /db00

I hope this paints a better picture of what I am doing and ultimately,
where I am failing.

Thanks all!



From isplist at logicore.net  Fri Feb  1 19:54:08 2008
From: isplist at logicore.net (isplist at logicore.net)
Date: Fri, 1 Feb 2008 13:54:08 -0600
Subject: [Linux-cluster] DLM Problem
In-Reply-To: <20080131233956.GA4485@omnius.hslc.wisc.edu>
Message-ID: <20082113548.625938@leena>

Update for anyone watching :).

I've eliminated GFS as being the slowdown at least. No ideas on the DLM 
problems but I'll get back to that after I figure out the slowdown.

Seems that the storage controller has problems so I'll either change out the 
chassis or controllers if I can. Once I nuke the delay issues, I'll get vlm 
back on then GFS and see what happens. 

Mike


On Thu, 31 Jan 2008 17:39:56 -0600, Brian Kroth wrote:
> Johannes Russek <johannes.russek at io-consulting.net>:
> 
>>> 
>>> i think that's the file he sent you ;) (starting with "# /etc/udev..")
>>> johannes
>>> 
> Yes.
> 
>>> 
>>> --
>>> Linux-cluster mailing list
>>> Linux-cluster at redhat.com
>>> https://www.redhat.com/mailman/listinfo/linux-cluster
>> thinking about it, i think i should add to say that you need to edit that
>> file for your needs (adjust the scsi id). i didn't use udev yet, the only
>> place where i scsi_id etc together with dm-multipath.
>> johannes
>> 
> True, you will need to edit it.  That example is coming from a gentoo
> install, so it'll probably be different for you.
> 
> Brian






From isplist at logicore.net  Fri Feb  1 19:56:45 2008
From: isplist at logicore.net (isplist at logicore.net)
Date: Fri, 1 Feb 2008 13:56:45 -0600
Subject: [Linux-cluster] DLM Problem
In-Reply-To: <47A2E733.4000401@redhat.com>
Message-ID: <200821135645.507559@leena>

> I don't need the LVM log. Sorry if I wasn't clear. I wanted the syslog
> extracts for the DLM startup. I also wanted to see the netstat AFTER
> starting the dlm on the first node (and if there were any errors), then
> the same things (on both nodes) when the second node was added.

Ok, I'll resolve the delay issues first then get back to this DLM issue. Is it 
possible that DLM or something was timing out because of the storage delay? 
Maybe it was screwing it up, not seeing the storage or not getting proper 
responses?

Mike





From isplist at logicore.net  Fri Feb  1 22:17:49 2008
From: isplist at logicore.net (isplist at logicore.net)
Date: Fri, 1 Feb 2008 16:17:49 -0600
Subject: [Linux-cluster] DLM Problem
In-Reply-To: <20080131233956.GA4485@omnius.hslc.wisc.edu>
Message-ID: <200821161749.373315@leena>

Ah, wonderful day knee deep in fibre channel. 
Does anyone know how I can test NFS speeds in a similar fashion to hdparm -tT? 
All the testing I've ever done was with hdparm so that's my reference point.

Mike


On Thu, 31 Jan 2008 17:39:56 -0600, Brian Kroth wrote:
> Johannes Russek <johannes.russek at io-consulting.net>:
> 
>>> 
>>> i think that's the file he sent you ;) (starting with "# /etc/udev..")
>>> johannes
>>> 
> Yes.
> 
>>> 
>>> --
>>> Linux-cluster mailing list
>>> Linux-cluster at redhat.com
>>> https://www.redhat.com/mailman/listinfo/linux-cluster
>> thinking about it, i think i should add to say that you need to edit that
>> file for your needs (adjust the scsi id). i didn't use udev yet, the only
>> place where i scsi_id etc together with dm-multipath.
>> johannes
>> 
> True, you will need to edit it.  That example is coming from a gentoo
> install, so it'll probably be different for you.
> 
> Brian






From johannes.russek at io-consulting.net  Fri Feb  1 22:52:10 2008
From: johannes.russek at io-consulting.net (Johannes Russek)
Date: Fri, 01 Feb 2008 23:52:10 +0100
Subject: [Linux-cluster] DLM Problem
In-Reply-To: <200821161749.373315@leena>
References: <200821161749.373315@leena>
Message-ID: <47A3A29A.4010701@io-consulting.net>

isplist at logicore.net schrieb:
> Ah, wonderful day knee deep in fibre channel. 
> Does anyone know how I can test NFS speeds in a similar fashion to hdparm -tT? 
> All the testing I've ever done was with hdparm so that's my reference point.
>
> Mike
>
>   

Hi Mike,
hdparm -tT is nice and easy but i'm afraid it's no reference point 
whatsoever. Out of my guts i'd say go for bonnie, both on your SAN and 
on the NFS shares.
a search for bonnie and nfs on google to see if bonnie is fine with nfs 
showed this first: http://sourceforge.net/projects/nfstestmatrix/
looks nice :)
go for bonnie!
johannes



From isplist at logicore.net  Fri Feb  1 22:55:34 2008
From: isplist at logicore.net (isplist at logicore.net)
Date: Fri, 1 Feb 2008 16:55:34 -0600
Subject: [Linux-cluster] DLM Problem
In-Reply-To: <47A3A29A.4010701@io-consulting.net>
Message-ID: <200821165534.518857@leena>

I looked at it before but it looked like I'd have to spend some time learning 
it as I was not able to find some example commands for basic drive speed 
stats.

Mike


On Fri, 01 Feb 2008 23:52:10 +0100, Johannes Russek wrote:
> isplist at logicore.net schrieb:
> 
>> Ah, wonderful day knee deep in fibre channel.
>> Does anyone know how I can test NFS speeds in a similar fashion to hdparm
>> -tT?
>> All the testing I've ever done was with hdparm so that's my reference
>> point.
>> 
>> Mike
>> 
>> 
> Hi Mike,
> hdparm -tT is nice and easy but i'm afraid it's no reference point
> whatsoever. Out of my guts i'd say go for bonnie, both on your SAN and
> on the NFS shares.
> a search for bonnie and nfs on google to see if bonnie is fine with nfs
> showed this first: http://sourceforge.net/projects/nfstestmatrix/
> looks nice :)
> go for bonnie!
> johannes






From johannes.russek at io-consulting.net  Fri Feb  1 23:03:39 2008
From: johannes.russek at io-consulting.net (Johannes Russek)
Date: Sat, 02 Feb 2008 00:03:39 +0100
Subject: [Linux-cluster] DLM Problem
In-Reply-To: <200821165534.518857@leena>
References: <200821165534.518857@leena>
Message-ID: <47A3A54B.90904@io-consulting.net>

isplist at logicore.net schrieb:
> I looked at it before but it looked like I'd have to spend some time learning 
> it as I was not able to find some example commands for basic drive speed 
> stats.
>
> Mike
>   
I can't test it right now, but i think it should just be
bonnie -s 2000
the number being any size of testfile you want to check (probably 
something bigger then how much cache is between you and the disk.
johannes



From gordan at bobich.net  Fri Feb  1 23:30:12 2008
From: gordan at bobich.net (Gordan Bobic)
Date: Fri, 01 Feb 2008 23:30:12 +0000
Subject: [Linux-cluster] DLM Problem
In-Reply-To: <200821161749.373315@leena>
References: <200821161749.373315@leena>
Message-ID: <47A3AB84.8090808@bobich.net>

For more meaningful results, try iozone.

Gordan

isplist at logicore.net wrote:
> Ah, wonderful day knee deep in fibre channel. 
> Does anyone know how I can test NFS speeds in a similar fashion to hdparm -tT? 
> All the testing I've ever done was with hdparm so that's my reference point.
> 
> Mike
> 
> 
> On Thu, 31 Jan 2008 17:39:56 -0600, Brian Kroth wrote:
>> Johannes Russek <johannes.russek at io-consulting.net>:
>>
>>>> i think that's the file he sent you ;) (starting with "# /etc/udev..")
>>>> johannes
>>>>
>> Yes.
>>
>>>> --
>>>> Linux-cluster mailing list
>>>> Linux-cluster at redhat.com
>>>> https://www.redhat.com/mailman/listinfo/linux-cluster
>>> thinking about it, i think i should add to say that you need to edit that
>>> file for your needs (adjust the scsi id). i didn't use udev yet, the only
>>> place where i scsi_id etc together with dm-multipath.
>>> johannes
>>>
>> True, you will need to edit it.  That example is coming from a gentoo
>> install, so it'll probably be different for you.
>>
>> Brian
> 
> 
> 
> 
> --
> Linux-cluster mailing list
> Linux-cluster at redhat.com
> https://www.redhat.com/mailman/listinfo/linux-cluster



From bpkroth at wisc.edu  Sat Feb  2 04:36:39 2008
From: bpkroth at wisc.edu (Brian Kroth)
Date: Fri, 01 Feb 2008 22:36:39 -0600
Subject: [Linux-cluster] DLM Problem
In-Reply-To: <47A3AB84.8090808@bobich.net>
References: <200821161749.373315@leena> <47A3AB84.8090808@bobich.net>
Message-ID: <20080202043639.GA12660@odin.hslc.wisc.edu>

Gordan Bobic <gordan at bobich.net>:
> For more meaningful results, try iozone.
>
> Gordan
>

yeah iozone -a is pretty easy.  For anyone who's interested: some graphs from
results I got a couple weeks ago while running it on 5 nodes at once:

https://mywebspace.wisc.edu/bpkroth/web/fs-cluster/fs-cluster-iozone-results.xls

The student I had put them together did it in MS Office, so they look nicer
there, but they're still readable in ooffice.

Brian
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/x-pkcs7-signature
Size: 2192 bytes
Desc: not available
URL: <http://listman.redhat.com/archives/linux-cluster/attachments/20080201/3d3a5a0e/attachment.bin>

From teemu.m2 at luukku.com  Sat Feb  2 06:45:36 2008
From: teemu.m2 at luukku.com (m.. mm..)
Date: Sat, 2 Feb 2008 08:45:36 +0200 (EET)
Subject: [Linux-cluster] Cluster nodenames, question
Message-ID: <1201934736227.teemu.m2.1600.j3lSZNC_LaD0TcWeA1d4uQ@luukku.com>

Hi everyone!

How about this RedHat ClusterSuite 5.1 configuration, if i have example 2 nodes test1 and test2:

Network is configured like this:
prodution network
test1 ip=10.10.10.5 
test2 ip=10.10.10.6

Private Heartbeat network
test1hb ip=192.168.0.2     (machine= test1)
test2hb ip=192.168.0.3     (-------= test2)

What names should i use when i add cluster member to my cluster "test". Is'it test1 or sould i use test1hb name?



-Reg.Teemu



...................................................................
Luukku Plus paketilla p??set eroon tila- ja turvallisuusongelmista.
Hanki Luukku Plus ja helpotat el?m??si. http://www.mtv3.fi/luukku




From shawnlhood at gmail.com  Sat Feb  2 07:35:03 2008
From: shawnlhood at gmail.com (Shawn Hood)
Date: Sat, 2 Feb 2008 02:35:03 -0500
Subject: [Linux-cluster] Speeding up GFS on 1 node cluster
Message-ID: <cfe2fc960802012335u5c57b37bi5af7ca6c5efae4a9@mail.gmail.com>

I currently have several machines I'm about to cluster using RHCS,
utilizing shared storage (XRAID w/ GFS).  I currently have another
existing XRAID which is mounted on one machine.  I need to move all
this data from this existing XRAID to the new GFS XRAID.  Right now, I
have a one-node cluster running.  This node has both XRAIDs mounted.
I am running an rsync job between them.  The transfer is writing at
about 25-35MB/s.

Anyhow, I need to speed up this initial sync.  Can I do this by
changing to a non-clustered locking, as only one node is running?
Part of this rsync is a huge set of small files.  I'm assuming I could
toy with gfs_tune to improve performance, as well.  Any advice is
appreciated.



From isplist at logicore.net  Sat Feb  2 18:48:05 2008
From: isplist at logicore.net (isplist at logicore.net)
Date: Sat, 2 Feb 2008 12:48:05 -0600
Subject: [Linux-cluster] DLM Problem
In-Reply-To: <47A3C96C.7070609@io-consulting.net>
Message-ID: <20082212485.382562@leena>

Another quick question...

Since I was not able to solve my fc problem, I decided it was time to
fire up my bluearc again. I have very fast nfs services now but am wondering 
if it my imagination that I've seen posts from some people talking about 
taking an nfs export and offering it up as a gfs volume?
 
Also, any thoughts on speeds with nfs vs iSCSI client? I just want to 
understand what I'm getting into a little better. Guessing they are similar 
since they would be Ethernet speed dependant other than various protocol 
overheads.

 Mike






From abhramica at gmail.com  Mon Feb  4 06:16:16 2008
From: abhramica at gmail.com (Abhra Paul)
Date: Mon, 4 Feb 2008 11:46:16 +0530
Subject: [Linux-cluster] Storage problem in Linux Cluster
In-Reply-To: <1201882379.1759.111.camel@ayanami.boston.devel.redhat.com>
References: <8e3fbac10802010127s511fa106w59302a27ec12161b@mail.gmail.com>
	<1201882379.1759.111.camel@ayanami.boston.devel.redhat.com>
Message-ID: <8e3fbac10802032216i37c01e9em34e1c7b81e7bd0da@mail.gmail.com>

On Feb 1, 2008 9:42 PM, Lon Hohberger <lhh at redhat.com> wrote:
> On Fri, 2008-02-01 at 14:57 +0530, Abhra Paul wrote:
> > Respected Users
> >
> >     I have a problem in cluster. One user of this cluster needs huge
> > amount of space. In this cluster one big partition(size 1TB) is
> > mounted on /data . So I provide this amount of space for his program
> > execution. At 1.30 PM he occupied 200GB of this storage(which is
> > mounted on /data). Now when I am going to check this /data , about
> > usage of space , using the command  du -sh * . In o/p there is no
> > entry for /data and courser is only blinking without showing total o/p
> > as well as command prompt is not coming back. Also when I am issuing
> > cd / same thing is happening . How I solve this problem.
>
> Could you check:
>   cman_tool services
>
> -- Lon
>
>
>
> --
> Linux-cluster mailing list
> Linux-cluster at redhat.com
> https://www.redhat.com/mailman/listinfo/linux-cluster
-------------------------------------------------------------------------------------------------------------

I have checked cman_tool services. But in my system there is no
cman_tool , as well as there is no man page entry for cman_tool. Now ,
how I will solve my problem. Please, help.


                              With regards

                              Abhra  Paul



From Alain.Moulle at bull.net  Mon Feb  4 07:33:52 2008
From: Alain.Moulle at bull.net (Alain Moulle)
Date: Mon, 04 Feb 2008 08:33:52 +0100
Subject: [Linux-cluster] CS5/ Question about behavior with a corrupted
	Quorum disk
Message-ID: <47A6BFE0.3000700@bull.net>

Hi

Just for information, I wonder if this behavior is normal :
I have a two-nodes cluster with a quorum disk, and the
CS5 is started on both nodes with a service on each one.
Quorum is working fine when I break the quorum disk format
(with a mkfs on the device !) so that mkqisk -L returns
none.
The behavior is : the CS5 is always working fine as if nothing
has happen. I wonder if it is only due to the heuristics or
if this behavior is simply the std behavior of CS5 with
regard to the quorum disk ?

Thanks
Regards
Alain Moull?



From pcaulfie at redhat.com  Mon Feb  4 08:23:18 2008
From: pcaulfie at redhat.com (Patrick Caulfeld)
Date: Mon, 04 Feb 2008 08:23:18 +0000
Subject: [Linux-cluster] Cluster nodenames, question
In-Reply-To: <1201934736227.teemu.m2.1600.j3lSZNC_LaD0TcWeA1d4uQ@luukku.com>
References: <1201934736227.teemu.m2.1600.j3lSZNC_LaD0TcWeA1d4uQ@luukku.com>
Message-ID: <47A6CB76.2030601@redhat.com>

m.. mm.. wrote:
> Hi everyone!
> 
> How about this RedHat ClusterSuite 5.1 configuration, if i have example 2 nodes test1 and test2:
> 
> Network is configured like this:
> prodution network
> test1 ip=10.10.10.5 
> test2 ip=10.10.10.6
> 
> Private Heartbeat network
> test1hb ip=192.168.0.2     (machine= test1)
> test2hb ip=192.168.0.3     (-------= test2)
> 
> What names should i use when i add cluster member to my cluster "test". Is'it test1 or sould i use test1hb name?


You should tell cluster suite the names of the heartbeat interfaces.
test1hb etc.

Patrick



From teemu.m2 at luukku.com  Mon Feb  4 11:41:45 2008
From: teemu.m2 at luukku.com (m.. mm..)
Date: Mon, 4 Feb 2008 13:41:45 +0200 (EET)
Subject: [Linux-cluster] Cluster nodenames, question
Message-ID: <1202125305640.teemu.m2.32496.rJNAwaPzmJwHsgT57E5wHQ@luukku.com>

Patrick Caulfeld kirjoitti 04.02.2008 kello 10:23:
> m.. mm.. wrote:
> > Hi everyone!
> > 
> > How about this RedHat ClusterSuite 5.1 configuration, if i have example 2
> nodes test1 and test2:
> > 
> > Network is configured like this:
> > prodution network
> > test1 ip=10.10.10.5 
> > test2 ip=10.10.10.6
> > 
> > Private Heartbeat network
> > test1hb ip=192.168.0.2     (machine= test1)
> > test2hb ip=192.168.0.3     (-------= test2)
> > 
> > What names should i use when i add cluster member to my cluster "test".
> Is'it test1 or sould i use test1hb name?
> 
> 
> You should tell cluster suite the names of the heartbeat interfaces.
> test1hb etc.
> 
> Patrick
> 
> --
> Linux-cluster mailing list
> Linux-cluster at redhat.com
> https://www.redhat.com/mailman/listinfo/linux-cluster


Hi,
But where? 


...................................................................
Luukku Plus paketilla p??set eroon tila- ja turvallisuusongelmista.
Hanki Luukku Plus ja helpotat el?m??si. http://www.mtv3.fi/luukku




From pcaulfie at redhat.com  Mon Feb  4 11:59:38 2008
From: pcaulfie at redhat.com (Patrick Caulfeld)
Date: Mon, 04 Feb 2008 11:59:38 +0000
Subject: [Linux-cluster] Cluster nodenames, question
In-Reply-To: <1202125305640.teemu.m2.32496.rJNAwaPzmJwHsgT57E5wHQ@luukku.com>
References: <1202125305640.teemu.m2.32496.rJNAwaPzmJwHsgT57E5wHQ@luukku.com>
Message-ID: <47A6FE2A.1090708@redhat.com>

m.. mm.. wrote:
> Patrick Caulfeld kirjoitti 04.02.2008 kello 10:23:
>> m.. mm.. wrote:
>>> Hi everyone!
>>>
>>> How about this RedHat ClusterSuite 5.1 configuration, if i have example 2
>> nodes test1 and test2:
>>> Network is configured like this:
>>> prodution network
>>> test1 ip=10.10.10.5 
>>> test2 ip=10.10.10.6
>>>
>>> Private Heartbeat network
>>> test1hb ip=192.168.0.2     (machine= test1)
>>> test2hb ip=192.168.0.3     (-------= test2)
>>>
>>> What names should i use when i add cluster member to my cluster "test".
>> Is'it test1 or sould i use test1hb name?
>>
>>
>> You should tell cluster suite the names of the heartbeat interfaces.
>> test1hb etc.
>>
>> Patrick
>>
>> --
>> Linux-cluster mailing list
>> Linux-cluster at redhat.com
>> https://www.redhat.com/mailman/listinfo/linux-cluster
> 
> 
> Hi,
> But where? 
> 


in /etc/cluster/cluster.conf

Patrick



From Santosh.Panigrahi at in.unisys.com  Mon Feb  4 12:17:26 2008
From: Santosh.Panigrahi at in.unisys.com (Panigrahi, Santosh Kumar)
Date: Mon, 4 Feb 2008 17:47:26 +0530
Subject: [Linux-cluster] Cluster nodenames, question
In-Reply-To: <1202125305640.teemu.m2.32496.rJNAwaPzmJwHsgT57E5wHQ@luukku.com>
References: <1202125305640.teemu.m2.32496.rJNAwaPzmJwHsgT57E5wHQ@luukku.com>
Message-ID: <D566E8CF3538B54D95B925CB69CB4D2A0BA2B7C9@inblr-exch1.eu.uis.unisys.com>

U have to configure this in /etc/cluster/cluster.conf file.
If you are new to RHCS better to use system-config-cluster or conga to configure the Redhat cluster.
Thanks,
--Santosh

-----Original Message-----
From: linux-cluster-bounces at redhat.com [mailto:linux-cluster-bounces at redhat.com] On Behalf Of m.. mm..
Sent: Monday, February 04, 2008 5:12 PM
To: linux clustering
Subject: Re: [Linux-cluster] Cluster nodenames, question

Patrick Caulfeld kirjoitti 04.02.2008 kello 10:23:
> m.. mm.. wrote:
> > Hi everyone!
> > 
> > How about this RedHat ClusterSuite 5.1 configuration, if i have example 2
> nodes test1 and test2:
> > 
> > Network is configured like this:
> > prodution network
> > test1 ip=10.10.10.5 
> > test2 ip=10.10.10.6
> > 
> > Private Heartbeat network
> > test1hb ip=192.168.0.2     (machine= test1)
> > test2hb ip=192.168.0.3     (-------= test2)
> > 
> > What names should i use when i add cluster member to my cluster "test".
> Is'it test1 or sould i use test1hb name?
> 
> 
> You should tell cluster suite the names of the heartbeat interfaces.
> test1hb etc.
> 
> Patrick
> 
> --
> Linux-cluster mailing list
> Linux-cluster at redhat.com
> https://www.redhat.com/mailman/listinfo/linux-cluster


Hi,
But where? 


...................................................................
Luukku Plus paketilla p??set eroon tila- ja turvallisuusongelmista.
Hanki Luukku Plus ja helpotat el?m??si. http://www.mtv3.fi/luukku


--
Linux-cluster mailing list
Linux-cluster at redhat.com
https://www.redhat.com/mailman/listinfo/linux-cluster



From shawnlhood at gmail.com  Mon Feb  4 16:54:16 2008
From: shawnlhood at gmail.com (Shawn Hood)
Date: Mon, 4 Feb 2008 11:54:16 -0500
Subject: [Linux-cluster] performace tuning
Message-ID: <cfe2fc960802040854l572f0babq810df6430e137e08@mail.gmail.com>

Hey all,

My company has gone live with a GFS cluster this morning.  It is a 4
node RHEL4U6 cluster, running RHCS and GFS.  It mounts an Apple 4.5TB
XRAID configured as RAID5, whose physical volumes are combined into
one large volume group.  From this volume group, five striped LVMs
(striped across the two physical volumes of the XRAID) were created.
Five GFS filesystems were created, one on each logical volume. Even
though there are currently four nodes, there are 12 journals for each
filesystem to allow for planned cluster growth.

Currently, each filesystem is mounted noatime, and tunebles
quota_enforce and quota_account are set to 0.  I have posted the
results of gfs_tool gettune /hq-san/nlp/nlp_qa below.  We have an
application which depends heavily upon a find command that lists a
number of files.  It looks something like this:
find $delta_home -name summary -maxdepth 2 -type f

Its output consists of thousands of files that exist on
/hq-san/nlp/nlp_qa.  This command is CRAWLING at the moment.  An ext3
filesystem would output hundreds of matches a second.  This GFS
filesystem is currently outputting 100-200/minutes.  This is crippling
one of our applications.  Any advice on tuning this filesystem for
this kind of access would be greatly appreciated.

Output from a gfs_tool df /hq-san/nlp_qa:

odin / # gfs_tool df /hq-san/nlp/nlp_qa
/hq-san/nlp/nlp_qa:
  SB lock proto = "lock_dlm"
  SB lock table = "boson:nlp_qa"
  SB ondisk format = 1309
  SB multihost format = 1401
  Block size = 4096
  Journals = 12
  Resource Groups = 3009
  Mounted lock proto = "lock_dlm"
  Mounted lock table = "boson:nlp_qa"
  Mounted host data = ""
  Journal number = 1
  Lock module flags =
  Local flocks = FALSE
  Local caching = FALSE
  Oopses OK = FALSE

  Type           Total          Used           Free           use%
  ------------------------------------------------------------------------
  inodes         15167101       15167101       0              100%
  metadata       868298         750012         118286         86%
  data           219476789      192088469      27388320       88%



Output from a df -h:

/dev/mapper/hq--san-cam_development 499G  201G  298G  41%
/hq-san/nlp/cam_development
/dev/mapper/hq--san-nlp_qa 899G  794G  105G  89% /hq-san/nlp/nlp_qa
/dev/mapper/hq--san-svn_users 1.5T  1.3T  282G  82% /hq-san/nlp/svn_users
/dev/mapper/hq--san-development 499G  373G  126G  75% /hq-san/nlp/development
/dev/mapper/hq--san-prod_reports 1023G  680G  343G  67% /hq-san/nlp/prod_reports

odin / # gfs_tool gettune /hq-san/nlp/nlp_qa
ilimit1 = 100
ilimit1_tries = 3
ilimit1_min = 1
ilimit2 = 500
ilimit2_tries = 10
ilimit2_min = 3
demote_secs = 300
incore_log_blocks = 1024
jindex_refresh_secs = 60
depend_secs = 60
scand_secs = 5
recoverd_secs = 60
logd_secs = 1
quotad_secs = 5
inoded_secs = 15
glock_purge = 0
quota_simul_sync = 64
quota_warn_period = 10
atime_quantum = 3600
quota_quantum = 60
quota_scale = 1.0000   (1, 1)
quota_enforce = 0
quota_account = 0
new_files_jdata = 0
new_files_directio = 0
max_atomic_write = 4194304
max_readahead = 262144
lockdump_size = 131072
stall_secs = 600
complain_secs = 10
reclaim_limit = 5000
entries_per_readdir = 32
prefetch_secs = 10
statfs_slots = 64
max_mhc = 10000
greedy_default = 100
greedy_quantum = 25
greedy_max = 250
rgrp_try_threshold = 100
statfs_fast = 0
seq_readahead = 0


Shawn



From gordan at bobich.net  Mon Feb  4 16:59:59 2008
From: gordan at bobich.net (gordan at bobich.net)
Date: Mon, 4 Feb 2008 16:59:59 +0000 (GMT)
Subject: [Linux-cluster] performace tuning
In-Reply-To: <cfe2fc960802040854l572f0babq810df6430e137e08@mail.gmail.com>
References: <cfe2fc960802040854l572f0babq810df6430e137e08@mail.gmail.com>
Message-ID: <alpine.LRH.1.00.0802041658430.3102@skynet.shatteredsilicon.net>

Try mounting the FS with noatime,nodiratime,noquota.

Gordan

On Mon, 4 Feb 2008, Shawn Hood wrote:

> Hey all,
>
> My company has gone live with a GFS cluster this morning.  It is a 4
> node RHEL4U6 cluster, running RHCS and GFS.  It mounts an Apple 4.5TB
> XRAID configured as RAID5, whose physical volumes are combined into
> one large volume group.  From this volume group, five striped LVMs
> (striped across the two physical volumes of the XRAID) were created.
> Five GFS filesystems were created, one on each logical volume. Even
> though there are currently four nodes, there are 12 journals for each
> filesystem to allow for planned cluster growth.
>
> Currently, each filesystem is mounted noatime, and tunebles
> quota_enforce and quota_account are set to 0.  I have posted the
> results of gfs_tool gettune /hq-san/nlp/nlp_qa below.  We have an
> application which depends heavily upon a find command that lists a
> number of files.  It looks something like this:
> find $delta_home -name summary -maxdepth 2 -type f
>
> Its output consists of thousands of files that exist on
> /hq-san/nlp/nlp_qa.  This command is CRAWLING at the moment.  An ext3
> filesystem would output hundreds of matches a second.  This GFS
> filesystem is currently outputting 100-200/minutes.  This is crippling
> one of our applications.  Any advice on tuning this filesystem for
> this kind of access would be greatly appreciated.
>
> Output from a gfs_tool df /hq-san/nlp_qa:
>
> odin / # gfs_tool df /hq-san/nlp/nlp_qa
> /hq-san/nlp/nlp_qa:
>  SB lock proto = "lock_dlm"
>  SB lock table = "boson:nlp_qa"
>  SB ondisk format = 1309
>  SB multihost format = 1401
>  Block size = 4096
>  Journals = 12
>  Resource Groups = 3009
>  Mounted lock proto = "lock_dlm"
>  Mounted lock table = "boson:nlp_qa"
>  Mounted host data = ""
>  Journal number = 1
>  Lock module flags =
>  Local flocks = FALSE
>  Local caching = FALSE
>  Oopses OK = FALSE
>
>  Type           Total          Used           Free           use%
>  ------------------------------------------------------------------------
>  inodes         15167101       15167101       0              100%
>  metadata       868298         750012         118286         86%
>  data           219476789      192088469      27388320       88%
>
>
>
> Output from a df -h:
>
> /dev/mapper/hq--san-cam_development 499G  201G  298G  41%
> /hq-san/nlp/cam_development
> /dev/mapper/hq--san-nlp_qa 899G  794G  105G  89% /hq-san/nlp/nlp_qa
> /dev/mapper/hq--san-svn_users 1.5T  1.3T  282G  82% /hq-san/nlp/svn_users
> /dev/mapper/hq--san-development 499G  373G  126G  75% /hq-san/nlp/development
> /dev/mapper/hq--san-prod_reports 1023G  680G  343G  67% /hq-san/nlp/prod_reports
>
> odin / # gfs_tool gettune /hq-san/nlp/nlp_qa
> ilimit1 = 100
> ilimit1_tries = 3
> ilimit1_min = 1
> ilimit2 = 500
> ilimit2_tries = 10
> ilimit2_min = 3
> demote_secs = 300
> incore_log_blocks = 1024
> jindex_refresh_secs = 60
> depend_secs = 60
> scand_secs = 5
> recoverd_secs = 60
> logd_secs = 1
> quotad_secs = 5
> inoded_secs = 15
> glock_purge = 0
> quota_simul_sync = 64
> quota_warn_period = 10
> atime_quantum = 3600
> quota_quantum = 60
> quota_scale = 1.0000   (1, 1)
> quota_enforce = 0
> quota_account = 0
> new_files_jdata = 0
> new_files_directio = 0
> max_atomic_write = 4194304
> max_readahead = 262144
> lockdump_size = 131072
> stall_secs = 600
> complain_secs = 10
> reclaim_limit = 5000
> entries_per_readdir = 32
> prefetch_secs = 10
> statfs_slots = 64
> max_mhc = 10000
> greedy_default = 100
> greedy_quantum = 25
> greedy_max = 250
> rgrp_try_threshold = 100
> statfs_fast = 0
> seq_readahead = 0
>
>
> Shawn
>
> --
> Linux-cluster mailing list
> Linux-cluster at redhat.com
> https://www.redhat.com/mailman/listinfo/linux-cluster
>



From lhh at redhat.com  Mon Feb  4 17:18:12 2008
From: lhh at redhat.com (Lon Hohberger)
Date: Mon, 04 Feb 2008 12:18:12 -0500
Subject: [Linux-cluster] CS5/ Question about behavior with a corrupted
	Quorum disk
In-Reply-To: <47A6BFE0.3000700@bull.net>
References: <47A6BFE0.3000700@bull.net>
Message-ID: <1202145492.1759.164.camel@ayanami.boston.devel.redhat.com>

On Mon, 2008-02-04 at 08:33 +0100, Alain Moulle wrote:
> Hi
> 
> Just for information, I wonder if this behavior is normal :
> I have a two-nodes cluster with a quorum disk, and the
> CS5 is started on both nodes with a service on each one.
> Quorum is working fine when I break the quorum disk format
> (with a mkfs on the device !) so that mkqisk -L returns
> none.

It will keep *trying* to operate.

> The behavior is : the CS5 is always working fine as if nothing
> has happen. I wonder if it is only due to the heuristics or
> if this behavior is simply the std behavior of CS5 with
> regard to the quorum disk ?

It /should/ throw warnings in the log for all the blocks that are
corrupt (and it will probably annoy you ;) ).  After 1 cycle, the blocks
corresponding to active cluster nodes will have correct/current data on
them, and life should continue, but reading the rest of the 16 node
blocks should continue throwing warnings:

[1533] warning: Error reading node ID block 3
[1533] warning: Error reading node ID block 4
[1533] warning: Error reading node ID block 5
[1533] warning: Error reading node ID block 6
[1533] warning: Error reading node ID block 7
...
[1533] warning: Error reading node ID block 16

(Granted, I used 'dd if=/dev/zero ...' instead mkfs)

Qdiskd will not function if you restart it, however, and nodes will be
unable to find the quorum disk after a reboot.  The header of the quorum
disk is not rewritten while qdiskd is running.  You'll have to run
mkqdisk to fix it - which should also work (but certainly isn't
recommended!).

This produced the following on the non-master node, but nothing
significant on the master node:

[1533] info: Node 1 shutdown
[1533] debug: Making bid for master
[1533] debug: Node 1 is marked master, but is dead.
[1533] debug: Node 1 is marked master, but is dead.
[1533] debug: Node 1 is marked master, but is dead.
[1533] debug: Node 1 is UP
[1533] info: Node 1 is the master

Looking at the code, if a node dies between the time you clobber qdisk
the quorum disk and the time qdiskd on that node writes a new block,
qdiskd won't evict that node.  Solution: Don't rub salt in cuts.

Also, intentionally corrupting your quorum disk could result in the
following:

https://bugzilla.redhat.com/show_bug.cgi?id=430264

-- Lon



From lhh at redhat.com  Mon Feb  4 17:49:23 2008
From: lhh at redhat.com (Lon Hohberger)
Date: Mon, 04 Feb 2008 12:49:23 -0500
Subject: [Linux-cluster] CS5/ Question about behavior with a corrupted
	Quorum disk
In-Reply-To: <1202145492.1759.164.camel@ayanami.boston.devel.redhat.com>
References: <47A6BFE0.3000700@bull.net>
	<1202145492.1759.164.camel@ayanami.boston.devel.redhat.com>
Message-ID: <1202147363.1759.166.camel@ayanami.boston.devel.redhat.com>

On Mon, 2008-02-04 at 12:18 -0500, Lon Hohberger wrote:
> On Mon, 2008-02-04 at 08:33 +0100, Alain Moulle wrote:
> > Hi
> > 
> > Just for information, I wonder if this behavior is normal :
> > I have a two-nodes cluster with a quorum disk, and the
> > CS5 is started on both nodes with a service on each one.
> > Quorum is working fine when I break the quorum disk format
> > (with a mkfs on the device !) so that mkqisk -L returns
> > none.
> 
> It will keep *trying* to operate.
> 
> > The behavior is : the CS5 is always working fine as if nothing
> > has happen. I wonder if it is only due to the heuristics or
> > if this behavior is simply the std behavior of CS5 with
> > regard to the quorum disk ?
> 
> It /should/ throw warnings in the log for all the blocks that are
> corrupt (and it will probably annoy you ;) ).  After 1 cycle, the blocks
> corresponding to active cluster nodes will have correct/current data on
> them, and life should continue, but reading the rest of the 16 node
> blocks should continue throwing warnings:
> 
> [1533] warning: Error reading node ID block 3
> [1533] warning: Error reading node ID block 4
> [1533] warning: Error reading node ID block 5
> [1533] warning: Error reading node ID block 6
> [1533] warning: Error reading node ID block 7
> ...
> [1533] warning: Error reading node ID block 16
> 
> (Granted, I used 'dd if=/dev/zero ...' instead mkfs)
> 
> Qdiskd will not function if you restart it, however, and nodes will be
> unable to find the quorum disk after a reboot.  The header of the quorum
> disk is not rewritten while qdiskd is running.  You'll have to run
> mkqdisk to fix it - which should also work (but certainly isn't
> recommended!).

Whoops - "should also work while the cluster is running (but certainly
isn't recommended)"

-- Lon




From abhramica at gmail.com  Tue Feb  5 06:03:05 2008
From: abhramica at gmail.com (Abhra Paul)
Date: Tue, 5 Feb 2008 11:33:05 +0530
Subject: [Linux-cluster] Cluster is slow
Message-ID: <8e3fbac10802042203j79785a84pf62d9818e964b202@mail.gmail.com>

Hi,

       I am using a cluster of 10 nodes. In node7,8,9,10  dirac is
running for 4 days. This dirac is also required huge amount of space.
Now when I am visiting individual node and issuing top ,o/p is not
showing and cursor is only blinking without any message or anything.
How I can solve this problem.


   With regards

    Abhra Paul



From jparsons at redhat.com  Tue Feb  5 06:13:17 2008
From: jparsons at redhat.com (jim parsons)
Date: Tue, 05 Feb 2008 01:13:17 -0500
Subject: [Linux-cluster] Cluster is slow
In-Reply-To: <8e3fbac10802042203j79785a84pf62d9818e964b202@mail.gmail.com>
References: <8e3fbac10802042203j79785a84pf62d9818e964b202@mail.gmail.com>
Message-ID: <1202191997.5859.3.camel@localhost.localdomain>

On Tue, 2008-02-05 at 11:33 +0530, Abhra Paul wrote:
> Hi,
> 
>        I am using a cluster of 10 nodes. In node7,8,9,10  dirac is
> running for 4 days. This dirac is also required huge amount of space.
> Now when I am visiting individual node and issuing top ,o/p is not
> showing and cursor is only blinking without any message or anything.
> How I can solve this problem.
> 
Can you provide some ancillary info, such as what version of cluster
software you are running on what hardware? Could you post your
cluster.conf file? Is this a new cluster, or has this cluster been
around for awhile working OK and this is a sudden problem?

-J



From abhramica at gmail.com  Tue Feb  5 07:37:53 2008
From: abhramica at gmail.com (Abhra Paul)
Date: Tue, 5 Feb 2008 13:07:53 +0530
Subject: [Linux-cluster] Cluster is slow
In-Reply-To: <1202191997.5859.3.camel@localhost.localdomain>
References: <8e3fbac10802042203j79785a84pf62d9818e964b202@mail.gmail.com>
	<1202191997.5859.3.camel@localhost.localdomain>
Message-ID: <8e3fbac10802042337w726e8973v6f0f909f99a527ca@mail.gmail.com>

On Feb 5, 2008 11:43 AM, jim parsons <jparsons at redhat.com> wrote:
>
> On Tue, 2008-02-05 at 11:33 +0530, Abhra Paul wrote:
> > Hi,
> >
> >        I am using a cluster of 10 nodes. In node7,8,9,10  dirac is
> > running for 4 days. This dirac is also required huge amount of space.
> > Now when I am visiting individual node and issuing top ,o/p is not
> > showing and cursor is only blinking without any message or anything.
> > How I can solve this problem.
> >
> Can you provide some ancillary info, such as what version of cluster
> software you are running on what hardware? Could you post your
> cluster.conf file? Is this a new cluster, or has this cluster been
> around for awhile working OK and this is a sudden problem?
>
> -J
>
> --
> Linux-cluster mailing list
> Linux-cluster at redhat.com
> https://www.redhat.com/mailman/listinfo/linux-cluster
>
-------------------------------------------------------------------------------------------------------------
As a cluster software I am using PBS package(pbs_server,
pbs_mom,pbs_schedl), and to submit the job I am using Moab Access
Potral job schedular. But I dont know the version of those clustering
software. Please tell me how I find the version. In my system there is
no cluster.conf file, I have searched by whereis command. This cluster
is approx 9 months old. This problem I am facing first time.

H/W configuration is as follows:
-- Total 12 nodes, one is master and others are slave.
-- I am using Quad-core intel processor
-- In slave node there is 12G Ram , in master 24G.
-- Infinyban , GHz switch

It is a BeoWoulf cluster. Also tell me where I can find the cluster
configuration file.



From marcos at digitaltecnologia.info  Tue Feb  5 13:39:42 2008
From: marcos at digitaltecnologia.info (Marcos Ferreira da Silva)
Date: Tue, 5 Feb 2008 08:39:42 -0500
Subject: [Linux-cluster] XEN VM Cluster
Message-ID: <ebafd72d2a694ba59b8d19e4cfa86c23@Mail61.safesecureweb.com>

I'm trying to do a two node cluster.
I want start a virtual machine at vserver1 and reallocate it to vserver2 if node 1 stop.
The VM is installed in a shared HP storage.
This access is made with two Emulex Corporation Zephyr-X LightPulse Fibre Channel Host Adapter.
If I start it manually which xm create its ok in both servers.
The partition is a LVM in /dev/VG2/LV01.
I install virtual machine directly in this partition.
The names vserver1 e vserv2 are in the /etc/hosts.
The cluster start but vserver2 join and after appear "Member Left".

I think that my problem is in fence device.
I don't have any equipament.
I have only the servers, storage, NICs and Emulex.

I didn't find any manual for this situation.

 
     +--- SWITCH ---+
     |              |
     |              |  
+----------+     +----------+
| XEN      |     | XEN      |
|   maq1   |     |          |
|          |     |          |
| vserver1 |     | vserver2 |
+----------+     +----------+
     |              |
     |              |
    +----------------+
    |  HP Storage    |
    +----------------+



My cluster.conf is: 

<?xml version="1.0"?>
<cluster alias="cluster1" config_version="13" name="cluster1">
        <fence_daemon clean_start="0" post_fail_delay="0" post_join_delay="3"/>
        <fence_xvmd family="ipv4" key_file="/etc/cluster/fence_xvm.key"/>
        <clusternodes>
                <clusternode name="vserver1.teste.br" nodeid="1" votes="1">
                        <fence>
                                <method name="1">
                                        <device domain="teste.br" name="maq1"/>
                                </method>
                        </fence>
                </clusternode>
                <clusternode name="vserver2.teste.br" nodeid="2" votes="1">
                        <fence/>
                </clusternode>
        </clusternodes>
        <cman expected_votes="1" two_node="1"/>
        <fencedevices>
                <fencedevice agent="fence_xvm" name="maq1" auth="none"/>
        </fencedevices>
        <rm>
                <failoverdomains>
                        <failoverdomain name="fodMaq1" ordered="1" restricted="1">
                                <failoverdomainnode name="vserver1.teste.br" priority="1"/>
                                <failoverdomainnode name="vserver2.teste.br" priority="2"/>
                        </failoverdomain>
                </failoverdomains>
                <resources/>
                <vm autostart="1" domain="fodMaq1" exclusive="0" name="maq1" path="/etc/xen" recovery="relocate"/>
        </rm>
</cluster>


------------------------------
Marcos Ferreira da Silva
Digital Tecnologia
Uberlandia-MG
(34) 9154-0150 / 3226-2534





From bfilipek at crscold.com  Tue Feb  5 14:26:16 2008
From: bfilipek at crscold.com (Brad Filipek)
Date: Tue, 5 Feb 2008 08:26:16 -0600
Subject: [Linux-cluster] EXT3 file system runs slow only right after it is
	mounted
Message-ID: <9C01E18EF3BC2448A3B1A4812EB87D02474D@SRVEDI.upark.crscold.com>

Hello,
 
I have a 2 node cluster connected via fibre to a SAN. This is an active/passive cluster and an EXT3 file system is mounted when the cluster services start on the active node. If we try to access data on this mount immediately after it is mounted, it takes an extremely long time. However, after about an hour, it runs extremely fast and is fine for good (until we un-mount and re-mount it, then it is slow again). So my question is, when you mount an ext3 partition (without any mount options), does it do something like scan the whole partition to see what is on the disk? This is the only thing I can think of that makes sense. The mount is 500GB in size. 
 
Thanks, 
Brad


Confidentiality Notice: This message is intended for the use of the individual or entity to which it is addressed and may contain information that is privileged, confidential and exempt from disclosure under applicable law. If the reader of this message is not the intended recipient or the employee or agent responsible for delivering this message to the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited. 

If you have received this communication in error, please notify us immediately by email reply or by telephone and immediately delete this message and any attachments.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://listman.redhat.com/archives/linux-cluster/attachments/20080205/81f161c2/attachment.htm>

From isplist at logicore.net  Tue Feb  5 15:38:08 2008
From: isplist at logicore.net (isplist at logicore.net)
Date: Tue, 5 Feb 2008 09:38:08 -0600
Subject: [Linux-cluster] NDMP
Message-ID: <2008259388.487694@leena>

Anyone aware of a good open source linux based NDMP server for an attached 
tape robot such as the Qualstar TLS series? 



Mike
 




From Alexandre.Racine at mhicc.org  Tue Feb  5 16:38:36 2008
From: Alexandre.Racine at mhicc.org (Alexandre Racine)
Date: Tue, 5 Feb 2008 11:38:36 -0500
Subject: [Linux-cluster] noatime
References: <200812910934.067039@leena>
	<C43CF0825BF59D4FBC1F6A2AF45EB88D6D12EE@cumulonimbus.RG.local>
Message-ID: <C43CF0825BF59D4FBC1F6A2AF45EB88D6D1322@cumulonimbus.RG.local>

(bump)

But, adding noatime to the fstab did not work in my case.

Is there another way for the noatime?



Alexandre Racine
514-461-1300 poste 3304
alexandre.racine at mhicc.org



-----Original Message-----
From: linux-cluster-bounces at redhat.com on behalf of Alexandre Racine
Sent: Tue 2008-01-29 11:37
To: linux clustering
Subject: RE: [Linux-cluster] noatime
 
Hi,

noatime will reduce traffic since if it's not there, each time you touch a file (read, write) it will change the value of the field "last access".

But, just adding it to the fstab did not work in my case.

Is there another way for the noatime?



Has for your isplist, look here http://sourceware.org/cluster/faq.html#gfs_slowaftermount


Alexandre Racine
514-461-1300 poste 3304
alexandre.racine at mhicc.org



-----Original Message-----
From: linux-cluster-bounces at redhat.com on behalf of isplist at logicore.net
Sent: Tue 2008-01-29 11:09
To: linux clustering
Subject: Re: [Linux-cluster] noatime
 
Were you trying this for a specific reason? I tried noatime to see if I could 
get a faster initial response time from the GFS volume. Every time I access 
it, there is a long delay initially, then things are fine until the next 
access.


On Tue, 29 Jan 2008 09:26:19 -0500, Alexandre Racine wrote:
> Hi all,
> 
> If I put in my fstab file:
> /dev/sdc5               /home           gfs     noatime
> 
> 
> Will it actually mount without atime? And how can I confirm this?
> 
> Thanks.
> 
> 
> Alexandre Racine
> 514-461-1300 poste 3304
> alexandre.racine at mhicc.org




--
Linux-cluster mailing list
Linux-cluster at redhat.com
https://www.redhat.com/mailman/listinfo/linux-cluster



-------------- next part --------------
A non-text attachment was scrubbed...
Name: winmail.dat
Type: application/ms-tnef
Size: 3280 bytes
Desc: not available
URL: <http://listman.redhat.com/archives/linux-cluster/attachments/20080205/4347fdde/attachment.bin>

From bpkroth at wisc.edu  Tue Feb  5 16:43:53 2008
From: bpkroth at wisc.edu (Brian Kroth)
Date: Tue, 05 Feb 2008 10:43:53 -0600
Subject: [Linux-cluster] noatime
In-Reply-To: <C43CF0825BF59D4FBC1F6A2AF45EB88D6D1322@cumulonimbus.RG.local>
References: <200812910934.067039@leena>
	<C43CF0825BF59D4FBC1F6A2AF45EB88D6D12EE@cumulonimbus.RG.local>
	<C43CF0825BF59D4FBC1F6A2AF45EB88D6D1322@cumulonimbus.RG.local>
Message-ID: <20080205164353.GA9669@wisc.edu>

You could try something like this:

mount -onoatime,remount /dev/sdX /mnt/Y

I'd like to see your fstab entries.

Brian

Alexandre Racine <Alexandre.Racine at mhicc.org>:
> (bump)
> 
> But, adding noatime to the fstab did not work in my case.
> 
> Is there another way for the noatime?
> 
> 
> 
> Alexandre Racine
> 514-461-1300 poste 3304
> alexandre.racine at mhicc.org
> 
> 
> 
> -----Original Message-----
> From: linux-cluster-bounces at redhat.com on behalf of Alexandre Racine
> Sent: Tue 2008-01-29 11:37
> To: linux clustering
> Subject: RE: [Linux-cluster] noatime
>  
> Hi,
> 
> noatime will reduce traffic since if it's not there, each time you touch a file (read, write) it will change the value of the field "last access".
> 
> But, just adding it to the fstab did not work in my case.
> 
> Is there another way for the noatime?
> 
> 
> 
> Has for your isplist, look here http://sourceware.org/cluster/faq.html#gfs_slowaftermount
> 
> 
> Alexandre Racine
> 514-461-1300 poste 3304
> alexandre.racine at mhicc.org
> 
> 
> 
> -----Original Message-----
> From: linux-cluster-bounces at redhat.com on behalf of isplist at logicore.net
> Sent: Tue 2008-01-29 11:09
> To: linux clustering
> Subject: Re: [Linux-cluster] noatime
>  
> Were you trying this for a specific reason? I tried noatime to see if I could 
> get a faster initial response time from the GFS volume. Every time I access 
> it, there is a long delay initially, then things are fine until the next 
> access.
> 
> 
> On Tue, 29 Jan 2008 09:26:19 -0500, Alexandre Racine wrote:
> > Hi all,
> > 
> > If I put in my fstab file:
> > /dev/sdc5               /home           gfs     noatime
> > 
> > 
> > Will it actually mount without atime? And how can I confirm this?
> > 
> > Thanks.
> > 
> > 
> > Alexandre Racine
> > 514-461-1300 poste 3304
> > alexandre.racine at mhicc.org
> 
> 
> 
> 
> --
> Linux-cluster mailing list
> Linux-cluster at redhat.com
> https://www.redhat.com/mailman/listinfo/linux-cluster
> 
> 
> 


> --
> Linux-cluster mailing list
> Linux-cluster at redhat.com
> https://www.redhat.com/mailman/listinfo/linux-cluster

-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/x-pkcs7-signature
Size: 2192 bytes
Desc: not available
URL: <http://listman.redhat.com/archives/linux-cluster/attachments/20080205/d9d460d6/attachment.bin>

From gordan at bobich.net  Tue Feb  5 16:45:15 2008
From: gordan at bobich.net (gordan at bobich.net)
Date: Tue, 5 Feb 2008 16:45:15 +0000 (GMT)
Subject: [Linux-cluster] noatime
In-Reply-To: <C43CF0825BF59D4FBC1F6A2AF45EB88D6D1322@cumulonimbus.RG.local>
References: <200812910934.067039@leena>
	<C43CF0825BF59D4FBC1F6A2AF45EB88D6D12EE@cumulonimbus.RG.local>
	<C43CF0825BF59D4FBC1F6A2AF45EB88D6D1322@cumulonimbus.RG.local>
Message-ID: <alpine.LRH.1.00.0802051643160.8917@skynet.shatteredsilicon.net>

IIRC, it only works on the clean mount. It won't work with
mount -o remount

The only other thing I can think of is that your netfs/gfs init script is 
broken.

Gordan

On Tue, 5 Feb 2008, Alexandre Racine wrote:

> (bump)
>
> But, adding noatime to the fstab did not work in my case.
>
> Is there another way for the noatime?
>
>
>
> Alexandre Racine
> 514-461-1300 poste 3304
> alexandre.racine at mhicc.org
>
>
>
> -----Original Message-----
> From: linux-cluster-bounces at redhat.com on behalf of Alexandre Racine
> Sent: Tue 2008-01-29 11:37
> To: linux clustering
> Subject: RE: [Linux-cluster] noatime
>
> Hi,
>
> noatime will reduce traffic since if it's not there, each time you touch a file (read, write) it will change the value of the field "last access".
>
> But, just adding it to the fstab did not work in my case.
>
> Is there another way for the noatime?
>
>
>
> Has for your isplist, look here http://sourceware.org/cluster/faq.html#gfs_slowaftermount
>
>
> Alexandre Racine
> 514-461-1300 poste 3304
> alexandre.racine at mhicc.org
>
>
>
> -----Original Message-----
> From: linux-cluster-bounces at redhat.com on behalf of isplist at logicore.net
> Sent: Tue 2008-01-29 11:09
> To: linux clustering
> Subject: Re: [Linux-cluster] noatime
>
> Were you trying this for a specific reason? I tried noatime to see if I could
> get a faster initial response time from the GFS volume. Every time I access
> it, there is a long delay initially, then things are fine until the next
> access.
>
>
> On Tue, 29 Jan 2008 09:26:19 -0500, Alexandre Racine wrote:
>> Hi all,
>>
>> If I put in my fstab file:
>> /dev/sdc5               /home           gfs     noatime
>>
>>
>> Will it actually mount without atime? And how can I confirm this?
>>
>> Thanks.
>>
>>
>> Alexandre Racine
>> 514-461-1300 poste 3304
>> alexandre.racine at mhicc.org
>
>
>
>
> --
> Linux-cluster mailing list
> Linux-cluster at redhat.com
> https://www.redhat.com/mailman/listinfo/linux-cluster
>
>
>
>



From lhh at redhat.com  Tue Feb  5 19:20:49 2008
From: lhh at redhat.com (Lon Hohberger)
Date: Tue, 05 Feb 2008 14:20:49 -0500
Subject: [Linux-cluster] EXT3 file system runs slow only right after it
	is mounted
In-Reply-To: <9C01E18EF3BC2448A3B1A4812EB87D02474D@SRVEDI.upark.crscold.com>
References: <9C01E18EF3BC2448A3B1A4812EB87D02474D@SRVEDI.upark.crscold.com>
Message-ID: <1202239249.21504.2.camel@ayanami.boston.devel.redhat.com>

On Tue, 2008-02-05 at 08:26 -0600, Brad Filipek wrote:
> Hello,
>  
> I have a 2 node cluster connected via fibre to a SAN. This is an
> active/passive cluster and an EXT3 file system is mounted when the
> cluster services start on the active node. If we try to access data on
> this mount immediately after it is mounted, it takes an extremely long
> time. However, after about an hour, it runs extremely fast and is fine
> for good (until we un-mount and re-mount it, then it is slow again).
> So my question is, when you mount an ext3 partition (without any mount
> options), does it do something like scan the whole partition to see
> what is on the disk? This is the only thing I can think of that makes
> sense. The mount is 500GB in size. 

Did you specify force_fsck or something?

-- Lon





From marcos at digitaltecnologia.info  Tue Feb  5 19:42:02 2008
From: marcos at digitaltecnologia.info (Marcos Ferreira da Silva)
Date: Tue, 5 Feb 2008 14:42:02 -0500
Subject: [Linux-cluster] Sharing GFS Partition
Message-ID: <72de961c26684084aa85d3fac994ee9b@Mail61.safesecureweb.com>

How could I share a partition in a storage with tow nodes running a service?

I create a partition and use mkfs
 mkfs.gfs -r2048 -p lock_dlm -t cluster1:gfsaluno -j 8 /dev/VGALUNO/LVAluno

 mount -t gfs /dev/VGALUNO/LVAluno /storage/aluno/

/sbin/mount.gfs: node not a member of the default fence domain
/sbin/mount.gfs: error mounting lockproto lock_dlm

My cluster.conf

<?xml version="1.0" ?>
<cluster alias="cluster1" config_version="16" name="cluster1">
        <fence_daemon clean_start="0" post_fail_delay="0" post_join_delay="3"/>
        <clusternodes>
                <clusternode name="vserver1.teste.br" nodeid="1" votes="1">
                        <fence/>
                </clusternode>
                <clusternode name="vserver2.teste.br" nodeid="2" votes="1">
                        <fence/>
                </clusternode>
        </clusternodes>
        <cman expected_votes="1" two_node="1"/>
        <fencedevices/>
        <rm>
                <failoverdomains/>
                <resources>
                        <clusterfs device="/dev/VGALUNO/LVAluno" force_unmount="0" fsid="63078" fstype="gfs" mountpoint="/storage/aluno" name="gfsaluno" options=""/>
                </resources>
                <service autostart="1" domain="fodAluno" name="teste">
                        <clusterfs ref="gfsaluno"/>
                </service>
        </rm>
</cluster>

------------------------------
Marcos Ferreira da Silva
Digital Tecnologia
Uberlandia-MG
(34) 9154-0150 / 3226-2534





From lhh at redhat.com  Tue Feb  5 19:54:48 2008
From: lhh at redhat.com (Lon Hohberger)
Date: Tue, 05 Feb 2008 14:54:48 -0500
Subject: [Linux-cluster] Sharing GFS Partition
In-Reply-To: <72de961c26684084aa85d3fac994ee9b@Mail61.safesecureweb.com>
References: <72de961c26684084aa85d3fac994ee9b@Mail61.safesecureweb.com>
Message-ID: <1202241288.21504.5.camel@ayanami.boston.devel.redhat.com>

On Tue, 2008-02-05 at 14:42 -0500, Marcos Ferreira da Silva wrote:
> How could I share a partition in a storage with tow nodes running a service?
> 
> I create a partition and use mkfs
>  mkfs.gfs -r2048 -p lock_dlm -t cluster1:gfsaluno -j 8 /dev/VGALUNO/LVAluno
> 
>  mount -t gfs /dev/VGALUNO/LVAluno /storage/aluno/
> 
> /sbin/mount.gfs: node not a member of the default fence domain
> /sbin/mount.gfs: error mounting lockproto lock_dlm
> 

chkconfig --level 2345 fenced on

(for starters). You *must* have fencing.

To make two services share it:

  <resources>
    <clusterfs ... name="mygfs" />
  </resources>
  <service name="foo">
    <clusterfs ref="mygfs"/>
  </service>
  <service name="bar">
    <clusterfs ref="mygfs"/>
  </service>

-- Lon



From isplist at logicore.net  Tue Feb  5 20:52:08 2008
From: isplist at logicore.net (isplist at logicore.net)
Date: Tue, 5 Feb 2008 14:52:08 -0600
Subject: [Linux-cluster] DLM Problem
In-Reply-To: <alpine.LRH.1.00.0801311521550.30904@skynet.shatteredsilicon.net>
Message-ID: <20082514528.743959@leena>

Who was it that said it was as simple as;

>yum install iscsi-target

Whew, if only it were that simple :). So far, I'm in some sort of hell. I've 
tried all sorts of ways to get this to install, nothing has worked. 

Now I'm trying to install this on a CentOS5 machine with no luck.

First, I tried the most basic;

# yum install iscsi-target
Loading "installonlyn" plugin
Setting up Install Process
Setting up repositories
Reading repository metadata in from local files
Parsing package install arguments
Nothing to do

# yum install iscsitarget
Loading "installonlyn" plugin
Setting up Install Process
Setting up repositories
Reading repository metadata in from local files
Parsing package install arguments
Nothing to do

Then I downloaded several versions and have been trying various combinations. 
The closest I've gotten so far is the following.

# yum install dkms-iscsi_trgt-0.4.13-2fc5.i386.rpm 
iscsitarget-0.4.13-2fc5.i386.rpm dkms-1.09-3.at.noarch.rpm

Running Transaction
  Installing: dkms                         ######################### [1/3]
  Installing: dkms-iscsi_trgt              ######################### [2/3]

Creating symlink /var/dkms/iscsi_trgt/0.4.13/source ->
                 /usr/src/iscsi_trgt-0.4.13

DKMS: Add Completed.

Preparing kernel 2.6.18-53.1.6.el5 for module build:
(This is not compiling a kernel, only just preparing kernel symbols)
Storing current .config to be restored when complete
Running Generic preparation routine
make mrproper....(bad exit status: 2)
Warning! Cannot find a .config file to prepare your kernel with.
Try using the --config option to specify where one can be found.
Your build will likely fail because of this.
make prepare-all....(bad exit status: 2)
make oldconfig....(bad exit status: 2)
/

Building module:
cleaning build area....
make KERNELRELEASE=2.6.18-53.1.6.el5 -C /lib/modules/2.6.18-53.1.6.el5/build 
SUBDIRS=/var/dkms/iscsi_trgt/0.4.13/build modules....(bad exit status: 2)

Error! Bad return status from module build for kernel: 2.6.18-53.1.6.el5
Consult the make.log in the build directory
/var/dkms/iscsi_trgt/0.4.13/build/ for more information.

Error! Could not locate iscsi_trgt.ko for module iscsi_trgt in the DKMS tree.
You must run a dkms build for kernel 2.6.18-53.1.6.el5 first.
  Installing: iscsitarget                  ######################### [3/3]

Installed: dkms.noarch 0:1.09-3.at dkms-iscsi_trgt.i386 0:0.4.13-2fc5 
iscsitarget.i386 0:0.4.13-2fc5
Complete!






From jbrassow at redhat.com  Tue Feb  5 20:56:36 2008
From: jbrassow at redhat.com (Jonathan Brassow)
Date: Tue, 5 Feb 2008 14:56:36 -0600
Subject: [Linux-cluster] Storage problem in Linux Cluster
In-Reply-To: <8e3fbac10802032216i37c01e9em34e1c7b81e7bd0da@mail.gmail.com>
References: <8e3fbac10802010127s511fa106w59302a27ec12161b@mail.gmail.com>
	<1201882379.1759.111.camel@ayanami.boston.devel.redhat.com>
	<8e3fbac10802032216i37c01e9em34e1c7b81e7bd0da@mail.gmail.com>
Message-ID: <87F62DE3-628F-4C89-AF9E-BD66462F260C@redhat.com>


On Feb 4, 2008, at 12:16 AM, Abhra Paul wrote:

> On Feb 1, 2008 9:42 PM, Lon Hohberger <lhh at redhat.com> wrote:
>> On Fri, 2008-02-01 at 14:57 +0530, Abhra Paul wrote:
>>> Respected Users
>>>
>>>    I have a problem in cluster. One user of this cluster needs huge
>>> amount of space. In this cluster one big partition(size 1TB) is
>>> mounted on /data . So I provide this amount of space for his program
>>> execution. At 1.30 PM he occupied 200GB of this storage(which is
>>> mounted on /data). Now when I am going to check this /data , about
>>> usage of space , using the command  du -sh * . In o/p there is no
>>> entry for /data and courser is only blinking without showing total  
>>> o/p
>>> as well as command prompt is not coming back. Also when I am issuing
>>> cd / same thing is happening . How I solve this problem.
>>
>> Could you check:
>>  cman_tool services
>>
>> -- Lon
>>
> -------------------------------------------------------------------------------------------------------------
>
> I have checked cman_tool services. But in my system there is no
> cman_tool , as well as there is no man page entry for cman_tool. Now ,
> how I will solve my problem. Please, help.
>
>
>                              With regards
>
>                              Abhra  Paul

What kind of cluster are you using?  If you don't have cman_tool, then  
you are likely not using rgmanager... or GFS... or cluster products  
that I am familiar with.  However, is there anything useful in /var/ 
log/messages?  Has the machine crashed?  hung? etc

  brassow



From isplist at logicore.net  Tue Feb  5 21:03:18 2008
From: isplist at logicore.net (isplist at logicore.net)
Date: Tue, 5 Feb 2008 15:03:18 -0600
Subject: [Linux-cluster] DLM Problem - Final Solution
In-Reply-To: <1201861486.29126.102.camel@admc.win-rar.local>
Message-ID: <20082515318.174544@leena>

Just an update on this way too long thread for anyone who ends up reading the 
whole thing.

I very much appreciate everyone's help on this, some good things have come 
from it, mostly, totally simplifying my longer term approach.

I think it start with Gordan's suggestion of building an aggregator and from 
there, it's expanded into other things for me based on the many suggestions 
from everyone on this and a couple of other threads.

I still don't know why I was having the strange GFS delays when first 
connecting or using a GFS volume. I thought it might be the storage device 
itself but that was not the case after a lot more testing. 

Talking about NFS got me pulling out my file servers and looking at them 
again. Turns out that it becomes my solution. at least for now. I might use 
GFS for one or two things but it's not going to be in production at this 
point. 

I'm finding that my NFS server will be perfect for sharing and serving up 
static web materials and that the aggregator suggestion ends up being the 
ongoing storage solution for media and other such data. 

I am going to limit my FC use to connecting storage to storage servers such as 
the NFS and aggregator servers. This will de-complicate my setup drastically 
and allow me to simply use a load balanced front end while not having to 
maintain a cluster of any sort. I am getting the same functionality for the 
most part, for the needs I have which are LAMP based services. 

I have several qualstar tape drives which have NDMP built which I will be 
hanging off of the FC network using bridges. For slower long term storage, I 
am trying to find a Linux solution which allows me to build an NDMP server 
which I can attach tape drives to, allowing the server to act as a NDMP front 
end to the tape drive/s.






From yanv at xandros.com  Tue Feb  5 21:27:31 2008
From: yanv at xandros.com (Yan Vinogradov)
Date: Tue, 5 Feb 2008 16:27:31 -0500
Subject: [Linux-cluster] problem with deleting a node from a cluster
Message-ID: <16468889.20851202246851369.JavaMail.root@ottmail>

I have a cluster of 3 nodes (RHEL5u1). Two are online and the third one is offline. I remove the offline one by propogating an updated version of cluster.conf by executing ccs_tool update command, then cman version command, and then I manually remove the cluster.conf from the offline node. Problem is after all these steps are performed clustat command on the remaining nodes in the cluster still shows the cluster as containing 3 nodes, including the one that I have just deleted. 

Thanks!
Yan
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://listman.redhat.com/archives/linux-cluster/attachments/20080205/db94afbb/attachment.htm>

From marcos at digitaltecnologia.info  Tue Feb  5 21:43:28 2008
From: marcos at digitaltecnologia.info (Marcos Ferreira da Silva)
Date: Tue, 5 Feb 2008 16:43:28 -0500
Subject: [Linux-cluster] Sharing GFS Partition
Message-ID: <1615ab867c794d99bd702ccebd73f828@Mail61.safesecureweb.com>

The cluster start but I couldn't mount.

The process fenced is started.
21399 ?        Ssl    0:00 /sbin/ccsd
21421 ?        Ss     0:00 /sbin/groupd
21429 ?        Ss     0:00 /sbin/fenced
21435 ?        Ss     0:00 /sbin/dlm_controld
21441 ?        Ss     0:00 /sbin/gfs_controld
21831 ?        Ssl    0:00 clvmd -T20


[root at vserver1 ~]# clustat
Member Status: Quorate

  Member Name                        ID   Status
  ------ ----                        ---- ------
  vserver1.teste.br                    1 Online, Local, rgmanager
  vserver2.teste.br                    2 Offline

  Service Name         Owner (Last)                   State
  ------- ----         ----- ------                   -----
  service:teste        (none)                         stopped

[root at vserver1 ~]# cman_tool services
type             level name       id       state
fence            0     default    00010001 JOIN_START_WAIT
[1]
dlm              1     clvmd      00020001 none
[1]
dlm              1     rgmanager  00030001 none
[1]

My cluster.conf:

<?xml version="1.0" ?>
<cluster alias="cluster1" config_version="18" name="cluster1">
        <fence_daemon clean_start="0" post_fail_delay="0" post_join_delay="3"/>
        <clusternodes>
                <clusternode name="vserver1.uniube.br" nodeid="1" votes="1">
                        <fence>
                                <method name="1"/>
                        </fence>
                </clusternode>
                <clusternode name="vserver2.uniube.br" nodeid="2" votes="1">
                        <fence/>
                </clusternode>
        </clusternodes>
        <cman expected_votes="1" two_node="1"/>
        <fencedevices/>
        <rm>
                <failoverdomains>
                        <failoverdomain name="gfsaluno" ordered="1" restricted="0">
                                <failoverdomainnode name="vserver1.uniube.br" priority="1"/>
                                <failoverdomainnode name="vserver2.uniube.br" priority="2"/>
                        </failoverdomain>
                </failoverdomains>
                <resources>
                        <clusterfs device="/dev/VGALUNO/LVAluno" force_unmount="0" fsid="63078" fstype="gfs" mountpoint="/storage/aluno" name="gfsaluno" options=""/>
                </resources>
                <service autostart="1" domain="gfsaluno" name="teste">
                        <clusterfs ref="gfsaluno"/>
                </service>
        </rm>
</cluster>

The service "teste" don't start.

[root at vserver1 cluster]# mount -t gfs /dev/VGALUNO/LVAluno /storage/aluno/
/sbin/mount.gfs: node not a member of the default fence domain
/sbin/mount.gfs: error mounting lockproto lock_dlm

[root at vserver1 cluster]# lsmod | grep dlm
lock_dlm               56009  1
gfs2                  522861  1 lock_dlm
dlm                   153185  13 lock_dlm
configfs               62301  2 dlm


------------------------------
Marcos Ferreira da Silva
Digital Tecnologia
Uberlandia-MG
(34) 9154-0150 / 3226-2534

-------- Mensagem Original --------
> De: Lon Hohberger <lhh at redhat.com>
> Enviado: ter?a-feira, 5 de fevereiro de 2008 17:55
> Para: marcos at digitaltecnologia.info, linux clustering <linux-cluster at redhat.com>
> Assunto: SPAM-LOW:  Re: [Linux-cluster] Sharing GFS Partition
> 
> On Tue, 2008-02-05 at 14:42 -0500, Marcos Ferreira da Silva wrote:
> > How could I share a partition in a storage with tow nodes running a service?
> > 
> > I create a partition and use mkfs
> >  mkfs.gfs -r2048 -p lock_dlm -t cluster1:gfsaluno -j 8 /dev/VGALUNO/LVAluno
> > 
> >  mount -t gfs /dev/VGALUNO/LVAluno /storage/aluno/
> > 
> > /sbin/mount.gfs: node not a member of the default fence domain
> > /sbin/mount.gfs: error mounting lockproto lock_dlm
> > 
> 
> chkconfig --level 2345 fenced on
> 
> (for starters). You *must* have fencing.
> 
> To make two services share it:
> 
>   <resources>
>     <clusterfs ... name="mygfs" />
>   </resources>
>   <service name="foo">
>     <clusterfs ref="mygfs"/>
>   </service>
>   <service name="bar">
>     <clusterfs ref="mygfs"/>
>   </service>
> 
> -- Lon 






From lhh at redhat.com  Tue Feb  5 21:46:49 2008
From: lhh at redhat.com (Lon Hohberger)
Date: Tue, 05 Feb 2008 16:46:49 -0500
Subject: [Linux-cluster] problem with deleting a node from a cluster
In-Reply-To: <16468889.20851202246851369.JavaMail.root@ottmail>
References: <16468889.20851202246851369.JavaMail.root@ottmail>
Message-ID: <1202248009.21504.7.camel@ayanami.boston.devel.redhat.com>

On Tue, 2008-02-05 at 16:27 -0500, Yan Vinogradov wrote:
> I have a cluster of 3 nodes (RHEL5u1). Two are online and the third
> one is offline. I remove the offline one by propogating an updated
> version of cluster.conf by executing ccs_tool update command, then
> cman version command, and then I manually remove the cluster.conf from
> the offline node. Problem is after all these steps are performed
> clustat command on the remaining nodes in the cluster still shows the
> cluster as containing 3 nodes, including the one that I have just
> deleted. 

Could be a bug.  Does it say 'estranged' in the output, or not?

-- Lon



From raycharles_man at yahoo.com  Wed Feb  6 03:55:58 2008
From: raycharles_man at yahoo.com (Ray Charles)
Date: Tue, 5 Feb 2008 19:55:58 -0800 (PST)
Subject: [Linux-cluster] XEN VM Cluster
In-Reply-To: <ebafd72d2a694ba59b8d19e4cfa86c23@Mail61.safesecureweb.com>
Message-ID: <384334.37325.qm@web32112.mail.mud.yahoo.com>

Hi Marcos,

Here are 2 links I found usefull when doing what
you're trying. 

http://www.linux.com/articles/55773

http://sources.redhat.com/cluster/wiki/VMClusterCookbook

I would also say be sure to give some attenttion to
the multicast messages between the hosts, make sure
that multicast is passing throught the switch. Seemed
to be a gotcha for me, and there's docs on that part
floating around.

-Ray



--- Marcos Ferreira da Silva
<marcos at digitaltecnologia.info> wrote:

> I'm trying to do a two node cluster.
> I want start a virtual machine at vserver1 and
> reallocate it to vserver2 if node 1 stop.
> The VM is installed in a shared HP storage.
> This access is made with two Emulex Corporation
> Zephyr-X LightPulse Fibre Channel Host Adapter.
> If I start it manually which xm create its ok in
> both servers.
> The partition is a LVM in /dev/VG2/LV01.
> I install virtual machine directly in this
> partition.
> The names vserver1 e vserv2 are in the /etc/hosts.
> The cluster start but vserver2 join and after appear
> "Member Left".
> 
> I think that my problem is in fence device.
> I don't have any equipament.
> I have only the servers, storage, NICs and Emulex.
> 
> I didn't find any manual for this situation.
> 
>  
>      +--- SWITCH ---+
>      |              |
>      |              |  
> +----------+     +----------+
> | XEN      |     | XEN      |
> |   maq1   |     |          |
> |          |     |          |
> | vserver1 |     | vserver2 |
> +----------+     +----------+
>      |              |
>      |              |
>     +----------------+
>     |  HP Storage    |
>     +----------------+
> 
> 
> 
> My cluster.conf is: 
> 
> <?xml version="1.0"?>
> <cluster alias="cluster1" config_version="13"
> name="cluster1">
>         <fence_daemon clean_start="0"
> post_fail_delay="0" post_join_delay="3"/>
>         <fence_xvmd family="ipv4"
> key_file="/etc/cluster/fence_xvm.key"/>
>         <clusternodes>
>                 <clusternode
> name="vserver1.teste.br" nodeid="1" votes="1">
>                         <fence>
>                                 <method name="1">
>                                         <device
> domain="teste.br" name="maq1"/>
>                                 </method>
>                         </fence>
>                 </clusternode>
>                 <clusternode
> name="vserver2.teste.br" nodeid="2" votes="1">
>                         <fence/>
>                 </clusternode>
>         </clusternodes>
>         <cman expected_votes="1" two_node="1"/>
>         <fencedevices>
>                 <fencedevice agent="fence_xvm"
> name="maq1" auth="none"/>
>         </fencedevices>
>         <rm>
>                 <failoverdomains>
>                         <failoverdomain
> name="fodMaq1" ordered="1" restricted="1">
>                                 <failoverdomainnode
> name="vserver1.teste.br" priority="1"/>
>                                 <failoverdomainnode
> name="vserver2.teste.br" priority="2"/>
>                         </failoverdomain>
>                 </failoverdomains>
>                 <resources/>
>                 <vm autostart="1" domain="fodMaq1"
> exclusive="0" name="maq1" path="/etc/xen"
> recovery="relocate"/>
>         </rm>
> </cluster>
> 
> 
> ------------------------------
> Marcos Ferreira da Silva
> Digital Tecnologia
> Uberlandia-MG
> (34) 9154-0150 / 3226-2534
> 
> 
> 
> --
> Linux-cluster mailing list
> Linux-cluster at redhat.com
>
https://www.redhat.com/mailman/listinfo/linux-cluster
> 



      ____________________________________________________________________________________
Looking for last minute shopping deals?  
Find them fast with Yahoo! Search.  http://tools.search.yahoo.com/newsearch/category.php?category=shopping



From fog at t.is  Wed Feb  6 07:22:32 2008
From: fog at t.is (=?iso-8859-1?Q?Finnur_=D6rn_Gu=F0mundsson_-_TM_Software?=)
Date: Wed, 6 Feb 2008 07:22:32 -0000
Subject: [Linux-cluster] DLM Problem
In-Reply-To: <20082514528.743959@leena>
References: <alpine.LRH.1.00.0801311521550.30904@skynet.shatteredsilicon.net>
	<20082514528.743959@leena>
Message-ID: <3DDA6E3E456E144DA3BB0A62A7F7F77901CAC88B@SKYHQAMX08.klasi.is>

Do you have kernel-devel installed ?

Bgrds,
Finnur

-----Original Message-----
From: linux-cluster-bounces at redhat.com [mailto:linux-cluster-bounces at redhat.com] On Behalf Of isplist at logicore.net
Sent: 5. febr?ar 2008 20:52
To: linux clustering
Subject: Re: [Linux-cluster] DLM Problem

Who was it that said it was as simple as;

>yum install iscsi-target

Whew, if only it were that simple :). So far, I'm in some sort of hell. I've 
tried all sorts of ways to get this to install, nothing has worked. 

Now I'm trying to install this on a CentOS5 machine with no luck.

First, I tried the most basic;

# yum install iscsi-target
Loading "installonlyn" plugin
Setting up Install Process
Setting up repositories
Reading repository metadata in from local files
Parsing package install arguments
Nothing to do

# yum install iscsitarget
Loading "installonlyn" plugin
Setting up Install Process
Setting up repositories
Reading repository metadata in from local files
Parsing package install arguments
Nothing to do

Then I downloaded several versions and have been trying various combinations. 
The closest I've gotten so far is the following.

# yum install dkms-iscsi_trgt-0.4.13-2fc5.i386.rpm 
iscsitarget-0.4.13-2fc5.i386.rpm dkms-1.09-3.at.noarch.rpm

Running Transaction
  Installing: dkms                         ######################### [1/3]
  Installing: dkms-iscsi_trgt              ######################### [2/3]

Creating symlink /var/dkms/iscsi_trgt/0.4.13/source ->
                 /usr/src/iscsi_trgt-0.4.13

DKMS: Add Completed.

Preparing kernel 2.6.18-53.1.6.el5 for module build:
(This is not compiling a kernel, only just preparing kernel symbols)
Storing current .config to be restored when complete
Running Generic preparation routine
make mrproper....(bad exit status: 2)
Warning! Cannot find a .config file to prepare your kernel with.
Try using the --config option to specify where one can be found.
Your build will likely fail because of this.
make prepare-all....(bad exit status: 2)
make oldconfig....(bad exit status: 2)
/

Building module:
cleaning build area....
make KERNELRELEASE=2.6.18-53.1.6.el5 -C /lib/modules/2.6.18-53.1.6.el5/build 
SUBDIRS=/var/dkms/iscsi_trgt/0.4.13/build modules....(bad exit status: 2)

Error! Bad return status from module build for kernel: 2.6.18-53.1.6.el5
Consult the make.log in the build directory
/var/dkms/iscsi_trgt/0.4.13/build/ for more information.

Error! Could not locate iscsi_trgt.ko for module iscsi_trgt in the DKMS tree.
You must run a dkms build for kernel 2.6.18-53.1.6.el5 first.
  Installing: iscsitarget                  ######################### [3/3]

Installed: dkms.noarch 0:1.09-3.at dkms-iscsi_trgt.i386 0:0.4.13-2fc5 
iscsitarget.i386 0:0.4.13-2fc5
Complete!




--
Linux-cluster mailing list
Linux-cluster at redhat.com
https://www.redhat.com/mailman/listinfo/linux-cluster



From marcos at digitaltecnologia.info  Wed Feb  6 09:28:22 2008
From: marcos at digitaltecnologia.info (Marcos Ferreira da Silva)
Date: Wed, 6 Feb 2008 04:28:22 -0500
Subject: [Linux-cluster] XEN VM Cluster
Message-ID: <8a2786b195ac4e778af0830a177e25d7@Mail61.safesecureweb.com>

Thanks for the docs.

In the VMClusterCookbook I don't understand where is the directory /guests.
Is a shared partition in a storage?
How could I configure this shared partition to be access for both machines?

Have I use a "disk in a file" like the doc? 
Or could I use a real partition in a shared storage (partitioon with no filesystem only created by lvm)?

------------------------------
Marcos Ferreira da Silva
Digital Tecnologia
Uberlandia-MG
(34) 9154-0150 / 3226-2534

-------- Mensagem Original --------
> De: Ray Charles <raycharles_man at yahoo.com>
> Enviado: quarta-feira, 6 de fevereiro de 2008 1:56
> Para: marcos at digitaltecnologia.info, linux clustering <linux-cluster at redhat.com>
> Assunto: Re: [Linux-cluster] XEN VM Cluster
> 
> Hi Marcos,
> 
> Here are 2 links I found usefull when doing what
> you're trying. 
> 
> http://www.linux.com/articles/55773
> 
> http://sources.redhat.com/cluster/wiki/VMClusterCookbook
> 
> I would also say be sure to give some attenttion to
> the multicast messages between the hosts, make sure
> that multicast is passing throught the switch. Seemed
> to be a gotcha for me, and there's docs on that part
> floating around.
> 
> -Ray
> 
> 
> 
> --- Marcos Ferreira da Silva
> <marcos at digitaltecnologia.info> wrote:
> 
> > I'm trying to do a two node cluster.
> > I want start a virtual machine at vserver1 and
> > reallocate it to vserver2 if node 1 stop.
> > The VM is installed in a shared HP storage.
> > This access is made with two Emulex Corporation
> > Zephyr-X LightPulse Fibre Channel Host Adapter.
> > If I start it manually which xm create its ok in
> > both servers.
> > The partition is a LVM in /dev/VG2/LV01.
> > I install virtual machine directly in this
> > partition.
> > The names vserver1 e vserv2 are in the /etc/hosts.
> > The cluster start but vserver2 join and after appear
> > "Member Left".
> > 
> > I think that my problem is in fence device.
> > I don't have any equipament.
> > I have only the servers, storage, NICs and Emulex.
> > 
> > I didn't find any manual for this situation.
> > 
> >  
> >      +--- SWITCH ---+
> >      |              |
> >      |              |  
> > +----------+     +----------+
> > | XEN      |     | XEN      |
> > |   maq1   |     |          |
> > |          |     |          |
> > | vserver1 |     | vserver2 |
> > +----------+     +----------+
> >      |              |
> >      |              |
> >     +----------------+
> >     |  HP Storage    |
> >     +----------------+
> > 
> > 
> > 
> > My cluster.conf is: 
> > 
> > <?xml version="1.0"?>
> > <cluster alias="cluster1" config_version="13"
> > name="cluster1">
> >         <fence_daemon clean_start="0"
> > post_fail_delay="0" post_join_delay="3"/>
> >         <fence_xvmd family="ipv4"
> > key_file="/etc/cluster/fence_xvm.key"/>
> >         <clusternodes>
> >                 <clusternode
> > name="vserver1.teste.br" nodeid="1" votes="1">
> >                         <fence>
> >                                 <method name="1">
> >                                         <device
> > domain="teste.br" name="maq1"/>
> >                                 </method>
> >                         </fence>
> >                 </clusternode>
> >                 <clusternode
> > name="vserver2.teste.br" nodeid="2" votes="1">
> >                         <fence/>
> >                 </clusternode>
> >         </clusternodes>
> >         <cman expected_votes="1" two_node="1"/>
> >         <fencedevices>
> >                 <fencedevice agent="fence_xvm"
> > name="maq1" auth="none"/>
> >         </fencedevices>
> >         <rm>
> >                 <failoverdomains>
> >                         <failoverdomain
> > name="fodMaq1" ordered="1" restricted="1">
> >                                 <failoverdomainnode
> > name="vserver1.teste.br" priority="1"/>
> >                                 <failoverdomainnode
> > name="vserver2.teste.br" priority="2"/>
> >                         </failoverdomain>
> >                 </failoverdomains>
> >                 <resources/>
> >                 <vm autostart="1" domain="fodMaq1"
> > exclusive="0" name="maq1" path="/etc/xen"
> > recovery="relocate"/>
> >         </rm>
> > </cluster>
> > 
> > 
> > ------------------------------
> > Marcos Ferreira da Silva
> > Digital Tecnologia
> > Uberlandia-MG
> > (34) 9154-0150 / 3226-2534
> > 
> > 
> > 
> > --
> > Linux-cluster mailing list
> > Linux-cluster at redhat.com
> >
> https://www.redhat.com/mailman/listinfo/linux-cluster
> > 
> 
> 
> 
>       ____________________________________________________________________________________
> Looking for last minute shopping deals?  
> Find them fast with Yahoo! Search.  http://tools.search.yahoo.com/newsearch/category.php?category=shopping 






From johannes.russek at io-consulting.net  Wed Feb  6 10:33:02 2008
From: johannes.russek at io-consulting.net (jr)
Date: Wed, 06 Feb 2008 11:33:02 +0100
Subject: [Linux-cluster] XEN VM Cluster
In-Reply-To: <8a2786b195ac4e778af0830a177e25d7@Mail61.safesecureweb.com>
References: <8a2786b195ac4e778af0830a177e25d7@Mail61.safesecureweb.com>
Message-ID: <1202293983.32498.32.camel@admc.win-rar.local>

Hi Marcos,

Am Mittwoch, den 06.02.2008, 04:28 -0500 schrieb Marcos Ferreira da
Silva:
> Thanks for the docs.
> 
> In the VMClusterCookbook I don't understand where is the directory /guests.
> Is a shared partition in a storage?
> How could I configure this shared partition to be access for both machines?

it should be anything that is available on both machines and shared
among them, i have a small GFS partition for that on my vm cluster, but
i guess you can use NFS for that too.

> 
> Have I use a "disk in a file" like the doc? 

that's nothing cluster specific but xen specific. it means that you use
a file as a "blockdevice" for your guest domain. (check xen docs)

> Or could I use a real partition in a shared storage (partitioon with no filesystem only created by lvm)?

even though the cookbooks suggested file images on a shared filesystem,
i simply used luns i carved from my SAN, which are then used as "phy"
blockdevices by the guests. Because i'm using multipathing on all
machines and thus have the luns in a consistent naming scheme on all
machines, it works pretty well for migration and failover.
enjoy,
johannes



From marcos at digitaltecnologia.info  Wed Feb  6 11:01:09 2008
From: marcos at digitaltecnologia.info (Marcos Ferreira da Silva)
Date: Wed, 6 Feb 2008 06:01:09 -0500
Subject: [Linux-cluster] XEN VM Cluster
Message-ID: <1e3d27e97a62428e9c581714cb2ebb96@Mail61.safesecureweb.com>

How could configure a partition to share a VM config for two machines?
Could you send me your cluster.conf for I compare with I want to do?

Then I need to have a shared partition to put the VMs config, that will be access by other machines, and a physical (LVM in a storage) to put the real machine.
Is it correct?

When I start a VM in a node 1 it will start in a physical device.
If I disconnect the node 1, will the vm migrate to node 2?
Will the clients connections lose?

I'm use a HP Storage and a two servers with multipath with emulex fiber channel.

------------------------------
Marcos Ferreira da Silva
Digital Tecnologia
Uberlandia-MG
(34) 9154-0150 / 3226-2534

-------- Mensagem Original --------
> De: jr <johannes.russek at io-consulting.net>
> Enviado: quarta-feira, 6 de fevereiro de 2008 8:35
> Para: marcos at digitaltecnologia.info, linux clustering <linux-cluster at redhat.com>
> Assunto: SPAM-LOW:  Re: [Linux-cluster] XEN VM Cluster
> 
> Hi Marcos,
> 
> Am Mittwoch, den 06.02.2008, 04:28 -0500 schrieb Marcos Ferreira da
> Silva:
> > Thanks for the docs.
> > 
> > In the VMClusterCookbook I don't understand where is the directory /guests.
> > Is a shared partition in a storage?
> > How could I configure this shared partition to be access for both machines?
> 
> it should be anything that is available on both machines and shared
> among them, i have a small GFS partition for that on my vm cluster, but
> i guess you can use NFS for that too.
> 
> > 
> > Have I use a "disk in a file" like the doc? 
> 
> that's nothing cluster specific but xen specific. it means that you use
> a file as a "blockdevice" for your guest domain. (check xen docs)
> 
> > Or could I use a real partition in a shared storage (partitioon with no filesystem only created by lvm)?
> 
> even though the cookbooks suggested file images on a shared filesystem,
> i simply used luns i carved from my SAN, which are then used as "phy"
> blockdevices by the guests. Because i'm using multipathing on all
> machines and thus have the luns in a consistent naming scheme on all
> machines, it works pretty well for migration and failover.
> enjoy,
> johannes 






From johannes.russek at io-consulting.net  Wed Feb  6 11:07:15 2008
From: johannes.russek at io-consulting.net (jr)
Date: Wed, 06 Feb 2008 12:07:15 +0100
Subject: [Linux-cluster] XEN VM Cluster
In-Reply-To: <1e3d27e97a62428e9c581714cb2ebb96@Mail61.safesecureweb.com>
References: <1e3d27e97a62428e9c581714cb2ebb96@Mail61.safesecureweb.com>
Message-ID: <1202296035.32498.37.camel@admc.win-rar.local>

> How could configure a partition to share a VM config for two machines?
> Could you send me your cluster.conf for I compare with I want to do?

no need for my cluster.conf. just use a GFS partition and it will be
fine. (don't forget to put it into fstab)

> 
> Then I need to have a shared partition to put the VMs config, that will be access by other machines, and a physical (LVM in a storage) to put the real machine.
> Is it correct?

i don't know what you mean by "real machine", but your guests not only
need the config, they will also need some storage for their system.
that's where you need a storage that's connected to your nodes, wether
it's luns, lvm lvs or image files, no matter. just keep in mind that if
you are using image files, you need to place them on GFS so that every
node in your cluster can access them the same.

> 
> When I start a VM in a node 1 it will start in a physical device.
> If I disconnect the node 1, will the vm migrate to node 2?
> Will the clients connections lose?

it's just failover, which means that if the cluster sees a problem with
one of the nodes, the other node will take over it's services, which
basically means that the vms will be started on the other node.
that does mean that your clients will get disconnected.

> 
> I'm use a HP Storage and a two servers with multipath with emulex fiber channel.

should be fine.

johannes



From marcos at digitaltecnologia.info  Wed Feb  6 11:34:45 2008
From: marcos at digitaltecnologia.info (Marcos Ferreira da Silva)
Date: Wed, 6 Feb 2008 06:34:45 -0500
Subject: [Linux-cluster] XEN VM Cluster
Message-ID: <c0e99d855e3a448eb1b8559cb04e32ca@Mail61.safesecureweb.com>

I have a problem when I'm trying to mount the partition.

Where is my mistake?

[root at vserver1 ~]# clustat
Member Status: Quorate

  Member Name                        ID   Status
  ------ ----                        ---- ------
  vserver1.teste.br                    1 Online, Local, rgmanager
  vserver2.teste.br                    2 Offline

  Service Name         Owner (Last)                   State
  ------- ----         ----- ------                   -----
  service:teste        (none)                         stopped

[root at vserver1 ~]# cat /etc/cluster/cluster.conf
<?xml version="1.0" ?>
<cluster alias="cluster1" config_version="19" name="cluster1">
        <fence_daemon clean_start="0" post_fail_delay="0" post_join_delay="3"/>
        <clusternodes>
                <clusternode name="vserver1.teste.br" nodeid="1" votes="1">
                        <fence>
                                <method name="1">
                                        <device name="manual" nodename="vserver1.teste.br"/>
                                </method>
                        </fence>
                </clusternode>
                <clusternode name="vserver2.teste.br" nodeid="2" votes="1">
                        <fence>
                                <method name="1">
                                        <device name="manual" nodename="vserver2.teste.br"/>
                                </method>
                        </fence>
                </clusternode>
        </clusternodes>
        <cman expected_votes="1" two_node="1"/>
        <fencedevices>
                <fencedevice agent="fence_manual" name="manual"/>
        </fencedevices>
        <rm>
                <failoverdomains>
                        <failoverdomain name="gfsaluno" ordered="1" restricted="0">
                                <failoverdomainnode name="vserver1.teste.br" priority="1"/>
                                <failoverdomainnode name="vserver2.teste.br" priority="2"/>
                        </failoverdomain>
                </failoverdomains>
                <resources>
                        <clusterfs device="/dev/VGALUNO/LVAluno" force_unmount="0" fsid="63078" fstype="gfs" mountpoint="/storage/aluno" name="gfsaluno" options=""/>
                </resources>
                <service autostart="1" domain="gfsaluno" name="teste">
                        <clusterfs ref="gfsaluno"/>
                </service>
        </rm>
</cluster>

[root at vserver1 ~]# mount -t gfs /dev/VGALUNO/LVAluno /storage/aluno/
/sbin/mount.gfs: node not a member of the default fence domain
/sbin/mount.gfs: error mounting lockproto lock_dlm

[root at vserver1 ~]# lsmod | grep dlm
lock_dlm               56009  1
gfs2                  522861  1 lock_dlm
dlm                   153185  13 lock_dlm
configfs               62301  2 dlm

[root at vserver1 ~]# gfs_edit /dev/VGALUNO/LVAluno

Block #10                of 31FF000          (superblock)
(1 of 4)
00010000 01161970 00000001 00000000 00000000 [...p............]
00010010 00000064 00000000 0000051D 00000579 [...d...........y]
00010020 00000000 00001000 0000000C 00000010 [................]
00010030 00000000 00000032 00000000 00000032 [.......2.......2]
00010040 00000000 00000033 00000000 00000033 [.......3.......3]
00010050 00000000 00000036 00000000 00000036 [.......6.......6]
00010060 6C6F636B 5F646C6D 00000000 00000000 [lock_dlm........]
00010070 00000000 00000000 00000000 00000000 [................]
00010080 00000000 00000000 00000000 00000000 [................]
00010090 00000000 00000000 00000000 00000000 [................]
000100A0 636C7573 74657231 3A676673 616C756E [cluster1:gfsalun]
000100B0 6F000000 00000000 00000000 00000000 [o...............]

------------------------------
Marcos Ferreira da Silva
Digital Tecnologia
Uberlandia-MG
(34) 9154-0150 / 3226-2534

-------- Mensagem Original --------
> De: jr <johannes.russek at io-consulting.net>
> Enviado: quarta-feira, 6 de fevereiro de 2008 9:07
> Para: marcos at digitaltecnologia.info, linux clustering <linux-cluster at redhat.com>
> Assunto: SPAM-LOW:  Re: [Linux-cluster] XEN VM Cluster
> 
> > How could configure a partition to share a VM config for two machines?
> > Could you send me your cluster.conf for I compare with I want to do?
> 
> no need for my cluster.conf. just use a GFS partition and it will be
> fine. (don't forget to put it into fstab)
> 
> > 
> > Then I need to have a shared partition to put the VMs config, that will be access by other machines, and a physical (LVM in a storage) to put the real machine.
> > Is it correct?
> 
> i don't know what you mean by "real machine", but your guests not only
> need the config, they will also need some storage for their system.
> that's where you need a storage that's connected to your nodes, wether
> it's luns, lvm lvs or image files, no matter. just keep in mind that if
> you are using image files, you need to place them on GFS so that every
> node in your cluster can access them the same.
> 
> > 
> > When I start a VM in a node 1 it will start in a physical device.
> > If I disconnect the node 1, will the vm migrate to node 2?
> > Will the clients connections lose?
> 
> it's just failover, which means that if the cluster sees a problem with
> one of the nodes, the other node will take over it's services, which
> basically means that the vms will be started on the other node.
> that does mean that your clients will get disconnected.
> 
> > 
> > I'm use a HP Storage and a two servers with multipath with emulex fiber channel.
> 
> should be fine.
> 
> johannes 






From bfilipek at crscold.com  Wed Feb  6 13:38:29 2008
From: bfilipek at crscold.com (Brad Filipek)
Date: Wed, 6 Feb 2008 07:38:29 -0600
Subject: [Linux-cluster] EXT3 file system runs slow only right after itis
	mounted
References: <9C01E18EF3BC2448A3B1A4812EB87D02474D@SRVEDI.upark.crscold.com>
	<1202239249.21504.2.camel@ayanami.boston.devel.redhat.com>
Message-ID: <9C01E18EF3BC2448A3B1A4812EB87D02474E@SRVEDI.upark.crscold.com>

Lon,
 
No I did not specify any mount options when creating the resource. Any ideas on what would help? 
 
 
Brad Filipek


________________________________

From: linux-cluster-bounces at redhat.com on behalf of Lon Hohberger
Sent: Tue 2/5/2008 1:20 PM
To: linux clustering
Subject: Re: [Linux-cluster] EXT3 file system runs slow only right after itis mounted



On Tue, 2008-02-05 at 08:26 -0600, Brad Filipek wrote:
> Hello,
> 
> I have a 2 node cluster connected via fibre to a SAN. This is an
> active/passive cluster and an EXT3 file system is mounted when the
> cluster services start on the active node. If we try to access data on
> this mount immediately after it is mounted, it takes an extremely long
> time. However, after about an hour, it runs extremely fast and is fine
> for good (until we un-mount and re-mount it, then it is slow again).
> So my question is, when you mount an ext3 partition (without any mount
> options), does it do something like scan the whole partition to see
> what is on the disk? This is the only thing I can think of that makes
> sense. The mount is 500GB in size.

Did you specify force_fsck or something?

-- Lon



--
Linux-cluster mailing list
Linux-cluster at redhat.com
https://www.redhat.com/mailman/listinfo/linux-cluster



Confidentiality Notice: This message is intended for the use of the individual or entity to which it is addressed and may contain information that is privileged, confidential and exempt from disclosure under applicable law. If the reader of this message is not the intended recipient or the employee or agent responsible for delivering this message to the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited. 

If you have received this communication in error, please notify us immediately by email reply or by telephone and immediately delete this message and any attachments.

-------------- next part --------------
A non-text attachment was scrubbed...
Name: winmail.dat
Type: application/ms-tnef
Size: 4865 bytes
Desc: not available
URL: <http://listman.redhat.com/archives/linux-cluster/attachments/20080206/ee9dcf45/attachment.bin>

From breeves at redhat.com  Wed Feb  6 13:47:42 2008
From: breeves at redhat.com (Bryn M. Reeves)
Date: Wed, 06 Feb 2008 13:47:42 +0000
Subject: [Linux-cluster] EXT3 file system runs slow only right after itis
	mounted
In-Reply-To: <9C01E18EF3BC2448A3B1A4812EB87D02474E@SRVEDI.upark.crscold.com>
References: <9C01E18EF3BC2448A3B1A4812EB87D02474D@SRVEDI.upark.crscold.com>	<1202239249.21504.2.camel@ayanami.boston.devel.redhat.com>
	<9C01E18EF3BC2448A3B1A4812EB87D02474E@SRVEDI.upark.crscold.com>
Message-ID: <47A9BA7E.6020503@redhat.com>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Brad Filipek wrote:
> Lon,
>  
> No I did not specify any mount options when creating the resource. Any ideas on what would help? 
>  
>  
> Brad Filipek

What's the host doing to the file system just after the mount?

If it's doing lots of directory traversal/stat (e.g. find, du, ls -R
/mount/path etc.) then it's going to be hammering the disks reading in
piles of metadata. If the nodes have a reasonable amount of RAM this'll
all end up cached, making later accesses faster.

If I run a find over one of my large data file systems immediately after
mounting it'll take an order of magnitude or two longer than the same
operation run against the same file system after a few hours of "normal
use".

If you're just reading in data files (and they fit into RAM), then you
might just be seeing the effects of the page cache.

Regards,
Bryn.

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.7 (GNU/Linux)
Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org

iD8DBQFHqbp+6YSQoMYUY94RAvnXAJ9Q/v4ZM2rhkIRDuL8LSbOec4kDqQCfb7++
F0BbA3EL2Vtr33H5BaHfeJI=
=NNEc
-----END PGP SIGNATURE-----



From jakub.suchy at enlogit.cz  Wed Feb  6 14:29:34 2008
From: jakub.suchy at enlogit.cz (Jakub Suchy)
Date: Wed, 6 Feb 2008 15:29:34 +0100
Subject: [Linux-cluster] LVM Snapshots
Message-ID: <20080206142934.GA24364@localhost>

Hi,
i am currently designing a cluster of XEN machines, having two nodes and
one shared storage (SAS). We have Recovery Point Objective of 15
minutes, so I am thinking about putting XEN machine on a LVM partition
and making a snapshot of this partition every 15 minutes.
Do anybody know any caveats of this? I wonder how fast would this be,
i am afraid that every 15 minutes is a little bit too often. XEN machine
will be Sybase server.

Thanks,
Jakub
-- 
Jakub Such? <jakub.suchy at enlogit.cz>
GSM: +420 - 777 817 949

Enlogit s.r.o, U Cukrovaru 509/4, 400 07 ?st? nad Labem
tel.: +420 - 474 745 159, fax: +420 - 474 745 160
e-mail: info at enlogit.cz, web: http://www.enlogit.cz



From gordan at bobich.net  Wed Feb  6 14:36:24 2008
From: gordan at bobich.net (gordan at bobich.net)
Date: Wed, 6 Feb 2008 14:36:24 +0000 (GMT)
Subject: [Linux-cluster] LVM Snapshots
In-Reply-To: <20080206142934.GA24364@localhost>
References: <20080206142934.GA24364@localhost>
Message-ID: <alpine.LRH.1.00.0802061428320.5255@skynet.shatteredsilicon.net>

On Wed, 6 Feb 2008, Jakub Suchy wrote:

> i am currently designing a cluster of XEN machines, having two nodes and
> one shared storage (SAS). We have Recovery Point Objective of 15
> minutes, so I am thinking about putting XEN machine on a LVM partition
> and making a snapshot of this partition every 15 minutes.
> Do anybody know any caveats of this? I wonder how fast would this be,
> i am afraid that every 15 minutes is a little bit too often. XEN machine
> will be Sybase server.

The caveat is that snapshot != backup. Not even close.
For a start, the underlying FS will be about as consistent as you'd expect 
it to be if you just power cycled the machine while it's working. A 
journalled FS will work around the need to fsck it, but your DB files (and 
in fact, any open files) are likely to end up not being internally 
consistent. You'd need to run check/repair on all your DB tables, for 
example. That may or may not be an acceptable solution for you, because it 
is not guaranteed that you will not lose any data.

Other than that, snapshotting frequency isn't a problem. It's just an undo 
log, not a complete copy. Bear in mind, though, that the more snapshots 
you concurrently have, the more times you multiply the writes, so the disk 
I/O preformance will degrade if you are running too many simultaneously.

Gordan



From isplist at logicore.net  Wed Feb  6 15:31:58 2008
From: isplist at logicore.net (isplist at logicore.net)
Date: Wed, 6 Feb 2008 09:31:58 -0600
Subject: [Linux-cluster] iSCSI Target Driver Install Problem
In-Reply-To: <3DDA6E3E456E144DA3BB0A62A7F7F77901CAC88B@SKYHQAMX08.klasi.is>
Message-ID: <20082693158.849919@leena>

On Wed, 6 Feb 2008 07:22:32 -0000, Finnur ?rn Gu?mundsson - TM Software wrote:
> Do you have kernel-devel installed ?

Yes, I do. That's one of the first things I did on the machine. Is it the fact 
that I'm trying to use CentOS in this case maybe? I don't like it as much as 
RHEL but I didn't have RHEL5 on network so had a CD problem while trying to 
install it. 

---

Now I'm trying to install this on a CentOS5 machine with no luck.

First, I tried the most basic;

# yum install iscsi-target
Loading "installonlyn" plugin
Setting up Install Process
Setting up repositories
Reading repository metadata in from local files
Parsing package install arguments
Nothing to do

# yum install iscsitarget
Loading "installonlyn" plugin
Setting up Install Process
Setting up repositories
Reading repository metadata in from local files
Parsing package install arguments
Nothing to do

Then I downloaded several versions and have been trying various combinations.
The closest I've gotten so far is the following.

# yum install dkms-iscsi_trgt-0.4.13-2fc5.i386.rpm
iscsitarget-0.4.13-2fc5.i386.rpm dkms-1.09-3.at.noarch.rpm

Running Transaction
  Installing: dkms                         ######################### [1/3]
  Installing: dkms-iscsi_trgt              ######################### [2/3]

Creating symlink /var/dkms/iscsi_trgt/0.4.13/source ->
                 /usr/src/iscsi_trgt-0.4.13

DKMS: Add Completed.

Preparing kernel 2.6.18-53.1.6.el5 for module build:
(This is not compiling a kernel, only just preparing kernel symbols)
Storing current .config to be restored when complete
Running Generic preparation routine
make mrproper....(bad exit status: 2)
Warning! Cannot find a .config file to prepare your kernel with.
Try using the --config option to specify where one can be found.
Your build will likely fail because of this.
make prepare-all....(bad exit status: 2)
make oldconfig....(bad exit status: 2)
/

Building module:
cleaning build area....
make KERNELRELEASE=2.6.18-53.1.6.el5 -C /lib/modules/2.6.18-53.1.6.el5/build
SUBDIRS=/var/dkms/iscsi_trgt/0.4.13/build modules....(bad exit status: 2)

Error! Bad return status from module build for kernel: 2.6.18-53.1.6.el5
Consult the make.log in the build directory
/var/dkms/iscsi_trgt/0.4.13/build/ for more information.

Error! Could not locate iscsi_trgt.ko for module iscsi_trgt in the DKMS tree.
You must run a dkms build for kernel 2.6.18-53.1.6.el5 first.
  Installing: iscsitarget                  ######################### [3/3]

Installed: dkms.noarch 0:1.09-3.at dkms-iscsi_trgt.i386 0:0.4.13-2fc5
iscsitarget.i386 0:0.4.13-2fc5
Complete!





From breeves at redhat.com  Wed Feb  6 15:48:47 2008
From: breeves at redhat.com (Bryn M. Reeves)
Date: Wed, 06 Feb 2008 15:48:47 +0000
Subject: [Linux-cluster] iSCSI Target Driver Install Problem
In-Reply-To: <20082693158.849919@leena>
References: <20082693158.849919@leena>
Message-ID: <47A9D6DF.1060302@redhat.com>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

isplist at logicore.net wrote:
> On Wed, 6 Feb 2008 07:22:32 -0000, Finnur ?rn Gu?mundsson - TM Software wrote:
>> Do you have kernel-devel installed ?
> 
> Yes, I do. That's one of the first things I did on the machine. Is it the fact 
> that I'm trying to use CentOS in this case maybe? I don't like it as much as 
> RHEL but I didn't have RHEL5 on network so had a CD problem while trying to 
> install it. 
> 
> ---
> 
> Now I'm trying to install this on a CentOS5 machine with no luck.
> 
> First, I tried the most basic;
> 
> # yum install iscsi-target
> Loading "installonlyn" plugin
> Setting up Install Process
> Setting up repositories
> Reading repository metadata in from local files
> Parsing package install arguments
> Nothing to do

In RHEL land, this would be in the "Cluster Storage" repo I believe. I
had a poke around in the CentOS mirrors and couldn't see the equivalent
(their repo structure seems quite different; extras, CentOS+ etc.).

Regards,
Bryn.

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.7 (GNU/Linux)
Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org

iD8DBQFHqdbf6YSQoMYUY94RAm3VAKCfTY0eI5HPHIWtRcWDeJTXyfz8wACgtf1q
REmX6ThZAZXjVABc4Lj11k0=
=uHmD
-----END PGP SIGNATURE-----



From isplist at logicore.net  Wed Feb  6 15:54:21 2008
From: isplist at logicore.net (isplist at logicore.net)
Date: Wed, 6 Feb 2008 09:54:21 -0600
Subject: [Linux-cluster] iSCSI Target Driver Install Problem
In-Reply-To: <47A9D6DF.1060302@redhat.com>
Message-ID: <20082695421.474368@leena>

> In RHEL land, this would be in the "Cluster Storage" repo I believe. I
> had a poke around in the CentOS mirrors and couldn't see the equivalent
> (their repo structure seems quite different; extras, CentOS+ etc.).

Yes, it wasn't in the repo, I found it using rpmfind then installed from the 
command line.

Mike





From breeves at redhat.com  Wed Feb  6 16:01:06 2008
From: breeves at redhat.com (Bryn M. Reeves)
Date: Wed, 06 Feb 2008 16:01:06 +0000
Subject: [Linux-cluster] iSCSI Target Driver Install Problem
In-Reply-To: <20082695421.474368@leena>
References: <20082695421.474368@leena>
Message-ID: <47A9D9C2.4040405@redhat.com>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

isplist at logicore.net wrote:
>> In RHEL land, this would be in the "Cluster Storage" repo I believe. I
>> had a poke around in the CentOS mirrors and couldn't see the equivalent
>> (their repo structure seems quite different; extras, CentOS+ etc.).
> 
> Yes, it wasn't in the repo, I found it using rpmfind then installed from the 
> command line.

I think the iscsi-target from RHEL's cluster storage and the iscsitarget
from rpmfind are quite different beasts; if you're following
instructions for the former you might find they don't apply to the
package you've installed (there are a number of different iSCSI target
implementation for Linux today).

Regards,
Bryn.

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.7 (GNU/Linux)
Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org

iD8DBQFHqdnC6YSQoMYUY94RAu5TAKCRRv1+Ie4jrRT7MuUJXk1ejfs8tgCeMOl6
UnDuKilHAlY8mcHYpdNLWsM=
=8Lt2
-----END PGP SIGNATURE-----



From isplist at logicore.net  Wed Feb  6 16:08:55 2008
From: isplist at logicore.net (isplist at logicore.net)
Date: Wed, 6 Feb 2008 10:08:55 -0600
Subject: [Linux-cluster] iSCSI Target Driver Install Problem
In-Reply-To: <47A9D9C2.4040405@redhat.com>
Message-ID: <20082610855.818722@leena>

> I think the iscsi-target from RHEL's cluster storage and the iscsitarget
> from rpmfind are quite different beasts; if you're following
> instructions for the former you might find they don't apply to the
> package you've installed (there are a number of different iSCSI target
> implementation for Linux today).

I'll have to spend more time looking into this also then. I set up rsync so 
that I could have a local repo but perhaps iscsi-target is part of another 
repo. On RHEL, I tried yum install iscsi-target and yum install iscsitarget 
with 'Nothing to do' as a result. That's why I'm guessing that it's part of 
another repo.

Mike






From johannes.russek at io-consulting.net  Wed Feb  6 16:11:33 2008
From: johannes.russek at io-consulting.net (jr)
Date: Wed, 06 Feb 2008 17:11:33 +0100
Subject: [Linux-cluster] iSCSI Target Driver Install Problem
In-Reply-To: <47A9D9C2.4040405@redhat.com>
References: <20082695421.474368@leena>  <47A9D9C2.4040405@redhat.com>
Message-ID: <1202314293.32498.47.camel@admc.win-rar.local>

actually, the centos thing is called scsi-target-utils:

scsi-target-utils.x86_64                 0.0-0.20070620snap.el5 base

it's in base, so no extra repos needed.
stay away from rpmfind if you don't want to screw your centos
updatepath.
regards,
johannes

Am Mittwoch, den 06.02.2008, 16:01 +0000 schrieb Bryn M. Reeves:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
> 
> isplist at logicore.net wrote:
> >> In RHEL land, this would be in the "Cluster Storage" repo I believe. I
> >> had a poke around in the CentOS mirrors and couldn't see the equivalent
> >> (their repo structure seems quite different; extras, CentOS+ etc.).
> > 
> > Yes, it wasn't in the repo, I found it using rpmfind then installed from the 
> > command line.
> 
> I think the iscsi-target from RHEL's cluster storage and the iscsitarget
> from rpmfind are quite different beasts; if you're following
> instructions for the former you might find they don't apply to the
> package you've installed (there are a number of different iSCSI target
> implementation for Linux today).
> 
> Regards,
> Bryn.
> 
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.7 (GNU/Linux)
> Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org
> 
> iD8DBQFHqdnC6YSQoMYUY94RAu5TAKCRRv1+Ie4jrRT7MuUJXk1ejfs8tgCeMOl6
> UnDuKilHAlY8mcHYpdNLWsM=
> =8Lt2
> -----END PGP SIGNATURE-----
> 
> --
> Linux-cluster mailing list
> Linux-cluster at redhat.com
> https://www.redhat.com/mailman/listinfo/linux-cluster



From bugsie.linux at gmail.com  Wed Feb  6 16:10:54 2008
From: bugsie.linux at gmail.com (bugsie)
Date: Thu, 07 Feb 2008 00:10:54 +0800
Subject: [Linux-cluster] problem with deleting a node from a cluster
In-Reply-To: <1202248009.21504.7.camel@ayanami.boston.devel.redhat.com>
References: <16468889.20851202246851369.JavaMail.root@ottmail>
	<1202248009.21504.7.camel@ayanami.boston.devel.redhat.com>
Message-ID: <47A9DC0E.9010406@gmail.com>

Hi Yan,

Is the configuration version greater than all the previous version?

Cheers,
bugsie

Lon Hohberger wrote:
> On Tue, 2008-02-05 at 16:27 -0500, Yan Vinogradov wrote:
>   
>> I have a cluster of 3 nodes (RHEL5u1). Two are online and the third
>> one is offline. I remove the offline one by propogating an updated
>> version of cluster.conf by executing ccs_tool update command, then
>> cman version command, and then I manually remove the cluster.conf from
>> the offline node. Problem is after all these steps are performed
>> clustat command on the remaining nodes in the cluster still shows the
>> cluster as containing 3 nodes, including the one that I have just
>> deleted. 
>>     
>
> Could be a bug.  Does it say 'estranged' in the output, or not?
>
> -- Lon
>
> --
> Linux-cluster mailing list
> Linux-cluster at redhat.com
> https://www.redhat.com/mailman/listinfo/linux-cluster
>
>   



From isplist at logicore.net  Wed Feb  6 16:20:34 2008
From: isplist at logicore.net (isplist at logicore.net)
Date: Wed, 6 Feb 2008 10:20:34 -0600
Subject: [Linux-cluster] iSCSI Target Driver Install Problem
In-Reply-To: <1202314293.32498.47.camel@admc.win-rar.local>
Message-ID: <200826102034.316800@leena>

On Wed, 06 Feb 2008 17:11:33 +0100, jr wrote:
> actually, the centos thing is called scsi-target-utils:
> scsi-target-utils.x86_64                 0.0-0.20070620snap.el5 base

Yup, installed immediately. Why do the different distro's use different names? 
Worse, why do sites like rpm.pbone.net (sorry, not rpmfind) show even more 
varieties? Is it because authors upload theirs with various names?

Mike


 
> it's in base, so no extra repos needed.
> stay away from rpmfind if you don't want to screw your centos
> updatepath.
> regards,
> johannes
> 
> Am Mittwoch, den 06.02.2008, 16:01 +0000 schrieb Bryn M. Reeves:
>> -----BEGIN PGP SIGNED MESSAGE-----
>> Hash: SHA1
>> 
>> isplist at logicore.net wrote:
>>>> In RHEL land, this would be in the "Cluster Storage" repo I believe. I
>>>> had a poke around in the CentOS mirrors and couldn't see the
>>>> equivalent
>>>> (their repo structure seems quite different; extras, CentOS+ etc.).
>>>> 
>>> Yes, it wasn't in the repo, I found it using rpmfind then installed
>>> from the
>>> command line.
>>> 
>> I think the iscsi-target from RHEL's cluster storage and the iscsitarget
>> from rpmfind are quite different beasts; if you're following
>> instructions for the former you might find they don't apply to the
>> package you've installed (there are a number of different iSCSI target
>> implementation for Linux today).
>> 
>> Regards,
>> Bryn.
>> 
>> -----BEGIN PGP SIGNATURE-----
>> Version: GnuPG v1.4.7 (GNU/Linux)
>> Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org
>> 
>> iD8DBQFHqdnC6YSQoMYUY94RAu5TAKCRRv1+Ie4jrRT7MuUJXk1ejfs8tgCeMOl6
>> UnDuKilHAlY8mcHYpdNLWsM=
>> =8Lt2
>> -----END PGP SIGNATURE-----
>> 
>> --
>> Linux-cluster mailing list
>> Linux-cluster at redhat.com
>> https://www.redhat.com/mailman/listinfo/linux-cluster
>> 
> --
> Linux-cluster mailing list
> Linux-cluster at redhat.com
> https://www.redhat.com/mailman/listinfo/linux-cluster






From breeves at redhat.com  Wed Feb  6 16:23:10 2008
From: breeves at redhat.com (Bryn M. Reeves)
Date: Wed, 06 Feb 2008 16:23:10 +0000
Subject: [Linux-cluster] iSCSI Target Driver Install Problem
In-Reply-To: <1202314293.32498.47.camel@admc.win-rar.local>
References: <20082695421.474368@leena> <47A9D9C2.4040405@redhat.com>
	<1202314293.32498.47.camel@admc.win-rar.local>
Message-ID: <47A9DEEE.1060304@redhat.com>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

jr wrote:
> actually, the centos thing is called scsi-target-utils:
> 
> scsi-target-utils.x86_64                 0.0-0.20070620snap.el5 base

Heh, what do you know - it's the same in RHEL (in Cluster-Storage):

http://rhn.redhat.com/errata/RHEA-2007-0713.html

I was looking for the wrong package name. :)

> it's in base, so no extra repos needed.
> stay away from rpmfind if you don't want to screw your centos

Sage words.

Regards,
Bryn.

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.7 (GNU/Linux)
Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org

iD8DBQFHqd7u6YSQoMYUY94RAj5QAJwJjWEPnbul4HF8cxXZnrX6w9iA8gCgiFvg
TIB62QoZIgitMeKU9ecF9ZE=
=fm8T
-----END PGP SIGNATURE-----



From breeves at redhat.com  Wed Feb  6 16:26:50 2008
From: breeves at redhat.com (Bryn M. Reeves)
Date: Wed, 06 Feb 2008 16:26:50 +0000
Subject: [Linux-cluster] iSCSI Target Driver Install Problem
In-Reply-To: <200826102034.316800@leena>
References: <200826102034.316800@leena>
Message-ID: <47A9DFCA.1010101@redhat.com>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

isplist at logicore.net wrote:
> On Wed, 06 Feb 2008 17:11:33 +0100, jr wrote:
>> actually, the centos thing is called scsi-target-utils:
>> scsi-target-utils.x86_64                 0.0-0.20070620snap.el5 base
> 
> Yup, installed immediately. Why do the different distro's use different names? 
> Worse, why do sites like rpm.pbone.net (sorry, not rpmfind) show even more 
> varieties? Is it because authors upload theirs with various names?
> 
> Mike

No - there are actually several different Linux iSCSI target
implementations. Ietd, Ardis, UNH, tgt, ...

The scsi-target-utils package uses the stgt project code and relies on
the kernel features that were merged into the mainline kernel in 2.6.20:

http://stgt.berlios.de/

Regards,
Bryn.

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.7 (GNU/Linux)
Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org

iD8DBQFHqd/K6YSQoMYUY94RAspSAJwNxHRTuYMlOs9VB7WmYOUBMtR3nACgsE63
f7InlwU4xx+ImMYdWptPn5Q=
=1mUS
-----END PGP SIGNATURE-----



From lhh at redhat.com  Wed Feb  6 17:20:41 2008
From: lhh at redhat.com (Lon Hohberger)
Date: Wed, 06 Feb 2008 12:20:41 -0500
Subject: [Linux-cluster] Re: problem deleting a node from a cluster
In-Reply-To: <23589450.23361202311274793.JavaMail.root@ottmail>
References: <23589450.23361202311274793.JavaMail.root@ottmail>
Message-ID: <1202318441.21504.57.camel@ayanami.boston.devel.redhat.com>

On Wed, 2008-02-06 at 10:21 -0500, Yan Vinogradov wrote:

> Could be a bug.  Does it say 'estranged' in the output, or not?
> 
> -- Lon
> 
> Hi Lon, yes, it does refer to the third node as estranged. Does it
> tell you anything?
> 

Clustat reports "Estranged" whenever it asks cman for a node list, and
the corresponding node does not show up in cluster.conf.

In your case, it means that cman still has state about the node despite
the configuration change in ccsd.

I'm not sure cman "purges" nodes that were dead (but part of
cluster.conf) that later are removed from cluster.conf.

Chrissie might know.

-- Lon



From lhh at redhat.com  Wed Feb  6 17:36:02 2008
From: lhh at redhat.com (Lon Hohberger)
Date: Wed, 06 Feb 2008 12:36:02 -0500
Subject: [Linux-cluster] Sharing GFS Partition
In-Reply-To: <1615ab867c794d99bd702ccebd73f828@Mail61.safesecureweb.com>
References: <1615ab867c794d99bd702ccebd73f828@Mail61.safesecureweb.com>
Message-ID: <1202319362.21504.67.camel@ayanami.boston.devel.redhat.com>

On Tue, 2008-02-05 at 16:43 -0500, Marcos Ferreira da Silva wrote:
> The cluster start but I couldn't mount.
> 
> The process fenced is started.
> 21399 ?        Ssl    0:00 /sbin/ccsd
> 21421 ?        Ss     0:00 /sbin/groupd
> 21429 ?        Ss     0:00 /sbin/fenced
> 21435 ?        Ss     0:00 /sbin/dlm_controld
> 21441 ?        Ss     0:00 /sbin/gfs_controld
> 21831 ?        Ssl    0:00 clvmd -T20
> 
> 

So, what's happening is that the node you have is trying to fence the
other node, but no fencing is configured, so it fails and retries
(forever!).  If you're running RHEL5 or from CVS/head or some other
recent version of cman, you can try this manual override to make fencing
complete:

while ! [ -e "/var/run/cluster/fenced_override" ]; do
  sleep 1
done
echo vserver2.teste.br > /var/run/cluster/fenced_override

... but if you are using Xen, the best thing to do is look here for
information about how to set up fencing so this doesn't happen in the
future:

  http://sources.redhat.com/cluster/wiki/VMClusterCookbook

Also, the FAQ article on CMAN may be helpful for understanding what's
going on:

  http://sources.redhat.com/cluster/wiki/FAQ/CMAN

-- Lon



From lhh at redhat.com  Wed Feb  6 18:45:00 2008
From: lhh at redhat.com (Lon Hohberger)
Date: Wed, 06 Feb 2008 13:45:00 -0500
Subject: [Linux-cluster] Re: problem deleting a node from a cluster
In-Reply-To: <1202318441.21504.57.camel@ayanami.boston.devel.redhat.com>
References: <23589450.23361202311274793.JavaMail.root@ottmail>
	<1202318441.21504.57.camel@ayanami.boston.devel.redhat.com>
Message-ID: <1202323500.21504.71.camel@ayanami.boston.devel.redhat.com>

On Wed, 2008-02-06 at 12:20 -0500, Lon Hohberger wrote:
> On Wed, 2008-02-06 at 10:21 -0500, Yan Vinogradov wrote:
> 
> > Could be a bug.  Does it say 'estranged' in the output, or not?
> > 
> > -- Lon
> > 
> > Hi Lon, yes, it does refer to the third node as estranged. Does it
> > tell you anything?
> > 
> 
> Clustat reports "Estranged" whenever it asks cman for a node list, and
> the corresponding node does not show up in cluster.conf.
> 
> In your case, it means that cman still has state about the node despite
> the configuration change in ccsd.
> 
> I'm not sure cman "purges" nodes that were dead (but part of
> cluster.conf) that later are removed from cluster.conf.
> 
> Chrissie might know.

To be simple, I could also just 'hide' the node in the output of clustat
if the node's "offline" + "estranged"... would that work for you? ;)

-- Lon



From yanv at xandros.com  Wed Feb  6 19:04:29 2008
From: yanv at xandros.com (Yan Vinogradov)
Date: Wed, 6 Feb 2008 14:04:29 -0500
Subject: [Linux-cluster] Re: problem deleting a node from a cluster
Message-ID: <1843832.25571202324669002.JavaMail.root@ottmail>



----- Original Message -----
From: Lon Hohberger <lhh at redhat.com>
Sent: Wed, 2/6/2008 1:45pm
To: linux clustering <linux-cluster at redhat.com>
Cc: Yan Vinogradov <yanv at xandros.com>
Subject: Re: [Linux-cluster] Re: problem deleting a node from a cluster

On Wed, 2008-02-06 at 12:20 -0500, Lon Hohberger wrote:
> On Wed, 2008-02-06 at 10:21 -0500, Yan Vinogradov wrote:
> 
> > Could be a bug.??Does it say 'estranged' in the output, or not?
> > 
> > -- Lon
> > 
> > Hi Lon, yes, it does refer to the third node as estranged. Does it
> > tell you anything?
> > 
> 
> Clustat reports "Estranged" whenever it asks cman for a node list, and
> the corresponding node does not show up in cluster.conf.
> 
> In your case, it means that cman still has state about the node despite
> the configuration change in ccsd.
> 
> I'm not sure cman "purges" nodes that were dead (but part of
> cluster.conf) that later are removed from cluster.conf.
> 
> Chrissie might know.

To be simple, I could also just 'hide' the node in the output of clustat
if the node's "offline" + "estranged"... would that work for you? ;)

-- Lon

Sure! What do you mean by 'hiding' the offline node?

Yan




From marcos at digitaltecnologia.info  Wed Feb  6 19:17:43 2008
From: marcos at digitaltecnologia.info (Marcos Ferreira da Silva)
Date: Wed, 06 Feb 2008 17:17:43 -0200
Subject: [Linux-cluster] XEN VM Cluster
In-Reply-To: <1202296035.32498.37.camel@admc.win-rar.local>
References: <1e3d27e97a62428e9c581714cb2ebb96@Mail61.safesecureweb.com>
	<1202296035.32498.37.camel@admc.win-rar.local>
Message-ID: <1202325463.3128.24.camel@matriz.digitaltecnologia.info>

I solved the mount gfs filesystem.

I forgot to run "fence_ack_manual -n vserver1.teste.br".

Now I can mount the gfs partition.

Now I have other problem.

One node appear offline to other node.

When I use command line to migrate online the vm to node 2 it's ok.
And of node 2 to node 1, too.

Appear this in messages file.

Feb  6 17:16:21 vserver1 fenced[5362]: fencing node "vserver2.uniube.br"
Feb  6 17:16:21 vserver1 fenced[5362]: fence "vserver2.uniube.br" failed


VSERVER1

[root at vserver1 ~]# clustat
Member Status: Quorate

  Member Name                        ID   Status
  ------ ----                        ---- ------
  vserver1.uniube.br                    1 Online, Local, rgmanager
  vserver2.uniube.br                    2 Offline

  Service Name         Owner (Last)                   State
  ------- ----         ----- ------                   -----
  vm:admin             vserver1.uniube.br             started
  vm:aluno             (none)                         disabled
  service:testeAdmin   (none)                         stopped
  service:testeAluno   (none)                         stopped


VSERVER2

[root at vserver2 ~]# clustat
Member Status: Quorate

  Member Name                        ID   Status
  ------ ----                        ---- ------
  vserver1.uniube.br                    1 Offline
  vserver2.uniube.br                    2 Online, Local, rgmanager

  Service Name         Owner (Last)                   State
  ------- ----         ----- ------                   -----
  vm:admin             (none)                         stopped
  vm:aluno             (none)                         disabled
  service:testeAdmin   vserver2.uniube.br             started
  service:testeAluno   vserver2.uniube.br             started



My cluster.conf:

<?xml version="1.0"?>
 <cluster alias="cluster1" config_version="24" name="cluster1">
  <fence_daemon clean_start="0" post_fail_delay="0"
             post_join_delay="3"/>
  <fence_xvmd family="ipv4" key_file="/etc/cluster/fence_xvm.key"/>
  <clusternodes>
    <clusternode name="vserver1.teste.br" nodeid="1" votes="1">
       <fence>
         <method name="1">
           <device domain="admin" name="admin"/>
         </method>
       </fence>
    </clusternode>
    <clusternode name="vserver2.teste.br" nodeid="2" votes="1">
       <fence>
         <method name="1">
           <device domain="aluno" name="aluno"/>
         </method>
      </fence>
    </clusternode>
  </clusternodes>
  <cman expected_votes="1" two_node="1"/>
  <fencedevices>
     <fencedevice agent="fence_xvm" name="admin"/>
     <fencedevice agent="fence_manual" name="manual"/>
  </fencedevices>
  <rm>
    <failoverdomains>
      <failoverdomain name="fodAdmin" ordered="1" restricted="1">
        <failoverdomainnode name="vserver1.teste.br" priority="2"/>
        <failoverdomainnode name="vserver2.teste.br" priority="1"/>
      </failoverdomain>
      <failoverdomain name="fodAluno" ordered="1" restricted="1">
        <failoverdomainnode name="vserver1.teste.br" priority="2"/>
        <failoverdomainnode name="vserver2.teste.br" priority="1"/>
      </failoverdomain>
    </failoverdomains>
    <resources>
      <clusterfs device="/dev/VGADMIN/LVAdmin" force_unmount="1"
fsid="63078" fstype="gfs" mountpoint="/storage/admin" name="gfsadmin"
options=""/>
      <clusterfs device="/dev/VGALUNO/LVAluno" force_unmount="1"
fsid="63078" fstype="gfs" mountpoint="/storage/aluno" name="gfsaluno"
options=""/>
    </resources>
    <vm autostart="1" domain="fodAdmin" exclusive="0" name="admin"
path="/etc/xen" recovery="relocate"/>
    <vm autostart="0" domain="fodAluno" exclusive="0" name="aluno"
path="/etc/xen" recovery="relocate"/>
    <service autostart="1" domain="gfsadmin" name="testeAdmin">
      <clusterfs ref="gfsadmin"/>
    </service>
    <service autostart="1" domain="gfsaluno" name="testeAluno">
      <clusterfs ref="gfsaluno"/>
    </service>
   </rm>
</cluster>



Em Qua, 2008-02-06 ?s 12:07 +0100, jr escreveu:
> > How could configure a partition to share a VM config for two machines?
> > Could you send me your cluster.conf for I compare with I want to do?
> 
> no need for my cluster.conf. just use a GFS partition and it will be
> fine. (don't forget to put it into fstab)
> 
> > 
> > Then I need to have a shared partition to put the VMs config, that will be access by other machines, and a physical (LVM in a storage) to put the real machine.
> > Is it correct?
> 
> i don't know what you mean by "real machine", but your guests not only
> need the config, they will also need some storage for their system.
> that's where you need a storage that's connected to your nodes, wether
> it's luns, lvm lvs or image files, no matter. just keep in mind that if
> you are using image files, you need to place them on GFS so that every
> node in your cluster can access them the same.
> 
> > 
> > When I start a VM in a node 1 it will start in a physical device.
> > If I disconnect the node 1, will the vm migrate to node 2?
> > Will the clients connections lose?
> 
> it's just failover, which means that if the cluster sees a problem with
> one of the nodes, the other node will take over it's services, which
> basically means that the vms will be started on the other node.
> that does mean that your clients will get disconnected.
> 
> > 
> > I'm use a HP Storage and a two servers with multipath with emulex fiber channel.
> 
> should be fine.
> 
> johannes
> 
-- 
_____________________________
Marcos Ferreira da Silva
DiGital Tecnologia
Uberl?ndia - MG
(34) 9154-0150 / 3226-2534





From lhh at redhat.com  Wed Feb  6 19:21:41 2008
From: lhh at redhat.com (Lon Hohberger)
Date: Wed, 06 Feb 2008 14:21:41 -0500
Subject: [Linux-cluster] Re: problem deleting a node from a cluster
In-Reply-To: <1843832.25571202324669002.JavaMail.root@ottmail>
References: <1843832.25571202324669002.JavaMail.root@ottmail>
Message-ID: <1202325701.21504.74.camel@ayanami.boston.devel.redhat.com>

On Wed, 2008-02-06 at 14:04 -0500, Yan Vinogradov wrote:

> To be simple, I could also just 'hide' the node in the output of clustat
> if the node's "offline" + "estranged"... would that work for you? ;)
> 
> -- Lon
> 
> Sure! What do you mean by 'hiding' the offline node?

Not displaying them in the output.  That is, once you remove the node
from cluster.conf and remove it from the cluster, clustat shouldn't
display it, even if it knows that the node existed at one time...

-- Lon



From marcos at digitaltecnologia.info  Wed Feb  6 19:21:58 2008
From: marcos at digitaltecnologia.info (Marcos Ferreira da Silva)
Date: Wed, 06 Feb 2008 17:21:58 -0200
Subject: [Linux-cluster] Sharing GFS Partition - SOLVED
In-Reply-To: <1202319362.21504.67.camel@ayanami.boston.devel.redhat.com>
References: <1615ab867c794d99bd702ccebd73f828@Mail61.safesecureweb.com>
	<1202319362.21504.67.camel@ayanami.boston.devel.redhat.com>
Message-ID: <1202325718.3128.28.camel@matriz.digitaltecnologia.info>

Thanks for all.

The problem was solved.

I opened other topic with subject "XEN VM Cluster" and I had help.

Em Qua, 2008-02-06 ?s 12:36 -0500, Lon Hohberger escreveu:
> On Tue, 2008-02-05 at 16:43 -0500, Marcos Ferreira da Silva wrote:
> > The cluster start but I couldn't mount.
> > 
> > The process fenced is started.
> > 21399 ?        Ssl    0:00 /sbin/ccsd
> > 21421 ?        Ss     0:00 /sbin/groupd
> > 21429 ?        Ss     0:00 /sbin/fenced
> > 21435 ?        Ss     0:00 /sbin/dlm_controld
> > 21441 ?        Ss     0:00 /sbin/gfs_controld
> > 21831 ?        Ssl    0:00 clvmd -T20
> > 
> > 
> 
> So, what's happening is that the node you have is trying to fence the
> other node, but no fencing is configured, so it fails and retries
> (forever!).  If you're running RHEL5 or from CVS/head or some other
> recent version of cman, you can try this manual override to make fencing
> complete:
> 
> while ! [ -e "/var/run/cluster/fenced_override" ]; do
>   sleep 1
> done
> echo vserver2.teste.br > /var/run/cluster/fenced_override
> 
> ... but if you are using Xen, the best thing to do is look here for
> information about how to set up fencing so this doesn't happen in the
> future:
> 
>   http://sources.redhat.com/cluster/wiki/VMClusterCookbook
> 
> Also, the FAQ article on CMAN may be helpful for understanding what's
> going on:
> 
>   http://sources.redhat.com/cluster/wiki/FAQ/CMAN
> 
> -- Lon
> 





From yanv at xandros.com  Wed Feb  6 19:25:01 2008
From: yanv at xandros.com (Yan Vinogradov)
Date: Wed, 6 Feb 2008 14:25:01 -0500
Subject: [Linux-cluster] Re: problem deleting a node from a cluster
In-Reply-To: <1202325701.21504.74.camel@ayanami.boston.devel.redhat.com>
Message-ID: <663105.26031202325901042.JavaMail.root@ottmail>


----- Original Message -----
From: Lon Hohberger <lhh at redhat.com>
Sent: Wed, 2/6/2008 2:21pm
To: Yan Vinogradov <yanv at xandros.com>
Cc: linux clustering <linux-cluster at redhat.com>
Subject: RE: [Linux-cluster] Re: problem deleting a node from a cluster

On Wed, 2008-02-06 at 14:04 -0500, Yan Vinogradov wrote:

> To be simple, I could also just 'hide' the node in the output of clustat
> if the node's "offline" + "estranged"... would that work for you? ;)
> 
> -- Lon
> 
> Sure! What do you mean by 'hiding' the offline node?

Not displaying them in the output.??That is, once you remove the node
from cluster.conf and remove it from the cluster, clustat shouldn't
display it, even if it knows that the node existed at one time...

-- Lon

Lon, that would be great!

Thanks,
Yan





From lhh at redhat.com  Wed Feb  6 19:46:10 2008
From: lhh at redhat.com (Lon Hohberger)
Date: Wed, 06 Feb 2008 14:46:10 -0500
Subject: [Linux-cluster] [PATCH] Don't show offline + estranged members
In-Reply-To: <663105.26031202325901042.JavaMail.root@ottmail>
References: <663105.26031202325901042.JavaMail.root@ottmail>
Message-ID: <1202327170.21504.79.camel@ayanami.boston.devel.redhat.com>

This patch prevents the 'clustat' utility from showing members which:

* are not part of the configuration, and
* offline/dead/etc.

-- Lon


Index: clustat.c
===================================================================
RCS file: /cvs/cluster/cluster/rgmanager/src/utils/clustat.c,v
retrieving revision 1.38
diff -u -r1.38 clustat.c
--- clustat.c	10 Dec 2007 18:11:56 -0000 1.38
+++ clustat.c	6 Feb 2008 19:34:35 -0000
@@ -719,6 +719,10 @@
 void
 txt_member_state(cman_node_t *node, int nodesize)
 {
+	/* If it's down and not in cluster.conf, don't show it */
+	if ((node->cn_member & (FLAG_NOCFG | FLAG_UP)) == FLAG_NOCFG)
+		return;
+
 	printf(" %-*.*s ", nodesize, nodesize, node->cn_name);
 	printf("%4d ", node->cn_nodeid);
 
@@ -754,6 +758,10 @@
 void
 xml_member_state(cman_node_t *node)
 {
+	/* If it's down and not in cluster.conf, don't show it */
+	if ((node->cn_member & (FLAG_NOCFG | FLAG_UP)) == FLAG_NOCFG)
+		return;
+
 	printf("    <node name=\"%s\" state=\"%d\" local=\"%d\" "
 	       "estranged=\"%d\" rgmanager=\"%d\" rgmanager_master=\"%d\" "
 	       "qdisk=\"%d\" nodeid=\"0x%08x\"/>\n",




From Alexandre.Racine at mhicc.org  Wed Feb  6 21:31:57 2008
From: Alexandre.Racine at mhicc.org (Alexandre Racine)
Date: Wed, 6 Feb 2008 16:31:57 -0500
Subject: [Linux-cluster] noatime
References: <200812910934.067039@leena><C43CF0825BF59D4FBC1F6A2AF45EB88D6D12EE@cumulonimbus.RG.local><C43CF0825BF59D4FBC1F6A2AF45EB88D6D1322@cumulonimbus.RG.local>
	<alpine.LRH.1.00.0802051643160.8917@skynet.shatteredsilicon.net>
Message-ID: <C43CF0825BF59D4FBC1F6A2AF45EB88D6D133D@cumulonimbus.RG.local>

Gordan,

>The only other thing I can think of is that your netfs/gfs init script is 
>broken.


Are you talking about the /etc/init.d/gfs script? Currently, I added this script in the startup. But should it start automatitly just like a nfs mount in the fstab?

Thanks.


This is my GFS part in my fstab (for Brian)
-------------
#
# iSCSI volumes (GFS)
#
/dev/sdd5               /home       gfs                 noatime
--------------

Alexandre Racine
514-461-1300 poste 3304
alexandre.racine at mhicc.org



-----Original Message-----
From: linux-cluster-bounces at redhat.com on behalf of gordan at bobich.net
Sent: Tue 2008-02-05 11:45
To: linux clustering
Subject: RE: [Linux-cluster] noatime
 
IIRC, it only works on the clean mount. It won't work with
mount -o remount

The only other thing I can think of is that your netfs/gfs init script is 
broken.

Gordan

On Tue, 5 Feb 2008, Alexandre Racine wrote:

> (bump)
>
> But, adding noatime to the fstab did not work in my case.
>
> Is there another way for the noatime?
>
>
>
> Alexandre Racine
> 514-461-1300 poste 3304
> alexandre.racine at mhicc.org
>
>
>
> -----Original Message-----
> From: linux-cluster-bounces at redhat.com on behalf of Alexandre Racine
> Sent: Tue 2008-01-29 11:37
> To: linux clustering
> Subject: RE: [Linux-cluster] noatime
>
> Hi,
>
> noatime will reduce traffic since if it's not there, each time you touch a file (read, write) it will change the value of the field "last access".
>
> But, just adding it to the fstab did not work in my case.
>
> Is there another way for the noatime?
>
>
>
> Has for your isplist, look here http://sourceware.org/cluster/faq.html#gfs_slowaftermount
>
>
> Alexandre Racine
> 514-461-1300 poste 3304
> alexandre.racine at mhicc.org
>
>
>
> -----Original Message-----
> From: linux-cluster-bounces at redhat.com on behalf of isplist at logicore.net
> Sent: Tue 2008-01-29 11:09
> To: linux clustering
> Subject: Re: [Linux-cluster] noatime
>
> Were you trying this for a specific reason? I tried noatime to see if I could
> get a faster initial response time from the GFS volume. Every time I access
> it, there is a long delay initially, then things are fine until the next
> access.
>
>
> On Tue, 29 Jan 2008 09:26:19 -0500, Alexandre Racine wrote:
>> Hi all,
>>
>> If I put in my fstab file:
>> /dev/sdc5               /home           gfs     noatime
>>
>>
>> Will it actually mount without atime? And how can I confirm this?
>>
>> Thanks.
>>
>>
>> Alexandre Racine
>> 514-461-1300 poste 3304
>> alexandre.racine at mhicc.org
>
>
>
>
> --
> Linux-cluster mailing list
> Linux-cluster at redhat.com
> https://www.redhat.com/mailman/listinfo/linux-cluster
>
>
>
>

--
Linux-cluster mailing list
Linux-cluster at redhat.com
https://www.redhat.com/mailman/listinfo/linux-cluster

-------------- next part --------------
A non-text attachment was scrubbed...
Name: winmail.dat
Type: application/ms-tnef
Size: 3800 bytes
Desc: not available
URL: <http://listman.redhat.com/archives/linux-cluster/attachments/20080206/84bff07c/attachment.bin>

From bpkroth at wisc.edu  Wed Feb  6 23:26:17 2008
From: bpkroth at wisc.edu (Brian Kroth)
Date: Wed, 06 Feb 2008 17:26:17 -0600
Subject: [Linux-cluster] noatime
In-Reply-To: <C43CF0825BF59D4FBC1F6A2AF45EB88D6D133D@cumulonimbus.RG.local>
References: <200812910934.067039@leena>
	<C43CF0825BF59D4FBC1F6A2AF45EB88D6D12EE@cumulonimbus.RG.local>
	<C43CF0825BF59D4FBC1F6A2AF45EB88D6D1322@cumulonimbus.RG.local>
	<alpine.LRH.1.00.0802051643160.8917@skynet.shatteredsilicon.net>
	<C43CF0825BF59D4FBC1F6A2AF45EB88D6D133D@cumulonimbus.RG.local>
Message-ID: <20080206232617.GB5771@odin.hslc.wisc.edu>

Alexandre Racine <Alexandre.Racine at mhicc.org>:
> Gordan,
> 
> >The only other thing I can think of is that your netfs/gfs init script is 
> >broken.
> 
> 
> Are you talking about the /etc/init.d/gfs script? Currently, I added this script in the startup. But should it start automatitly just like a nfs mount in the fstab?
> 
> Thanks.

Look in the script itself and make sure that it's making use of the options you
define in your fstab.  I had to fix the old one on gentoo before it worked as
expected.

Brian

-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/x-pkcs7-signature
Size: 2192 bytes
Desc: not available
URL: <http://listman.redhat.com/archives/linux-cluster/attachments/20080206/bf909035/attachment.bin>

From prakash.c-k at hp.com  Thu Feb  7 07:03:28 2008
From: prakash.c-k at hp.com (Kesavan, Prakash C)
Date: Thu, 7 Feb 2008 12:33:28 +0530
Subject: [Linux-cluster] Help : CONFIGURING REDHAT CLUSTER WITH
	CONGA-RHEL5(active /Passive)
In-Reply-To: <663105.26031202325901042.JavaMail.root@ottmail>
Message-ID: <7496B97B2FDFD443B185F157079888B103D51410@bgeexc05.asiapacific.cpqcorp.net>


Hi All,

I am in a project in which we are suppose to configure redhat cluster.

The following is the clients requirement.

They want to configure a redhat cluster suit for there three tire web
application(Apache,jboss,mysql,).They need to configure the server in
active passive mode.

We are planning to configure mysql active in one machine and passive in
other machine then jboss active in one machine and passive in other
machine. (not sure whether it is possible).

We have a san storage also.

Could any body have done the set up earlier the same with two node,
request to share the knowledge.

The main constraint now is  1) "How to setup the active passive setup in
conga"
				    2) "What is the stability of the
configuration with conga any limitation compairing with the
method using files"
				    3)  Any body have any other method
of configuring the setup. using conventional method using
files.
				    4) Fencing configuration with
ILO.power switch. Script for password sharing..etc...



Thanks in advance
Prakash C Kesavan



From singh.rajeshwar at gmail.com  Thu Feb  7 07:32:06 2008
From: singh.rajeshwar at gmail.com (Rajesh singh)
Date: Thu, 7 Feb 2008 13:02:06 +0530
Subject: [Linux-cluster] Help : CONFIGURING REDHAT CLUSTER WITH
	CONGA-RHEL5(active /Passive)
In-Reply-To: <7496B97B2FDFD443B185F157079888B103D51410@bgeexc05.asiapacific.cpqcorp.net>
References: <663105.26031202325901042.JavaMail.root@ottmail>
	<7496B97B2FDFD443B185F157079888B103D51410@bgeexc05.asiapacific.cpqcorp.net>
Message-ID: <e2a5a8050802062332pbbd9bf9r28dda372ec841282@mail.gmail.com>

Hi Kesavan,
Take a simple approach:
a) Configure MySQL and Active Passive mode
b) Use JBoss clustering (it is inbuilt with product) feature to cluster
JBoss
c) If you are not comfortable with conga, use system-config-cluster to
configure
cluster.

regards


On Feb 7, 2008 12:33 PM, Kesavan, Prakash C <prakash.c-k at hp.com> wrote:

>
> Hi All,
>
> I am in a project in which we are suppose to configure redhat cluster.
>
> The following is the clients requirement.
>
> They want to configure a redhat cluster suit for there three tire web
> application(Apache,jboss,mysql,).They need to configure the server in
> active passive mode.
>
> We are planning to configure mysql active in one machine and passive in
> other machine then jboss active in one machine and passive in other
> machine. (not sure whether it is possible).
>
> We have a san storage also.
>
> Could any body have done the set up earlier the same with two node,
> request to share the knowledge.
>
> The main constraint now is  1) "How to setup the active passive setup in
> conga"
>                                    2) "What is the stability of the
> configuration with conga any limitation compairing with the
> method using files"
>                                    3)  Any body have any other method
> of configuring the setup. using conventional method using
> files.
>                                    4) Fencing configuration with
> ILO.power switch. Script for password sharing..etc...
>
>
>
> Thanks in advance
> Prakash C Kesavan
>
> --
> Linux-cluster mailing list
> Linux-cluster at redhat.com
> https://www.redhat.com/mailman/listinfo/linux-cluster
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://listman.redhat.com/archives/linux-cluster/attachments/20080207/b9451846/attachment.htm>

From prakash.c-k at hp.com  Thu Feb  7 07:34:58 2008
From: prakash.c-k at hp.com (Kesavan, Prakash C)
Date: Thu, 7 Feb 2008 13:04:58 +0530
Subject: [Linux-cluster] Help : CONFIGURING REDHAT CLUSTER
	WITHCONGA-RHEL5(active /Passive)
In-Reply-To: <e2a5a8050802062332pbbd9bf9r28dda372ec841282@mail.gmail.com>
Message-ID: <7496B97B2FDFD443B185F157079888B103D5144F@bgeexc05.asiapacific.cpqcorp.net>

thanks  a lot.
 
-prakash

________________________________

From: linux-cluster-bounces at redhat.com
[mailto:linux-cluster-bounces at redhat.com] On Behalf Of Rajesh singh
Sent: Thursday, February 07, 2008 1:02 PM
To: linux clustering
Subject: Re: [Linux-cluster] Help : CONFIGURING REDHAT CLUSTER
WITHCONGA-RHEL5(active /Passive)


Hi Kesavan,
Take a simple approach:
a) Configure MySQL and Active Passive mode
b) Use JBoss clustering (it is inbuilt with product) feature to cluster
JBoss
c) If you are not comfortable with conga, use system-config-cluster to
configure
cluster.

regards



On Feb 7, 2008 12:33 PM, Kesavan, Prakash C <prakash.c-k at hp.com> wrote:



	Hi All,
	
	I am in a project in which we are suppose to configure redhat
cluster.
	
	The following is the clients requirement.
	
	They want to configure a redhat cluster suit for there three
tire web
	application(Apache,jboss,mysql,).They need to configure the
server in
	active passive mode.
	
	We are planning to configure mysql active in one machine and
passive in
	other machine then jboss active in one machine and passive in
other
	machine. (not sure whether it is possible).
	
	We have a san storage also.
	
	Could any body have done the set up earlier the same with two
node,
	request to share the knowledge.
	
	The main constraint now is  1) "How to setup the active passive
setup in
	conga"
	                                   2) "What is the stability of
the
	configuration with conga any limitation compairing with the
	method using files"
	                                   3)  Any body have any other
method
	of configuring the setup. using conventional method using
	files.
	                                   4) Fencing configuration with
	ILO.power switch. Script for password sharing..etc...
	
	
	
	Thanks in advance
	Prakash C Kesavan
	
	--
	Linux-cluster mailing list
	Linux-cluster at redhat.com
	https://www.redhat.com/mailman/listinfo/linux-cluster
	


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://listman.redhat.com/archives/linux-cluster/attachments/20080207/8632acf4/attachment.htm>

From pcaulfie at redhat.com  Thu Feb  7 08:54:02 2008
From: pcaulfie at redhat.com (Christine Caulfield)
Date: Thu, 07 Feb 2008 08:54:02 +0000
Subject: [Linux-cluster] Re: problem deleting a node from a cluster
In-Reply-To: <1202323500.21504.71.camel@ayanami.boston.devel.redhat.com>
References: <23589450.23361202311274793.JavaMail.root@ottmail>	<1202318441.21504.57.camel@ayanami.boston.devel.redhat.com>
	<1202323500.21504.71.camel@ayanami.boston.devel.redhat.com>
Message-ID: <47AAC72A.7060203@redhat.com>

Lon Hohberger wrote:
> On Wed, 2008-02-06 at 12:20 -0500, Lon Hohberger wrote:
>> On Wed, 2008-02-06 at 10:21 -0500, Yan Vinogradov wrote:
>>
>>> Could be a bug.  Does it say 'estranged' in the output, or not?
>>>
>>> -- Lon
>>>
>>> Hi Lon, yes, it does refer to the third node as estranged. Does it
>>> tell you anything?
>>>
>> Clustat reports "Estranged" whenever it asks cman for a node list, and
>> the corresponding node does not show up in cluster.conf.
>>
>> In your case, it means that cman still has state about the node despite
>> the configuration change in ccsd.
>>
>> I'm not sure cman "purges" nodes that were dead (but part of
>> cluster.conf) that later are removed from cluster.conf.
>>
>> Chrissie might know.

That's right, cman never removes a node from its list. That's chiefly
because it can't easily tell whether it might suddenly appear again,
which was mainly the case in RHEL4 where cman was in the kernel and
didn't have easy access to cluster.conf.

Actually, in RHEL5 it could be possibly to purge a node from cman, it is
something I've considered and might have a look at in the future, if
people think it's worthwhile.

Chrissie



From asim.husanovic at gmail.com  Thu Feb  7 15:14:20 2008
From: asim.husanovic at gmail.com (Asim Husanovic)
Date: Thu, 7 Feb 2008 16:14:20 +0100
Subject: [Linux-cluster] Monitoring shared disk
Message-ID: <3c1234d0802070714y21d88c88x1569bcb88b898238@mail.gmail.com>

Hi

How to identify shared disk/volumes?

How to collect the cluster FS information?

How to display shared disks on node/s? Which node/s?

------
How to run RH CS on SLES 10 without any SP, or on openSUSE 10.x


WR
Asim



From bpkroth at wisc.edu  Thu Feb  7 15:28:42 2008
From: bpkroth at wisc.edu (Brian Kroth)
Date: Thu, 07 Feb 2008 09:28:42 -0600
Subject: [Linux-cluster] Monitoring shared disk
In-Reply-To: <3c1234d0802070714y21d88c88x1569bcb88b898238@mail.gmail.com>
References: <3c1234d0802070714y21d88c88x1569bcb88b898238@mail.gmail.com>
Message-ID: <20080207152842.GC30561@wisc.edu>

Here are some quick examples.  There are almost certainly other ways to do
it.

Asim Husanovic <asim.husanovic at gmail.com>:
> Hi
> 
> How to identify shared disk/volumes?

scsi_id

> How to collect the cluster FS information?

gfs_tool

> How to display shared disks on node/s? Which node/s?

gfs_tool list
cman_tool services


You can wrap all of these inside snmp scripts/oids or use nagios passive
checks if you want to monitor them remotely/automatically.

Brian
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/x-pkcs7-signature
Size: 2192 bytes
Desc: not available
URL: <http://listman.redhat.com/archives/linux-cluster/attachments/20080207/4ac0d23c/attachment.bin>

From gordan at bobich.net  Thu Feb  7 15:32:26 2008
From: gordan at bobich.net (gordan at bobich.net)
Date: Thu, 7 Feb 2008 15:32:26 +0000 (GMT)
Subject: [Linux-cluster] 2-node tie-breaking
Message-ID: <alpine.LRH.1.00.0802071523160.7145@skynet.shatteredsilicon.net>

Hi,

I've got a slightly peculiar problem. 2-node cluster acting as a load 
balanced fail-over router. 3 NICs: public, private, cluster.
Cluster NICs are connected with a cross-over cable, the other two are on 
switches. The cluster NIC is only used for DRBD/GFS/DLM and associated 
things.

The failure mode that I'm trying to account for is the one of the cluster 
NIC failing on one machine. On the public and privace networks, both 
machines can still see everything (including each other). That means that 
a tie-breaker based on other visible things will not work.

So, which machine gets fenced in the case of the cluster NIC failure (or 
more likely, if the x-over cable falls out)?

Is there a sane, tested way to handle this condition? It would be quite 
embarrasing if both, otherwise fully functional nodes, decided to shut 
fence the other one off by shutting it down.

Thanks.

Gordan



From asim.husanovic at gmail.com  Thu Feb  7 15:40:51 2008
From: asim.husanovic at gmail.com (Asim Husanovic)
Date: Thu, 7 Feb 2008 16:40:51 +0100
Subject: [Linux-cluster] Monitoring shared disk
In-Reply-To: <20080207152842.GC30561@wisc.edu>
References: <3c1234d0802070714y21d88c88x1569bcb88b898238@mail.gmail.com>
	<20080207152842.GC30561@wisc.edu>
Message-ID: <3c1234d0802070740x990ed92o61be4ca385755b64@mail.gmail.com>

Thanks.
Asim

On Feb 7, 2008 4:28 PM, Brian Kroth <bpkroth at wisc.edu> wrote:
> Here are some quick examples.  There are almost certainly other ways to do
> it.
>
> Asim Husanovic <asim.husanovic at gmail.com>:
> > Hi
> >
> > How to identify shared disk/volumes?
>
> scsi_id
>
> > How to collect the cluster FS information?
>
> gfs_tool
>
> > How to display shared disks on node/s? Which node/s?
>
> gfs_tool list
> cman_tool services
>
>
> You can wrap all of these inside snmp scripts/oids or use nagios passive
> checks if you want to monitor them remotely/automatically.
>
> Brian
>



From bpkroth at wisc.edu  Thu Feb  7 15:44:25 2008
From: bpkroth at wisc.edu (Brian Kroth)
Date: Thu, 07 Feb 2008 09:44:25 -0600
Subject: [Linux-cluster] 2-node tie-breaking
In-Reply-To: <alpine.LRH.1.00.0802071523160.7145@skynet.shatteredsilicon.net>
References: <alpine.LRH.1.00.0802071523160.7145@skynet.shatteredsilicon.net>
Message-ID: <20080207154424.GE30561@wisc.edu>

A simple way might be to check for that case specifically and assign a
preference to the node you want to win.  For instance:

if $can_ping_internal_nodes \
	&& $can_ping_external_nodes \
	&& ! $can_ping_cluster_node; then

	if [ $HOSTNAME == node2 ]; then
		self_fence
	else
		steal_cluster_nodes_resources
	fi
fi

I know that you can do this via clever scoring in heartbeat [1], but I'm
not sure about rgmanager.

[1] linux-ha.org

Brian

gordan at bobich.net <gordan at bobich.net>:
> Hi,
>
> I've got a slightly peculiar problem. 2-node cluster acting as a load 
> balanced fail-over router. 3 NICs: public, private, cluster.
> Cluster NICs are connected with a cross-over cable, the other two are on 
> switches. The cluster NIC is only used for DRBD/GFS/DLM and associated 
> things.
>
> The failure mode that I'm trying to account for is the one of the cluster 
> NIC failing on one machine. On the public and privace networks, both 
> machines can still see everything (including each other). That means that a 
> tie-breaker based on other visible things will not work.
>
> So, which machine gets fenced in the case of the cluster NIC failure (or 
> more likely, if the x-over cable falls out)?
>
> Is there a sane, tested way to handle this condition? It would be quite 
> embarrasing if both, otherwise fully functional nodes, decided to shut 
> fence the other one off by shutting it down.
>
> Thanks.
>
> Gordan
>
> --
> Linux-cluster mailing list
> Linux-cluster at redhat.com
> https://www.redhat.com/mailman/listinfo/linux-cluster
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/x-pkcs7-signature
Size: 2192 bytes
Desc: not available
URL: <http://listman.redhat.com/archives/linux-cluster/attachments/20080207/aa9fc3a9/attachment.bin>

From gordan at bobich.net  Thu Feb  7 15:52:11 2008
From: gordan at bobich.net (gordan at bobich.net)
Date: Thu, 7 Feb 2008 15:52:11 +0000 (GMT)
Subject: [Linux-cluster] 2-node tie-breaking
In-Reply-To: <20080207154424.GE30561@wisc.edu>
References: <alpine.LRH.1.00.0802071523160.7145@skynet.shatteredsilicon.net>
	<20080207154424.GE30561@wisc.edu>
Message-ID: <alpine.LRH.1.00.0802071549290.7503@skynet.shatteredsilicon.net>

Thanks for that. How could this be hooked from cluster.conf? I wasn't 
planning to use the heartbeat stuff.

Gordan

On Thu, 7 Feb 2008, Brian Kroth wrote:

> A simple way might be to check for that case specifically and assign a
> preference to the node you want to win.  For instance:
>
> if $can_ping_internal_nodes \
> 	&& $can_ping_external_nodes \
> 	&& ! $can_ping_cluster_node; then
>
> 	if [ $HOSTNAME == node2 ]; then
> 		self_fence
> 	else
> 		steal_cluster_nodes_resources
> 	fi
> fi
>
> I know that you can do this via clever scoring in heartbeat [1], but I'm
> not sure about rgmanager.
>
> [1] linux-ha.org
>
> Brian
>
> gordan at bobich.net <gordan at bobich.net>:
>> Hi,
>>
>> I've got a slightly peculiar problem. 2-node cluster acting as a load
>> balanced fail-over router. 3 NICs: public, private, cluster.
>> Cluster NICs are connected with a cross-over cable, the other two are on
>> switches. The cluster NIC is only used for DRBD/GFS/DLM and associated
>> things.
>>
>> The failure mode that I'm trying to account for is the one of the cluster
>> NIC failing on one machine. On the public and privace networks, both
>> machines can still see everything (including each other). That means that a
>> tie-breaker based on other visible things will not work.
>>
>> So, which machine gets fenced in the case of the cluster NIC failure (or
>> more likely, if the x-over cable falls out)?
>>
>> Is there a sane, tested way to handle this condition? It would be quite
>> embarrasing if both, otherwise fully functional nodes, decided to shut
>> fence the other one off by shutting it down.
>>
>> Thanks.
>>
>> Gordan
>>
>> --
>> Linux-cluster mailing list
>> Linux-cluster at redhat.com
>> https://www.redhat.com/mailman/listinfo/linux-cluster
>



From fog at t.is  Thu Feb  7 17:24:51 2008
From: fog at t.is (=?iso-8859-1?Q?Finnur_=D6rn_Gu=F0mundsson_-_TM_Software?=)
Date: Thu, 7 Feb 2008 17:24:51 -0000
Subject: [Linux-cluster] NFS clustering - how to use fsid= options for the
	exports
Message-ID: <3DDA6E3E456E144DA3BB0A62A7F7F77901CACD9D@SKYHQAMX08.klasi.is>

Hi,

 

I have setup a active-standby NFS cluster.

 

Everything is working like it should, except for one thing.

 

In HP ServiceGuard you use /etc/exports on each node in a active-standby cluster to manage exports, and there you can use the fsid=X for each filesystem you want to export (helps with stale nfs errors after a failover).

 

In RHCS i cannot seem to get the server to correctly use the options ...

 

Here is my service:

 

                <service autostart="1" domain="nfsdomain" name="nfs">

                        <nfsexport name="home1">

                                <nfsclient name="nfshome" options="rw,sync,fsid=150" path="/home" target="10.50.102.128/25"/>

                                <nfsclient name="nfsdata" options="rw,fsid=50,sync" path="/data" target="10.50.102.128/25"/>

                                <clusterfs ref="home"/>

                                <ip ref="10.10.10.10"/>

                                <clusterfs ref="data"/>

                        </nfsexport>

 

Would this not be the correct way ? Is there a other way to do this except for manually using /etc/exports and just have RHCS manage the IP address transfer beteween the nodes?

 

K?r kve?ja / Best Regards,

Finnur ?rn Gu?mundsson
Network Engineer - Network Operations
fog at t.is <mailto:fog at t.is> 

TM Software
Ur?arhvarf 6, IS-203 K?pavogur, Iceland
Tel: +354 545 3000 - fax +354 545 3610
www.tm-software.is <http://www.tm-software.is/> 

This e-mail message and any attachments are confidential and may be privileged. TM Software e-mail disclaimer: www.tm-software.is/disclaimer <http://www.tm-software.is/disclaimer>  

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://listman.redhat.com/archives/linux-cluster/attachments/20080207/89342efa/attachment.htm>

From rpeterso at redhat.com  Thu Feb  7 19:19:34 2008
From: rpeterso at redhat.com (Bob Peterson)
Date: Thu, 07 Feb 2008 13:19:34 -0600
Subject: [Linux-cluster] New Cluster Wiki and FAQ
Message-ID: <1202411974.7223.42.camel@technetium.msp.redhat.com>

Hi People,

I'm happy to announce that, thanks to the ingenuity of Lon Hohberger,
we now have a cluster wiki.  It's still in its infancy, but since it's
a wiki, it should be easier to update, and it should allow you to
add / modify / improve the content as well.  The cluster wiki is at:

http://sources.redhat.com/cluster/wiki

Lon has also migrated the Cluster FAQ to a wiki page:

http://sources.redhat.com/cluster/wiki/FAQ

Hopefully all the contents are there from the old FAQ.  Let me know if
you have problems with it.  To help keep spam from invading the wiki,
if you want to change any of the pages, you have to first set up an
account: A simple name, password and email address.

>From now on I plan to keep the wiki up to date and let the old cluster
FAQ fade away.

Regards,

Bob Peterson
Red Hat GFS/GFS2




From lhh at redhat.com  Thu Feb  7 19:35:37 2008
From: lhh at redhat.com (Lon H. Hohberger)
Date: Thu, 07 Feb 2008 14:35:37 -0500
Subject: [Linux-cluster] 2-node tie-breaking
In-Reply-To: <alpine.LRH.1.00.0802071523160.7145@skynet.shatteredsilicon.net>
References: <alpine.LRH.1.00.0802071523160.7145@skynet.shatteredsilicon.net>
Message-ID: <1202412937.2938.55.camel@localhost.localdomain>


On Thu, 2008-02-07 at 15:32 +0000, gordan at bobich.net wrote:
> Hi,
> 
> I've got a slightly peculiar problem. 2-node cluster acting as a load 
> balanced fail-over router. 3 NICs: public, private, cluster.
> Cluster NICs are connected with a cross-over cable, the other two are on 
> switches. The cluster NIC is only used for DRBD/GFS/DLM and associated 
> things.
> 
> The failure mode that I'm trying to account for is the one of the cluster 
> NIC failing on one machine. On the public and privace networks, both 
> machines can still see everything (including each other). That means that 
> a tie-breaker based on other visible things will not work.
> 
> So, which machine gets fenced in the case of the cluster NIC failure (or 
> more likely, if the x-over cable falls out?

... whichever gets fenced first ;)

1. You can do a clever heuristic using qdiskd if you wanted, for example:

 * assign an IP on the private cluster network and make rgmanager manage
it as a service (even though it doesn't do anything). Make sure to
*disable* monitor_link, or rgmanager will stop the service!

 * make a script to check for:
   * ethernet link of the private interface, and
   * if that fails, ping the service IP address
     * if that fails, we are *dead*; give up and
       -do not- try to fence

If you put the IP as part of the "most critical" service that
rgmanager's running, then the operator of that service will continue
running while the other node is not allowed to continue running.

Because the first check is whether we have a cluster link - and the
*second* check is the ping of the service, 

Something like this...

<quorumd ...>
  <heuristic program="/usr/local/sbin/private-link-script" ... />
</quorumd>

<rm>
  ...
  <service name="pinger-ip" >
    <ip address="10.1.1.2" monitor_link="no"/>
  </service>
  ...
</rm>

Script might something like:

#!/bin/sh

DEVICE=eth3
PINGIP=10.1.1.2

#
# Ensure the device is there!
#
ethtool $DEVICE || exit 1

#
# Check for link
#
ethtool $DEVICE | grep -q "Link detected.*yes" 
if [ $? -eq 0 ]; then
  exit 0
fi

#
# XXX Work around signal bug for now.
#
ping_func()
{
        declare retries=0
        declare PID

        ping -c3 -t2 $1 &
        PID=`jobs -p`
        while [ $retries -lt 2 ]; do
                sleep 1
                ((retries++))

                kill -n 0 $PID &> /dev/null
                if [ $? -eq 1 ]; then
                        wait $PID
                        return $?
                fi
        done

        kill -9 $PID
        return 1
}

#
# Ping service ip address.
#
ping_func $1
exit $?
-------------------------------

Disadvantage is that it's hard to start the cluster w/o both nodes
online without some sort of override.


2.  You can do something like Brian said, too - e.g. "if I am the right
host and the link isn't up, I win":

#!/bin/sh

DEVICE=eth3
OTHER_NODE_PUBLIC_IP="192.168.1.2"

#
# Ensure the device is there!
#
ethtool $DEVICE || exit 1

#
# Check for link
#
ethtool $DEVICE | grep -q "Link detected.*yes" 
if [ $? -eq 0 ]; then
  exit 0
fi

#
# XXX Work around signal bug for now.
#
ping_func()
{
        declare retries=0
        declare PID

        ping -c3 -t2 $1 &
        PID=`jobs -p`
        while [ $retries -lt 2 ]; do
                sleep 1
                ((retries++))

                kill -n 0 $PID &> /dev/null
                if [ $? -eq 1 ]; then
                        wait $PID
                        return $?
                fi
        done

        kill -9 $PID
        return 1
}

#
# Ok, no link on private net
#
ping_func $OTHER_NODE_PUBLIC_IP
if [ $? -eq 0 ]; then
  [ "`uname -n`" == "node1" ]
  exit $?
fi

#
# Other node is down and we're not - 
# we win
#
exit 0
-------------------------------



3.  Another simple way to do it is to use a fake "fencing agent" to
introduce a delay:

   <fencedevice agent="/bin/sleep-10" name="sleeper" .../>

(where /bin/sleep-10 is something like:
#!/bin/sh
sleep 10
exit 0
)

Reference that agent as part of -one- node's fencing, and that node will
lose by default.  This way, you don't have to set up qdiskd.  You could
do the same thing by just editing the fencing agent directly on that
node, as well - in which case, you wouldn't have to edit cluster.conf at
all.


-- Lon



From dsharp at ivytech.edu  Thu Feb  7 19:38:35 2008
From: dsharp at ivytech.edu (Doug Sharp)
Date: Thu, 7 Feb 2008 14:38:35 -0500
Subject: [Linux-cluster] NFS clustering - how to use fsid= options for
	theexports
References: <3DDA6E3E456E144DA3BB0A62A7F7F77901CACD9D@SKYHQAMX08.klasi.is>
Message-ID: <02CC84960E52F745860DFF29ADC62091025E5477@MSEXCHNG-02.ivytech.local>

> Would this not be the correct way ? Is there a other way to do 
> this except for manually using /etc/exports and just have RHCS 
> manage the IP address transfer beteween the nodes?

 
http://sources.redhat.com/cluster/doc/nfscookbook.pdf
See the description of "Managed NFS" for a way to manage NFS completely within cluster.conf

Doug
-------------- next part --------------
A non-text attachment was scrubbed...
Name: winmail.dat
Type: application/ms-tnef
Size: 2781 bytes
Desc: not available
URL: <http://listman.redhat.com/archives/linux-cluster/attachments/20080207/a635ee05/attachment.bin>

From lhh at redhat.com  Thu Feb  7 19:43:52 2008
From: lhh at redhat.com (Lon H. Hohberger)
Date: Thu, 07 Feb 2008 14:43:52 -0500
Subject: [Linux-cluster] New Cluster Wiki and FAQ
In-Reply-To: <1202411974.7223.42.camel@technetium.msp.redhat.com>
References: <1202411974.7223.42.camel@technetium.msp.redhat.com>
Message-ID: <1202413432.2938.58.camel@localhost.localdomain>


On Thu, 2008-02-07 at 13:19 -0600, Bob Peterson wrote:

> Hopefully all the contents are there from the old FAQ.  Let me know if
> you have problems with it.  To help keep spam from invading the wiki,
> if you want to change any of the pages, you have to first set up an
> account: A simple name, password and email address.

Note - when creating your account, please use 'FirstLast' so we can
track pages and such more easily :)

ex -

LonHohberger
BobPeterson

etc.

-- Lon



From gordan at bobich.net  Thu Feb  7 20:18:09 2008
From: gordan at bobich.net (Gordan Bobic)
Date: Thu, 07 Feb 2008 20:18:09 +0000
Subject: [Linux-cluster] Pseudo-Fencing for 2-node DRBD+GFS
Message-ID: <47AB6781.4060201@bobich.net>

Hi,

Thanks for the replies on the other thread. I'm still assimilating them. 
Meanwhile, however, I am faced with a different problem. It turns out 
that the servers I've got to prototype this with only have MegaRAC 780 
(a.k.a. DRAC 2) management cards in them. The problem with this is that, 
to the best of my ability to tell, these don't seem to provide a sanely 
usable interface to allow for the machine to be powered down via the 
command line (Windows only management utility - I can't even get it to 
ping, only arping, and nmap isn't coming up with anything!)

So, I need a poor man's pseudo-fencing hack that will protect the shared 
file system by stopping the DRBD replication between the hosts (range of 
options available including using iptables to firewall the cluster NIC, 
or just downing the interface completely, as it's not used for anything 
else). The theoretical assumption (I don't really have a choice...) is 
that if one of the machines fails, it will fail completely and not 
attempt to fight over the resources that need to be failed over (in this 
case just IP addresses).

Is there a minimum API that a fencing script has to implement to be 
usable via cluster.conf? If so, can anyone please point me at some 
documentation for it? Would this be a reasonable way to implement 
fencing in a 2-node case?

Thanks.

Gordan



From gordan at bobich.net  Thu Feb  7 21:02:10 2008
From: gordan at bobich.net (Gordan Bobic)
Date: Thu, 07 Feb 2008 21:02:10 +0000
Subject: [Linux-cluster] 2-node tie-breaking
In-Reply-To: <1202412937.2938.55.camel@localhost.localdomain>
References: <alpine.LRH.1.00.0802071523160.7145@skynet.shatteredsilicon.net>
	<1202412937.2938.55.camel@localhost.localdomain>
Message-ID: <47AB71D2.2040201@bobich.net>

Lon H. Hohberger wrote:

[...]

> 3.  Another simple way to do it is to use a fake "fencing agent" to
> introduce a delay:
> 
>    <fencedevice agent="/bin/sleep-10" name="sleeper" .../>
> 
> (where /bin/sleep-10 is something like:
> #!/bin/sh
> sleep 10
> exit 0
> )
> 
> Reference that agent as part of -one- node's fencing, and that node will
> lose by default.  This way, you don't have to set up qdiskd.  You could
> do the same thing by just editing the fencing agent directly on that
> node, as well - in which case, you wouldn't have to edit cluster.conf at
> all.

Funnily enough, this is exactly what I was just thinking about. Thanks. :-)

Unfortunately, things just got a bit more complicated for me, because it 
looks like my fencing device won't work. :-( Instead, it may have to end 
up being something as bodgy as ifdown-ing the cluster interface on the 
surviving node - in the 2 node scenario, that ought to be as good a 
using a managed switch based fencing device. The file systems will 
diverge if both nodes keep running, but neither fork will be corrupted.

Thinking about this a bit more, a tie-breaking IP ping may need to be 
implemented on the public and private NICs. On the public side, the 
tie-breaker would need to be the next router along. Are there hooks for 
implementing such a thing as a simple ping script, or heartbeat or 
similar that can be used to achieve this?

Thanks.

Gordan



From lhh at redhat.com  Thu Feb  7 21:56:06 2008
From: lhh at redhat.com (Lon H. Hohberger)
Date: Thu, 07 Feb 2008 16:56:06 -0500
Subject: [Linux-cluster] 2-node tie-breaking
In-Reply-To: <47AB71D2.2040201@bobich.net>
References: <alpine.LRH.1.00.0802071523160.7145@skynet.shatteredsilicon.net>
	<1202412937.2938.55.camel@localhost.localdomain>
	<47AB71D2.2040201@bobich.net>
Message-ID: <1202421366.2938.70.camel@localhost.localdomain>


On Thu, 2008-02-07 at 21:02 +0000, Gordan Bobic wrote:

> Thinking about this a bit more, a tie-breaking IP ping may need to be 
> implemented on the public and private NICs. On the public side, the 
> tie-breaker would need to be the next router along. Are there hooks for 
> implementing such a thing as a simple ping script, or heartbeat or 
> similar that can be used to achieve this?

Hmm, the problem is that using qdisk requires... well, a shared disk
(that doesn't need pesky things like network communications...).

Well, here's a cheap 'out' ;)

Ebay item # 250213910258

8 port WTI NPS for $70 + $15 s/h.

-- Lon



From harry.sutton at hp.com  Thu Feb  7 22:08:22 2008
From: harry.sutton at hp.com (Sutton, Harry (MSE))
Date: Thu, 07 Feb 2008 17:08:22 -0500
Subject: [Linux-cluster] Two-node cluster unpatched B doesn't see patched A
Message-ID: <47AB8156.6010205@hp.com>

The most recent set of patches for RHCS, comprising:

RHBA-2008:0093    dlm-kernel bug fix update
RHBA-2008:0092    cman-kernel bug fix update
RHBA-2008:0060    cman bug fix update
RHBA-2008:0095    gnbd-kernel bug fix update
RHBA-2008:0096    GFS-kernel bug fix update
RHSA-2008:0055    Important: kernel security and bug fix update

has resulted in a problem in my two-node (production) cluster. Let me 
explain ;-)

I have a three-node test cluster where I install all patches before 
rolling them into my (two-node) production cluster; I know, I know, 
they're not the same, and that's the only difference I can see in what 
has happened here (a first in two years). In the three-node cluster 
(which, just to complicate things, only had two active nodes at the 
time), I rolled these patches through the two nodes without taking the 
whole cluster down. That is:

1. Stop all cluster services on Node A. Disable auto-start using 
chkconfig off <cluster-service-name>. Services stop successfully, Node A 
leaves the cluster, Node B continues running all shared cluster services 
(GFS, Fibre-channel-connected shared storage, HP MSA1000).
2. Patch Node A, reboot to new kernel, re-install HP-supplied QLogic 
driver, edit /etc/modprobe.conf for failover settings, rebuild initrd 
file for QLogic drivers, reboot, re-enable auto-start of cluster 
services, reboot once more and the cluster re-forms.
3. Repeat Steps 1 and 2 for Node B
4. Cluster is restored to normal operation, both nodes fully patched.

On my production cluster, which uses a Quorum Disk in place of the third 
node, I completed steps 1 and 2 on Node A, but the cluster did NOT 
reform. cman sends out its advertisement, and I can see that Node B 
receives it (by looking at the tcpdump traces), but Node B never responds.

So: before I take down Node B (which is currently the only one running 
my production services), can someone either (a) explain why the cluster 
is not re-forming, or (b) assure me that by restoring both systems to 
the same patch level, the cluster WILL reform properly? (Which begs the 
question: why did my test cluster survive the patch process and my 
production cluster didn't? Same versions of everything......)

Thanks in advance, and best regards,

    /Harry Sutton, RHCA
     Hewlett-Packard Company
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/x-pkcs7-signature
Size: 6255 bytes
Desc: S/MIME Cryptographic Signature
URL: <http://listman.redhat.com/archives/linux-cluster/attachments/20080207/0a325d13/attachment.bin>

From gordan at bobich.net  Thu Feb  7 22:19:56 2008
From: gordan at bobich.net (Gordan Bobic)
Date: Thu, 07 Feb 2008 22:19:56 +0000
Subject: [Linux-cluster] 2-node tie-breaking
In-Reply-To: <1202421366.2938.70.camel@localhost.localdomain>
References: <alpine.LRH.1.00.0802071523160.7145@skynet.shatteredsilicon.net>	<1202412937.2938.55.camel@localhost.localdomain>	<47AB71D2.2040201@bobich.net>
	<1202421366.2938.70.camel@localhost.localdomain>
Message-ID: <47AB840C.8040905@bobich.net>

Lon H. Hohberger wrote:
> On Thu, 2008-02-07 at 21:02 +0000, Gordan Bobic wrote:
> 
>> Thinking about this a bit more, a tie-breaking IP ping may need to be 
>> implemented on the public and private NICs. On the public side, the 
>> tie-breaker would need to be the next router along. Are there hooks for 
>> implementing such a thing as a simple ping script, or heartbeat or 
>> similar that can be used to achieve this?
> 
> Hmm, the problem is that using qdisk requires... well, a shared disk
> (that doesn't need pesky things like network communications...).

Sure, I understand that. But since there are only 2 nodes, fencing by 
downing the local cluster interface would at least stop the file system 
from getting hosed.

> Well, here's a cheap 'out' ;)
> 
> Ebay item # 250213910258
> 
> 8 port WTI NPS for $70 + $15 s/h.

Indeed, that would be tempting if it wasn't on the wrong side of the 
atlantic. A more local search for similar things doesn't seem to come up 
with anything. :-(

Gordan



From jakub.suchy at enlogit.cz  Thu Feb  7 22:31:08 2008
From: jakub.suchy at enlogit.cz (Jakub Suchy)
Date: Thu, 7 Feb 2008 23:31:08 +0100
Subject: [Linux-cluster] 2-node tie-breaking
In-Reply-To: <47AB840C.8040905@bobich.net>
References: <alpine.LRH.1.00.0802071523160.7145@skynet.shatteredsilicon.net>
	<1202412937.2938.55.camel@localhost.localdomain>
	<47AB71D2.2040201@bobich.net>
	<1202421366.2938.70.camel@localhost.localdomain>
	<47AB840C.8040905@bobich.net>
Message-ID: <20080207223108.GA15215@localhost>

> Indeed, that would be tempting if it wasn't on the wrong side of the 
> atlantic. A more local search for similar things doesn't seem to come up 
> with anything. :-(

Have you considered something like this?
http://www.oracle.com/technology/pub/articles/hunter_rac10gr2.html
Build Your Own Oracle RAC 10g Release 2 Cluster on Linux and FireWire

forget those Oracle things and see information about low-cost shared
disk. i didn't try, i am not sure if it works, but it's interesting :-)

Jakub
-- 
Jakub Such? <jakub.suchy at enlogit.cz>
GSM: +420 - 777 817 949

Enlogit s.r.o, U Cukrovaru 509/4, 400 07 ?st? nad Labem
tel.: +420 - 474 745 159, fax: +420 - 474 745 160
e-mail: info at enlogit.cz, web: http://www.enlogit.cz



From jakub.suchy at enlogit.cz  Thu Feb  7 22:39:51 2008
From: jakub.suchy at enlogit.cz (Jakub Suchy)
Date: Thu, 7 Feb 2008 23:39:51 +0100
Subject: [Linux-cluster] 2-node tie-breaking
In-Reply-To: <47AB840C.8040905@bobich.net>
References: <alpine.LRH.1.00.0802071523160.7145@skynet.shatteredsilicon.net>
	<1202412937.2938.55.camel@localhost.localdomain>
	<47AB71D2.2040201@bobich.net>
	<1202421366.2938.70.camel@localhost.localdomain>
	<47AB840C.8040905@bobich.net>
Message-ID: <20080207223951.GB15215@localhost>

>> Well, here's a cheap 'out' ;)
>> Ebay item # 250213910258
>> 8 port WTI NPS for $70 + $15 s/h.
>
> Indeed, that would be tempting if it wasn't on the wrong side of the 
> atlantic. A more local search for similar things doesn't seem to come up 
> with anything. :-(

Another "cheap" power switch may be:

http://www.hw-group.com/products/ip_watchdog/index_lite_en.html

Made by a Czech Republic (= right side of the atlantic :) company,
allows power switching of two servers. Requires you to write a fencing
script and connect power output cables from this device to power
switches in the servers. Again - never tried, but it's around 3188 Czech
crowns, which is approx. $187.

Jakub

-- 
Jakub Such? <jakub.suchy at enlogit.cz>



From peter at widexs.nl  Thu Feb  7 23:07:27 2008
From: peter at widexs.nl (Peter Bosgraaf)
Date: Fri, 8 Feb 2008 00:07:27 +0100
Subject: [Linux-cluster] 2-node tie-breaking
In-Reply-To: <20080207223951.GB15215@localhost>
References: <alpine.LRH.1.00.0802071523160.7145@skynet.shatteredsilicon.net>
	<1202412937.2938.55.camel@localhost.localdomain>
	<47AB71D2.2040201@bobich.net>
	<1202421366.2938.70.camel@localhost.localdomain>
	<47AB840C.8040905@bobich.net> <20080207223951.GB15215@localhost>
Message-ID: <20080207230727.GE63223@widexs.nl>

Hi,

On Thu, Feb 07, 2008 at 11:39:51PM +0100, Jakub Suchy wrote:
> >> Well, here's a cheap 'out' ;)
> >> Ebay item # 250213910258
> >> 8 port WTI NPS for $70 + $15 s/h.
> >
> > Indeed, that would be tempting if it wasn't on the wrong side of the 
> > atlantic. A more local search for similar things doesn't seem to come up 
> > with anything. :-(

*Don't flame me, i didn't want to spam the list with commerial stuff but
thought this might help you out*

If your interested in a powerswitch solution i would recommend you to look
at the solutions from www.lubenco.nl 

They have 8 port (C13) 10 amp powerswitches with load monitoring and
snmp configuration support for about 117 euro a pice. (new) If your
willing to buy in bulk the price even drops well below 100 euro.

Cheers,
Peter



From gordan at bobich.net  Thu Feb  7 23:24:55 2008
From: gordan at bobich.net (Gordan Bobic)
Date: Thu, 07 Feb 2008 23:24:55 +0000
Subject: [Linux-cluster] 2-node tie-breaking
In-Reply-To: <20080207223951.GB15215@localhost>
References: <alpine.LRH.1.00.0802071523160.7145@skynet.shatteredsilicon.net>	<1202412937.2938.55.camel@localhost.localdomain>	<47AB71D2.2040201@bobich.net>	<1202421366.2938.70.camel@localhost.localdomain>	<47AB840C.8040905@bobich.net>
	<20080207223951.GB15215@localhost>
Message-ID: <47AB9347.6050601@bobich.net>

Jakub Suchy wrote:
>>> Well, here's a cheap 'out' ;)
>>> Ebay item # 250213910258
>>> 8 port WTI NPS for $70 + $15 s/h.
>> Indeed, that would be tempting if it wasn't on the wrong side of the 
>> atlantic. A more local search for similar things doesn't seem to come up 
>> with anything. :-(
> 
> Another "cheap" power switch may be:
> 
> http://www.hw-group.com/products/ip_watchdog/index_lite_en.html
> 
> Made by a Czech Republic (= right side of the atlantic :) company,
> allows power switching of two servers. Requires you to write a fencing
> script and connect power output cables from this device to power
> switches in the servers. Again - never tried, but it's around 3188 Czech
> crowns, which is approx. $187.

Yeah, but that's not that far off a couple of cheap UPS-es with basic 
serial interfaces. I could cross-connect them so that Server-A is 
powered off UPS-A, and is controlling UPS-B via serial/USB. Same in 
reverse on the other machine.

That way Server-A can power off Server-B and vice versa.

The upshot being that at least that way I have UPS capability.

But it'd still be nice to have a software only "might work most of the 
time" solution. It should work at least in the cases where preservation 
of the GFS is the main concern, as all the surviving nodes should be 
able to firewall off the node they think has died. Resource fail-over 
might still be an issue, but at least the cluster itself would stay safe 
and functional.

Gordan



From doseyg at r-networks.net  Fri Feb  8 05:01:57 2008
From: doseyg at r-networks.net (Glen Dosey)
Date: Fri, 08 Feb 2008 00:01:57 -0500
Subject: [Linux-cluster] GFS2 loses data under kernel 2.6.24...
Message-ID: <1202446917.5942.19.camel@eclipse.office.r-networks.net>

I experienced this today at work on a RHEL5 system and have verified it
today at home on Fedora 8. Perhaps I am doing something foolish ....

I have a fully patched RHEL5 x86_64 system which works fine with the Red
Hat supplied cluster stuff, except the NFS server performance is abysmal
(~640Mb/s NFS). After pulling my hair trying to fix NFS I decided to
just grab the latest kernel which fixed the problem (~980Mb/s NFS). But
it introduced another much more serious problem, which I've duplicated
on my FC8 x86_64 system at home. 

I already have all the cman/clvmd/openais/gfs[2]-utils packages
installed through the package manager. I downloaded kernel 2.6.24 from
kernel.org and did a straight `make -j4 rpm ` and installed the
resulting rpm in both instances. Both systems worked fine with
RHEL/Fedora kernels, but here's what happens under 2.6.24

[root at eclipse test]# dd if=/dev/zero of=test3.dd bs=512M count=1
1+0 records in
1+0 records out
536870912 bytes (537 MB) copied, 7.95285 s, 67.5 MB/s
[root at eclipse test]# ll
total 2101312
-rw-r--r-- 1 root root          0 2008-02-07 23:25 test2.dd
-rw-r--r-- 1 root root  536870912 2008-02-07 23:42 test3.dd
-rw-r--r-- 1 root root 1073741824 2008-02-07 22:54 test.dd
[root at eclipse test]# cd ..
[root at eclipse mnt]# umount /mnt/test/
[root at eclipse mnt]# mount /mnt/test/
[root at eclipse mnt]# mount | grep test
/dev/mapper/disk00-test on /mnt/test type gfs2
(rw,hostdata=jid=0:id=524289:first=1)
[root at eclipse mnt]# cd /mnt/test/
[root at eclipse test]# ll
total 2101312
-rw-r--r-- 1 root root          0 2008-02-07 23:25 test2.dd
-rw-r--r-- 1 root root          0 2008-02-07 23:42 test3.dd
-rw-r--r-- 1 root root 1073741824 2008-02-07 22:54 test.dd

Files that have data just go zero size after an umount and remount. I've
tried a variety of file sizes and tried it with file containing data as
well (not all zeros). This worked under the RHEL kernels, so is there
something I'm doing wrong ?

Both systems are running cman and are a quorate 2 node cluster (where
the second node doesn't exist). At work it's a 1TB shared filesystem but
here at home it's just a local disk, so there's nothing else with any
access to it.

If someone could maybe point out what I'm doing wrong I'd appreciate it,
or just let me know this won't work for whatever reason. I haven't even
touched on getting the GFS1 modules to build into this.

Thanks,
Glen




From swhiteho at redhat.com  Fri Feb  8 09:30:59 2008
From: swhiteho at redhat.com (Steven Whitehouse)
Date: Fri, 08 Feb 2008 09:30:59 +0000
Subject: [Linux-cluster] GFS2 loses data under kernel 2.6.24...
In-Reply-To: <1202446917.5942.19.camel@eclipse.office.r-networks.net>
References: <1202446917.5942.19.camel@eclipse.office.r-networks.net>
Message-ID: <1202463059.22038.421.camel@quoit>

Hi,

Does this patch fix it for you?

http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commitdiff;h=9656b2c14c6ee0806c90a6be41dec71117fc8f50

or you can just upgrade to the latest upstream Linus kernel. It was a
result of the write_end function not working in exactly the same way as
the older commit_write used to,

Steve.

On Fri, 2008-02-08 at 00:01 -0500, Glen Dosey wrote:
> I experienced this today at work on a RHEL5 system and have verified it
> today at home on Fedora 8. Perhaps I am doing something foolish ....
> 
> I have a fully patched RHEL5 x86_64 system which works fine with the Red
> Hat supplied cluster stuff, except the NFS server performance is abysmal
> (~640Mb/s NFS). After pulling my hair trying to fix NFS I decided to
> just grab the latest kernel which fixed the problem (~980Mb/s NFS). But
> it introduced another much more serious problem, which I've duplicated
> on my FC8 x86_64 system at home. 
> 
> I already have all the cman/clvmd/openais/gfs[2]-utils packages
> installed through the package manager. I downloaded kernel 2.6.24 from
> kernel.org and did a straight `make -j4 rpm ` and installed the
> resulting rpm in both instances. Both systems worked fine with
> RHEL/Fedora kernels, but here's what happens under 2.6.24
> 
> [root at eclipse test]# dd if=/dev/zero of=test3.dd bs=512M count=1
> 1+0 records in
> 1+0 records out
> 536870912 bytes (537 MB) copied, 7.95285 s, 67.5 MB/s
> [root at eclipse test]# ll
> total 2101312
> -rw-r--r-- 1 root root          0 2008-02-07 23:25 test2.dd
> -rw-r--r-- 1 root root  536870912 2008-02-07 23:42 test3.dd
> -rw-r--r-- 1 root root 1073741824 2008-02-07 22:54 test.dd
> [root at eclipse test]# cd ..
> [root at eclipse mnt]# umount /mnt/test/
> [root at eclipse mnt]# mount /mnt/test/
> [root at eclipse mnt]# mount | grep test
> /dev/mapper/disk00-test on /mnt/test type gfs2
> (rw,hostdata=jid=0:id=524289:first=1)
> [root at eclipse mnt]# cd /mnt/test/
> [root at eclipse test]# ll
> total 2101312
> -rw-r--r-- 1 root root          0 2008-02-07 23:25 test2.dd
> -rw-r--r-- 1 root root          0 2008-02-07 23:42 test3.dd
> -rw-r--r-- 1 root root 1073741824 2008-02-07 22:54 test.dd
> 
> Files that have data just go zero size after an umount and remount. I've
> tried a variety of file sizes and tried it with file containing data as
> well (not all zeros). This worked under the RHEL kernels, so is there
> something I'm doing wrong ?
> 
> Both systems are running cman and are a quorate 2 node cluster (where
> the second node doesn't exist). At work it's a 1TB shared filesystem but
> here at home it's just a local disk, so there's nothing else with any
> access to it.
> 
> If someone could maybe point out what I'm doing wrong I'd appreciate it,
> or just let me know this won't work for whatever reason. I haven't even
> touched on getting the GFS1 modules to build into this.
> 
> Thanks,
> Glen
> 
> 
> --
> Linux-cluster mailing list
> Linux-cluster at redhat.com
> https://www.redhat.com/mailman/listinfo/linux-cluster



From celso at webbertek.com.br  Fri Feb  8 13:18:20 2008
From: celso at webbertek.com.br (Celso K. Webber)
Date: Fri, 8 Feb 2008 11:18:20 -0200
Subject: [Linux-cluster] RHCS 5.1 latest packages, 2-node cluster,
	doesn't come up with only 1 node
Message-ID: <20080208130449.M21432@webbertek.com.br>

Hello all,

I'm having a situation here that might be a bug, or maybe it's some mistake
from my part.

* Scenario: 2-node cluster on Dell PE-2950 servers, Dell MD-3000 storage (SAS
direct-attach), using IPMI-Lan as fencing devices, 2 NICs on each server
(public and heartbeat networks), using Qdisk in the shared storage

* Problem: if I shutdown one node and keep it shut down, and then reboot the
other node, although CMAN comes up after 5 minutes or so, rgmanager does not
start.

I remember having this same problem with RHCS 4.4, but it was solved by
upgrading to 4.5. But with RHCS 4.4 CMAN didn't come up, with my setup in RHCS
5.1 CMAN comes up after giving up waiting for the other node, but rgmanager
doesn't, so services get not started. This is bad in an unattended situation.

Here are some steps and details I've collected from the machine (sorry for a
so long message):

* Shutdown node1

* Reboot node2
  - after boot, took around 5 minutes in the "start fencing" message
  - reported a startup FAIL for the "cman" service after this period of time

* Boot completed

* Logged in:
  - clustat reported inquorate and quorum disk as "offline":
[root at mrp02 ~]# clustat
msg_open: No such file or directory
Member Status: Inquorate

  Member Name                        ID   Status
  ------ ----                        ---- ------
  node1                                 1 Offline
  node2                                 2 Online, Local
  /dev/sdc1                             0 Offline

* After a few seconds, clustat reported quorate and quorum disk as "online":
[root at mrp02 ~]# clustat
msg_open: No such file or directory
Member Status: Quorate

  Member Name                        ID   Status
  ------ ----                        ---- ------
  node1                                 1 Offline
  node2                                 2 Online, Local
  /dev/sdc1                             0 Online, Quorum Disk

* Logs in /var/log/messages showed that after qdiskd assumed "master role",
cman reported regaining quorum:
Feb  7 20:06:59 mrp02 qdiskd[5854]: <info> Assuming master role
Feb  7 20:07:00 mrp02 ccsd[5694]: Cluster is not quorate.  Refusing connection.
Feb  7 20:07:00 mrp02 ccsd[5694]: Error while processing connect: Connection
refused
Feb  7 20:07:00 mrp02 ccsd[5694]: Cluster is not quorate.  Refusing connection.
Feb  7 20:07:00 mrp02 ccsd[5694]: Error while processing connect: Connection
refused
Feb  7 20:07:00 mrp02 openais[5714]: [CMAN ] quorum regained, resuming activity
Feb  7 20:07:01 mrp02 clurgmgrd[7523]: <notice> Quorum formed, starting
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  -> Note that rgmanager started after quorum was regained, but seemed not to
work anymore later on (please see below).
Feb  7 20:07:01 mrp02 kernel: dlm: no local IP address has been set
Feb  7 20:07:01 mrp02 kernel: dlm: cannot start dlm lowcomms -107

* Noticed that in "clustat" there as an error message:
  -> msg_open: No such file or directory

* Checked rgmanager to see if it was related:
[root at mrp02 ~]# chkconfig --list rgmanager
rgmanager       0:off   1:off   2:on    3:on    4:on    5:on    6:off
[root at mrp02 ~]# service rgmanager status
clurgmgrd dead but pid file exists

* Since rgmanager did not come back by itself, restarted it manually:
[root at mrp02 init.d]# service rgmanager restart
Starting Cluster Service Manager: dlm: Using TCP for communications
                                                           [  OK  ]

* This time clustat did not show the "msg_open" error anymore:
[root at mrp02 init.d]# clustat
Member Status: Quorate

  Member Name                        ID   Status
  ------ ----                        ---- ------
  node1                                 1 Offline
  node2                                 2 Online, Local
  /dev/sdc1                             0 Online, Quorum Disk

* It seems to me that in case of cman regaining quorum after a lost quorum, at
least in a initial "no quorum" state, rgmanager is not "woke up"

* This setup had no services configured, so I repeated the test configuring a
simple start/stop/status service using the "crond" service as an example, same
results

* Copy /etc/cluster/cluster.conf:
  -> Notice: I'm using Qdiskd with "always ok" heuristics, since the customer
does not have a "always-on" IP tiebraker device to use with a "ping" command
as heuristics.
<?xml version="1.0"?>
<cluster config_version="4" name="clu_mrp">
	<quorumd interval="1" label="clu_mrp" min_score="1" tko="30" votes="1">
		<heuristic interval="2" program="/bin/true" score="1"/>
	</quorumd>
	<fence_daemon post_fail_delay="40" post_join_delay="3"/>
	<clusternodes>
		<clusternode name="node1" nodeid="1" votes="1">
			<fence>
				<method name="1">
					<device lanplus="1" name="node1-ipmi"/>
				</method>
			</fence>
		</clusternode>
		<clusternode name="node2" nodeid="2" votes="1">
			<fence>
				<method name="1">
					<device lanplus="1" name="node2-ipmi"/>
				</method>
			</fence>
		</clusternode>
	</clusternodes>
	<cman deadnode_timer="38"/>
	<fencedevices>
		<fencedevice agent="fence_ipmilan" auth="none" ipaddr="node1-ipmi"
login="root" name="node1-ipmi" passwd="xxx"/>
		<fencedevice agent="fence_ipmilan" auth="none" ipaddr="node2-ipmi"
login="root" name="node2-ipmi" passwd="xxx"/>
	</fencedevices>
	<rm>
		<failoverdomains/>
		<resources/>
	</rm>
</cluster>


Could someone tell me with this is a expected behaviour? Shouldn't rgmanager
start up automatically in this case?

Thank you all,

Celso.

-- 
*Celso Kopp Webber*

celso at webbertek.com.br <mailto:celso at webbertek.com.br>

*Webbertek - Opensource Knowledge*
(41) 8813-1919 - celular
(41) 4063-8448, ramal 102 - fixo


-- 
Esta mensagem foi verificada pelo sistema de antiv?rus e
 acredita-se estar livre de perigo.



From celso at webbertek.com.br  Fri Feb  8 13:25:09 2008
From: celso at webbertek.com.br (Celso K. Webber)
Date: Fri, 8 Feb 2008 11:25:09 -0200
Subject: [Linux-cluster] RHCS 5.1 latest packages, 2-node cluster,
	doesn't come up with only 1 node
In-Reply-To: <20080208130449.M21432@webbertek.com.br>
References: <20080208130449.M21432@webbertek.com.br>
Message-ID: <20080208132257.M22787@webbertek.com.br>

Hello,

I forgot to add some versioning information from the Cluster packages, here
they are:

* Main cluster packages:
cman-2.0.73-1.el5_1.1.x86_64.rpm
openais-0.80.3-7.el5.x86_64.rpm
perl-Net-Telnet-3.03-5.noarch.rpm 

* Admin tools packages:
Cluster_Administration-en-US-5.1.0-7.noarch.rpm 
cluster-cim-0.10.0-5.el5_1.1.x86_64.rpm 
cluster-snmp-0.10.0-5.el5_1.1.x86_64.rpm 
luci-0.10.0-6.el5.x86_64.rpm 
modcluster-0.10.0-5.el5_1.1.x86_64.rpm 
rgmanager-2.0.31-1.el5.x86_64.rpm 
ricci-0.10.0-6.el5.x86_64.rpm 
system-config-cluster-1.0.50-1.3.noarch.rpm 
tog-pegasus-2.6.1-2.el5_1.1.*.rpm
oddjob-*.rpm

Thank you,

Celso.

On Fri, 8 Feb 2008 11:18:20 -0200, Celso K. Webber wrote
> Hello all,
> 
> I'm having a situation here that might be a bug, or maybe it's some mistake
> from my part.
> 
> * Scenario: 2-node cluster on Dell PE-2950 servers, Dell MD-3000 
> storage (SAS direct-attach), using IPMI-Lan as fencing devices, 2 
> NICs on each server
> (public and heartbeat networks), using Qdisk in the shared storage
> 
> * Problem: if I shutdown one node and keep it shut down, and then 
> reboot the other node, although CMAN comes up after 5 minutes or so, 
> rgmanager does not start.
> 
> I remember having this same problem with RHCS 4.4, but it was solved 
> by upgrading to 4.5. But with RHCS 4.4 CMAN didn't come up, with my 
> setup in RHCS
> 5.1 CMAN comes up after giving up waiting for the other node, but rgmanager
> doesn't, so services get not started. This is bad in an unattended situation.
> 
> Here are some steps and details I've collected from the machine 
> (sorry for a so long message):
> 
> * Shutdown node1
> 
> * Reboot node2
>   - after boot, took around 5 minutes in the "start fencing" message
>   - reported a startup FAIL for the "cman" service after this period 
> of time
> 
> * Boot completed
> 
> * Logged in:
>   - clustat reported inquorate and quorum disk as "offline":
> [root at mrp02 ~]# clustat
> msg_open: No such file or directory
> Member Status: Inquorate
> 
>   Member Name                        ID   Status
>   ------ ----                        ---- ------
>   node1                                 1 Offline
>   node2                                 2 Online, Local
>   /dev/sdc1                             0 Offline
> 
> * After a few seconds, clustat reported quorate and quorum disk as "online":
> [root at mrp02 ~]# clustat
> msg_open: No such file or directory
> Member Status: Quorate
> 
>   Member Name                        ID   Status
>   ------ ----                        ---- ------
>   node1                                 1 Offline
>   node2                                 2 Online, Local
>   /dev/sdc1                             0 Online, Quorum Disk
> 
> * Logs in /var/log/messages showed that after qdiskd assumed "master 
> role", cman reported regaining quorum:
> Feb  7 20:06:59 mrp02 qdiskd[5854]: <info> Assuming master role
> Feb  7 20:07:00 mrp02 ccsd[5694]: Cluster is not quorate.  Refusing connection.
> 
> Feb  7 20:07:00 mrp02 ccsd[5694]: Error while processing connect: Connection
> refused
> 
> Feb  7 20:07:00 mrp02 ccsd[5694]: Cluster is not quorate.  Refusing connection.
> 
> Feb  7 20:07:00 mrp02 ccsd[5694]: Error while processing connect: Connection
> refused
> 
> Feb  7 20:07:00 mrp02 openais[5714]: [CMAN ] quorum regained,
>  resuming activity
> Feb  7 20:07:01 mrp02 clurgmgrd[7523]: <notice> Quorum formed, starting
> ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
>   -> Note that rgmanager started after quorum was regained, but 
> seemed not to work anymore later on (please see below).
> Feb  7 20:07:01 mrp02 kernel: dlm: no local IP address has been set
> Feb  7 20:07:01 mrp02 kernel: dlm: cannot start dlm lowcomms -107
> 
> * Noticed that in "clustat" there as an error message:
>   -> msg_open: No such file or directory
> 
> * Checked rgmanager to see if it was related:
> [root at mrp02 ~]# chkconfig --list rgmanager
> rgmanager       0:off   1:off   2:on    3:on    4:on    5:on    6:off
> [root at mrp02 ~]# service rgmanager status
> clurgmgrd dead but pid file exists
> 
> * Since rgmanager did not come back by itself, restarted it manually:
> [root at mrp02 init.d]# service rgmanager restart
> Starting Cluster Service Manager: dlm: Using TCP for communications
>                                                            [  OK  ]
> 
> * This time clustat did not show the "msg_open" error anymore:
> [root at mrp02 init.d]# clustat
> Member Status: Quorate
> 
>   Member Name                        ID   Status
>   ------ ----                        ---- ------
>   node1                                 1 Offline
>   node2                                 2 Online, Local
>   /dev/sdc1                             0 Online, Quorum Disk
> 
> * It seems to me that in case of cman regaining quorum after a lost 
> quorum, at least in a initial "no quorum" state, rgmanager is not 
> "woke up"
> 
> * This setup had no services configured, so I repeated the test 
> configuring a simple start/stop/status service using the "crond" 
> service as an example, same results
> 
> * Copy /etc/cluster/cluster.conf:
>   -> Notice: I'm using Qdiskd with "always ok" heuristics, since the 
> customer does not have a "always-on" IP tiebraker device to use with 
> a "ping" command as heuristics. <?xml version="1.0"?> <cluster 
> config_version="4" name="clu_mrp"> 	<quorumd interval="1" 
> label="clu_mrp" min_score="1" tko="30" votes="1"> 		<heuristic 
> interval="2" program="/bin/true" score="1"/> 	</quorumd> 
> 	<fence_daemon post_fail_delay="40" post_join_delay="3"/> 	<clusternodes>
> 		<clusternode name="node1" nodeid="1" votes="1">
> 			<fence>
> 				<method name="1">
> 					<device lanplus="1" name="node1-ipmi"/>
> 				</method>
> 			</fence>
> 		</clusternode>
> 		<clusternode name="node2" nodeid="2" votes="1">
> 			<fence>
> 				<method name="1">
> 					<device lanplus="1" name="node2-ipmi"/>
> 				</method>
> 			</fence>
> 		</clusternode>
> 	</clusternodes>
> 	<cman deadnode_timer="38"/>
> 	<fencedevices>
> 		<fencedevice agent="fence_ipmilan" auth="none" ipaddr="node1-ipmi"
> login="root" name="node1-ipmi" passwd="xxx"/>
> 		<fencedevice agent="fence_ipmilan" auth="none" ipaddr="node2-ipmi"
> login="root" name="node2-ipmi" passwd="xxx"/>
> 	</fencedevices>
> 	<rm>
> 		<failoverdomains/>
> 		<resources/>
> 	</rm>
> </cluster>
> 
> Could someone tell me with this is a expected behaviour? Shouldn't rgmanager
> start up automatically in this case?
> 
> Thank you all,
> 
> Celso.
> 
> -- 
> *Celso Kopp Webber*
> 
> celso at webbertek.com.br <mailto:celso at webbertek.com.br>
> 
> *Webbertek - Opensource Knowledge*
> (41) 8813-1919 - celular
> (41) 4063-8448, ramal 102 - fixo
> 
> -- 
> Esta mensagem foi verificada pelo sistema de antiv?rus e
>  acredita-se estar livre de perigo.
> 
> --
> Linux-cluster mailing list
> Linux-cluster at redhat.com
> https://www.redhat.com/mailman/listinfo/linux-cluster


-- 
*Celso Kopp Webber*

celso at webbertek.com.br <mailto:celso at webbertek.com.br>

*Webbertek - Opensource Knowledge*
(41) 8813-1919 - celular
(41) 4063-8448, ramal 102 - fixo


-- 
Esta mensagem foi verificada pelo sistema de antiv?rus e
 acredita-se estar livre de perigo.



From lhh at redhat.com  Fri Feb  8 15:12:57 2008
From: lhh at redhat.com (Lon Hohberger)
Date: Fri, 08 Feb 2008 10:12:57 -0500
Subject: [Linux-cluster] 2-node tie-breaking
In-Reply-To: <20080207230727.GE63223@widexs.nl>
References: <alpine.LRH.1.00.0802071523160.7145@skynet.shatteredsilicon.net>
	<1202412937.2938.55.camel@localhost.localdomain>
	<47AB71D2.2040201@bobich.net>
	<1202421366.2938.70.camel@localhost.localdomain>
	<47AB840C.8040905@bobich.net> <20080207223951.GB15215@localhost>
	<20080207230727.GE63223@widexs.nl>
Message-ID: <1202483577.21504.96.camel@ayanami.boston.devel.redhat.com>

On Fri, 2008-02-08 at 00:07 +0100, Peter Bosgraaf wrote:
> Hi,
> 
> On Thu, Feb 07, 2008 at 11:39:51PM +0100, Jakub Suchy wrote:
> > >> Well, here's a cheap 'out' ;)
> > >> Ebay item # 250213910258
> > >> 8 port WTI NPS for $70 + $15 s/h.
> > >
> > > Indeed, that would be tempting if it wasn't on the wrong side of the 
> > > atlantic. A more local search for similar things doesn't seem to come up 
> > > with anything. :-(
> 
> *Don't flame me, i didn't want to spam the list with commerial stuff but
> thought this might help you out*
> 
> If your interested in a powerswitch solution i would recommend you to look
> at the solutions from www.lubenco.nl 
> 
> They have 8 port (C13) 10 amp powerswitches with load monitoring and
> snmp configuration support for about 117 euro a pice. (new) If your
> willing to buy in bulk the price even drops well below 100 euro.

Guys, this is good stuff - the problem is we need to make an agent that
can talk to them before we can really solve Gordan's problem.  Does
anyone want to volunteer?   I'll write up a fence agent API "howto"
today ...

-- Lon



From johannes.russek at io-consulting.net  Fri Feb  8 15:15:51 2008
From: johannes.russek at io-consulting.net (jr)
Date: Fri, 08 Feb 2008 16:15:51 +0100
Subject: [Linux-cluster] 2-node tie-breaking
In-Reply-To: <1202483577.21504.96.camel@ayanami.boston.devel.redhat.com>
References: <alpine.LRH.1.00.0802071523160.7145@skynet.shatteredsilicon.net>
	<1202412937.2938.55.camel@localhost.localdomain>
	<47AB71D2.2040201@bobich.net>
	<1202421366.2938.70.camel@localhost.localdomain>
	<47AB840C.8040905@bobich.net> <20080207223951.GB15215@localhost>
	<20080207230727.GE63223@widexs.nl>
	<1202483577.21504.96.camel@ayanami.boston.devel.redhat.com>
Message-ID: <1202483751.3388.30.camel@admc.win-rar.local>


> Guys, this is good stuff - the problem is we need to make an agent that
> can talk to them before we can really solve Gordan's problem.  Does
> anyone want to volunteer?   I'll write up a fence agent API "howto"
> today ...
> 
> -- Lon

well, if there would be any kind of documentation on their webpage that
tells anything about how to control it, it'd be simple.. but there just
isn't (or i couldn't find).
johannes

> 
> --
> Linux-cluster mailing list
> Linux-cluster at redhat.com
> https://www.redhat.com/mailman/listinfo/linux-cluster



From gordan at bobich.net  Fri Feb  8 15:32:27 2008
From: gordan at bobich.net (gordan at bobich.net)
Date: Fri, 8 Feb 2008 15:32:27 +0000 (GMT)
Subject: [Linux-cluster] 2-node tie-breaking
In-Reply-To: <1202483577.21504.96.camel@ayanami.boston.devel.redhat.com>
References: <alpine.LRH.1.00.0802071523160.7145@skynet.shatteredsilicon.net>
	<1202412937.2938.55.camel@localhost.localdomain>
	<47AB71D2.2040201@bobich.net>
	<1202421366.2938.70.camel@localhost.localdomain>
	<47AB840C.8040905@bobich.net> <20080207223951.GB15215@localhost>
	<20080207230727.GE63223@widexs.nl>
	<1202483577.21504.96.camel@ayanami.boston.devel.redhat.com>
Message-ID: <alpine.LRH.1.00.0802081514250.15647@skynet.shatteredsilicon.net>

On Fri, 8 Feb 2008, Lon Hohberger wrote:

>>>>> Well, here's a cheap 'out' ;)
>>>>> Ebay item # 250213910258
>>>>> 8 port WTI NPS for $70 + $15 s/h.
>>>>
>>>> Indeed, that would be tempting if it wasn't on the wrong side of the
>>>> atlantic. A more local search for similar things doesn't seem to come up
>>>> with anything. :-(
>>
>> *Don't flame me, i didn't want to spam the list with commerial stuff but
>> thought this might help you out*
>>
>> If your interested in a powerswitch solution i would recommend you to look
>> at the solutions from www.lubenco.nl
>>
>> They have 8 port (C13) 10 amp powerswitches with load monitoring and
>> snmp configuration support for about 117 euro a pice. (new) If your
>> willing to buy in bulk the price even drops well below 100 euro.
>
> Guys, this is good stuff - the problem is we need to make an agent that
> can talk to them before we can really solve Gordan's problem.  Does
> anyone want to volunteer?   I'll write up a fence agent API "howto"
> today ...

Thanks for all this, guys, much appreciated. :-)

I just had another thought. Most motherboards these days are ATX, which 
means ATX type "short-pins-to-power-on" power switches. That means that as 
a _REALLY_ cheap solution I could just get something like a small relay 
switch and wire it into the serial port. When a pin on RS232 goes high 
(e.g. DTR), it activates the switch. I think it would be pretty reliable, 
and the total cost of components would be pennies. The fence agent would 
also be a total of about 10 lines of code, too. :)

Can anyone think of why this wouldn't work? OK, it involves a bit of DIY, 
but it would work for a 2-node cluster. With more nodes, pulsing the power 
switch repeatedly might bring the node back up, which would be less than 
ideal if it's _really_ nastily intermittent. But since this isn't really 
scalable to cluster with more than 3 nodes (2 serial ports per node), it 
probably doesn't matter.

Gordan



From peter at widexs.nl  Fri Feb  8 15:42:17 2008
From: peter at widexs.nl (Peter Bosgraaf)
Date: Fri, 8 Feb 2008 16:42:17 +0100
Subject: [Linux-cluster] 2-node tie-breaking
In-Reply-To: <1202483751.3388.30.camel@admc.win-rar.local>
References: <alpine.LRH.1.00.0802071523160.7145@skynet.shatteredsilicon.net>
	<1202412937.2938.55.camel@localhost.localdomain>
	<47AB71D2.2040201@bobich.net>
	<1202421366.2938.70.camel@localhost.localdomain>
	<47AB840C.8040905@bobich.net> <20080207223951.GB15215@localhost>
	<20080207230727.GE63223@widexs.nl>
	<1202483577.21504.96.camel@ayanami.boston.devel.redhat.com>
	<1202483751.3388.30.camel@admc.win-rar.local>
Message-ID: <20080208154217.GA68659@widexs.nl>

Hi,

On Fri, Feb 08, 2008 at 04:15:51PM +0100, jr wrote:
> well, if there would be any kind of documentation on their webpage that
> tells anything about how to control it, it'd be simple.. but there just
> isn't (or i couldn't find).
> johannes
> 

Their a small company which explains the rather sober website.
I could mail you the MIB if your interested.

Also i'm sure they would be willing to send you a sample to testdrive it
for a while, i know we got one when we asked for it.

Cheers,

-- 
Peter Bosgraaf  //  Hosting Architect  //  WideXS
PBG666-RIPE     //  T: 023-5698070     //  F: 023-5698099

PGP KeyID: 0xB436C25B (hkp://pgp.mit.edu)
Fingerprint: 49D1 E1EE 3142 31F2 BDF0  CBBF 9675 8267 B436 C25B



From jdozarchuk at babcock.com  Fri Feb  8 17:47:26 2008
From: jdozarchuk at babcock.com (Ozarchuk, John D)
Date: Fri, 8 Feb 2008 12:47:26 -0500
Subject: [Linux-cluster] NFS clustering - how to use fsid= options for
	theexports
References: <3DDA6E3E456E144DA3BB0A62A7F7F77901CACD9D@SKYHQAMX08.klasi.is>
Message-ID: <89FEB3FDB047394C998E7A0077715A670DCB66@barbpo4.bwes.net>

I have a simliar setup, but I just set a Service to manage the IP address and filesystems. It's not that difficult to manage two /etc/exports files...  

________________________________

From: linux-cluster-bounces at redhat.com on behalf of Finnur ?rn Gu?mundsson - TM Software
Sent: Thu 2/7/2008 12:24 PM
To: linux-cluster at redhat.com
Subject: [Linux-cluster] NFS clustering - how to use fsid= options for theexports



Hi,

 

I have setup a active-standby NFS cluster.

 

Everything is working like it should, except for one thing.

 

In HP ServiceGuard you use /etc/exports on each node in a active-standby cluster to manage exports, and there you can use the fsid=X for each filesystem you want to export (helps with stale nfs errors after a failover).

 

In RHCS i cannot seem to get the server to correctly use the options ...

 

Here is my service:

 

                <service autostart="1" domain="nfsdomain" name="nfs">

                        <nfsexport name="home1">

                                <nfsclient name="nfshome" options="rw,sync,fsid=150" path="/home" target="10.50.102.128/25"/>

                                <nfsclient name="nfsdata" options="rw,fsid=50,sync" path="/data" target="10.50.102.128/25"/>

                                <clusterfs ref="home"/>

                                <ip ref="10.10.10.10"/>

                                <clusterfs ref="data"/>

                        </nfsexport>

 

Would this not be the correct way ? Is there a other way to do this except for manually using /etc/exports and just have RHCS manage the IP address transfer beteween the nodes?

 

K?r kve?ja / Best Regards,

Finnur ?rn Gu?mundsson
Network Engineer - Network Operations
fog at t.is <mailto:fog at t.is> 

TM Software
Ur?arhvarf 6, IS-203 K?pavogur, Iceland
Tel: +354 545 3000 - fax +354 545 3610
www.tm-software.is <http://www.tm-software.is/> 

This e-mail message and any attachments are confidential and may be privileged. TM Software e-mail disclaimer: www.tm-software.is/disclaimer <http://www.tm-software.is/disclaimer>  




-----------------------------------------
This message is intended only for the individual or entity to which
it is addressed and contains information that is proprietary to The
Babcock & Wilcox Company and/or its affiliates, or may be otherwise
confidential.  If the reader of this message is not the intended
recipient, or the employee agent responsible for delivering the
message to the intended recipient, you are hereby notified that any
dissemination, distribution or copying of this communication is
strictly prohibited.  If you have received this communication in
error, please notify the sender immediately by return e-mail and
delete this message from your computer.  Thank you.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: winmail.dat
Type: application/ms-tnef
Size: 7097 bytes
Desc: not available
URL: <http://listman.redhat.com/archives/linux-cluster/attachments/20080208/1e743098/attachment.bin>

From fog at t.is  Fri Feb  8 17:56:58 2008
From: fog at t.is (=?iso-8859-1?Q?Finnur_=D6rn_Gu=F0mundsson_-_TM_Software?=)
Date: Fri, 8 Feb 2008 17:56:58 -0000
Subject: [Linux-cluster] NFS clustering - how to use fsid= options for
	theexports
In-Reply-To: <89FEB3FDB047394C998E7A0077715A670DCB66@barbpo4.bwes.net>
References: <3DDA6E3E456E144DA3BB0A62A7F7F77901CACD9D@SKYHQAMX08.klasi.is>
	<89FEB3FDB047394C998E7A0077715A670DCB66@barbpo4.bwes.net>
Message-ID: <3DDA6E3E456E144DA3BB0A62A7F7F77901CACFDA@SKYHQAMX08.klasi.is>

Exactly, that is what i ended up with!

 

Thanks though,

 

Finnur

 

From: linux-cluster-bounces at redhat.com [mailto:linux-cluster-bounces at redhat.com] On Behalf Of Ozarchuk, John D
Sent: 8. febr?ar 2008 17:47
To: linux clustering
Subject: RE: [Linux-cluster] NFS clustering - how to use fsid= options for theexports

 

I have a simliar setup, but I just set a Service to manage the IP address and filesystems. It's not that difficult to manage two /etc/exports files...  

 

________________________________

From: linux-cluster-bounces at redhat.com on behalf of Finnur ?rn Gu?mundsson - TM Software
Sent: Thu 2/7/2008 12:24 PM
To: linux-cluster at redhat.com
Subject: [Linux-cluster] NFS clustering - how to use fsid= options for theexports

Hi,

 

I have setup a active-standby NFS cluster.

 

Everything is working like it should, except for one thing.

 

In HP ServiceGuard you use /etc/exports on each node in a active-standby cluster to manage exports, and there you can use the fsid=X for each filesystem you want to export (helps with stale nfs errors after a failover).

 

In RHCS i cannot seem to get the server to correctly use the options ...

 

Here is my service:

 

                <service autostart="1" domain="nfsdomain" name="nfs">

                        <nfsexport name="home1">

                                <nfsclient name="nfshome" options="rw,sync,fsid=150" path="/home" target="10.50.102.128/25"/>

                                <nfsclient name="nfsdata" options="rw,fsid=50,sync" path="/data" target="10.50.102.128/25"/>

                                <clusterfs ref="home"/>

                                <ip ref="10.10.10.10"/>

                                <clusterfs ref="data"/>

                        </nfsexport>

 

Would this not be the correct way ? Is there a other way to do this except for manually using /etc/exports and just have RHCS manage the IP address transfer beteween the nodes?

 

K?r kve?ja / Best Regards,

Finnur ?rn Gu?mundsson
Network Engineer - Network Operations
fog at t.is

TM Software
Ur?arhvarf 6, IS-203 K?pavogur, Iceland
Tel: +354 545 3000 - fax +354 545 3610
www.tm-software.is <http://www.tm-software.is/> 

This e-mail message and any attachments are confidential and may be privileged. TM Software e-mail disclaimer: www.tm-software.is/disclaimer 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://listman.redhat.com/archives/linux-cluster/attachments/20080208/b59b7d83/attachment.htm>

From lhh at redhat.com  Fri Feb  8 21:15:36 2008
From: lhh at redhat.com (Lon Hohberger)
Date: Fri, 08 Feb 2008 16:15:36 -0500
Subject: [Linux-cluster] RHCS 5.1 latest packages, 2-node cluster,
	doesn't come up with only 1 node
In-Reply-To: <20080208130449.M21432@webbertek.com.br>
References: <20080208130449.M21432@webbertek.com.br>
Message-ID: <1202505336.6443.87.camel@ayanami.boston.devel.redhat.com>

On Fri, 2008-02-08 at 11:18 -0200, Celso K. Webber wrote:
> Feb  7 20:07:01 mrp02 kernel: dlm: no local IP address has been set
> Feb  7 20:07:01 mrp02 kernel: dlm: cannot start dlm lowcomms -107

This is why rgmanager didn't work (and possibly even exited).  Does
'uname -n' match what's in cluster.conf?

-- Lon



From lhh at redhat.com  Fri Feb  8 21:19:27 2008
From: lhh at redhat.com (Lon Hohberger)
Date: Fri, 08 Feb 2008 16:19:27 -0500
Subject: [Linux-cluster] RHCS 5.1 latest packages, 2-node cluster,
	doesn't come up with only 1 node
In-Reply-To: <1202505336.6443.87.camel@ayanami.boston.devel.redhat.com>
References: <20080208130449.M21432@webbertek.com.br>
	<1202505336.6443.87.camel@ayanami.boston.devel.redhat.com>
Message-ID: <1202505567.6443.91.camel@ayanami.boston.devel.redhat.com>

On Fri, 2008-02-08 at 16:15 -0500, Lon Hohberger wrote:
> On Fri, 2008-02-08 at 11:18 -0200, Celso K. Webber wrote:
> > Feb  7 20:07:01 mrp02 kernel: dlm: no local IP address has been set
> > Feb  7 20:07:01 mrp02 kernel: dlm: cannot start dlm lowcomms -107
> 
> This is why rgmanager didn't work (and possibly even exited).  Does
> 'uname -n' match what's in cluster.conf?

Hmm - strange that trying to start it again would cause dlm to suddenly
work.  I wonder why that would be.

In 4.4, we had a bug in cman where it wasn't passing transitions of the
quorum disk down to the internal CMAN service manager, but that's fixed.

rgmanager literally just sits there waiting for quorum before trying to
acquire the DLM lockspace.

So, it looks like if we stay inquorate for some time, dlm_controld or
groupd doesn't correctly set the local node name.

-- Lon



From lhh at redhat.com  Fri Feb  8 21:25:49 2008
From: lhh at redhat.com (Lon Hohberger)
Date: Fri, 08 Feb 2008 16:25:49 -0500
Subject: [Linux-cluster] Two-node cluster unpatched B doesn't see patched A
In-Reply-To: <47AB8156.6010205@hp.com>
References: <47AB8156.6010205@hp.com>
Message-ID: <1202505949.6443.97.camel@ayanami.boston.devel.redhat.com>

On Thu, 2008-02-07 at 17:08 -0500, Sutton, Harry (MSE) wrote:

> On my production cluster, which uses a Quorum Disk in place of the third 
> node, I completed steps 1 and 2 on Node A, but the cluster did NOT 
> reform. cman sends out its advertisement, and I can see that Node B 
> receives it (by looking at the tcpdump traces), but Node B never responds.

That's strange, I hardly think it's related to qdiskd.

Maybe check 'cman_tool version' on both and ensure that the cluster.conf
version matches the output of 'cman_tool version' - that's a common way
to prevent the cluster from forming on RHEL4.


If they're out of sync:

  * get the right cluster.conf in place & bump the config version #
  * run 'cman_tool version -r <new_config_version_#>'
  * copy cluster.conf to other node

Note: Restoring the nodes to the same package versions will have utterly
no effect if the config version is out of sync!

-- Lon




From celso at webbertek.com.br  Fri Feb  8 21:33:33 2008
From: celso at webbertek.com.br (Celso K. Webber)
Date: Fri, 8 Feb 2008 19:33:33 -0200
Subject: [Linux-cluster] RHCS 5.1 latest packages, 2-node cluster,
	doesn't come up with only 1 node
In-Reply-To: <1202505336.6443.87.camel@ayanami.boston.devel.redhat.com>
References: <20080208130449.M21432@webbertek.com.br>
	<1202505336.6443.87.camel@ayanami.boston.devel.redhat.com>
Message-ID: <20080208211828.M67336@webbertek.com.br>

Hi Lon,

On Fri, 08 Feb 2008 16:15:36 -0500, Lon Hohberger wrote
> On Fri, 2008-02-08 at 11:18 -0200, Celso K. Webber wrote:
> > Feb  7 20:07:01 mrp02 kernel: dlm: no local IP address has been set
> > Feb  7 20:07:01 mrp02 kernel: dlm: cannot start dlm lowcomms -107
> 
> This is why rgmanager didn't work (and possibly even exited).  Does
> 'uname -n' match what's in cluster.conf?
> 
No, it does not! I didn't know it should match, I'm configuring RHCS Clusters 
since version 2.1 and this never bothered me, sorry!!!

Well, I usually do the following in /etc/hosts:
-> assume network 192.168.1.0/24 is for public access
-> assume network 10.0.0.0/8 is for heartbeat

192.168.1.1   realservername1.domainname realservername1
192.168.1.2   realservername2.domainname realservername2

10.0.0.1      node1.localdomain node1
10.0.0.2      node2.localdomain node2

192.168.1.3   servicename1.domainname servicename1
192.168.1.4   servicename2.domainname servicename2
... and so on for other virtual IPs for services ...

Then I configure in cluster.conf the names associated with the private 
addresses/interfaces, so that I'm sure that heartbeat traffic is going 
through the correct interfaces.

For obvious reasons, "uname -n" returns the public hostnames, such as 
realservername1.domainname.

I noticed that from some time there is a question in the FAQ explaining how 
to "bind" the heartbeat traffic to a specific interface/address. But I was 
happy with my solution, specially because the answer to that question 
suggested touching the init script, and I don't like to alter standard system 
files, specially init scripts. At least in RHCS v4, I didn't find a better 
way to "bind" the heartbeat traffic to a specific interface. I didn't 
experiment about this with RHCS v5, I just went on with my previous method.

For me this is common practice, for instance, Oracle Database respects an 
environment variable called ORACLE_HOSTNAME, so that you can "instruct" the 
several utilities to consider that name instead of the real server's name. 
This is very useful in a Cluster environment.

Please tell me:
* is it really wrong set the node names in cluster.conf to a name different 
to that reported by "uname -n"?
* if it is "ugly" or considered wrong, what is the best way to instruct CMAN 
which interface to use for heartbeat?
* does this solution work both for RHCS v4 and v5?
* would it be better to have only one interface for public and heartbeat 
traffic, maybe channel bonding dual NICs?
* is there any other significant difference between RHCSv4 and v5 I should be 
aware of?

As always, thank you very very much for your support!

Regards,

Celso.
-- 
*Celso Kopp Webber*

celso at webbertek.com.br <mailto:celso at webbertek.com.br>

*Webbertek - Opensource Knowledge*
(41) 8813-1919 - celular
(41) 4063-8448, ramal 102 - fixo


-- 
Esta mensagem foi verificada pelo sistema de antiv?rus e
 acredita-se estar livre de perigo.



From harry.sutton at hp.com  Fri Feb  8 22:00:08 2008
From: harry.sutton at hp.com (Sutton, Harry (MSE))
Date: Fri, 08 Feb 2008 17:00:08 -0500
Subject: [Linux-cluster] Two-node cluster unpatched B doesn't see patched A
In-Reply-To: <1202505949.6443.97.camel@ayanami.boston.devel.redhat.com>
References: <47AB8156.6010205@hp.com>
	<1202505949.6443.97.camel@ayanami.boston.devel.redhat.com>
Message-ID: <47ACD0E8.4050603@hp.com>

Lon Hohberger wrote:
> Maybe check 'cman_tool version' on both and ensure that the cluster.conf
> version matches the output of 'cman_tool version' - that's a common way
> to prevent the cluster from forming on RHEL4.
>
>   
No joy there, Lon - the values match.

    /Harry
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/x-pkcs7-signature
Size: 6255 bytes
Desc: S/MIME Cryptographic Signature
URL: <http://listman.redhat.com/archives/linux-cluster/attachments/20080208/59c6c88d/attachment.bin>

From lhh at redhat.com  Fri Feb  8 22:16:49 2008
From: lhh at redhat.com (Lon Hohberger)
Date: Fri, 08 Feb 2008 17:16:49 -0500
Subject: [Linux-cluster] RHCS 5.1 latest packages, 2-node cluster,
	doesn't come up with only 1 node
In-Reply-To: <20080208211828.M67336@webbertek.com.br>
References: <20080208130449.M21432@webbertek.com.br>
	<1202505336.6443.87.camel@ayanami.boston.devel.redhat.com>
	<20080208211828.M67336@webbertek.com.br>
Message-ID: <1202509009.6443.140.camel@ayanami.boston.devel.redhat.com>

On Fri, 2008-02-08 at 19:33 -0200, Celso K. Webber wrote:
> Hi Lon,
> 
> On Fri, 08 Feb 2008 16:15:36 -0500, Lon Hohberger wrote
> > On Fri, 2008-02-08 at 11:18 -0200, Celso K. Webber wrote:
> > > Feb  7 20:07:01 mrp02 kernel: dlm: no local IP address has been set
> > > Feb  7 20:07:01 mrp02 kernel: dlm: cannot start dlm lowcomms -107
> > 
> > This is why rgmanager didn't work (and possibly even exited).  Does
> > 'uname -n' match what's in cluster.conf?
> > 
> No, it does not! I didn't know it should match, I'm configuring RHCS Clusters 
> since version 2.1 and this never bothered me, sorry!!!
> 
> Well, I usually do the following in /etc/hosts:
> -> assume network 192.168.1.0/24 is for public access
> -> assume network 10.0.0.0/8 is for heartbeat
> 
> 192.168.1.1   realservername1.domainname realservername1
> 192.168.1.2   realservername2.domainname realservername2
> 
> 10.0.0.1      node1.localdomain node1
> 10.0.0.2      node2.localdomain node2
> 
> 192.168.1.3   servicename1.domainname servicename1
> 192.168.1.4   servicename2.domainname servicename2
> ... and so on for other virtual IPs for services ...
> 
> Then I configure in cluster.conf the names associated with the private 
> addresses/interfaces, so that I'm sure that heartbeat traffic is going 
> through the correct interfaces.
> 
> For obvious reasons, "uname -n" returns the public hostnames, such as 
> realservername1.domainname.
> 
> I noticed that from some time there is a question in the FAQ explaining how 
> to "bind" the heartbeat traffic to a specific interface/address. But I was 
> happy with my solution, specially because the answer to that question 
> suggested touching the init script, and I don't like to alter standard system 
> files, specially init scripts. At least in RHCS v4, I didn't find a better 
> way to "bind" the heartbeat traffic to a specific interface. I didn't 
> experiment about this with RHCS v5, I just went on with my previous method.
> 
> For me this is common practice, for instance, Oracle Database respects an 
> environment variable called ORACLE_HOSTNAME, so that you can "instruct" the 
> several utilities to consider that name instead of the real server's name. 
> This is very useful in a Cluster environment.
> 
> Please tell me:
> * is it really wrong set the node names in cluster.conf to a name different 
> to that reported by "uname -n"?
> * if it is "ugly" or considered wrong, what is the best way to instruct CMAN 
> which interface to use for heartbeat?

I think it's mostly fixed in RHEL5.

We have updated the CMAN init script for RHEL5 to
allow /etc/sysconfig/cluster to have "NODENAME=preferred_host_name".  It
will go out with the next update, but here it is in CVS:

*massive url*

http://sources.redhat.com/cgi-bin/cvsweb.cgi/~checkout~/cluster/cman/init.d/Attic/cman?rev=1.26.2.6&content-type=text/plain&cvsroot=cluster&hideattic=0&only_with_tag=RHEL5

tinyurl:

http://tinyurl.com/2fg6nd


It still could be a bug.  The dlm unable to determine the local hostname
is definitely why rgmanager died (it needs the DLM!).  Updating the
script / trying to force CMAN with a specific node name is just one way
to eliminate a possible cause (and it might fix it, too ;) ).


> * does this solution work both for RHCS v4 and v5?

The RHEL5 script is not backwards compatible, but cman_tool join -n
<preferred_host_name> is.


> * would it be better to have only one interface for public and heartbeat 
> traffic, maybe channel bonding dual NICs?

Better is certainly a matter of perception in this case.  I would expect
you'd want to get your current configuration working before altering
your network topology.  Also, it's not like your configuration is
particularly strange...


> * is there any other significant difference between RHCSv4 and v5 I should be 
> aware of?


> As always, thank you very very much for your support!

We do what we can, but please keep in mind that a public mailing list
isn't a very good support forum compared to (for example): 

  https://www.redhat.com/apps/support/

-- Lon



From marcos at digitaltecnologia.info  Sat Feb  9 08:26:22 2008
From: marcos at digitaltecnologia.info (Marcos Ferreira da Silva)
Date: Sat, 9 Feb 2008 03:26:22 -0500
Subject: [Linux-cluster] Fenced failed
Message-ID: <ff15887d7018409b85c1d36f5105d36c@Mail61.safesecureweb.com>

I have two nodes and in the log appear many messages:

Feb  9 06:22:39 vserver1 ccsd[18304]: process_get: Invalid connection descriptor received.
Feb  9 06:22:39 vserver1 ccsd[18304]: Error while processing get: Invalid request descriptor
Feb  9 06:22:39 vserver1 fenced[18334]: fence "vserver2.teste.br" failed

My cluster.conf

<?xml version="1.0" ?>
<cluster alias="cluster1" config_version="32" name="cluster1">
        <fence_daemon clean_start="0" post_fail_delay="0" post_join_delay="3"/>
        <fence_xvmd family="ipv4" key_file="/etc/cluster/fence_xvm.key"/>
        <clusternodes>
                <clusternode name="vserver1.teste.br" nodeid="1" votes="1">
                        <fence>
                                <method name="1">
                                        <device domain="admin" name="admin"/>
                                </method>
                        </fence>
                </clusternode>
                <clusternode name="vserver2.teste.br" nodeid="2" votes="1">
                        <fence>
                                <method name="1">
                                        <device name="manual" nodename="vserver2.teste.br"/>
                                </method>
                        </fence>
                </clusternode>
        </clusternodes>
        <cman expected_votes="1" two_node="1"/>
        <fencedevices>
                <fencedevice agent="fence_xvm" auth="none" name="admin"/>
                <fencedevice agent="fence_xvm" auth="none" name="aluno"/>
                <fencedevice agent="fence_manual" name="manual"/>
        </fencedevices>
        <rm>
                <failoverdomains>
                        <failoverdomain name="fodAdmin" ordered="1" restricted="1">
                                <failoverdomainnode name="vserver1.teste.br" priority="2"/>
                                <failoverdomainnode name="vserver2.teste.br" priority="1"/>
                        </failoverdomain>
                        <failoverdomain name="fodAluno" ordered="1" restricted="1">
                                <failoverdomainnode name="vserver1.teste.br" priority="2"/>
                                <failoverdomainnode name="vserver2.teste.br" priority="1"/>
                        </failoverdomain>
                </failoverdomains>
                <resources>
                        <clusterfs device="/dev/VGADMIN/LVAdmin" force_unmount="1" fsid="63078" fstype="gfs" mountpoint="/storage/admin" name="gfsadmin" options=""/>
                        <clusterfs device="/dev/VGALUNO/LVAluno" force_unmount="1" fsid="63078" fstype="gfs" mountpoint="/storage/aluno" name="gfsaluno" options=""/>
                </resources>
                <vm autostart="1" domain="fodAdmin" exclusive="0" name="admin" path="/etc/xen" recovery="relocate"/>
                <vm autostart="0" domain="fodAluno" exclusive="0" name="aluno" path="/etc/xen" recovery="relocate"/>
                <service autostart="1" domain="fodAdmin" name="testeAdmin">
                        <clusterfs ref="gfsadmin"/>
                </service>
                <service autostart="1" domain="fodAluno" name="testeAluno">
                        <clusterfs ref="gfsaluno"/>
                </service>
        </rm>
</cluster>

My /etc/hosts:

192.168.200.200 vserver1.teste.br vserver1
192.168.200.201 vserver2.teste.br vserver2

------------------------------
Marcos Ferreira da Silva
Digital Tecnologia
Uberlandia-MG
(34) 9154-0150 / 3226-2534





From marcos at digitaltecnologia.info  Sat Feb  9 12:16:46 2008
From: marcos at digitaltecnologia.info (Marcos Ferreira da Silva)
Date: Sat, 9 Feb 2008 07:16:46 -0500
Subject: [Linux-cluster] Node Offline
Message-ID: <4407800e1b774121bb5e2e7209c9f966@Mail61.safesecureweb.com>

I start my cluster but the nodes don't see each other.

[root at vserv3 ~]# clustat
Member Status: Quorate

  Member Name                        ID   Status
  ------ ----                        ---- ------
  vserv3.uniube.br                      1 Online, Local, rgmanager
  vserv4.uniube.br                      2 Offline

  Service Name         Owner (Last)                   State
  ------- ----         ----- ------                   -----
  service:gfsweb       (none)                         stopped


[root at vserv4 ~]# clustat
Member Status: Quorate

  Member Name                        ID   Status
  ------ ----                        ---- ------
  vserv3.uniube.br                      1 Offline
  vserv4.uniube.br                      2 Online, Local, rgmanager

  Service Name         Owner (Last)                   State
  ------- ----         ----- ------                   -----
  service:gfsweb       (none)                         stopped

The firewall was stopped.
The network is ok.

------------------------------
Marcos Ferreira da Silva
Digital Tecnologia
Uberlandia-MG
(34) 9154-0150 / 3226-2534





From NiCE2Kn0w at web.de  Sat Feb  9 13:51:42 2008
From: NiCE2Kn0w at web.de (Markus Neis)
Date: Sat, 09 Feb 2008 14:51:42 +0100
Subject: [Linux-cluster] gfs locking on samba 
Message-ID: <1939546029@web.de>

Hi there, 
I found out that when I use samba on gfs it's very slow until I use locking = no. This makes any transfer really fast, but in some situations I really need locking. Is there any possibility or any parameters I can use instead?

regards


_____________________________________________________________________
Unbegrenzter Speicherplatz f?r Ihr E-Mail Postfach? Jetzt aktivieren!
http://www.digitaledienste.web.de/freemail/club/lp/?lp=7




From damjan.stulic at edwardjones.com  Sun Feb 10 03:36:30 2008
From: damjan.stulic at edwardjones.com (Stulic,Damjan)
Date: Sat, 9 Feb 2008 21:36:30 -0600
Subject: [Linux-cluster] watchdog: rebootig
In-Reply-To: <1939546029@web.de>
References: <1939546029@web.de>
Message-ID: <B2ED9364017FF54FB9392221F9A498450276E718@nwpsrv08.edj.ad.edwardjones.com>

Having occasional problems with cluster watchdog rebooting servers.
Any ideas on why this might be helping, or how to troubleshoot this
problem?

Any help is greatly appreciated,
Damjan Stulic
IS Security Identity Management
Edward Jones


Feb  9 21:10:58 s_sys at nlpgbrdns-2.edj.ad.edwardjones.com
clurgmgrd[29771]: <notice> Stopping service dns-dhcp-services
Feb  9 21:10:58 s_sys at nlpgbrdns-2.edj.ad.edwardjones.com clurgmgrd:
[29771]: <info> Executing /etc/init.d/named stop
Feb  9 21:10:58 s_sys at nlpgbrdns-2.edj.ad.edwardjones.com named:
succeeded
Feb  9 21:10:58 s_sys at nlpgbrdns-2.edj.ad.edwardjones.com clurgmgrd:
[29771]: <info> Executing /etc/init.d/dhcpd stop
Feb  9 21:10:58 s_sys at nlpgbrdns-2.edj.ad.edwardjones.com dhcpd: dhcpd
shutdown succeeded
Feb  9 21:10:58 s_sys at nlpgbrdns-2.edj.ad.edwardjones.com clurgmgrd:
[29771]: <info> Removing IPv4 address 172.17.163.80 from bond0
Feb  9 21:11:08 s_sys at nlpgbrdns-2.edj.ad.edwardjones.com
clurgmgrd[29771]: <notice> Service dns-dhcp-services is stopped
Feb  9 21:11:08 s_sys at nlpgbrdns-2.edj.ad.edwardjones.com
syslog-ng[3063]: Changing permissions on special file /dev/console
Feb  9 21:11:08 s_sys at nlpgbrdns-2.edj.ad.edwardjones.com kernel:
clurgmgrd[12018]: segfault at 0000000000000050 rip 000000000040399e rsp
0000000041442010 error4
Feb  9 21:11:12 s_sys at nlpgbrdns-2.edj.ad.edwardjones.com
clurgmgrd[29770]: <crit> Watchdog: Daemon died, rebooting...
 
 If you are not the intended recipient of this message (including attachments), or if you have received this message in error, immediately notify us and delete it and any attachments.  If you no longer wish to receive e-mail from Edward Jones, please send this request to messages at edwardjones.com.  You must include the e-mail address that you wish not to receive e-mail communications.  For important additional information related to this e-mail, visit www.edwardjones.com/US_email_disclosure



From jpalmae at gmail.com  Sun Feb 10 23:58:20 2008
From: jpalmae at gmail.com (Jorge Palma)
Date: Sun, 10 Feb 2008 20:58:20 -0300
Subject: [Linux-cluster] watchdog: rebootig
In-Reply-To: <B2ED9364017FF54FB9392221F9A498450276E718@nwpsrv08.edj.ad.edwardjones.com>
References: <1939546029@web.de>
	<B2ED9364017FF54FB9392221F9A498450276E718@nwpsrv08.edj.ad.edwardjones.com>
Message-ID: <5b65f1b10802101558y694a0520p7c1ee62557e429d5@mail.gmail.com>

On Feb 10, 2008 12:36 AM, Stulic,Damjan <damjan.stulic at edwardjones.com> wrote:
> Having occasional problems with cluster watchdog rebooting servers.
> Any ideas on why this might be helping, or how to troubleshoot this
> problem?
>
> Any help is greatly appreciated,
> Damjan Stulic
> IS Security Identity Management
> Edward Jones
>
>
> Feb  9 21:10:58 s_sys at nlpgbrdns-2.edj.ad.edwardjones.com
> clurgmgrd[29771]: <notice> Stopping service dns-dhcp-services
> Feb  9 21:10:58 s_sys at nlpgbrdns-2.edj.ad.edwardjones.com clurgmgrd:
> [29771]: <info> Executing /etc/init.d/named stop
> Feb  9 21:10:58 s_sys at nlpgbrdns-2.edj.ad.edwardjones.com named:
> succeeded
> Feb  9 21:10:58 s_sys at nlpgbrdns-2.edj.ad.edwardjones.com clurgmgrd:
> [29771]: <info> Executing /etc/init.d/dhcpd stop
> Feb  9 21:10:58 s_sys at nlpgbrdns-2.edj.ad.edwardjones.com dhcpd: dhcpd
> shutdown succeeded
> Feb  9 21:10:58 s_sys at nlpgbrdns-2.edj.ad.edwardjones.com clurgmgrd:
> [29771]: <info> Removing IPv4 address 172.17.163.80 from bond0
> Feb  9 21:11:08 s_sys at nlpgbrdns-2.edj.ad.edwardjones.com
> clurgmgrd[29771]: <notice> Service dns-dhcp-services is stopped
> Feb  9 21:11:08 s_sys at nlpgbrdns-2.edj.ad.edwardjones.com
> syslog-ng[3063]: Changing permissions on special file /dev/console
> Feb  9 21:11:08 s_sys at nlpgbrdns-2.edj.ad.edwardjones.com kernel:
> clurgmgrd[12018]: segfault at 0000000000000050 rip 000000000040399e rsp
> 0000000041442010 error4
> Feb  9 21:11:12 s_sys at nlpgbrdns-2.edj.ad.edwardjones.com
> clurgmgrd[29770]: <crit> Watchdog: Daemon died, rebooting...
>
>  If you are not the intended recipient of this message (including attachments), or if you have received this message in error, immediately notify us and delete it and any attachments.  If you no longer wish to receive e-mail from Edward Jones, please send this request to messages at edwardjones.com.  You must include the e-mail address that you wish not to receive e-mail communications.  For important additional information related to this e-mail, visit www.edwardjones.com/US_email_disclosure
>
> --
> Linux-cluster mailing list
> Linux-cluster at redhat.com
> https://www.redhat.com/mailman/listinfo/linux-cluster
>

Are patches a day?



-- 
Jorge Palma Escobar
Ingeniero de Sistemas
Red Hat Linux Certified Engineer
Certificate N? 804005089418233



From jpalmae at gmail.com  Mon Feb 11 00:00:33 2008
From: jpalmae at gmail.com (Jorge Palma)
Date: Sun, 10 Feb 2008 21:00:33 -0300
Subject: [Linux-cluster] Fenced failed
In-Reply-To: <ff15887d7018409b85c1d36f5105d36c@Mail61.safesecureweb.com>
References: <ff15887d7018409b85c1d36f5105d36c@Mail61.safesecureweb.com>
Message-ID: <5b65f1b10802101600o45b11b23t565f8434efcd34f5@mail.gmail.com>

On Feb 9, 2008 5:26 AM, Marcos Ferreira da Silva
<marcos at digitaltecnologia.info> wrote:
> I have two nodes and in the log appear many messages:
>
> Feb  9 06:22:39 vserver1 ccsd[18304]: process_get: Invalid connection descriptor received.
> Feb  9 06:22:39 vserver1 ccsd[18304]: Error while processing get: Invalid request descriptor
> Feb  9 06:22:39 vserver1 fenced[18334]: fence "vserver2.teste.br" failed
>
> My cluster.conf
>
> <?xml version="1.0" ?>
> <cluster alias="cluster1" config_version="32" name="cluster1">
>         <fence_daemon clean_start="0" post_fail_delay="0" post_join_delay="3"/>
>         <fence_xvmd family="ipv4" key_file="/etc/cluster/fence_xvm.key"/>
>         <clusternodes>
>                 <clusternode name="vserver1.teste.br" nodeid="1" votes="1">
>                         <fence>
>                                 <method name="1">
>                                         <device domain="admin" name="admin"/>
>                                 </method>
>                         </fence>
>                 </clusternode>
>                 <clusternode name="vserver2.teste.br" nodeid="2" votes="1">
>                         <fence>
>                                 <method name="1">
>                                         <device name="manual" nodename="vserver2.teste.br"/>
>                                 </method>
>                         </fence>
>                 </clusternode>
>         </clusternodes>
>         <cman expected_votes="1" two_node="1"/>
>         <fencedevices>
>                 <fencedevice agent="fence_xvm" auth="none" name="admin"/>
>                 <fencedevice agent="fence_xvm" auth="none" name="aluno"/>
>                 <fencedevice agent="fence_manual" name="manual"/>
>         </fencedevices>
>         <rm>
>                 <failoverdomains>
>                         <failoverdomain name="fodAdmin" ordered="1" restricted="1">
>                                 <failoverdomainnode name="vserver1.teste.br" priority="2"/>
>                                 <failoverdomainnode name="vserver2.teste.br" priority="1"/>
>                         </failoverdomain>
>                         <failoverdomain name="fodAluno" ordered="1" restricted="1">
>                                 <failoverdomainnode name="vserver1.teste.br" priority="2"/>
>                                 <failoverdomainnode name="vserver2.teste.br" priority="1"/>
>                         </failoverdomain>
>                 </failoverdomains>
>                 <resources>
>                         <clusterfs device="/dev/VGADMIN/LVAdmin" force_unmount="1" fsid="63078" fstype="gfs" mountpoint="/storage/admin" name="gfsadmin" options=""/>
>                         <clusterfs device="/dev/VGALUNO/LVAluno" force_unmount="1" fsid="63078" fstype="gfs" mountpoint="/storage/aluno" name="gfsaluno" options=""/>
>                 </resources>
>                 <vm autostart="1" domain="fodAdmin" exclusive="0" name="admin" path="/etc/xen" recovery="relocate"/>
>                 <vm autostart="0" domain="fodAluno" exclusive="0" name="aluno" path="/etc/xen" recovery="relocate"/>
>                 <service autostart="1" domain="fodAdmin" name="testeAdmin">
>                         <clusterfs ref="gfsadmin"/>
>                 </service>
>                 <service autostart="1" domain="fodAluno" name="testeAluno">
>                         <clusterfs ref="gfsaluno"/>
>                 </service>
>         </rm>
> </cluster>
>
> My /etc/hosts:
>
> 192.168.200.200 vserver1.teste.br vserver1
> 192.168.200.201 vserver2.teste.br vserver2
>
> ------------------------------
> Marcos Ferreira da Silva
> Digital Tecnologia
> Uberlandia-MG
> (34) 9154-0150 / 3226-2534
>
>
>
> --
> Linux-cluster mailing list
> Linux-cluster at redhat.com
> https://www.redhat.com/mailman/listinfo/linux-cluster
>

Attach fencing agent fence_xvm to the nodes and eliminates fence_manual

Greetings

-- 
Jorge Palma Escobar
Ingeniero de Sistemas
Red Hat Linux Certified Engineer
Certificate N? 804005089418233



From qqlka at nask.pl  Mon Feb 11 08:55:34 2008
From: qqlka at nask.pl (=?iso-8859-2?Q?Agnieszka_Kuka=B3owicz?=)
Date: Mon, 11 Feb 2008 09:55:34 +0100
Subject: [Linux-cluster] Fence_xvmd/fence_xvm problem
Message-ID: <0ba401c86c8b$dd4b9070$0777b5c2@gda07ak>

Hi,
 
I was trying to configure Xen guests as virtual services under Cluster
Suite. My configuration is simple:
 
Node one "d1" runs xen guest as virtual service "vm_service1", and node
one "d2" runs virtual service "vm_service2". 
 
The /etc/cluster/cluster.conf file is below:
 
<?xml version="1.0"?>
<cluster alias="VM_Data_Cluster" config_version="112"
name="VM_Data_Cluster">
        <fence_daemon clean_start="0" post_fail_delay="0"
post_join_delay="300"/>
        <clusternodes>
                <clusternode name="d1" nodeid="1" votes="1">
                        <multicast addr="225.0.0.1" interface="eth0"/>
                        <fence>
                                <method name="1">
                                        <device name="apc_power_switch"
port="1"/>
                                </method>
                        </fence>
                </clusternode>
                <clusternode name="d2" nodeid="2" votes="1">
                        <multicast addr="225.0.0.1" interface="eth0"/>
                        <fence>
                                <method name="1">
                                        <device name="apc_power_switch"
port="2"/>
                                </method>
                        </fence>
                </clusternode>
        </clusternodes>
        <cman expected_votes="1" two_node="1">
                <multicast addr="225.0.0.1"/>
        </cman>
        <fencedevices>
                <fencedevice agent="fence_apc" ipaddr="X.X.X.X"
login="apc" name="apc_power_switch"   passwd="apc"/>
        </fencedevices>
        <rm>
                <failoverdomains>
                        <failoverdomain name="VM_d1_failover"
ordered="0" restricted="0">
                                <failoverdomainnode name="d1"
priority="1"/>
                        </failoverdomain>
                        <failoverdomain name="VM_d2_failover"
ordered="0" restricted="0">
                                <failoverdomainnode name="d2"
priority="1"/>
                        </failoverdomain>
                <resources/>
                <vm autostart="1" domain="VM_d1_failover" exclusive="0"
name="vm_service1"        
                    path="/virts/service1" recovery="relocate"/>
                <vm autostart="1" domain="VM_d2_failover" exclusive="0"
name="vm_service2"
                    path="/virts/service2" recovery="relocate"/>
        </rm>
        <totem consensus="4800" join="60" token="10000"
token_retransmits_before_loss_const="20"/>
        <fence_xvmd family="ipv4"/>
</cluster>
 
On guests "vm_service1"  and "vm_service2" I have configured the second
cluster. 
 
<cluster alias="SV_Data_Cluster" config_version="29"
name="SV_Data_Cluster">
        <fence_daemon clean_start="0" post_fail_delay="0"
post_join_delay="3"/>
        <clusternodes>
                <clusternode name="d11" nodeid="1" votes="1">
                        <fence>
                                <method name="1">
                                        <device domain="d11"
name="virtual_fence"/>
                                </method>
                        </fence>
                </clusternode>
                <clusternode name="d12" nodeid="2" votes="1">
                        <fence>
                                <method name="1">
                                        <device domain="d12"
name="virtual_fence"/>
                                </method>
                        </fence>
                </clusternode>
        </clusternodes>
        <cman expected_votes="1" two_node="1"/>
        <fencedevices>
                <fencedevice agent="fence_xvm" name="virtual_fence"/>
        </fencedevices>
        <rm>
.
       </rm>
</cluster>
 
The problem is that the fence_xvmd/fence_xvm mechanism doesn't work due
to propably misconfiguration of multicast. 
 
Physical nodes "d1" and "d2" and xen guests "vm_service1" and
"vm_service2"  have two ethernet interfaces: private- 10.0.200.x (eth0)
and public (eth1). 
 
On physical nodes, "fence_xvmd" deamon listens defaults on eth1
interface: 
[root at d2 ~]# netstat -g
IPv6/IPv4 Group Memberships
Interface       RefCnt Group
--------------- ------ ---------------------
lo              1      ALL-SYSTEMS.MCAST.NET
eth0            1      225.0.0.1
eth0            1      ALL-SYSTEMS.MCAST.NET
eth1            1      225.0.0.12
eth1            1      ALL-SYSTEMS.MCAST.NET
virbr0          1      ALL-SYSTEMS.MCAST.NET
lo              1      ff02::1
..
 
Next when I make on xen guest "vm_service1"  a test to fence guest
"vm_service2"  I get:
 
[root at d11 cluster]# /sbin/fence_xvm -H d12 -ddddd
Debugging threshold is now 5
-- args @ 0xbf8aea70 --
  args->addr = 225.0.0.12
  args->domain = d12
  args->key_file = /etc/cluster/fence_xvm.key
  args->op = 2
  args->hash = 2
  args->auth = 2
  args->port = 1229
  args->family = 2
  args->timeout = 30
  args->retr_time = 20
  args->flags = 0
  args->debug = 5
-- end args --
Reading in key file /etc/cluster/fence_xvm.key into 0xbf8ada1c (4096 max
size)
Actual key length = 4096 bytesOpening /dev/urandom
Sending to 225.0.0.12 via 127.0.0.1
Opening /dev/urandom
Sending to 225.0.0.12 via X.X.X.X
Opening /dev/urandom
Sending to 225.0.0.12 via 10.0.200.124
Waiting for connection from XVM host daemon.
..
Waiting for connection from XVM host daemon.
Timed out waiting for response
 
On the node "d2" where "vm_service2" is running I get:
 
[root at d2 ~]# /sbin/fence_xvmd -fddd
Debugging threshold is now 3
-- args @ 0xbfc54e3c --
  args->addr = 225.0.0.12
  args->domain = (null)
  args->key_file = /etc/cluster/fence_xvm.key
  args->op = 2
  args->hash = 2
  args->auth = 2
  args->port = 1229
  args->family = 2
  args->timeout = 30
  args->retr_time = 20
  args->flags = 1
  args->debug = 3
-- end args --
Reading in key file /etc/cluster/fence_xvm.key into 0xbfc53e3c (4096 max
size)
Actual key length = 4096 bytesOpened ckpt vm_states
My Node ID = 1
Domain                   UUID                                 Owner
State
------                   ----                                 -----
-----
Domain-0                 00000000-0000-0000-0000-000000000000 00001
00001
vm_service2      2dd8193f-e4d4-f41c-a4af-f5b30d19fe00 00001 00001
Storing vm_service2
Domain                   UUID                                 Owner
State
------                   ----                                 -----
-----
Domain-0                 00000000-0000-0000-0000-000000000000 00001
00001
vm_service2     2dd8193f-e4d4-f41c-a4af-f5b30d19fe00 00001 00001
Storing vm_service2
Request to fence: d12.
Evaluating Domain: d12   Last Owner/State Unknown
Domain                   UUID                                 Owner
State
------                   ----                                 -----
-----
Domain-0                 00000000-0000-0000-0000-000000000000 00001
00001
vm_service2      2dd8193f-e4d4-f41c-a4af-f5b30d19fe00 00001 00001
Storing vm_service2
Request to fence: d12
Evaluating Domain: d12   Last Owner/State Unknown
 
So it looks like the fence_xvmd and fence_xvm cannot communicate earch
other. 
But "fence_xvm" on "vm_service1" sends multicast packets through all
interfaces and node "d2" can receive them. Tcpdump on node "d2" says
that the node "d2" receives the packages:
 
[root at d2 ~]# tcpdump  -i peth0 -n host 225.0.0.12
listening on peth0, link-type EN10MB (Ethernet), capture size 96 bytes
17:50:47.972477 IP 10.0.200.124.filenet-pch > 225.0.0.12.novell-zfs:
UDP, length 176
17:50:49.960841 IP 10.0.200.124.filenet-pch > 225.0.0.12.novell-zfs:
UDP, length 176
17:50:51.977425 IP 10.0.200.124.filenet-pch > 225.0.0.12.novell-zfs:
UDP, length 176
 
[root at d2 ~]# tcpdump  -i peth1 -n host 225.0.0.12
listening on peth1, link-type EN10MB (Ethernet), capture size 96 bytes
17:51:26.168132 IP X.X.X.X.filenet-pch > 225.0.0.12.novell-zfs: UDP,
length 176
17:51:28.184802 IP X.X.X.X.filenet-pch > 225.0.0.12.novell-zfs: UDP,
length 176
17:51:30.196875 IP X.X.X.X.filenet-pch > 225.0.0.12.novell-zfs: UDP,
length 176
 
But I can't see the "node2" sends anything to xen guest "vm_service1".
So "fence_xvm" gets timeout.
What can I do wrong?
 
Cheers
 
Agnieszka Kuka?owicz
NASK, Polska.pl
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://listman.redhat.com/archives/linux-cluster/attachments/20080211/55f6f4dd/attachment.htm>

From asim.husanovic at gmail.com  Mon Feb 11 09:55:45 2008
From: asim.husanovic at gmail.com (Asim Husanovic)
Date: Mon, 11 Feb 2008 10:55:45 +0100
Subject: [Linux-cluster] Monitoring shared disk
In-Reply-To: <3c1234d0802070740x990ed92o61be4ca385755b64@mail.gmail.com>
References: <3c1234d0802070714y21d88c88x1569bcb88b898238@mail.gmail.com>
	<20080207152842.GC30561@wisc.edu>
	<3c1234d0802070740x990ed92o61be4ca385755b64@mail.gmail.com>
Message-ID: <3c1234d0802110155s70f64508wefbafc0fc0af908e@mail.gmail.com>

Hi, again

I have three different configuration (im testing :) RH CS )

Note:
Hardwer is virtual (VMware server 1.0.4 on windows xp host)
Linux is CentOS 4.6

First:
====> LVM partition with GFS <====
in wmx file:
#SHARED Disk 1
scsi1.present = "TRUE"
scsi1.virtualDev = "lsilogic"
scsi1.sharedBus = "virtual"
scsi1:0.present = "TRUE"
scsi1:0.fileName = "D:\VmWare\clusterdisks\SharedDisk1.vmdk"
scsi1:0.mode = "independent-persistent"
scsi1:0.redo = ""
scsi1:0.deviceType = "disk"

#SHARED Disk 2
scsi2.present = "TRUE"
scsi2.virtualDev = "lsilogic"
scsi2.sharedBus = "virtual"
scsi2:0.present = "TRUE"
scsi2:0.fileName = "D:\VmWare\clusterdisks\SharedDisk2.vmdk"
scsi2:0.mode = "independent-persistent"
scsi2:0.redo = ""
scsi2:0.deviceType = "disk"

#SHARED BUS settings
disk.locking = "FALSE"
diskLib.dataCacheMaxReadAheadSize = "0"
diskLib.dataCacheMinReadAheadSize = "0"
diskLib.dataCacheMaxSize = "0"
diskLib.dataCachePageSize = "4096"
diskLib.maxUnsyncedWrites = "0"

[root at ankebut]# cat /etc/hosts
# Do not remove the following line, or various programs
# that require network functionality will fail.

10.81.4.98      ankebut.domain.com       ankebut
172.16.40.10    node1.localdomain       node1
10.81.4.104     yildiz.domain.com        yildiz
172.16.40.11    node2.localdomain       node2
127.0.0.1       localhost.localdomain   localhost

Installing this packages from
http://mirror.centos.org/centos/4/csgfs/CentOS-csgfs.repo:
rgmanager-1.9.72-1
system-config-cluster-1.0.51-2.0
ccs-1.0.11-1
magma-1.0.8-1
magma-plugins-1.0.12-0
cman-1.0.17-0
cman-kernel-2.6.9-53.5
gulm-1.0.10-0
dlm-1.0.7-1
dlm-kernel-2.6.9-52.2
fence-1.32.50-2
iddev-2.0.0-4
perl-Net-Telnet-3.03-3
GFS-6.1.15-1
GFS-kernel-2.6.9-75.9
GFS-kernheaders-2.6.9-75.9
gnbd-1.0.9-1
gnbd-kernel-2.6.9-10.29
gnbd-kernheaders-2.6.9-10.29
lvm2-cluster-2.02.27-2.el4.centos.1

[root at ankebut ~]# vgdisplay -v /dev/VG_SHARE
    Using volume group(s) on command line
    Finding volume group "VG_SHARE"
  --- Volume group ---
  VG Name               VG_SHARE
  System ID
  Format                lvm2
  Metadata Areas        2
  Metadata Sequence No  3
  VG Access             read/write
  VG Status             resizable
  MAX LV                0
  Cur LV                1
  Open LV               0
  Max PV                0
  Cur PV                2
  Act PV                2
  VG Size               15.99 GB
  PE Size               4.00 MB
  Total PE              4094
  Alloc PE / Size       1002 / 3.91 GB
  Free  PE / Size       3092 / 12.08 GB
  VG UUID               C6D0HQ-AeIW-4k8a-Tzl5-ayGx-Tv14-DwkTe7

  --- Logical volume ---
  LV Name                /dev/VG_SHARE/LV_SHARE
  VG Name                VG_SHARE
  LV UUID                7zA1Wf-bn5J-XmD4-azfK-CM3F-y90F-XviVNn
  LV Write Access        read/write
  LV Status              available
  # open                 0
  LV Size                3.91 GB
  Current LE             1002
  Segments               1
  Allocation             inherit
  Read ahead sectors     0
  Block device           253:2

  --- Physical volumes ---
  PV Name               /dev/sda1
  PV UUID               qn9dKj-CIHQ-hyxr-JBdi-rsna-cKkL-SY2OM0
  PV Status             allocatable
  Total PE / Free PE    2047 / 1045

  PV Name               /dev/sdb1
  PV UUID               Kr4yil-DAks-i7jB-HU7M-CLjW-BK2e-9oO91W
  PV Status             allocatable
  Total PE / Free PE    2047 / 2047

[root at ankebut ~]# gfs_mkfs -j 8 -t CentOS_RHCS:sharedd -p lock_dlm
/dev/VG_SHARE/LV_SHARE

[root at ankebut]# cat /etc/cluster/cluster.conf
<?xml version="1.0"?>
<cluster alias="CentOS_RHCS" config_version="1" name="CentOS_RHCS">
  <fence_daemon post_fail_delay="0" post_join_delay="3"/>
  <clusternodes>
    <clusternode name="node1.localdomain" votes="1">
      <com_info>
        <syslog name="node1.localdomain"/>
          <sharedd name="/dev/VG_SHARE/LV_SHARE"/>
      </com_info>
      <fence>
        <method name="1">
          <device name="ManualFence" nodename="node1.localdomain"/>
        </method>
      </fence>
    </clusternode>
    <clusternode name="node2.localdomain" votes="1">
      <com_info>
        <syslog name="node2.localdomain"/>
          <sharedd name="/dev/VG_SHARE/LV_SHARE"/>
      </com_info>
      <fence>
        <method name="1">
          <device name="ManualFence" nodename="node2.localdomain"/>
        </method>
      </fence>
    </clusternode>
  </clusternodes>
  <cman expected_votes="1" two_node="1"/>
  <fencedevices>
    <fencedevice agent="fence_manual" name="ManualFence"/>
  </fencedevices>
  <rm>
    <failoverdomains/>
    <resources/>
  </rm>
</cluster>

[root at ankebut]# mount -t gfs /dev/VG_SHARE/LV_SHARE /share/

[root at ankebut]# cat /etc/fstab
/dev/VG_SHARE/LV_SHARE  /share                  gfs     _netdev 0 0

TEST SHARING
[root at ankebut]# echo 'Date from ankebut is:' `date` >> /share/date
[root at ankebut]# cat /share/date
Date from ankebut is: Fri Feb 1 12:40:17 CET 2008

[root at yildiz ~]# echo 'Date from yildiz is:' `date` >> /share/date
[root at yildiz ~]# cat /share/date
Date from ankebut is: Fri Feb 1 12:40:17 CET 2008
Date from yildiz is: Fri Feb 1 13:40:39 CET 2008


====> LVM partition with GFS <====
in vmw file
#SHARED Disk 1
scsi1.present = "TRUE"
scsi1.virtualDev = "lsilogic"
scsi1.sharedBus = "virtual"
scsi1:0.present = "TRUE"
scsi1:0.fileName = "D:\VmWare\clusterdisks\QuorumDisk.vmdk"
scsi1:0.mode = "independent-persistent"
scsi1:0.redo = ""
scsi1:0.deviceType = "disk"

#SHARED BUS settings
disk.locking = "FALSE"
diskLib.dataCacheMaxReadAheadSize = "0"
diskLib.dataCacheMinReadAheadSize = "0"
diskLib.dataCacheMaxSize = "0"
diskLib.dataCachePageSize = "4096"
diskLib.maxUnsyncedWrites = "0"

[root at ankebut]# cat /etc/hosts
# Do not remove the following line, or various programs
# that require network functionality will fail.

10.81.4.98      ankebut.domain.com      ankebut
172.16.40.10    node1.localdomain       node1
10.81.4.104     yildiz.domain.com        yildiz
172.16.40.11    node2.localdomain       node2
127.0.0.1       localhost.localdomain   localhost

Installing this packages from
http://mirror.centos.org/centos/4/csgfs/CentOS-csgfs.repo:
rgmanager-1.9.72-1
system-config-cluster-1.0.51-2.0
ccs-1.0.11-1
magma-1.0.8-1
magma-plugins-1.0.12-0
cman-1.0.17-0
cman-kernel-2.6.9-53.5
gulm-1.0.10-0
dlm-1.0.7-1
dlm-kernel-2.6.9-52.2
fence-1.32.50-2
iddev-2.0.0-4
perl-Net-Telnet-3.03-3

[root at ankebut]# parted /dev/sda
(parted) p
Disk geometry for /dev/sda: 0.000-8192.000 megabytes
Disk label type: msdos
Minor    Start       End     Type      Filesystem  Flags
1          0.031      7.844  primary
2          7.844   8189.384  primary

[root at ankebut]# mkqdisk -c /dev/sda1 -l QuorumLabel

[root at ankebut]# mkqdisk -L
mkqdisk v0.5.1
/dev/sda1:
        Magic:   eb7a62c2
        Label:   QuorumLabel
        Created: Mon Feb  4 09:58:58 2008
        Host:    ankebut.domain.com

[root at ankebut]# cat /etc/cluster/cluster.conf
<?xml version="1.0"?>
<cluster alias="CentOS_RHCS" config_version="1" name="CentOS_RHCS">
  <fence_daemon post_fail_delay="0" post_join_delay="3"/>
  <clusternodes>
    <clusternode name="node1.localdomain" votes="1">
      <fence>
        <method name="1">
          <device name="ManualFence" nodename="node1.localdomain"/>
        </method>
      </fence>
    </clusternode>
    <clusternode name="node2.localdomain" votes="1">
      <fence>
        <method name="1">
          <device name="ManualFence" nodename="node2.localdomain"/>
        </method>
      </fence>
    </clusternode>
  </clusternodes>
  <quorumd interval="1" tko="5" votes="3" log_level="7"
label="QuorumLabel" status_file="/tmp/quorum-status">
    <heuristic interval="2" program="/bin/ping node1.localdomain -c1
-t1" score="1"/>
    <heuristic interval="2" program="/bin/ping node2.localdomain -c1
-t1" score="1"/>
  </quorumd>
  <cman expected_votes="1" two_node="1"/>
  <fencedevices>
    <fencedevice agent="fence_manual" name="ManualFence"/>
  </fencedevices>
  <rm>
    <failoverdomains/>
    <resources/>
  </rm>
</cluster>

TEST QUORUM DISK
[root at ankebut]# cman_tool nodes
Node  Votes Exp Sts  Name
   0    3    0   M   /dev/sda1
   1    1    1   M   node2.localdomain
   2    1    1   M   node1.localdomain

[root at ankebut]# cman_tool status
Protocol version: 5.0.1
Config version: 1
Cluster name: CentOS_RHCS
Cluster ID: 42649
Cluster Member: Yes
Membership state: Cluster-Member
Nodes: 2
Expected_votes: 1
Total_votes: 5
Quorum: 1
Active subsystems: 2
Node name: node1.localdomain
Node ID: 2

[root at ankebut]# cat /tmp/quorum-status
Time Stamp: Mon Feb  4 10:29:08 2008
Node ID: 2
Score: 1/1 (Minimum required = 1)
Current state: Master
Initializing Set: { }
Visible Set: { 1 2 }
Master Node ID: 2
Quorate Set: { 1 2 }


====> RAW partitions for Oracle <====
in vmx file:
#SHARED Disk 1
scsi1.present = "TRUE"
scsi1.virtualDev = "lsilogic"
scsi1.sharedBus = "virtual"
scsi1:0.present = "TRUE"
scsi1:0.fileName = "D:\VmWare\clusterdisks\SharedDisk.vmdk"
scsi1:0.mode = "independent-persistent"
scsi1:0.redo = ""
scsi1:0.deviceType = "disk"

#SHARED BUS settings
disk.locking = "FALSE"
diskLib.dataCacheMaxReadAheadSize = "0"
diskLib.dataCacheMinReadAheadSize = "0"
diskLib.dataCacheMaxSize = "0"
diskLib.dataCachePageSize = "4096"
diskLib.maxUnsyncedWrites = "0"

[root at ankebut]# cat /etc/hosts
# Do not remove the following line, or various programs
# that require network functionality will fail.

10.81.4.98      ankebut.domain.com       ankebut
172.16.40.10    node1.localdomain       node1
10.81.4.104     yildiz.domain.com        yildiz
172.16.40.11    node2.localdomain       node2
127.0.0.1       localhost.localdomain   localhost

Installing this packages from
http://mirror.centos.org/centos/4/csgfs/CentOS-csgfs.repo:
rgmanager-1.9.72-1
system-config-cluster-1.0.51-2.0
ccs-1.0.11-1
magma-1.0.8-1
magma-plugins-1.0.12-0
cman-1.0.17-0
cman-kernel-2.6.9-53.5
gulm-1.0.10-0
dlm-1.0.7-1
dlm-kernel-2.6.9-52.2
fence-1.32.50-2
iddev-2.0.0-4
perl-Net-Telnet-3.03-3

[root at ankebut ~]# fdisk /dev/sda
Command (m for help): p

Disk /dev/sda: 8589 MB, 8589934592 bytes
255 heads, 63 sectors/track, 1044 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

   Device Boot      Start         End      Blocks   Id  System
/dev/sda1               1         522     4192933+  83  Linux
/dev/sda2             523        1044     4192965   83  Linux

[root at ankebut]# cat /etc/sysconfig/rawdevices
# This file and interface are deprecated.
# Applications needing raw device access should open regular
# block devices with O_DIRECT.
# raw device bindings
# format:  <rawdev> <major> <minor>
#          <rawdev> <blockdev>
# example: /dev/raw/raw1 /dev/sda1
#          /dev/raw/raw2 8 5
/dev/raw/raw1 /dev/sda1
/dev/raw/raw2 /dev/sda2

[root at ankebut]# service rawdevices restart
Assigning devices:
           /dev/raw/raw1  -->   /dev/sda1
/dev/raw/raw1:  bound to major 8, minor 1
           /dev/raw/raw2  -->   /dev/sda2
/dev/raw/raw2:  bound to major 8, minor 2
Done

[root at ankebut]# raw -qa
/dev/raw/raw1:  bound to major 8, minor 1
/dev/raw/raw2:  bound to major 8, minor 2


[root at ankebut /]# mkfs.ext3 -j -b 4096 /dev/sda1
[root at ankebut /]# mkfs.ext3 -j -b 4096 /dev/sda2

[root at ankebut]# cat /etc/cluster/cluster.conf
:(, I dont know how to create cluster.conf for raw configuration in my case

TEST RAW DISK
I dont know how to test RAW configuration


Please, check my configurations and please tell me where i make
mistake, if i make :)
Thanks.

With Regards
Asim

On Feb 7, 2008 4:40 PM, Asim Husanovic <asim.husanovic at gmail.com> wrote:
> Thanks.
> Asim
>
>
> On Feb 7, 2008 4:28 PM, Brian Kroth <bpkroth at wisc.edu> wrote:
> > Here are some quick examples.  There are almost certainly other ways to do
> > it.
> >
> > Asim Husanovic <asim.husanovic at gmail.com>:
> > > Hi
> > >
> > > How to identify shared disk/volumes?
> >
> > scsi_id
> >
> > > How to collect the cluster FS information?
> >
> > gfs_tool
> >
> > > How to display shared disks on node/s? Which node/s?
> >
> > gfs_tool list
> > cman_tool services
> >
> >
> > You can wrap all of these inside snmp scripts/oids or use nagios passive
> > checks if you want to monitor them remotely/automatically.
> >
> > Brian
> >
>



From lhh at redhat.com  Mon Feb 11 14:24:42 2008
From: lhh at redhat.com (Lon Hohberger)
Date: Mon, 11 Feb 2008 09:24:42 -0500
Subject: [Linux-cluster] Fence_xvmd/fence_xvm problem
In-Reply-To: <0ba401c86c8b$dd4b9070$0777b5c2@gda07ak>
References: <0ba401c86c8b$dd4b9070$0777b5c2@gda07ak>
Message-ID: <1202739882.6443.142.camel@ayanami.boston.devel.redhat.com>

On Mon, 2008-02-11 at 09:55 +0100, Agnieszka Kuka?owicz wrote:
> Hi,
> 
>  
> 
> I was trying to configure Xen guests as virtual services under Cluster
> Suite. My configuration is simple:
> 
>  
> 
> Node one "d1" runs xen guest as virtual service "vm_service1", and
> node one "d2" runs virtual service "vm_service2". 

There's currently a limitation - you need to have your VM names match
the filename in /etc/xen, which needs to match 'name = XXXXX'
in /etc/xen/<vm_name>

-- Lon

> 



From lhh at redhat.com  Mon Feb 11 14:25:20 2008
From: lhh at redhat.com (Lon Hohberger)
Date: Mon, 11 Feb 2008 09:25:20 -0500
Subject: [Linux-cluster] Node Offline
In-Reply-To: <4407800e1b774121bb5e2e7209c9f966@Mail61.safesecureweb.com>
References: <4407800e1b774121bb5e2e7209c9f966@Mail61.safesecureweb.com>
Message-ID: <1202739920.6443.144.camel@ayanami.boston.devel.redhat.com>

On Sat, 2008-02-09 at 07:16 -0500, Marcos Ferreira da Silva wrote:
> I start my cluster but the nodes don't see each other.
> 
> [root at vserv3 ~]# clustat
> Member Status: Quorate
> 
>   Member Name                        ID   Status
>   ------ ----                        ---- ------
>   vserv3.uniube.br                      1 Online, Local, rgmanager
>   vserv4.uniube.br                      2 Offline
> 
>   Service Name         Owner (Last)                   State
>   ------- ----         ----- ------                   -----
>   service:gfsweb       (none)                         stopped

Fencing configured?

Any 'totem' messages?

-- Lon




From lhh at redhat.com  Mon Feb 11 14:57:25 2008
From: lhh at redhat.com (Lon Hohberger)
Date: Mon, 11 Feb 2008 09:57:25 -0500
Subject: [Linux-cluster] watchdog: rebootig
In-Reply-To: <B2ED9364017FF54FB9392221F9A498450276E718@nwpsrv08.edj.ad.edwardjones.com>
References: <1939546029@web.de>
	<B2ED9364017FF54FB9392221F9A498450276E718@nwpsrv08.edj.ad.edwardjones.com>
Message-ID: <1202741846.6443.148.camel@ayanami.boston.devel.redhat.com>

On Sat, 2008-02-09 at 21:36 -0600, Stulic,Damjan wrote:
> Having occasional problems with cluster watchdog rebooting servers.
> Any ideas on why this might be helping, or how to troubleshoot this
> problem?

Hi Damjan,

Could you tell me what version of rgmanager you're running?

-- Lon





From bernard.chew at muvee.com  Mon Feb 11 15:01:58 2008
From: bernard.chew at muvee.com (Bernard Chew)
Date: Mon, 11 Feb 2008 23:01:58 +0800
Subject: [Linux-cluster] Fence_xvmd/fence_xvm problem
In-Reply-To: <0ba401c86c8b$dd4b9070$0777b5c2@gda07ak>
References: <0ba401c86c8b$dd4b9070$0777b5c2@gda07ak>
Message-ID: <229C73600EB0E54DA818AB599482BCE9022379DA@shadowfax.sg.muvee.net>

> From: linux-cluster-bounces at redhat.com [mailto:linux-cluster-bounces at redhat.com] On Behalf Of Agnieszka 
> Kukalowicz
> Sent: Monday, February 11, 2008 4:56 PM
> To: linux-cluster at redhat.com
> Subject: [Linux-cluster] Fence_xvmd/fence_xvm problem
> 
> Hi,
> 
> I was trying to configure Xen guests as virtual services under Cluster Suite. My configuration is simple:
>
> Node one "d1" runs xen guest as virtual service "vm_service1", and node one "d2" runs virtual service 
> "vm_service2". 
> 
> The /etc/cluster/cluster.conf file is below:
>
> <?xml version="1.0"?>
> <cluster alias="VM_Data_Cluster" config_version="112" name="VM_Data_Cluster">
>        <fence_daemon clean_start="0" post_fail_delay="0" post_join_delay="300"/>
>        <clusternodes>
>                <clusternode name="d1" nodeid="1" votes="1">
>                        <multicast addr="225.0.0.1" interface="eth0"/>
>                        <fence>
>                                <method name="1">
>                                        <device name="apc_power_switch" port="1"/>
>                                </method>
>                        </fence>
>                </clusternode>
>                <clusternode name="d2" nodeid="2" votes="1">
>                        <multicast addr="225.0.0.1" interface="eth0"/>
>                        <fence>
>                                <method name="1">
>                                        <device name="apc_power_switch" port="2"/>
>                                </method>
>                        </fence>
>                </clusternode>
>        </clusternodes>
>        <cman expected_votes="1" two_node="1">
>                <multicast addr="225.0.0.1"/>
>        </cman>
>        <fencedevices>
>                <fencedevice agent="fence_apc" ipaddr="X.X.X.X" login="apc" name="apc_power_switch"   
> passwd="apc"/>
>        </fencedevices>
>        <rm>
>                <failoverdomains>
>                        <failoverdomain name="VM_d1_failover" ordered="0" restricted="0">
>                                <failoverdomainnode name="d1" priority="1"/>
>                        </failoverdomain>
>                        <failoverdomain name="VM_d2_failover" ordered="0" restricted="0">
>                                <failoverdomainnode name="d2" priority="1"/>
>                        </failoverdomain>
>                <resources/>
>                <vm autostart="1" domain="VM_d1_failover" exclusive="0" name="vm_service1"        
>                    path="/virts/service1" recovery="relocate"/>
>                <vm autostart="1" domain="VM_d2_failover" exclusive="0" name="vm_service2"
>                    path="/virts/service2" recovery="relocate"/>
>        </rm>
>        <totem consensus="4800" join="60" token="10000" token_retransmits_before_loss_const="20"/>
>        <fence_xvmd family="ipv4"/>
> </cluster>
>
> On guests "vm_service1"  and "vm_service2" I have configured the second cluster. 
>
> <cluster alias="SV_Data_Cluster" config_version="29" name="SV_Data_Cluster">
>        <fence_daemon clean_start="0" post_fail_delay="0" post_join_delay="3"/>
>        <clusternodes>
>                <clusternode name="d11" nodeid="1" votes="1">
>                        <fence>
>                                <method name="1">
>                                        <device domain="d11" name="virtual_fence"/>
>                                </method>
>                        </fence>
>                </clusternode>
>                <clusternode name="d12" nodeid="2" votes="1">
>                        <fence>
>                                <method name="1">
>                                        <device domain="d12" name="virtual_fence"/>
>                                </method>
>                        </fence>
>                </clusternode>
>        </clusternodes>
>        <cman expected_votes="1" two_node="1"/>
>        <fencedevices>
>                <fencedevice agent="fence_xvm" name="virtual_fence"/>
>        </fencedevices>
>        <rm>
>       ...
>       </rm>
> </cluster>
>
> The problem is that the fence_xvmd/fence_xvm mechanism doesn't work due to propably misconfiguration of 
> multicast. 
>
> Physical nodes "d1" and "d2" and xen guests "vm_service1" and "vm_service2"  have two ethernet interfaces: 
> private- 10.0.200.x (eth0) and public (eth1). 
>
> On physical nodes, "fence_xvmd" deamon listens defaults on eth1 interface: 
> [root at d2 ~]# netstat -g
> IPv6/IPv4 Group Memberships
> Interface       RefCnt Group
> --------------- ------ ---------------------
> lo              1      ALL-SYSTEMS.MCAST.NET
> eth0            1      225.0.0.1
> eth0            1      ALL-SYSTEMS.MCAST.NET
> eth1            1      225.0.0.12
> eth1            1      ALL-SYSTEMS.MCAST.NET
> virbr0          1      ALL-SYSTEMS.MCAST.NET
> lo              1      ff02::1
> ....
> 
> Next when I make on xen guest "vm_service1"  a test to fence guest "vm_service2"  I get:
>
> [root at d11 cluster]# /sbin/fence_xvm -H d12 -ddddd
> Debugging threshold is now 5
> -- args @ 0xbf8aea70 --
>  args->addr = 225.0.0.12
>  args->domain = d12
>  args->key_file = /etc/cluster/fence_xvm.key
>  args->op = 2
>  args->hash = 2
>  args->auth = 2
>  args->port = 1229
>  args->family = 2
>  args->timeout = 30
>  args->retr_time = 20
>  args->flags = 0
>  args->debug = 5
> -- end args --
> Reading in key file /etc/cluster/fence_xvm.key into 0xbf8ada1c (4096 max size)
> Actual key length = 4096 bytesOpening /dev/urandom
> Sending to 225.0.0.12 via 127.0.0.1
> Opening /dev/urandom
> Sending to 225.0.0.12 via X.X.X.X
> Opening /dev/urandom
> Sending to 225.0.0.12 via 10.0.200.124
> Waiting for connection from XVM host daemon.
> ....
> Waiting for connection from XVM host daemon.
> Timed out waiting for response
>
> On the node "d2" where "vm_service2" is running I get:
>
> [root at d2 ~]# /sbin/fence_xvmd -fddd
> Debugging threshold is now 3
> -- args @ 0xbfc54e3c --
>  args->addr = 225.0.0.12
>  args->domain = (null)
>  args->key_file = /etc/cluster/fence_xvm.key
>  args->op = 2
>  args->hash = 2
>  args->auth = 2
>  args->port = 1229
> args->family = 2
>  args->timeout = 30
>  args->retr_time = 20
>  args->flags = 1
>  args->debug = 3
> -- end args --
> Reading in key file /etc/cluster/fence_xvm.key into 0xbfc53e3c (4096 max size)
> Actual key length = 4096 bytesOpened ckpt vm_states
> My Node ID = 1
> Domain                   UUID                                 Owner State
> ------                   ----                                 ----- -----
> Domain-0                 00000000-0000-0000-0000-000000000000 00001 00001
> vm_service2      2dd8193f-e4d4-f41c-a4af-f5b30d19fe00 00001 00001
> Storing vm_service2
> Domain                   UUID                                 Owner State
> ------                   ----                                 ----- -----
> Domain-0                 00000000-0000-0000-0000-000000000000 00001 00001
> vm_service2     2dd8193f-e4d4-f41c-a4af-f5b30d19fe00 00001 00001
> Storing vm_service2
> Request to fence: d12.
> Evaluating Domain: d12   Last Owner/State Unknown
> Domain                   UUID                                 Owner State
> ------                   ----                                 ----- -----
> Domain-0                 00000000-0000-0000-0000-000000000000 00001 00001
> vm_service2      2dd8193f-e4d4-f41c-a4af-f5b30d19fe00 00001 00001
> Storing vm_service2
> Request to fence: d12
> Evaluating Domain: d12   Last Owner/State Unknown
>
> So it looks like the fence_xvmd and fence_xvm cannot communicate earch other. 
> But "fence_xvm" on "vm_service1" sends multicast packets through all interfaces and node "d2" can receive them. 
> Tcpdump on node "d2" says that the node "d2" receives the packages:
>
> [root at d2 ~]# tcpdump  -i peth0 -n host 225.0.0.12
> listening on peth0, link-type EN10MB (Ethernet), capture size 96 bytes
> 17:50:47.972477 IP 10.0.200.124.filenet-pch > 225.0.0.12.novell-zfs: UDP, length 176
> 17:50:49.960841 IP 10.0.200.124.filenet-pch > 225.0.0.12.novell-zfs: UDP, length 176
> 17:50:51.977425 IP 10.0.200.124.filenet-pch > 225.0.0.12.novell-zfs: UDP, length 176
>
> [root at d2 ~]# tcpdump  -i peth1 -n host 225.0.0.12
> listening on peth1, link-type EN10MB (Ethernet), capture size 96 bytes
> 17:51:26.168132 IP X.X.X.X.filenet-pch > 225.0.0.12.novell-zfs: UDP, length 176
> 17:51:28.184802 IP X.X.X.X.filenet-pch > 225.0.0.12.novell-zfs: UDP, length 176
> 17:51:30.196875 IP X.X.X.X.filenet-pch > 225.0.0.12.novell-zfs: UDP, length 176
>
> But I can't see the "node2" sends anything to xen guest "vm_service1". So "fence_xvm" gets timeout.
> What can I do wrong?
> 
> Cheers
> 
> Agnieszka Kuka?owicz
> NASK, Polska.pl


Hi,

Can you show the results of "netstat -nr" as well?

Regards,
Bernard Chew



From lhh at redhat.com  Mon Feb 11 15:06:37 2008
From: lhh at redhat.com (Lon Hohberger)
Date: Mon, 11 Feb 2008 10:06:37 -0500
Subject: [Linux-cluster] Fence_xvmd/fence_xvm problem
In-Reply-To: <0ba401c86c8b$dd4b9070$0777b5c2@gda07ak>
References: <0ba401c86c8b$dd4b9070$0777b5c2@gda07ak>
Message-ID: <1202742397.6443.158.camel@ayanami.boston.devel.redhat.com>

On Mon, 2008-02-11 at 09:55 +0100, Agnieszka Kuka?owicz wrote:
> 
>                                 <method name="1">
> 
>                                        <device domain="d12"
> name="virtual_fence"/>
> 
>                                 </method>
> 

My error; my previous email was in the case your VMs were restarting
constantly.


For fencing, the virtual machines need to know their virtual machine
names according to domain0.  The 'domain=' should match this, not the
virtual machine's hostname.

vm_service2      2dd8193f-e4d4-f41c-a4af-f5b30d19fe00 00001 00001
^^^^^^^^^^^
Request to fence: d12.
                  ^^^

So, if vm_service2 == d12, you need to change cluster.conf:

    <clusternode name="d12" nodeid="2" votes="1">
      <fence>
        <method name="1">
          <device domain="d12" name="virtual_fence"/>
      <!--                ^^^           -->
      <!--    should be "vm_cluster2"   --> 

        </method>
      </fence>
    </clusternode>

-- Lon



From marcos at digitaltecnologia.info  Mon Feb 11 16:21:24 2008
From: marcos at digitaltecnologia.info (Marcos Ferreira da Silva)
Date: Mon, 11 Feb 2008 14:21:24 -0200
Subject: [Linux-cluster] Node Offline
In-Reply-To: <1202739920.6443.144.camel@ayanami.boston.devel.redhat.com>
References: <4407800e1b774121bb5e2e7209c9f966@Mail61.safesecureweb.com>
	<1202739920.6443.144.camel@ayanami.boston.devel.redhat.com>
Message-ID: <1202746884.3078.12.camel@matriz.digitaltecnologia.info>

I change the service to xvm.

I wnat that vm admin start at vserver1 and intranetteste at vserver2.

[root at vserver1 ~]# clustat
Member Status: Quorate

  Member Name                        ID   Status
  ------ ----                        ---- ------
  vserver1.uniube.br                    1 Online, Local, rgmanager
  vserver2.uniube.br                    2 Offline

  Service Name         Owner (Last)                   State
  ------- ----         ----- ------                   -----
  vm:admin             (none)                         disabled
  vm:intranetteste     (none)                         disabled


[root at vserver2 ~]# clustat
Member Status: Quorate

  Member Name                        ID   Status
  ------ ----                        ---- ------
  vserver1.uniube.br                    1 Offline
  vserver2.uniube.br                    2 Online, Local, rgmanager

  Service Name         Owner (Last)                   State
  ------- ----         ----- ------                   -----
  vm:admin             (none)                         disabled
  vm:intranetteste     (none)                         disabled


My cluster.conf

<?xml version="1.0" ?>
<cluster config_version="39" name="cluster1">
  <fence_daemon clean_start="0" post_fail_delay="0"
post_join_delay="30"/>
  <fence_xvmd/>
  <totem token="21000"/>
  <clusternodes>
    <clusternode name="vserver1.uniube.br" nodeid="1" votes="1">
      <fence>
        <method name="1">
          <device domain="admin" name="xvm"/>
        </method>
      </fence>
    </clusternode>
    <clusternode name="vserver2.uniube.br" nodeid="2" votes="1">
      <fence>
        <method name="1">
          <device domain="intranetteste" name="xvm"/>
        </method>
      </fence>
    </clusternode>
  </clusternodes>
  <cman expected_votes="1" two_node="1"/>
  <fencedevices>
    <fencedevice agent="fence_xvm" name="xvm"/>
  </fencedevices>
  <rm>
    <failoverdomains/>
    <resources/>
    <vm autostart="0" name="admin" path="/etc/xen"/>
    <vm autostart="0" name="intranetteste" path="/etc/xen"/>
  </rm>
</cluster>

The vserver1 start ok.

But when I start the vserver2 node then I have a problem.

In my log messages:

Feb 11 14:18:43 vserver2 openais[6643]: [CLM  ] CLM CONFIGURATION CHANGE
Feb 11 14:18:43 vserver2 openais[6643]: [CLM  ] New Configuration:
Feb 11 14:18:43 vserver2 openais[6643]: [CLM  ]         r(0)
ip(192.168.200.201)
Feb 11 14:18:43 vserver2 openais[6643]: [CLM  ] Members Left:
Feb 11 14:18:43 vserver2 openais[6643]: [CLM  ] Members Joined:
Feb 11 14:18:43 vserver2 openais[6643]: [CLM  ] CLM CONFIGURATION CHANGE
Feb 11 14:18:43 vserver2 openais[6643]: [CLM  ] New Configuration:
Feb 11 14:18:43 vserver2 openais[6643]: [CLM  ]         r(0)
ip(192.168.200.200)
Feb 11 14:18:43 vserver2 openais[6643]: [CLM  ]         r(0)
ip(192.168.200.201)
Feb 11 14:18:43 vserver2 openais[6643]: [CLM  ] Members Left:
Feb 11 14:18:44 vserver2 openais[6643]: [CLM  ] Members Joined:
Feb 11 14:18:44 vserver2 openais[6643]: [CLM  ]         r(0)
ip(192.168.200.200)
Feb 11 14:18:44 vserver2 openais[6643]: [SYNC ] This node is within the
primary component and will provide service.
Feb 11 14:18:44 vserver2 openais[6643]: [TOTEM] entering OPERATIONAL
state.
Feb 11 14:18:44 vserver2 openais[6643]: [TOTEM] Retransmit List: 1

after :

Feb 11 14:19:24 vserver2 openais[6643]: [CLM  ] CLM CONFIGURATION CHANGE
Feb 11 14:19:24 vserver2 openais[6643]: [CLM  ] New Configuration:
Feb 11 14:19:24 vserver2 openais[6643]: [CLM  ]         r(0)
ip(192.168.200.201)
Feb 11 14:19:24 vserver2 openais[6643]: [CLM  ] Members Left:
Feb 11 14:19:24 vserver2 openais[6643]: [CLM  ]         r(0)
ip(192.168.200.200)
Feb 11 14:19:24 vserver2 openais[6643]: [CLM  ] Members Joined:
Feb 11 14:19:24 vserver2 openais[6643]: [CLM  ] CLM CONFIGURATION CHANGE
Feb 11 14:19:24 vserver2 openais[6643]: [CLM  ] New Configuration:
Feb 11 14:19:24 vserver2 openais[6643]: [CLM  ]         r(0)
ip(192.168.200.201)
Feb 11 14:19:24 vserver2 openais[6643]: [CLM  ] Members Left:
Feb 11 14:19:24 vserver2 openais[6643]: [CLM  ] Members Joined:
Feb 11 14:19:24 vserver2 openais[6643]: [SYNC ] This node is within the
primary component and will provide service.
Feb 11 14:19:24 vserver2 openais[6643]: [TOTEM] entering OPERATIONAL
state.

and the cluster of node2 crash:

Feb 11 14:20:48 vserver2 openais[6643]: [CLM  ] CLM CONFIGURATION CHANGE
Feb 11 14:20:48 vserver2 openais[6643]: [CLM  ] New Configuration:
Feb 11 14:20:48 vserver2 openais[6643]: [CLM  ]         r(0)
ip(192.168.200.201)
Feb 11 14:20:48 vserver2 openais[6643]: [CLM  ] Members Left:
Feb 11 14:20:48 vserver2 openais[6643]: [CLM  ] Members Joined:
Feb 11 14:20:48 vserver2 openais[6643]: [CLM  ] CLM CONFIGURATION CHANGE
Feb 11 14:20:48 vserver2 openais[6643]: [CLM  ] New Configuration:
Feb 11 14:20:48 vserver2 openais[6643]: [CLM  ]         r(0)
ip(192.168.200.200)
Feb 11 14:20:48 vserver2 openais[6643]: [CLM  ]         r(0)
ip(192.168.200.201)
Feb 11 14:20:49 vserver2 openais[6643]: [CLM  ] Members Left:
Feb 11 14:20:49 vserver2 openais[6643]: [CLM  ] Members Joined:
Feb 11 14:20:49 vserver2 openais[6643]: [CLM  ]         r(0)
ip(192.168.200.200)
Feb 11 14:20:49 vserver2 openais[6643]: [SYNC ] This node is within the
primary component and will provide service.
Feb 11 14:20:49 vserver2 openais[6643]: [TOTEM] entering OPERATIONAL
state.
Feb 11 14:20:49 vserver2 openais[6643]: [MAIN ] Killing node
vserver1.uniube.br because it has rejoined the cluster without cman_tool
join
Feb 11 14:20:49 vserver2 openais[6643]: [CMAN ] cman killed by node 1
because we rejoined the cluster without a full restart
Feb 11 14:20:49 vserver2 gfs_controld[6679]: cluster is down, exiting
Feb 11 14:20:49 vserver2 dlm_controld[6673]: groupd is down, exiting
Feb 11 14:20:49 vserver2 fenced[6667]: cluster is down, exiting
Feb 11 14:20:49 vserver2 kernel: dlm: closing connection to node 2
Feb 11 14:21:15 vserver2 ccsd[6634]: Unable to connect to cluster
infrastructure after 30 seconds.
Feb 11 14:21:45 vserver2 ccsd[6634]: Unable to connect to cluster
infrastructure after 60 seconds.
Feb 11 14:22:15 vserver2 ccsd[6634]: Unable to connect to cluster
infrastructure after 90 seconds.


-  
_____________________________
Marcos Ferreira da Silva
DiGital Tecnologia
Uberl?ndia - MG
(34) 9154-0150 / 3226-2534


Em Seg, 2008-02-11 ?s 09:25 -0500, Lon Hohberger escreveu:
> On Sat, 2008-02-09 at 07:16 -0500, Marcos Ferreira da Silva wrote:
> > I start my cluster but the nodes don't see each other.
> > 
> > [root at vserv3 ~]# clustat
> > Member Status: Quorate
> > 
> >   Member Name                        ID   Status
> >   ------ ----                        ---- ------
> >   vserv3.teste.br                      1 Online, Local, rgmanager
> >   vserv4.teste.br                      2 Offline
> > 
> >   Service Name         Owner (Last)                   State
> >   ------- ----         ----- ------                   -----
> >   service:gfsweb       (none)                         stopped
> 
> Fencing configured?
> 
> Any 'totem' messages?
> 
> -- Lon
> 
> 





From ccaulfie at redhat.com  Mon Feb 11 16:47:50 2008
From: ccaulfie at redhat.com (Christine Caulfield)
Date: Mon, 11 Feb 2008 16:47:50 +0000
Subject: [Linux-cluster] Two-node cluster unpatched B doesn't see patched A
In-Reply-To: <47AB8156.6010205@hp.com>
References: <47AB8156.6010205@hp.com>
Message-ID: <47B07C36.5070202@redhat.com>

Sutton, Harry (MSE) wrote:
> The most recent set of patches for RHCS, comprising:
> 
> RHBA-2008:0093    dlm-kernel bug fix update
> RHBA-2008:0092    cman-kernel bug fix update
> RHBA-2008:0060    cman bug fix update
> RHBA-2008:0095    gnbd-kernel bug fix update
> RHBA-2008:0096    GFS-kernel bug fix update
> RHSA-2008:0055    Important: kernel security and bug fix update
> 
> has resulted in a problem in my two-node (production) cluster. Let me
> explain ;-)
> 
> I have a three-node test cluster where I install all patches before
> rolling them into my (two-node) production cluster; I know, I know,
> they're not the same, and that's the only difference I can see in what
> has happened here (a first in two years). In the three-node cluster
> (which, just to complicate things, only had two active nodes at the
> time), I rolled these patches through the two nodes without taking the
> whole cluster down. That is:
> 
> 1. Stop all cluster services on Node A. Disable auto-start using
> chkconfig off <cluster-service-name>. Services stop successfully, Node A
> leaves the cluster, Node B continues running all shared cluster services
> (GFS, Fibre-channel-connected shared storage, HP MSA1000).
> 2. Patch Node A, reboot to new kernel, re-install HP-supplied QLogic
> driver, edit /etc/modprobe.conf for failover settings, rebuild initrd
> file for QLogic drivers, reboot, re-enable auto-start of cluster
> services, reboot once more and the cluster re-forms.
> 3. Repeat Steps 1 and 2 for Node B
> 4. Cluster is restored to normal operation, both nodes fully patched.
> 
> On my production cluster, which uses a Quorum Disk in place of the third
> node, I completed steps 1 and 2 on Node A, but the cluster did NOT
> reform. cman sends out its advertisement, and I can see that Node B
> receives it (by looking at the tcpdump traces), but Node B never responds.
> 
> So: before I take down Node B (which is currently the only one running
> my production services), can someone either (a) explain why the cluster
> is not re-forming, or (b) assure me that by restoring both systems to
> the same patch level, the cluster WILL reform properly? (Which begs the
> question: why did my test cluster survive the patch process and my
> production cluster didn't? Same versions of everything......)
> 
> Thanks in advance, and best regards,

I'm pretty certain that even simply rebooting node B will let the
cluster re-form. I've heard of this problem before but never got to the
bottom of it because it seems to be quite rare. It is almost certainly
some state in node B that is preventing it replying to node A's join
requests - I suspect it's a bug to do with protocol ACK numbers but
can't be sure.

Before you do it, would you be so kind as to send me the tcpdumps of the
(non-)conversation, including the HELLO messages from node B. It might
help in tracking it down.

Thanks,

-- 

Chrissie



From marcos at digitaltecnologia.info  Mon Feb 11 17:02:01 2008
From: marcos at digitaltecnologia.info (Marcos Ferreira da Silva)
Date: Mon, 11 Feb 2008 15:02:01 -0200
Subject: [Linux-cluster] ccsd error
Message-ID: <1202749321.3078.15.camel@matriz.digitaltecnologia.info>

It's appearing many of these errors in my log.

Feb 11 15:01:21 vserver1 ccsd[2424]: process_get: Invalid connection
descriptor received.
Feb 11 15:01:21 vserver1 ccsd[2424]: Error while processing get: Invalid
request descriptor
Feb 11 15:01:21 vserver1 fenced[2453]: fence "vserver2.teste.br" failed
Feb 11 15:01:26 vserver1 fenced[2453]: fencing node "vserver2.teste.br"

My cluster.conf:

<?xml version="1.0" ?>
<cluster config_version="40" name="cluster1">
  <fence_daemon clean_start="0" post_fail_delay="0"
post_join_delay="30"/>
  <fence_xvmd family="ipv4" key_file="/etc/cluster/fence_xvm.key"/>
  <totem token="21000"/>
  <clusternodes>
    <clusternode name="vserver1.teste.br" nodeid="1" votes="1">
      <fence>
        <method name="1">
          <device domain="admin" name="xvm1"/>
        </method>
      </fence>
    </clusternode>
    <clusternode name="vserver2.teste.br" nodeid="2" votes="1">
      <fence>
        <method name="1">
          <device domain="intranetteste" name="xvm2"/>
        </method>
      </fence>
    </clusternode>
  </clusternodes>
  <cman expected_votes="1" two_node="1"/>
  <fencedevices>
    <fencedevice agent="fence_xvm" name="xvm1"/>
    <fencedevice agent="fence_xvm" name="xvm2"/>
  </fencedevices>
  <rm>
    <failoverdomains/>
    <resources/>
    <vm autostart="0" name="admin" path="/etc/xen"/>
    <vm autostart="0" name="intranetteste" path="/etc/xen"/>
  </rm>
</cluster>

-  
_____________________________
Marcos Ferreira da Silva
DiGital Tecnologia
Uberl?ndia - MG
(34) 9154-0150 / 3226-2534






From damjan.stulic at edwardjones.com  Mon Feb 11 17:18:07 2008
From: damjan.stulic at edwardjones.com (Stulic,Damjan)
Date: Mon, 11 Feb 2008 11:18:07 -0600
Subject: [Linux-cluster] watchdog: rebootig
In-Reply-To: <1202741846.6443.148.camel@ayanami.boston.devel.redhat.com>
References: <1939546029@web.de><B2ED9364017FF54FB9392221F9A498450276E718@nwpsrv08.edj.ad.edwardjones.com>
	<1202741846.6443.148.camel@ayanami.boston.devel.redhat.com>
Message-ID: <B2ED9364017FF54FB9392221F9A498450276E8C5@nwpsrv08.edj.ad.edwardjones.com>

If you are not the intended recipient of this message (including attachments), or if you have received this message in error, immediately notify us and delete it and any attachments.  If you no longer wish to receive e-mail from Edward Jones, please send this request to messages at edwardjones.com.  You must include the e-mail address that you wish not to receive e-mail communications.  For important additional information related to this e-mail, visit www.edwardjones.com/US_email_disclosure
 
-----Original Message-----
 

From: linux-cluster-bounces at redhat.com
[mailto:linux-cluster-bounces at redhat.com] On Behalf Of Lon Hohberger
Sent: Monday, February 11, 2008 08:57
To: linux clustering
Subject: Re: [Linux-cluster] watchdog: rebootig

> On Sat, 2008-02-09 at 21:36 -0600, Stulic,Damjan wrote:
>> Having occasional problems with cluster watchdog rebooting servers.
>> Any ideas on why this might be helping, or how to troubleshoot this
>> problem?

> Hi Damjan,
>
> Could you tell me what version of rgmanager you're running?
> 
> -- Lon


rgmanager-1.9.54-1.x86_64
Name        : rgmanager                    Relocations: (not
relocatable)
Version     : 1.9.54                            Vendor: Red Hat, Inc.
Release     : 1                             Build Date: Fri 06 Oct 2006
11:43:10 AM CDT 

Red Hat Enterprise Linux ES release 4

We went through the update process about a month ago, all the newest
packages were downloaded and installed.
We had this problem before, cluster would occasionally panic during the
clusvcadm -R. But this time it was different, there was no clusvcadm
commands being issued (or any other cluster commands).

Thank you,
Damjan



From doseyg at r-networks.net  Mon Feb 11 21:08:26 2008
From: doseyg at r-networks.net (Glen Dosey)
Date: Mon, 11 Feb 2008 16:08:26 -0500 (EST)
Subject: [Linux-cluster] GFS1 NFS problems under 2.6.25-rc1  (was: GFS2 
	loses data under kernel 2.6.24...)
In-Reply-To: <1202463059.22038.421.camel@quoit>
References: <1202446917.5942.19.camel@eclipse.office.r-networks.net>
	<1202463059.22038.421.camel@quoit>
Message-ID: <38964.155.82.73.253.1202764106.squirrel@www.r-networks.net>

Yes, it fixes that problem, thank you.

So I grabbed the latest code from kernel.org, 2.6.25-rc1 and tested it
successfully. The problem now is that I cannot seem to get the GFS1 code
working properly. I grabbed the latest HEAD from CVS and modified sys.c to
work with the new kobject calls. Or at least I think I have, perhaps that
is what is wrong, I have attached the diff.

The gfs module builds successfully against the 2.6.25-rc1 kernel and
loads. Locally on the server everything appears to work, but on the GFs
filesystem NFS exported from the server, clients can create files but they
sometimes fail to store any data. For example:

[root at nccws00 gfs]# echo test > newfile
[root at nccws00 gfs]# cat newfile
test
[root at nccws00 gfs]# dd if=/dev/zero of=test1.dd bs=8k count=2
dd: closing output file `test1.dd': Invalid argument
[root at nccws00 gfs]# cp /tmp/patch-2.6.24.2.bz2 .
cp: closing `./patch-2.6.24.2.bz2': Invalid argument
[root at nccws00 gfs]# ll
total 3152084
-rw-r--r-- 1 root root          5 Feb 11 16:00 newfile
-rw-r--r-- 1 root root          0 Feb 11 16:01 patch-2.6.24.2.bz2
-rw-rw-rw- 1 root root          0 Feb 11 16:01 test1.dd
-rw-r--r-- 1 root root 1073741824 Feb  7 17:16 test2.dd
-rw-r--r-- 1 root root 1073741824 Feb  7 17:19 test3.dd
-rw-r--r-- 1 root root 1073741824 Feb  7 19:38 test4.dd
[root at nccws00 gfs]#



Am I missing some other significant changes which need patches as well ? I
only need GFS1 to work over NFS currently.


Thanks,
Glen Dosey


> Hi,
>
> Does this patch fix it for you?
>
> http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commitdiff;h=9656b2c14c6ee0806c90a6be41dec71117fc8f50
>
> or you can just upgrade to the latest upstream Linus kernel. It was a
> result of the write_end function not working in exactly the same way as
> the older commit_write used to,
>
> Steve.
>
> On Fri, 2008-02-08 at 00:01 -0500, Glen Dosey wrote:
>> I experienced this today at work on a RHEL5 system and have verified it
>> today at home on Fedora 8. Perhaps I am doing something foolish ....
>>
>> I have a fully patched RHEL5 x86_64 system which works fine with the Red
>> Hat supplied cluster stuff, except the NFS server performance is abysmal
>> (~640Mb/s NFS). After pulling my hair trying to fix NFS I decided to
>> just grab the latest kernel which fixed the problem (~980Mb/s NFS). But
>> it introduced another much more serious problem, which I've duplicated
>> on my FC8 x86_64 system at home.
>>
>> I already have all the cman/clvmd/openais/gfs[2]-utils packages
>> installed through the package manager. I downloaded kernel 2.6.24 from
>> kernel.org and did a straight `make -j4 rpm ` and installed the
>> resulting rpm in both instances. Both systems worked fine with
>> RHEL/Fedora kernels, but here's what happens under 2.6.24
>>
>> [root at eclipse test]# dd if=/dev/zero of=test3.dd bs=512M count=1
>> 1+0 records in
>> 1+0 records out
>> 536870912 bytes (537 MB) copied, 7.95285 s, 67.5 MB/s
>> [root at eclipse test]# ll
>> total 2101312
>> -rw-r--r-- 1 root root          0 2008-02-07 23:25 test2.dd
>> -rw-r--r-- 1 root root  536870912 2008-02-07 23:42 test3.dd
>> -rw-r--r-- 1 root root 1073741824 2008-02-07 22:54 test.dd
>> [root at eclipse test]# cd ..
>> [root at eclipse mnt]# umount /mnt/test/
>> [root at eclipse mnt]# mount /mnt/test/
>> [root at eclipse mnt]# mount | grep test
>> /dev/mapper/disk00-test on /mnt/test type gfs2
>> (rw,hostdata=jid=0:id=524289:first=1)
>> [root at eclipse mnt]# cd /mnt/test/
>> [root at eclipse test]# ll
>> total 2101312
>> -rw-r--r-- 1 root root          0 2008-02-07 23:25 test2.dd
>> -rw-r--r-- 1 root root          0 2008-02-07 23:42 test3.dd
>> -rw-r--r-- 1 root root 1073741824 2008-02-07 22:54 test.dd
>>
>> Files that have data just go zero size after an umount and remount. I've
>> tried a variety of file sizes and tried it with file containing data as
>> well (not all zeros). This worked under the RHEL kernels, so is there
>> something I'm doing wrong ?
>>
>> Both systems are running cman and are a quorate 2 node cluster (where
>> the second node doesn't exist). At work it's a 1TB shared filesystem but
>> here at home it's just a local disk, so there's nothing else with any
>> access to it.
>>
>> If someone could maybe point out what I'm doing wrong I'd appreciate it,
>> or just let me know this won't work for whatever reason. I haven't even
>> touched on getting the GFS1 modules to build into this.
>>
>> Thanks,
>> Glen
>>
>>
>> --
>> Linux-cluster mailing list
>> Linux-cluster at redhat.com
>> https://www.redhat.com/mailman/listinfo/linux-cluster
>
> --
> Linux-cluster mailing list
> Linux-cluster at redhat.com
> https://www.redhat.com/mailman/listinfo/linux-cluster
>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: GFS_kobject.patch
Type: application/octet-stream
Size: 1396 bytes
Desc: not available
URL: <http://listman.redhat.com/archives/linux-cluster/attachments/20080211/e482b2ee/attachment.obj>

From lhh at redhat.com  Mon Feb 11 21:29:24 2008
From: lhh at redhat.com (Lon Hohberger)
Date: Mon, 11 Feb 2008 16:29:24 -0500
Subject: [Linux-cluster] watchdog: rebootig
In-Reply-To: <B2ED9364017FF54FB9392221F9A498450276E8C5@nwpsrv08.edj.ad.edwardjones.com>
References: <1939546029@web.de>
	<B2ED9364017FF54FB9392221F9A498450276E718@nwpsrv08.edj.ad.edwardjones.com>
	<1202741846.6443.148.camel@ayanami.boston.devel.redhat.com>
	<B2ED9364017FF54FB9392221F9A498450276E8C5@nwpsrv08.edj.ad.edwardjones.com>
Message-ID: <1202765364.20118.6.camel@ayanami.boston.devel.redhat.com>

On Mon, 2008-02-11 at 11:18 -0600, Stulic,Damjan wrote:

> rgmanager-1.9.54-1.x86_64
> Name        : rgmanager                    Relocations: (not
> relocatable)
> Version     : 1.9.54                            Vendor: Red Hat, Inc.
> Release     : 1                             Build Date: Fri 06 Oct 2006
> 11:43:10 AM CDT 

Ah, it's probably the rg_thread.c assertion failure; here's the patch:

https://bugzilla.redhat.com/attachment.cgi?id=139908&action=edit

Apparently we never opened the bug (for public viewing), but it was
fixed in the 4.5 updates (note... recent ccs package would be needed
too).

-- Lon



From qqlka at nask.pl  Tue Feb 12 11:30:26 2008
From: qqlka at nask.pl (=?iso-8859-2?Q?Agnieszka_Kuka=B3owicz?=)
Date: Tue, 12 Feb 2008 12:30:26 +0100
Subject: [Linux-cluster] Fence_xvmd/fence_xvm problem
In-Reply-To: <1202742397.6443.158.camel@ayanami.boston.devel.redhat.com>
Message-ID: <0c9501c86d6a$aab79ca0$0777b5c2@gda07ak>

> For fencing, the virtual machines need to know their virtual machine
> names according to domain0.  The 'domain=' should match this, not the
> virtual machine's hostname.
> 
> vm_service2      2dd8193f-e4d4-f41c-a4af-f5b30d19fe00 00001 00001
> ^^^^^^^^^^^
> Request to fence: d12.
>                   ^^^
> 
> So, if vm_service2 == d12, you need to change cluster.conf:

I've changed cluster.conf and now everything works. It was my mistake.
Thanks a lot.

Cheers
Agnieszka Kukalowicz
 
 




From asim.husanovic at gmail.com  Tue Feb 12 11:49:12 2008
From: asim.husanovic at gmail.com (Asim Husanovic)
Date: Tue, 12 Feb 2008 12:49:12 +0100
Subject: [Linux-cluster] Monitoring shared disk
In-Reply-To: <3c1234d0802110155s70f64508wefbafc0fc0af908e@mail.gmail.com>
References: <3c1234d0802070714y21d88c88x1569bcb88b898238@mail.gmail.com>
	<20080207152842.GC30561@wisc.edu>
	<3c1234d0802070740x990ed92o61be4ca385755b64@mail.gmail.com>
	<3c1234d0802110155s70f64508wefbafc0fc0af908e@mail.gmail.com>
Message-ID: <3c1234d0802120349j25874194td27ed0782b2d8dbf@mail.gmail.com>

Please, check
Please help

Asim

On Feb 11, 2008 10:55 AM, Asim Husanovic <asim.husanovic at gmail.com> wrote:
> Hi, again
>
> I have three different configuration (im testing :) RH CS )
>
> Note:
> Hardwer is virtual (VMware server 1.0.4 on windows xp host)
> Linux is CentOS 4.6
>
> First:
> ====> LVM partition with GFS <====
> in wmx file:
> #SHARED Disk 1
> scsi1.present = "TRUE"
> scsi1.virtualDev = "lsilogic"
> scsi1.sharedBus = "virtual"
> scsi1:0.present = "TRUE"
> scsi1:0.fileName = "D:\VmWare\clusterdisks\SharedDisk1.vmdk"
> scsi1:0.mode = "independent-persistent"
> scsi1:0.redo = ""
> scsi1:0.deviceType = "disk"
>
> #SHARED Disk 2
> scsi2.present = "TRUE"
> scsi2.virtualDev = "lsilogic"
> scsi2.sharedBus = "virtual"
> scsi2:0.present = "TRUE"
> scsi2:0.fileName = "D:\VmWare\clusterdisks\SharedDisk2.vmdk"
> scsi2:0.mode = "independent-persistent"
> scsi2:0.redo = ""
> scsi2:0.deviceType = "disk"
>
> #SHARED BUS settings
> disk.locking = "FALSE"
> diskLib.dataCacheMaxReadAheadSize = "0"
> diskLib.dataCacheMinReadAheadSize = "0"
> diskLib.dataCacheMaxSize = "0"
> diskLib.dataCachePageSize = "4096"
> diskLib.maxUnsyncedWrites = "0"
>
> [root at ankebut]# cat /etc/hosts
> # Do not remove the following line, or various programs
> # that require network functionality will fail.
>
> 10.81.4.98      ankebut.domain.com       ankebut
> 172.16.40.10    node1.localdomain       node1
> 10.81.4.104     yildiz.domain.com        yildiz
> 172.16.40.11    node2.localdomain       node2
> 127.0.0.1       localhost.localdomain   localhost
>
> Installing this packages from
> http://mirror.centos.org/centos/4/csgfs/CentOS-csgfs.repo:
> rgmanager-1.9.72-1
> system-config-cluster-1.0.51-2.0
> ccs-1.0.11-1
> magma-1.0.8-1
> magma-plugins-1.0.12-0
> cman-1.0.17-0
> cman-kernel-2.6.9-53.5
> gulm-1.0.10-0
> dlm-1.0.7-1
> dlm-kernel-2.6.9-52.2
> fence-1.32.50-2
> iddev-2.0.0-4
> perl-Net-Telnet-3.03-3
> GFS-6.1.15-1
> GFS-kernel-2.6.9-75.9
> GFS-kernheaders-2.6.9-75.9
> gnbd-1.0.9-1
> gnbd-kernel-2.6.9-10.29
> gnbd-kernheaders-2.6.9-10.29
> lvm2-cluster-2.02.27-2.el4.centos.1
>
> [root at ankebut ~]# vgdisplay -v /dev/VG_SHARE
>     Using volume group(s) on command line
>     Finding volume group "VG_SHARE"
>   --- Volume group ---
>   VG Name               VG_SHARE
>   System ID
>   Format                lvm2
>   Metadata Areas        2
>   Metadata Sequence No  3
>   VG Access             read/write
>   VG Status             resizable
>   MAX LV                0
>   Cur LV                1
>   Open LV               0
>   Max PV                0
>   Cur PV                2
>   Act PV                2
>   VG Size               15.99 GB
>   PE Size               4.00 MB
>   Total PE              4094
>   Alloc PE / Size       1002 / 3.91 GB
>   Free  PE / Size       3092 / 12.08 GB
>   VG UUID               C6D0HQ-AeIW-4k8a-Tzl5-ayGx-Tv14-DwkTe7
>
>   --- Logical volume ---
>   LV Name                /dev/VG_SHARE/LV_SHARE
>   VG Name                VG_SHARE
>   LV UUID                7zA1Wf-bn5J-XmD4-azfK-CM3F-y90F-XviVNn
>   LV Write Access        read/write
>   LV Status              available
>   # open                 0
>   LV Size                3.91 GB
>   Current LE             1002
>   Segments               1
>   Allocation             inherit
>   Read ahead sectors     0
>   Block device           253:2
>
>   --- Physical volumes ---
>   PV Name               /dev/sda1
>   PV UUID               qn9dKj-CIHQ-hyxr-JBdi-rsna-cKkL-SY2OM0
>   PV Status             allocatable
>   Total PE / Free PE    2047 / 1045
>
>   PV Name               /dev/sdb1
>   PV UUID               Kr4yil-DAks-i7jB-HU7M-CLjW-BK2e-9oO91W
>   PV Status             allocatable
>   Total PE / Free PE    2047 / 2047
>
> [root at ankebut ~]# gfs_mkfs -j 8 -t CentOS_RHCS:sharedd -p lock_dlm
> /dev/VG_SHARE/LV_SHARE
>
> [root at ankebut]# cat /etc/cluster/cluster.conf
> <?xml version="1.0"?>
> <cluster alias="CentOS_RHCS" config_version="1" name="CentOS_RHCS">
>   <fence_daemon post_fail_delay="0" post_join_delay="3"/>
>   <clusternodes>
>     <clusternode name="node1.localdomain" votes="1">
>       <com_info>
>         <syslog name="node1.localdomain"/>
>           <sharedd name="/dev/VG_SHARE/LV_SHARE"/>
>       </com_info>
>       <fence>
>         <method name="1">
>           <device name="ManualFence" nodename="node1.localdomain"/>
>         </method>
>       </fence>
>     </clusternode>
>     <clusternode name="node2.localdomain" votes="1">
>       <com_info>
>         <syslog name="node2.localdomain"/>
>           <sharedd name="/dev/VG_SHARE/LV_SHARE"/>
>       </com_info>
>       <fence>
>         <method name="1">
>           <device name="ManualFence" nodename="node2.localdomain"/>
>         </method>
>       </fence>
>     </clusternode>
>   </clusternodes>
>   <cman expected_votes="1" two_node="1"/>
>   <fencedevices>
>     <fencedevice agent="fence_manual" name="ManualFence"/>
>   </fencedevices>
>   <rm>
>     <failoverdomains/>
>     <resources/>
>   </rm>
> </cluster>
>
> [root at ankebut]# mount -t gfs /dev/VG_SHARE/LV_SHARE /share/
>
> [root at ankebut]# cat /etc/fstab
> /dev/VG_SHARE/LV_SHARE  /share                  gfs     _netdev 0 0
>
> TEST SHARING
> [root at ankebut]# echo 'Date from ankebut is:' `date` >> /share/date
> [root at ankebut]# cat /share/date
> Date from ankebut is: Fri Feb 1 12:40:17 CET 2008
>
> [root at yildiz ~]# echo 'Date from yildiz is:' `date` >> /share/date
> [root at yildiz ~]# cat /share/date
> Date from ankebut is: Fri Feb 1 12:40:17 CET 2008
> Date from yildiz is: Fri Feb 1 13:40:39 CET 2008
>
>
> ====> LVM partition with GFS <====
> in vmw file
> #SHARED Disk 1
> scsi1.present = "TRUE"
> scsi1.virtualDev = "lsilogic"
> scsi1.sharedBus = "virtual"
> scsi1:0.present = "TRUE"
> scsi1:0.fileName = "D:\VmWare\clusterdisks\QuorumDisk.vmdk"
> scsi1:0.mode = "independent-persistent"
> scsi1:0.redo = ""
> scsi1:0.deviceType = "disk"
>
> #SHARED BUS settings
> disk.locking = "FALSE"
> diskLib.dataCacheMaxReadAheadSize = "0"
> diskLib.dataCacheMinReadAheadSize = "0"
> diskLib.dataCacheMaxSize = "0"
> diskLib.dataCachePageSize = "4096"
> diskLib.maxUnsyncedWrites = "0"
>
> [root at ankebut]# cat /etc/hosts
> # Do not remove the following line, or various programs
> # that require network functionality will fail.
>
> 10.81.4.98      ankebut.domain.com      ankebut
> 172.16.40.10    node1.localdomain       node1
> 10.81.4.104     yildiz.domain.com        yildiz
> 172.16.40.11    node2.localdomain       node2
> 127.0.0.1       localhost.localdomain   localhost
>
> Installing this packages from
> http://mirror.centos.org/centos/4/csgfs/CentOS-csgfs.repo:
> rgmanager-1.9.72-1
> system-config-cluster-1.0.51-2.0
> ccs-1.0.11-1
> magma-1.0.8-1
> magma-plugins-1.0.12-0
> cman-1.0.17-0
> cman-kernel-2.6.9-53.5
> gulm-1.0.10-0
> dlm-1.0.7-1
> dlm-kernel-2.6.9-52.2
> fence-1.32.50-2
> iddev-2.0.0-4
> perl-Net-Telnet-3.03-3
>
> [root at ankebut]# parted /dev/sda
> (parted) p
> Disk geometry for /dev/sda: 0.000-8192.000 megabytes
> Disk label type: msdos
> Minor    Start       End     Type      Filesystem  Flags
> 1          0.031      7.844  primary
> 2          7.844   8189.384  primary
>
> [root at ankebut]# mkqdisk -c /dev/sda1 -l QuorumLabel
>
> [root at ankebut]# mkqdisk -L
> mkqdisk v0.5.1
> /dev/sda1:
>         Magic:   eb7a62c2
>         Label:   QuorumLabel
>         Created: Mon Feb  4 09:58:58 2008
>         Host:    ankebut.domain.com
>
> [root at ankebut]# cat /etc/cluster/cluster.conf
> <?xml version="1.0"?>
> <cluster alias="CentOS_RHCS" config_version="1" name="CentOS_RHCS">
>   <fence_daemon post_fail_delay="0" post_join_delay="3"/>
>   <clusternodes>
>     <clusternode name="node1.localdomain" votes="1">
>       <fence>
>         <method name="1">
>           <device name="ManualFence" nodename="node1.localdomain"/>
>         </method>
>       </fence>
>     </clusternode>
>     <clusternode name="node2.localdomain" votes="1">
>       <fence>
>         <method name="1">
>           <device name="ManualFence" nodename="node2.localdomain"/>
>         </method>
>       </fence>
>     </clusternode>
>   </clusternodes>
>   <quorumd interval="1" tko="5" votes="3" log_level="7"
> label="QuorumLabel" status_file="/tmp/quorum-status">
>     <heuristic interval="2" program="/bin/ping node1.localdomain -c1
> -t1" score="1"/>
>     <heuristic interval="2" program="/bin/ping node2.localdomain -c1
> -t1" score="1"/>
>   </quorumd>
>   <cman expected_votes="1" two_node="1"/>
>   <fencedevices>
>     <fencedevice agent="fence_manual" name="ManualFence"/>
>   </fencedevices>
>   <rm>
>     <failoverdomains/>
>     <resources/>
>   </rm>
> </cluster>
>
> TEST QUORUM DISK
> [root at ankebut]# cman_tool nodes
> Node  Votes Exp Sts  Name
>    0    3    0   M   /dev/sda1
>    1    1    1   M   node2.localdomain
>    2    1    1   M   node1.localdomain
>
> [root at ankebut]# cman_tool status
> Protocol version: 5.0.1
> Config version: 1
> Cluster name: CentOS_RHCS
> Cluster ID: 42649
> Cluster Member: Yes
> Membership state: Cluster-Member
> Nodes: 2
> Expected_votes: 1
> Total_votes: 5
> Quorum: 1
> Active subsystems: 2
> Node name: node1.localdomain
> Node ID: 2
>
> [root at ankebut]# cat /tmp/quorum-status
> Time Stamp: Mon Feb  4 10:29:08 2008
> Node ID: 2
> Score: 1/1 (Minimum required = 1)
> Current state: Master
> Initializing Set: { }
> Visible Set: { 1 2 }
> Master Node ID: 2
> Quorate Set: { 1 2 }
>
>
> ====> RAW partitions for Oracle <====
> in vmx file:
> #SHARED Disk 1
> scsi1.present = "TRUE"
> scsi1.virtualDev = "lsilogic"
> scsi1.sharedBus = "virtual"
> scsi1:0.present = "TRUE"
> scsi1:0.fileName = "D:\VmWare\clusterdisks\SharedDisk.vmdk"
> scsi1:0.mode = "independent-persistent"
> scsi1:0.redo = ""
> scsi1:0.deviceType = "disk"
>
> #SHARED BUS settings
> disk.locking = "FALSE"
> diskLib.dataCacheMaxReadAheadSize = "0"
> diskLib.dataCacheMinReadAheadSize = "0"
> diskLib.dataCacheMaxSize = "0"
> diskLib.dataCachePageSize = "4096"
> diskLib.maxUnsyncedWrites = "0"
>
> [root at ankebut]# cat /etc/hosts
> # Do not remove the following line, or various programs
> # that require network functionality will fail.
>
> 10.81.4.98      ankebut.domain.com       ankebut
> 172.16.40.10    node1.localdomain       node1
> 10.81.4.104     yildiz.domain.com        yildiz
> 172.16.40.11    node2.localdomain       node2
> 127.0.0.1       localhost.localdomain   localhost
>
> Installing this packages from
> http://mirror.centos.org/centos/4/csgfs/CentOS-csgfs.repo:
> rgmanager-1.9.72-1
> system-config-cluster-1.0.51-2.0
> ccs-1.0.11-1
> magma-1.0.8-1
> magma-plugins-1.0.12-0
> cman-1.0.17-0
> cman-kernel-2.6.9-53.5
> gulm-1.0.10-0
> dlm-1.0.7-1
> dlm-kernel-2.6.9-52.2
> fence-1.32.50-2
> iddev-2.0.0-4
> perl-Net-Telnet-3.03-3
>
> [root at ankebut ~]# fdisk /dev/sda
> Command (m for help): p
>
> Disk /dev/sda: 8589 MB, 8589934592 bytes
> 255 heads, 63 sectors/track, 1044 cylinders
> Units = cylinders of 16065 * 512 = 8225280 bytes
>
>    Device Boot      Start         End      Blocks   Id  System
> /dev/sda1               1         522     4192933+  83  Linux
> /dev/sda2             523        1044     4192965   83  Linux
>
> [root at ankebut]# cat /etc/sysconfig/rawdevices
> # This file and interface are deprecated.
> # Applications needing raw device access should open regular
> # block devices with O_DIRECT.
> # raw device bindings
> # format:  <rawdev> <major> <minor>
> #          <rawdev> <blockdev>
> # example: /dev/raw/raw1 /dev/sda1
> #          /dev/raw/raw2 8 5
> /dev/raw/raw1 /dev/sda1
> /dev/raw/raw2 /dev/sda2
>
> [root at ankebut]# service rawdevices restart
> Assigning devices:
>            /dev/raw/raw1  -->   /dev/sda1
> /dev/raw/raw1:  bound to major 8, minor 1
>            /dev/raw/raw2  -->   /dev/sda2
> /dev/raw/raw2:  bound to major 8, minor 2
> Done
>
> [root at ankebut]# raw -qa
> /dev/raw/raw1:  bound to major 8, minor 1
> /dev/raw/raw2:  bound to major 8, minor 2
>
>
> [root at ankebut /]# mkfs.ext3 -j -b 4096 /dev/sda1
> [root at ankebut /]# mkfs.ext3 -j -b 4096 /dev/sda2
>
> [root at ankebut]# cat /etc/cluster/cluster.conf
> :(, I dont know how to create cluster.conf for raw configuration in my case
>
> TEST RAW DISK
> I dont know how to test RAW configuration
>
>
> Please, check my configurations and please tell me where i make
> mistake, if i make :)
> Thanks.
>
> With Regards
> Asim
>
>
> On Feb 7, 2008 4:40 PM, Asim Husanovic <asim.husanovic at gmail.com> wrote:
> > Thanks.
> > Asim
> >
> >
> > On Feb 7, 2008 4:28 PM, Brian Kroth <bpkroth at wisc.edu> wrote:
> > > Here are some quick examples.  There are almost certainly other ways to do
> > > it.
> > >
> > > Asim Husanovic <asim.husanovic at gmail.com>:
> > > > Hi
> > > >
> > > > How to identify shared disk/volumes?
> > >
> > > scsi_id
> > >
> > > > How to collect the cluster FS information?
> > >
> > > gfs_tool
> > >
> > > > How to display shared disks on node/s? Which node/s?
> > >
> > > gfs_tool list
> > > cman_tool services
> > >
> > >
> > > You can wrap all of these inside snmp scripts/oids or use nagios passive
> > > checks if you want to monitor them remotely/automatically.
> > >
> > > Brian
> > >
> >
>



From lhh at redhat.com  Tue Feb 12 14:50:32 2008
From: lhh at redhat.com (Lon Hohberger)
Date: Tue, 12 Feb 2008 09:50:32 -0500
Subject: [Linux-cluster] 2-node tie-breaking
In-Reply-To: <alpine.LRH.1.00.0802081514250.15647@skynet.shatteredsilicon.net>
References: <alpine.LRH.1.00.0802071523160.7145@skynet.shatteredsilicon.net>
	<1202412937.2938.55.camel@localhost.localdomain>
	<47AB71D2.2040201@bobich.net>
	<1202421366.2938.70.camel@localhost.localdomain>
	<47AB840C.8040905@bobich.net> <20080207223951.GB15215@localhost>
	<20080207230727.GE63223@widexs.nl>
	<1202483577.21504.96.camel@ayanami.boston.devel.redhat.com>
	<alpine.LRH.1.00.0802081514250.15647@skynet.shatteredsilicon.net>
Message-ID: <1202827832.2970.3.camel@localhost.localdomain>


On Fri, 2008-02-08 at 15:32 +0000, gordan at bobich.net wrote:

> I just had another thought. Most motherboards these days are ATX, which 
> means ATX type "short-pins-to-power-on" power switches. That means that as 
> a _REALLY_ cheap solution I could just get something like a small relay 
> switch and wire it into the serial port. When a pin on RS232 goes high 
> (e.g. DTR), it activates the switch. I think it would be pretty reliable, 
> and the total cost of components would be pennies. The fence agent would 
> also be a total of about 10 lines of code, too. :)

It'd have to be a 'press-and-hold' sort of thing.  E.g. either activate
or deactivate DTR for 5+ seconds. ;)

"Reboot" -

Power-off:
+dtr
sleep 5
-dtr

Power-on:
+dtr
-dtr

This reminds me of the 'clapper' agent someone suggested awhile ago.

-- Lon



From lhh at redhat.com  Tue Feb 12 15:59:03 2008
From: lhh at redhat.com (Lon Hohberger)
Date: Tue, 12 Feb 2008 10:59:03 -0500
Subject: [Linux-cluster] watchdog: rebootig
In-Reply-To: <1202765364.20118.6.camel@ayanami.boston.devel.redhat.com>
References: <1939546029@web.de>
	<B2ED9364017FF54FB9392221F9A498450276E718@nwpsrv08.edj.ad.edwardjones.com>
	<1202741846.6443.148.camel@ayanami.boston.devel.redhat.com>
	<B2ED9364017FF54FB9392221F9A498450276E8C5@nwpsrv08.edj.ad.edwardjones.com>
	<1202765364.20118.6.camel@ayanami.boston.devel.redhat.com>
Message-ID: <1202831943.2970.5.camel@localhost.localdomain>


On Mon, 2008-02-11 at 16:29 -0500, Lon Hohberger wrote:
> On Mon, 2008-02-11 at 11:18 -0600, Stulic,Damjan wrote:
> 
> > rgmanager-1.9.54-1.x86_64
> > Name        : rgmanager                    Relocations: (not
> > relocatable)
> > Version     : 1.9.54                            Vendor: Red Hat, Inc.
> > Release     : 1                             Build Date: Fri 06 Oct 2006
> > 11:43:10 AM CDT 
> 
> Ah, it's probably the rg_thread.c assertion failure; here's the patch:
> 
> https://bugzilla.redhat.com/attachment.cgi?id=139908&action=edit
> 
> Apparently we never opened the bug (for public viewing), but it was
> fixed in the 4.5 updates (note... recent ccs package would be needed
> too).

Ah - here it is:

https://bugzilla.redhat.com/show_bug.cgi?id=250085

-- Lon




From rpeterso at redhat.com  Tue Feb 12 17:30:50 2008
From: rpeterso at redhat.com (Bob Peterson)
Date: Tue, 12 Feb 2008 11:30:50 -0600
Subject: [Linux-cluster] GFS1 NFS problems under 2.6.25-rc1  (was: GFS2
	loses data under kernel 2.6.24...)
In-Reply-To: <38964.155.82.73.253.1202764106.squirrel@www.r-networks.net>
References: <1202446917.5942.19.camel@eclipse.office.r-networks.net>
	<1202463059.22038.421.camel@quoit>
	<38964.155.82.73.253.1202764106.squirrel@www.r-networks.net>
Message-ID: <1202837450.2701.6.camel@technetium.msp.redhat.com>

On Mon, 2008-02-11 at 16:08 -0500, Glen Dosey wrote:
> The gfs module builds successfully against the 2.6.25-rc1 kernel and
> loads. Locally on the server everything appears to work, but on the GFs
> filesystem NFS exported from the server, clients can create files but they
> sometimes fail to store any data. For example:

Hi Glen,

I'll try to verify that the HEAD branch contains all of the recent
fixes found in the RHEL5 branch.  I'll also try to recreate the problem
when I can.  In the mean time, can you open up a bugzilla record for
this problem and assign it to me?  Thanks.

Regards,

Bob Peterson
Red Hat GFS




From wferi at niif.hu  Tue Feb 12 18:13:10 2008
From: wferi at niif.hu (Wagner Ferenc)
Date: Tue, 12 Feb 2008 19:13:10 +0100
Subject: [Linux-cluster] no version for "gfs2_unmount_lockproto"
Message-ID: <878x1q59hl.fsf@szonett.ki.iif.hu>

Hi,

I've compiled cluster-2.01.00 against Linux 2.6.23.16.  On modprobe
gfs I got the following two kernel messages:

gfs: no version for "gfs2_unmount_lockproto" found: kernel tainted.
GFS 2.01.00 (built Feb 12 2008 14:42:50) installed

Strange.  I went on, and the mount command froze (Ctrl-C can't kill
it, though it isn't in D state: it's consuming 5% of CPU) with these
messages:

Trying to join cluster "lock_dlm", "pilot:test"
Joined cluster. Now mounting FS...
GFS: fsid=pilot:test.4294967295: can't mount journal #4294967295
GFS: fsid=pilot:test.4294967295: there are only 6 journals (0 - 5)

Right before issuing the mount command, cman_tool services reported:

type             level name     id       state       
fence            0     default  00010001 none        
[1 3]
dlm              1     clvmd    00020001 none        
[1 3]

On node 3, the same command reports:

type             level name     id       state       
fence            0     default  00010001 none        
[1 3]
dlm              1     clvmd    00020001 none        
[1 3]
dlm              1     test     00020002 none        
[1 3]
gfs              2     test     00010003 none        
[3]

This node can indeed use the filesystem.  It's running Linux 2.6.23.8
with the same cluster suite.

Anybody has an idea what can be wrong?
-- 
Thanks,
Feri.



From rpeterso at redhat.com  Tue Feb 12 18:34:34 2008
From: rpeterso at redhat.com (Bob Peterson)
Date: Tue, 12 Feb 2008 12:34:34 -0600
Subject: [Linux-cluster] no version for "gfs2_unmount_lockproto"
In-Reply-To: <878x1q59hl.fsf@szonett.ki.iif.hu>
References: <878x1q59hl.fsf@szonett.ki.iif.hu>
Message-ID: <1202841274.2701.15.camel@technetium.msp.redhat.com>

On Tue, 2008-02-12 at 19:13 +0100, Wagner Ferenc wrote:
> Hi,
> 
> I've compiled cluster-2.01.00 against Linux 2.6.23.16.  On modprobe
> gfs I got the following two kernel messages:
> 
> gfs: no version for "gfs2_unmount_lockproto" found: kernel tainted.
> GFS 2.01.00 (built Feb 12 2008 14:42:50) installed

Hi Wagner,

The HEAD / RHEL5 / (similar) versions of GFS use part of gfs2's
locking infrastructure.  For RHEL5, we did a patch to export
those symbols from GFS2.  The patch looks like the one I have
below.  So the GFS2 module has to be loaded for GFS to work
and that's just so GFS and GFS2 share the same locking protocol.
(i.e. people can mount both gfs and gfs2 at the same time and
go through the same dlm).  The exporting of those symbols did
not get pushed into upstream GFS2 because it's only needed for
GFS(1), which itself isn't part of the upstream kernel.

If you add these symbol exports to GFS2 it should allow GFS
to mount properly.

Regards,

Bob Peterson
Red Hat GFS
--
--- a/fs/gfs2/locking.c	2008-02-11 11:10:57.000000000 -0600
+++ b/fs/gfs2/locking.c	2008-02-08 14:10:36.000000000 -0600
@@ -181,4 +181,6 @@ void gfs2_withdraw_lockproto(struct lm_l
 
 EXPORT_SYMBOL_GPL(gfs2_register_lockproto);
 EXPORT_SYMBOL_GPL(gfs2_unregister_lockproto);
-
+EXPORT_SYMBOL_GPL(gfs2_withdraw_lockproto);
+EXPORT_SYMBOL_GPL(gfs2_mount_lockproto);
+EXPORT_SYMBOL_GPL(gfs2_unmount_lockproto);




From bpkroth at wisc.edu  Tue Feb 12 18:46:26 2008
From: bpkroth at wisc.edu (Brian Kroth)
Date: Tue, 12 Feb 2008 12:46:26 -0600
Subject: [Linux-cluster] no version for "gfs2_unmount_lockproto"
In-Reply-To: <1202841274.2701.15.camel@technetium.msp.redhat.com>
References: <878x1q59hl.fsf@szonett.ki.iif.hu>
	<1202841274.2701.15.camel@technetium.msp.redhat.com>
Message-ID: <20080212184626.GH10361@wisc.edu>

Bob Peterson <rpeterso at redhat.com>:
> Hi Wagner,
> 
> The HEAD / RHEL5 / (similar) versions of GFS use part of gfs2's
> locking infrastructure.  For RHEL5, we did a patch to export
> those symbols from GFS2.  The patch looks like the one I have
> below.  So the GFS2 module has to be loaded for GFS to work
> and that's just so GFS and GFS2 share the same locking protocol.
> (i.e. people can mount both gfs and gfs2 at the same time and
> go through the same dlm).  The exporting of those symbols did
> not get pushed into upstream GFS2 because it's only needed for
> GFS(1), which itself isn't part of the upstream kernel.
> 
> If you add these symbol exports to GFS2 it should allow GFS
> to mount properly.
> 
> Regards,
> 
> Bob Peterson
> Red Hat GFS
> --
> --- a/fs/gfs2/locking.c	2008-02-11 11:10:57.000000000 -0600
> +++ b/fs/gfs2/locking.c	2008-02-08 14:10:36.000000000 -0600
> @@ -181,4 +181,6 @@ void gfs2_withdraw_lockproto(struct lm_l
>  
>  EXPORT_SYMBOL_GPL(gfs2_register_lockproto);
>  EXPORT_SYMBOL_GPL(gfs2_unregister_lockproto);
> -
> +EXPORT_SYMBOL_GPL(gfs2_withdraw_lockproto);
> +EXPORT_SYMBOL_GPL(gfs2_mount_lockproto);
> +EXPORT_SYMBOL_GPL(gfs2_unmount_lockproto);

I'm curious.  Are there plans to include this patch in the mainline?  Any
reasons why or why not?

Thanks,
Brian
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/x-pkcs7-signature
Size: 2192 bytes
Desc: not available
URL: <http://listman.redhat.com/archives/linux-cluster/attachments/20080212/807fbcd9/attachment.bin>

From alaack at ustrap.com  Tue Feb 12 18:53:53 2008
From: alaack at ustrap.com (Andrea Laack)
Date: Tue, 12 Feb 2008 12:53:53 -0600
Subject: [Linux-cluster] cluster crash problem
Message-ID: <200802121835.m1CIZBCb015988@gate.ustrap.com>

We are running RHEL 3.0 with version 1.0.3 of RedHat cluster suite.  We are
utilizing a Promise Vtrak 15200 for shared storage and an Adaptec ASA-7211C
iSCSI initiator.
Having problems with any process that uses high I/O across the iSCSI link.

Last night dba attempted to create an Oracle instance on the shared storage
device.  The cluster crashed and failed over the the backup node.  Nothing
in the logs.  Log level set at 6.  Only indication I have that something
happened is from the graphs of the disk I/O (HotSanic).  This shows 69.42
Pentabytes (yes, it shows pentabytes).

We are using a watchdog timer.

This has happened before when copying *very* large amounts of data that
includes *very* large files.  Many small files does not cause the cluster to
crash.

Has anyone seen this type of problem?  Any help will be sincerely
appreciated.  Adaptec will only talk to me if I pay them $199/phone call.

Thanks
Andrea

Andrea Laack
Network Administrator
Universal Strap 
W209N17500 Industrial Drive
Jackson, WI  53037
262-677-3641 Ext 5220



From rpeterso at redhat.com  Tue Feb 12 19:06:30 2008
From: rpeterso at redhat.com (Bob Peterson)
Date: Tue, 12 Feb 2008 13:06:30 -0600
Subject: [Linux-cluster] no version for "gfs2_unmount_lockproto"
In-Reply-To: <20080212184626.GH10361@wisc.edu>
References: <878x1q59hl.fsf@szonett.ki.iif.hu>
	<1202841274.2701.15.camel@technetium.msp.redhat.com>
	<20080212184626.GH10361@wisc.edu>
Message-ID: <1202843190.2701.29.camel@technetium.msp.redhat.com>

On Tue, 2008-02-12 at 12:46 -0600, Brian Kroth wrote:
> I'm curious.  Are there plans to include this patch in the mainline?  Any
> reasons why or why not?
> 
> Thanks,
> Brian

Hi Brian,

That's a gfs2 patch, and gfs2 "mainline" is the upstream git tree from
kernel.org.  We've never tried to add that patch to the upstream kernel
because we figured it would be rejected by the upstream community.
Those people likely wouldn't accept the suggestion that it should be
added "just in case someone wants to run out-of-tree gfs on top of
gfs2."  After all, the patch is really only useful if gfs (vers. 1) is
required, but gfs is not part of that upstream kernel.

>From what I've heard, the Fedora community doesn't really accept
anything along those lines anymore either.  So far they've let us get
away with it, but I've heard that it's unacceptable for us going
forward (Fedora 9 or 10?  I'm not sure where the cutoff is). So lately
we've been discussing whether/how to separate out the gfs1 and gfs2
infrastructure so that there isn't that crossover.  That issue is still
work-in-progress.

Regards,

Bob Peterson
Red Hat GFS




From swhiteho at redhat.com  Tue Feb 12 19:52:05 2008
From: swhiteho at redhat.com (Steven Whitehouse)
Date: Tue, 12 Feb 2008 19:52:05 +0000
Subject: [Linux-cluster] no version for "gfs2_unmount_lockproto"
In-Reply-To: <1202843190.2701.29.camel@technetium.msp.redhat.com>
References: <878x1q59hl.fsf@szonett.ki.iif.hu>
	<1202841274.2701.15.camel@technetium.msp.redhat.com>
	<20080212184626.GH10361@wisc.edu>
	<1202843190.2701.29.camel@technetium.msp.redhat.com>
Message-ID: <1202845925.3740.15.camel@localhost.localdomain>

Hi,

On Tue, 2008-02-12 at 13:06 -0600, Bob Peterson wrote:
> On Tue, 2008-02-12 at 12:46 -0600, Brian Kroth wrote:
> > I'm curious.  Are there plans to include this patch in the mainline?  Any
> > reasons why or why not?
> > 
> > Thanks,
> > Brian
> 
> Hi Brian,
> 
> That's a gfs2 patch, and gfs2 "mainline" is the upstream git tree from
> kernel.org.  We've never tried to add that patch to the upstream kernel
> because we figured it would be rejected by the upstream community.
> Those people likely wouldn't accept the suggestion that it should be
> added "just in case someone wants to run out-of-tree gfs on top of
> gfs2."  After all, the patch is really only useful if gfs (vers. 1) is
> required, but gfs is not part of that upstream kernel.
> 
> >From what I've heard, the Fedora community doesn't really accept
> anything along those lines anymore either.  So far they've let us get
> away with it, but I've heard that it's unacceptable for us going
> forward (Fedora 9 or 10?  I'm not sure where the cutoff is). So lately
> we've been discussing whether/how to separate out the gfs1 and gfs2
> infrastructure so that there isn't that crossover.  That issue is still
> work-in-progress.
> 
> Regards,
> 
> Bob Peterson
> Red Hat GFS
> 
Just to confirm some of the details, F-8 is the last one which will have
our exports in it. The reason that we haven't pushed the export patch
upstream is that in the future for GFS2 we intend to get rid of that
particular interface, so we didn't want to export it in case someone
else started using it and thus prevented or slowed that process. Also
exports for use by out-of-tree code tend to be frowned upon.

The plan is that the interface between the filesystem and the lock
manager will be the DLM's interface, so we will still allow pluggable
lock managers, but just at a slightly different level in the code.

So at some stage we'll need to duplicate the lock modules for GFS
anyway, and about now seems as good a time as any to start that process,

Steve.





From swhiteho at redhat.com  Tue Feb 12 20:02:19 2008
From: swhiteho at redhat.com (Steven Whitehouse)
Date: Tue, 12 Feb 2008 20:02:19 +0000
Subject: [Linux-cluster] 2-node tie-breaking
In-Reply-To: <1202827832.2970.3.camel@localhost.localdomain>
References: <alpine.LRH.1.00.0802071523160.7145@skynet.shatteredsilicon.net>
	<1202412937.2938.55.camel@localhost.localdomain>
	<47AB71D2.2040201@bobich.net>
	<1202421366.2938.70.camel@localhost.localdomain>
	<47AB840C.8040905@bobich.net> <20080207223951.GB15215@localhost>
	<20080207230727.GE63223@widexs.nl>
	<1202483577.21504.96.camel@ayanami.boston.devel.redhat.com>
	<alpine.LRH.1.00.0802081514250.15647@skynet.shatteredsilicon.net>
	<1202827832.2970.3.camel@localhost.localdomain>
Message-ID: <1202846539.3740.24.camel@localhost.localdomain>

Hi,

On Tue, 2008-02-12 at 09:50 -0500, Lon Hohberger wrote:
> On Fri, 2008-02-08 at 15:32 +0000, gordan at bobich.net wrote:
> 
> > I just had another thought. Most motherboards these days are ATX, which 
> > means ATX type "short-pins-to-power-on" power switches. That means that as 
> > a _REALLY_ cheap solution I could just get something like a small relay 
> > switch and wire it into the serial port. When a pin on RS232 goes high 
> > (e.g. DTR), it activates the switch. I think it would be pretty reliable, 
> > and the total cost of components would be pennies. The fence agent would 
> > also be a total of about 10 lines of code, too. :)
> 
> It'd have to be a 'press-and-hold' sort of thing.  E.g. either activate
> or deactivate DTR for 5+ seconds. ;)
> 
I did something similar in the early days of Sistina. I used a (ISA
bus!) lab card with 12 relays on it, one of which was connected across
the reset switch of my test machine. Together with a serial console that
gave me all the control that I generally needed when working remotely.

Its relatively unlikely that an RS-232 port would supply enough current
to drive a relay directly, but you might find a suitable alternative in
an opto-isolator, and that would also have the advantage of not being
inductive and thus it won't potentially put a surge onto your
power-rails in case your decoupling isn't 100%. Its also cheaper.

Steve.




From jakub.suchy at enlogit.cz  Tue Feb 12 20:36:43 2008
From: jakub.suchy at enlogit.cz (Jakub Suchy)
Date: Tue, 12 Feb 2008 21:36:43 +0100
Subject: [Linux-cluster] 2-node tie-breaking
In-Reply-To: <1202846539.3740.24.camel@localhost.localdomain>
References: <1202412937.2938.55.camel@localhost.localdomain>
	<47AB71D2.2040201@bobich.net>
	<1202421366.2938.70.camel@localhost.localdomain>
	<47AB840C.8040905@bobich.net> <20080207223951.GB15215@localhost>
	<20080207230727.GE63223@widexs.nl>
	<1202483577.21504.96.camel@ayanami.boston.devel.redhat.com>
	<alpine.LRH.1.00.0802081514250.15647@skynet.shatteredsilicon.net>
	<1202827832.2970.3.camel@localhost.localdomain>
	<1202846539.3740.24.camel@localhost.localdomain>
Message-ID: <20080212203643.GA29087@localhost>

> Its relatively unlikely that an RS-232 port would supply enough current
> to drive a relay directly, but you might find a suitable alternative in
> an opto-isolator, and that would also have the advantage of not being
> inductive and thus it won't potentially put a surge onto your
> power-rails in case your decoupling isn't 100%. Its also cheaper.

Czech Republic is a Wi-Fi giant. As Wi-Fi access points have been really
unreliable, many Wi-Fi amateurs developed Watchdogs on their own.
This is one of them:

http://www.simandl.cz/stranky/elektro/resetator/resetator.htm

In Czech only, but it may be OK for an experienced developer. I can
provide rough translation if needed.

Jakub

-- 
Jakub Such? <jakub.suchy at enlogit.cz>
GSM: +420 - 777 817 949

Enlogit s.r.o, U Cukrovaru 509/4, 400 07 ?st? nad Labem
tel.: +420 - 474 745 159, fax: +420 - 474 745 160
e-mail: info at enlogit.cz, web: http://www.enlogit.cz



From christopher.barry at qlogic.com  Tue Feb 12 20:51:00 2008
From: christopher.barry at qlogic.com (Christopher Barry)
Date: Tue, 12 Feb 2008 14:51:00 -0600
Subject: [Linux-cluster] Here is my cluster node shutdown script
Message-ID: <D158540CCC0AB54C8FD4818F823CCB2453AE25@EPEXCH1.qlogic.org>


Hi All,

Just throwing this out there in case anyone has a use for it. 
It works well for me, and I know that until I wrote it, 
shutdowns were painful. (they were fences, really ;)

Improvements, and or comments welcome.

A small way of giving back ;)

Cheers,
-C

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://listman.redhat.com/archives/linux-cluster/attachments/20080212/5a8851cc/attachment.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: shutdown_node.bz2
Type: application/x-bzip
Size: 1244 bytes
Desc: shutdown_node.bz2
URL: <http://listman.redhat.com/archives/linux-cluster/attachments/20080212/5a8851cc/attachment.bin>

From wferi at niif.hu  Tue Feb 12 21:29:45 2008
From: wferi at niif.hu (Ferenc Wagner)
Date: Tue, 12 Feb 2008 22:29:45 +0100
Subject: [Linux-cluster] no version for "gfs2_unmount_lockproto"
In-Reply-To: <1202841274.2701.15.camel@technetium.msp.redhat.com> (Bob
	Peterson's message of "Tue, 12 Feb 2008 12:34:34 -0600")
References: <878x1q59hl.fsf@szonett.ki.iif.hu>
	<1202841274.2701.15.camel@technetium.msp.redhat.com>
Message-ID: <87skzxq2wm.fsf@szonett.ki.iif.hu>

Bob Peterson <rpeterso at redhat.com> writes:

> On Tue, 2008-02-12 at 19:13 +0100, Wagner Ferenc wrote:
> 
>> I've compiled cluster-2.01.00 against Linux 2.6.23.16.  On modprobe
>> gfs I got the following two kernel messages:
>> 
>> gfs: no version for "gfs2_unmount_lockproto" found: kernel tainted.
>> GFS 2.01.00 (built Feb 12 2008 14:42:50) installed
>
> The HEAD / RHEL5 / (similar) versions of GFS use part of gfs2's
> locking infrastructure.  For RHEL5, we did a patch to export
> those symbols from GFS2.  The patch looks like the one I have
> below. [...]
>
> --- a/fs/gfs2/locking.c	2008-02-11 11:10:57.000000000 -0600
> +++ b/fs/gfs2/locking.c	2008-02-08 14:10:36.000000000 -0600
> @@ -181,4 +181,6 @@ void gfs2_withdraw_lockproto(struct lm_l
>  
>  EXPORT_SYMBOL_GPL(gfs2_register_lockproto);
>  EXPORT_SYMBOL_GPL(gfs2_unregister_lockproto);
> -
> +EXPORT_SYMBOL_GPL(gfs2_withdraw_lockproto);
> +EXPORT_SYMBOL_GPL(gfs2_mount_lockproto);
> +EXPORT_SYMBOL_GPL(gfs2_unmount_lockproto);

Actually, I also patched my kernel tree like this.  In cases when I
forgot it, I wasn't even allowed to load the gfs module into the
kernel.  In this case the "tainted" warning was related to a slight
vermagic mismatch, and after recompiling everything properly, it went
away.

But the issue remained: the mount command just sits there, consuming
some CPU, and by now I've got the following console output (with my
notes in the brackets):

[modprobe gfs]
GFS 2.01.00 (built Feb 12 2008 22:07:48) installed
[starting the cluster infrastructure]
dlm: Using TCP for communications
dlm: connecting to 3
dlm: got connection from 3
[mount /mnt]
Trying to join cluster "lock_dlm", "pilot:test"
Joined cluster. Now mounting FS...
GFS: fsid=pilot:test.4294967295: can't mount journal #4294967295
GFS: fsid=pilot:test.4294967295: there are only 6 journals (0 - 5)
[a couple of minutes passed here]
GFS: fsid=pilot:test.4294967295: Unmount seems to be stalled. Dumping lock state...
Glock (2, 25)
  gl_flags = 
  gl_count = 2
  gl_state = 0
  req_gh = no
  req_bh = no
  lvb_count = 0
  object = yes
  new_le = no
  incore_le = no
  reclaim = no
  aspace = 0
  ail_bufs = no
  Inode:
    num = 25/25
    type = 1
    i_count = 1
    i_flags = 
    vnode = no
Glock (5, 25)
  gl_flags = 
  gl_count = 2
  gl_state = 3
  req_gh = no
  req_bh = no
  lvb_count = 0
  object = yes
  new_le = no
  incore_le = no
  reclaim = no
  aspace = no
  ail_bufs = no
  Holder
    owner = -1
    gh_state = 3
    gh_flags = 5 7 
    error = 0
    gh_iflags = 1 6 7 

Now, mount is still stalled, and still consumes 6% of CPU.
-- 
Regards,
Feri.



From l_x2828 at yahoo.com  Tue Feb 12 21:32:32 2008
From: l_x2828 at yahoo.com (BJ)
Date: Tue, 12 Feb 2008 13:32:32 -0800 (PST)
Subject: [Linux-cluster] Help - how to check if a node is still healthy
	after upgrade GFS on it?
Message-ID: <681346.60850.qm@web55508.mail.re4.yahoo.com>

Hi,

Could some one please tell me what is the safe/best
way to check if a cluster node is still healthy after
we upgrade GFS on this node?  

I guess it's probably not very safe to say it's
healthy by verifying this node can rejoin the cluster
after being upgraded and then rebooted.

A bit more information on the upgrade.  We upgrade one
of the three nodes in a cluster from GFS-6.0.2-25 to
GFS-6.0.2.36-1.

Regards,
BJ
--




      ____________________________________________________________________________________
Never miss a thing.  Make Yahoo your home page. 
http://www.yahoo.com/r/hs



From randy.brown at noaa.gov  Tue Feb 12 22:03:03 2008
From: randy.brown at noaa.gov (Randy Brown)
Date: Tue, 12 Feb 2008 17:03:03 -0500
Subject: [Linux-cluster] One node rebooting quite often
Message-ID: <47B21797.90005@noaa.gov>

I am attaching the relevant log entries from a node that is rebooting 
about twice per day on average.  I can't seem to pinpoint why?  I was 
hoping someone could Identify something I'm overlooking.  I will gladly 
provide more information as needed. 

I'm running a two-node nfs cluster on Centos 5 with the following packages:
rgmanager-2.0.31-1.el5.centos
gfs2-utils-0.1.38-1.el5
gfs-utils-0.1.12-1.el5
system-config-lvm-1.0.22-1.0.el5
cman-2.0.73-1.el5_1.1
lvm2-cluster-2.02.26-1.el5
kmod-gfs-0.1.16-6.2.6.18_8.1.15.el5
lvm2-2.02.26-3.el5
kmod-gfs-0.1.19-7.el5_1.1
kernel-2.6.18-53.1.6.el5

Thanks!

Randy
-------------- next part --------------
A non-text attachment was scrubbed...
Name: cluster.log
Type: text/x-log
Size: 190498 bytes
Desc: not available
URL: <http://listman.redhat.com/archives/linux-cluster/attachments/20080212/a4aea143/attachment.bin>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: cluster.conf
Type: text/xml
Size: 5045 bytes
Desc: not available
URL: <http://listman.redhat.com/archives/linux-cluster/attachments/20080212/a4aea143/attachment.xml>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: randy.brown.vcf
Type: text/x-vcard
Size: 313 bytes
Desc: not available
URL: <http://listman.redhat.com/archives/linux-cluster/attachments/20080212/a4aea143/attachment.vcf>

From rpeterso at redhat.com  Tue Feb 12 22:43:22 2008
From: rpeterso at redhat.com (Bob Peterson)
Date: Tue, 12 Feb 2008 16:43:22 -0600
Subject: [Linux-cluster] no version for "gfs2_unmount_lockproto"
In-Reply-To: <87skzxq2wm.fsf@szonett.ki.iif.hu>
References: <878x1q59hl.fsf@szonett.ki.iif.hu>
	<1202841274.2701.15.camel@technetium.msp.redhat.com>
	<87skzxq2wm.fsf@szonett.ki.iif.hu>
Message-ID: <1202856202.2701.43.camel@technetium.msp.redhat.com>

On Tue, 2008-02-12 at 22:29 +0100, Ferenc Wagner wrote:
> Actually, I also patched my kernel tree like this.  In cases when I
> forgot it, I wasn't even allowed to load the gfs module into the
> kernel.  In this case the "tainted" warning was related to a slight
> vermagic mismatch, and after recompiling everything properly, it went
> away.
> 
> But the issue remained: the mount command just sits there, consuming
> some CPU, and by now I've got the following console output (with my
> notes in the brackets):

> Now, mount is still stalled, and still consumes 6% of CPU.

Hi Ferenc,

This gfs hang on failed mounts is documented in bugzilla bug #425421,
and I've already got a patch for it.  Since this bug was reported
internally to Red Hat, I don't know if this bug record is viewable by
the public.  (I don't have control over the permission bits and how
they default, so don't shoot the messenger.)  :7)  The fix has not been
shipped yet due to code freeze, but I'll attach the patch that fixes 
it below.

Regards,

Bob Peterson
Red Hat GFS
--
Index: ops_fstype.c
===================================================================
RCS file: /cvs/cluster/cluster/gfs-kernel/src/gfs/ops_fstype.c,v
retrieving revision 1.28.2.5
diff -w -u -p -p -u -r1.28.2.5 ops_fstype.c
--- ops_fstype.c	19 Jun 2007 21:06:10 -0000	1.28.2.5
+++ ops_fstype.c	1 Feb 2008 20:16:38 -0000
@@ -388,6 +388,7 @@ out:
 	return error;
 
 fail_dput:
+	gfs_inode_put(sdp->sd_linode);
 	if (sb->s_root) {
 		dput(sb->s_root);
 		sb->s_root = NULL;




From nhuczp at gmail.com  Wed Feb 13 05:51:43 2008
From: nhuczp at gmail.com (chenzp)
Date: Wed, 13 Feb 2008 13:51:43 +0800
Subject: [Linux-cluster] RHCS 5.1 latest packages, 2-node cluster,
	doesn't come up with only 1 node
In-Reply-To: <20080208132257.M22787@webbertek.com.br>
References: <20080208130449.M21432@webbertek.com.br>
	<20080208132257.M22787@webbertek.com.br>
Message-ID: <6cc6db6f0802122151j23720c86jc70c834420371bf3@mail.gmail.com>

2008/2/8, Celso K. Webber <celso at webbertek.com.br>:
>
> Hello,
>
> I forgot to add some versioning information from the Cluster packages,
> here
> they are:
>
> * Main cluster packages:
> cman-2.0.73-1.el5_1.1.x86_64.rpm
> openais-0.80.3-7.el5.x86_64.rpm
> perl-Net-Telnet-3.03-5.noarch.rpm
>
> * Admin tools packages:
> Cluster_Administration-en-US-5.1.0-7.noarch.rpm
> cluster-cim-0.10.0-5.el5_1.1.x86_64.rpm
> cluster-snmp-0.10.0-5.el5_1.1.x86_64.rpm
> luci-0.10.0-6.el5.x86_64.rpm
> modcluster-0.10.0-5.el5_1.1.x86_64.rpm
> rgmanager-2.0.31-1.el5.x86_64.rpm
> ricci-0.10.0-6.el5.x86_64.rpm


please use luci and ricci build cluster !!

RHEL-5-manual:
http://www.redhat.com/docs/manuals/enterprise/RHEL-5-manual/en-US/RHEL510/Cluster_Administration/s1-start-luci-ricci-conga-CA.html

Conga User Manual:
http://sources.redhat.com/cluster/conga/doc/user_manual.html

system-config-cluster-1.0.50-1.3.noarch.rpm
> tog-pegasus-2.6.1-2.el5_1.1.*.rpm
> oddjob-*.rpm
>
> Thank you,
>
> Celso.
>
> On Fri, 8 Feb 2008 11:18:20 -0200, Celso K. Webber wrote
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://listman.redhat.com/archives/linux-cluster/attachments/20080213/00dd98d4/attachment.htm>

From wferi at niif.hu  Wed Feb 13 08:23:00 2008
From: wferi at niif.hu (Ferenc Wagner)
Date: Wed, 13 Feb 2008 09:23:00 +0100
Subject: [Linux-cluster] no version for "gfs2_unmount_lockproto"
In-Reply-To: <1202856202.2701.43.camel@technetium.msp.redhat.com> (Bob
	Peterson's message of "Tue, 12 Feb 2008 16:43:22 -0600")
References: <878x1q59hl.fsf@szonett.ki.iif.hu>
	<1202841274.2701.15.camel@technetium.msp.redhat.com>
	<87skzxq2wm.fsf@szonett.ki.iif.hu>
	<1202856202.2701.43.camel@technetium.msp.redhat.com>
Message-ID: <87bq6lp8nv.fsf@szonett.ki.iif.hu>

Bob Peterson <rpeterso at redhat.com> writes:

> On Tue, 2008-02-12 at 22:29 +0100, Ferenc Wagner wrote:
>> Actually, I also patched my kernel tree like this.  In cases when I
>> forgot it, I wasn't even allowed to load the gfs module into the
>> kernel.  In this case the "tainted" warning was related to a slight
>> vermagic mismatch, and after recompiling everything properly, it went
>> away.
>> 
>> But the issue remained: the mount command just sits there, consuming
>> some CPU, and by now I've got the following console output (with my
>> notes in the brackets):
>
>> Now, mount is still stalled, and still consumes 6% of CPU.
>
> This gfs hang on failed mounts is documented in bugzilla bug #425421,
> and I've already got a patch for it.  Since this bug was reported
> internally to Red Hat, I don't know if this bug record is viewable by
> the public.  (I don't have control over the permission bits and how
> they default, so don't shoot the messenger.)  :7)

:) I certainly wouldn't have, especially that you provided the patch.
But no worries, the bugzilla entry was perfectly accessible for me.

> The fix has not been shipped yet due to code freeze, but I'll attach
> the patch that fixes it below.

Thanks!  This patch indeed fixed the hang.  But of course not the
mount:

Trying to join cluster "lock_dlm", "pilot:test"
Joined cluster. Now mounting FS...
GFS: fsid=pilot:test.4294967295: can't mount journal #4294967295
GFS: fsid=pilot:test.4294967295: there are only 6 journals (0 - 5)

A stab in the dark:

# gfs_tool jindex /dev/mapper/gfs-test 
gfs_tool: /dev/mapper/gfs-test is not a GFS file/filesystem

Scary.  What may be the problem?  The other node is using this
volume...  Can even unmount/remount it.  Though in dmesg it says:

GFS: fsid=pilot:test.0: jid=0: Trying to acquire journal lock...
GFS: fsid=pilot:test.0: jid=0: Looking at journal...
GFS: fsid=pilot:test.0: jid=0: Done
GFS: fsid=pilot:test.0: jid=1: Trying to acquire journal lock...
GFS: fsid=pilot:test.0: jid=1: Looking at journal...
GFS: fsid=pilot:test.0: jid=1: Done
GFS: fsid=pilot:test.0: jid=2: Trying to acquire journal lock...
GFS: fsid=pilot:test.0: jid=2: Looking at journal...
GFS: fsid=pilot:test.0: jid=2: Done
GFS: fsid=pilot:test.0: jid=3: Trying to acquire journal lock...
GFS: fsid=pilot:test.0: jid=3: Looking at journal...
GFS: fsid=pilot:test.0: jid=3: Done
GFS: fsid=pilot:test.0: jid=4: Trying to acquire journal lock...
GFS: fsid=pilot:test.0: jid=4: Looking at journal...
GFS: fsid=pilot:test.0: jid=4: Done
GFS: fsid=pilot:test.0: jid=5: Trying to acquire journal lock...
GFS: fsid=pilot:test.0: jid=5: Looking at journal...
GFS: fsid=pilot:test.0: jid=5: Done

Maybe it's locking all journals?  Why?
-- 
Thanks,
Feri.



From fs at debian.org  Tue Feb 12 14:09:59 2008
From: fs at debian.org (Frederik Schueler)
Date: Tue, 12 Feb 2008 15:09:59 +0100
Subject: [Linux-cluster] nfsd looping with 100% CPU
Message-ID: <20080212140948.GE9620@mail.lowpingbastards.de>

Hello,

I am experiencing some serious trouble with an NFS Server running 
2.6.24: after a couple of minutes, one kernel nfsd process loops with 
100% CPU, and the load raises continuously. After some more minutes, 
there are two, then tree nfsds looping, and the load continues to 
slowly raise. 

top - 18:10:28 up 45 min,  1 user,  load average: 7.11, 6.27, 3.69
Tasks:  79 total,   5 running,  74 sleeping,   0 stopped,   0 zombie
Cpu(s):  0.0%us, 50.0%sy,  0.0%ni, 49.8%id,  0.2%wa,  0.0%hi,  0.0%si,
0.0%st
Mem:   2074496k total,   151112k used,  1923384k free,     7848k buffers
Swap:  1951856k total,        0k used,  1951856k free,    73748k cached

  PID USER      PR  NI  VIRT  RES  SHR S %CPU %MEM    TIME+  COMMAND                                                                                         
 5589 root      24   4     0    0    0 R  100  0.0  11:11.88 nfsd                                                                                             
    1 root      20   0  1940  644  548 S    0  0.0   0:01.44 init                                                                                             
    2 root      15  -5     0    0    0 S    0  0.0   0:00.00 kthreadd                                                                                         
    3 root      RT  -5     0    0    0 S    0  0.0   0:00.02 migration/0                                                                                      
    4 root      15  -5     0    0    0 S    0  0.0   0:00.02 ksoftirqd/0                                                                                      
    5 root      RT  -5     0    0    0 S    0  0.0   0:00.00 watchdog/0                                                                                       
    6 root      RT  -5     0    0    0 S    0  0.0   0:00.02 migration/1                                                                                      
    7 root      15  -5     0    0    0 S    0  0.0   0:00.00 ksoftirqd/1                                                                                      

This is a 32bit P4 box exporting two 1TB GFS shares to ~80 clients, and
3-4 of those clients use to write continuously with ~300-1500Kbit/s onto 
one  of the shares. With 2.6.24, I get max ~250Kbit/s and the clients
writing have increasing load values.

This is a 2 nodes GFS cluster, the second node is a fallback running the 
old version from which I am trying to upgrade.

I have attached the kernel config and the sysrq-t log, if that may be of
any help.


Best regards
Frederik Sch?ler

-- 
ENOSIG

#
# Automatically generated make config: don't edit
# Linux kernel version: 2.6.24
# Thu Feb  7 16:59:30 2008
#
# CONFIG_64BIT is not set
CONFIG_X86_32=y
# CONFIG_X86_64 is not set
CONFIG_X86=y
CONFIG_GENERIC_TIME=y
CONFIG_GENERIC_CMOS_UPDATE=y
CONFIG_CLOCKSOURCE_WATCHDOG=y
CONFIG_GENERIC_CLOCKEVENTS=y
CONFIG_GENERIC_CLOCKEVENTS_BROADCAST=y
CONFIG_LOCKDEP_SUPPORT=y
CONFIG_STACKTRACE_SUPPORT=y
CONFIG_SEMAPHORE_SLEEPERS=y
CONFIG_MMU=y
CONFIG_ZONE_DMA=y
CONFIG_QUICKLIST=y
CONFIG_GENERIC_ISA_DMA=y
CONFIG_GENERIC_IOMAP=y
CONFIG_GENERIC_BUG=y
CONFIG_GENERIC_HWEIGHT=y
CONFIG_ARCH_MAY_HAVE_PC_FDC=y
CONFIG_DMI=y
# CONFIG_RWSEM_GENERIC_SPINLOCK is not set
CONFIG_RWSEM_XCHGADD_ALGORITHM=y
# CONFIG_ARCH_HAS_ILOG2_U32 is not set
# CONFIG_ARCH_HAS_ILOG2_U64 is not set
CONFIG_GENERIC_CALIBRATE_DELAY=y
# CONFIG_GENERIC_TIME_VSYSCALL is not set
CONFIG_ARCH_SUPPORTS_OPROFILE=y
# CONFIG_ZONE_DMA32 is not set
CONFIG_ARCH_POPULATES_NODE_MAP=y
# CONFIG_AUDIT_ARCH is not set
CONFIG_GENERIC_HARDIRQS=y
CONFIG_GENERIC_IRQ_PROBE=y
CONFIG_GENERIC_PENDING_IRQ=y
CONFIG_X86_SMP=y
CONFIG_X86_HT=y
CONFIG_X86_BIOS_REBOOT=y
CONFIG_X86_TRAMPOLINE=y
CONFIG_KTIME_SCALAR=y
CONFIG_DEFCONFIG_LIST="/lib/modules/$UNAME_RELEASE/.config"

#
# General setup
#
CONFIG_EXPERIMENTAL=y
CONFIG_LOCK_KERNEL=y
CONFIG_INIT_ENV_ARG_LIMIT=32
CONFIG_LOCALVERSION=""
# CONFIG_LOCALVERSION_AUTO is not set
CONFIG_SWAP=y
CONFIG_SYSVIPC=y
CONFIG_SYSVIPC_SYSCTL=y
CONFIG_POSIX_MQUEUE=y
CONFIG_BSD_PROCESS_ACCT=y
CONFIG_BSD_PROCESS_ACCT_V3=y
CONFIG_TASKSTATS=y
CONFIG_TASK_DELAY_ACCT=y
CONFIG_TASK_XACCT=y
CONFIG_TASK_IO_ACCOUNTING=y
# CONFIG_USER_NS is not set
# CONFIG_PID_NS is not set
CONFIG_AUDIT=y
CONFIG_AUDITSYSCALL=y
CONFIG_AUDIT_TREE=y
# CONFIG_IKCONFIG is not set
CONFIG_LOG_BUF_SHIFT=20
CONFIG_CGROUPS=y
# CONFIG_CGROUP_DEBUG is not set
CONFIG_CGROUP_NS=y
CONFIG_CPUSETS=y
CONFIG_FAIR_GROUP_SCHED=y
CONFIG_FAIR_USER_SCHED=y
# CONFIG_FAIR_CGROUP_SCHED is not set
CONFIG_CGROUP_CPUACCT=y
CONFIG_SYSFS_DEPRECATED=y
CONFIG_PROC_PID_CPUSET=y
CONFIG_RELAY=y
CONFIG_BLK_DEV_INITRD=y
CONFIG_INITRAMFS_SOURCE=""
CONFIG_CC_OPTIMIZE_FOR_SIZE=y
CONFIG_SYSCTL=y
# CONFIG_EMBEDDED is not set
CONFIG_UID16=y
CONFIG_SYSCTL_SYSCALL=y
CONFIG_KALLSYMS=y
# CONFIG_KALLSYMS_ALL is not set
# CONFIG_KALLSYMS_EXTRA_PASS is not set
CONFIG_HOTPLUG=y
CONFIG_PRINTK=y
CONFIG_BUG=y
CONFIG_ELF_CORE=y
CONFIG_BASE_FULL=y
CONFIG_FUTEX=y
CONFIG_ANON_INODES=y
CONFIG_EPOLL=y
CONFIG_SIGNALFD=y
CONFIG_EVENTFD=y
CONFIG_SHMEM=y
CONFIG_VM_EVENT_COUNTERS=y
CONFIG_SLAB=y
# CONFIG_SLUB is not set
# CONFIG_SLOB is not set
CONFIG_SLABINFO=y
CONFIG_RT_MUTEXES=y
# CONFIG_TINY_SHMEM is not set
CONFIG_BASE_SMALL=0
CONFIG_MODULES=y
CONFIG_MODULE_UNLOAD=y
CONFIG_MODULE_FORCE_UNLOAD=y
CONFIG_MODVERSIONS=y
# CONFIG_MODULE_SRCVERSION_ALL is not set
CONFIG_KMOD=y
CONFIG_STOP_MACHINE=y
CONFIG_BLOCK=y
CONFIG_LBD=y
CONFIG_BLK_DEV_IO_TRACE=y
CONFIG_LSF=y
# CONFIG_BLK_DEV_BSG is not set

#
# IO Schedulers
#
CONFIG_IOSCHED_NOOP=y
CONFIG_IOSCHED_AS=y
CONFIG_IOSCHED_DEADLINE=y
CONFIG_IOSCHED_CFQ=y
# CONFIG_DEFAULT_AS is not set
# CONFIG_DEFAULT_DEADLINE is not set
CONFIG_DEFAULT_CFQ=y
# CONFIG_DEFAULT_NOOP is not set
CONFIG_DEFAULT_IOSCHED="cfq"
CONFIG_PREEMPT_NOTIFIERS=y

#
# Processor type and features
#
CONFIG_TICK_ONESHOT=y
# CONFIG_NO_HZ is not set
CONFIG_HIGH_RES_TIMERS=y
CONFIG_GENERIC_CLOCKEVENTS_BUILD=y
CONFIG_SMP=y
CONFIG_X86_PC=y
# CONFIG_X86_ELAN is not set
# CONFIG_X86_VOYAGER is not set
# CONFIG_X86_NUMAQ is not set
# CONFIG_X86_SUMMIT is not set
# CONFIG_X86_BIGSMP is not set
# CONFIG_X86_VISWS is not set
# CONFIG_X86_GENERICARCH is not set
# CONFIG_X86_ES7000 is not set
# CONFIG_X86_VSMP is not set
CONFIG_SCHED_NO_NO_OMIT_FRAME_POINTER=y
CONFIG_PARAVIRT=y
CONFIG_PARAVIRT_GUEST=y
# CONFIG_XEN is not set
CONFIG_VMI=y
CONFIG_LGUEST_GUEST=y
# CONFIG_M386 is not set
# CONFIG_M486 is not set
# CONFIG_M586 is not set
# CONFIG_M586TSC is not set
# CONFIG_M586MMX is not set
CONFIG_M686=y
# CONFIG_MPENTIUMII is not set
# CONFIG_MPENTIUMIII is not set
# CONFIG_MPENTIUMM is not set
# CONFIG_MPENTIUM4 is not set
# CONFIG_MK6 is not set
# CONFIG_MK7 is not set
# CONFIG_MK8 is not set
# CONFIG_MCRUSOE is not set
# CONFIG_MEFFICEON is not set
# CONFIG_MWINCHIPC6 is not set
# CONFIG_MWINCHIP2 is not set
# CONFIG_MWINCHIP3D is not set
# CONFIG_MGEODEGX1 is not set
# CONFIG_MGEODE_LX is not set
# CONFIG_MCYRIXIII is not set
# CONFIG_MVIAC3_2 is not set
# CONFIG_MVIAC7 is not set
# CONFIG_MPSC is not set
# CONFIG_MCORE2 is not set
# CONFIG_GENERIC_CPU is not set
# CONFIG_X86_GENERIC is not set
CONFIG_X86_CMPXCHG=y
CONFIG_X86_L1_CACHE_SHIFT=5
CONFIG_X86_XADD=y
CONFIG_X86_PPRO_FENCE=y
CONFIG_X86_WP_WORKS_OK=y
CONFIG_X86_INVLPG=y
CONFIG_X86_BSWAP=y
CONFIG_X86_POPAD_OK=y
CONFIG_X86_GOOD_APIC=y
CONFIG_X86_USE_PPRO_CHECKSUM=y
CONFIG_X86_TSC=y
CONFIG_X86_CMOV=y
CONFIG_X86_MINIMUM_CPU_FAMILY=4
CONFIG_HPET_TIMER=y
CONFIG_NR_CPUS=8
CONFIG_SCHED_SMT=y
CONFIG_SCHED_MC=y
CONFIG_PREEMPT_NONE=y
# CONFIG_PREEMPT_VOLUNTARY is not set
# CONFIG_PREEMPT is not set
# CONFIG_PREEMPT_BKL is not set
CONFIG_X86_LOCAL_APIC=y
CONFIG_X86_IO_APIC=y
CONFIG_X86_MCE=y
CONFIG_X86_MCE_NONFATAL=m
CONFIG_X86_MCE_P4THERMAL=y
CONFIG_VM86=y
CONFIG_TOSHIBA=m
CONFIG_I8K=m
# CONFIG_X86_REBOOTFIXUPS is not set
CONFIG_MICROCODE=m
CONFIG_MICROCODE_OLD_INTERFACE=y
CONFIG_X86_MSR=m
CONFIG_X86_CPUID=m
# CONFIG_NOHIGHMEM is not set
CONFIG_HIGHMEM4G=y
# CONFIG_HIGHMEM64G is not set
CONFIG_PAGE_OFFSET=0xC0000000
CONFIG_HIGHMEM=y
CONFIG_ARCH_FLATMEM_ENABLE=y
CONFIG_ARCH_SPARSEMEM_ENABLE=y
CONFIG_ARCH_SELECT_MEMORY_MODEL=y
CONFIG_SELECT_MEMORY_MODEL=y
CONFIG_FLATMEM_MANUAL=y
# CONFIG_DISCONTIGMEM_MANUAL is not set
# CONFIG_SPARSEMEM_MANUAL is not set
CONFIG_FLATMEM=y
CONFIG_FLAT_NODE_MEM_MAP=y
CONFIG_SPARSEMEM_STATIC=y
# CONFIG_SPARSEMEM_VMEMMAP_ENABLE is not set
CONFIG_SPLIT_PTLOCK_CPUS=4
# CONFIG_RESOURCES_64BIT is not set
CONFIG_ZONE_DMA_FLAG=1
CONFIG_BOUNCE=y
CONFIG_NR_QUICK=1
CONFIG_VIRT_TO_BUS=y
# CONFIG_HIGHPTE is not set
# CONFIG_MATH_EMULATION is not set
CONFIG_MTRR=y
CONFIG_EFI=y
# CONFIG_IRQBALANCE is not set
CONFIG_BOOT_IOREMAP=y
# CONFIG_SECCOMP is not set
# CONFIG_HZ_100 is not set
CONFIG_HZ_250=y
# CONFIG_HZ_300 is not set
# CONFIG_HZ_1000 is not set
CONFIG_HZ=250
CONFIG_KEXEC=y
# CONFIG_CRASH_DUMP is not set
CONFIG_PHYSICAL_START=0x100000
# CONFIG_RELOCATABLE is not set
CONFIG_PHYSICAL_ALIGN=0x100000
CONFIG_HOTPLUG_CPU=y
CONFIG_COMPAT_VDSO=y
CONFIG_ARCH_ENABLE_MEMORY_HOTPLUG=y

#
# Power management options
#
CONFIG_PM=y
CONFIG_PM_LEGACY=y
# CONFIG_PM_DEBUG is not set
CONFIG_PM_SLEEP_SMP=y
CONFIG_PM_SLEEP=y
CONFIG_SUSPEND_SMP_POSSIBLE=y
CONFIG_SUSPEND=y
CONFIG_HIBERNATION_SMP_POSSIBLE=y
CONFIG_HIBERNATION=y
CONFIG_PM_STD_PARTITION=""
CONFIG_ACPI=y
CONFIG_ACPI_SLEEP=y
CONFIG_ACPI_PROCFS=y
# CONFIG_ACPI_PROCFS_POWER is not set
CONFIG_ACPI_SYSFS_POWER=y
CONFIG_ACPI_PROC_EVENT=y
CONFIG_ACPI_AC=m
CONFIG_ACPI_BATTERY=m
CONFIG_ACPI_BUTTON=m
CONFIG_ACPI_VIDEO=m
CONFIG_ACPI_FAN=m
CONFIG_ACPI_DOCK=m
CONFIG_ACPI_BAY=m
CONFIG_ACPI_PROCESSOR=m
CONFIG_ACPI_HOTPLUG_CPU=y
CONFIG_ACPI_THERMAL=m
CONFIG_ACPI_ASUS=m
CONFIG_ACPI_TOSHIBA=m
CONFIG_ACPI_BLACKLIST_YEAR=0
# CONFIG_ACPI_DEBUG is not set
CONFIG_ACPI_EC=y
CONFIG_ACPI_POWER=y
CONFIG_ACPI_SYSTEM=y
CONFIG_X86_PM_TIMER=y
CONFIG_ACPI_CONTAINER=m
CONFIG_ACPI_SBS=m
CONFIG_APM=m
# CONFIG_APM_IGNORE_USER_SUSPEND is not set
# CONFIG_APM_DO_ENABLE is not set
# CONFIG_APM_CPU_IDLE is not set
# CONFIG_APM_DISPLAY_BLANK is not set
# CONFIG_APM_ALLOW_INTS is not set
# CONFIG_APM_REAL_MODE_POWER_OFF is not set

#
# CPU Frequency scaling
#
CONFIG_CPU_FREQ=y
CONFIG_CPU_FREQ_TABLE=m
# CONFIG_CPU_FREQ_DEBUG is not set
CONFIG_CPU_FREQ_STAT=m
# CONFIG_CPU_FREQ_STAT_DETAILS is not set
CONFIG_CPU_FREQ_DEFAULT_GOV_PERFORMANCE=y
# CONFIG_CPU_FREQ_DEFAULT_GOV_USERSPACE is not set
# CONFIG_CPU_FREQ_DEFAULT_GOV_ONDEMAND is not set
# CONFIG_CPU_FREQ_DEFAULT_GOV_CONSERVATIVE is not set
CONFIG_CPU_FREQ_GOV_PERFORMANCE=y
CONFIG_CPU_FREQ_GOV_POWERSAVE=m
CONFIG_CPU_FREQ_GOV_USERSPACE=m
CONFIG_CPU_FREQ_GOV_ONDEMAND=m
CONFIG_CPU_FREQ_GOV_CONSERVATIVE=m

#
# CPUFreq processor drivers
#
CONFIG_X86_ACPI_CPUFREQ=m
CONFIG_X86_POWERNOW_K6=m
CONFIG_X86_POWERNOW_K7=m
CONFIG_X86_POWERNOW_K7_ACPI=y
CONFIG_X86_POWERNOW_K8=m
CONFIG_X86_POWERNOW_K8_ACPI=y
CONFIG_X86_GX_SUSPMOD=m
CONFIG_X86_SPEEDSTEP_CENTRINO=m
CONFIG_X86_SPEEDSTEP_CENTRINO_TABLE=y
CONFIG_X86_SPEEDSTEP_ICH=m
CONFIG_X86_SPEEDSTEP_SMI=m
CONFIG_X86_P4_CLOCKMOD=m
CONFIG_X86_CPUFREQ_NFORCE2=m
CONFIG_X86_LONGRUN=m
CONFIG_X86_LONGHAUL=m
CONFIG_X86_E_POWERSAVER=m

#
# shared options
#
# CONFIG_X86_ACPI_CPUFREQ_PROC_INTF is not set
CONFIG_X86_SPEEDSTEP_LIB=m
CONFIG_X86_SPEEDSTEP_RELAXED_CAP_CHECK=y
CONFIG_CPU_IDLE=y
CONFIG_CPU_IDLE_GOV_LADDER=y

#
# Bus options (PCI etc.)
#
CONFIG_PCI=y
# CONFIG_PCI_GOBIOS is not set
# CONFIG_PCI_GOMMCONFIG is not set
# CONFIG_PCI_GODIRECT is not set
CONFIG_PCI_GOANY=y
CONFIG_PCI_BIOS=y
CONFIG_PCI_DIRECT=y
CONFIG_PCI_MMCONFIG=y
CONFIG_PCI_DOMAINS=y
CONFIG_PCIEPORTBUS=y
CONFIG_HOTPLUG_PCI_PCIE=m
CONFIG_PCIEAER=y
CONFIG_ARCH_SUPPORTS_MSI=y
CONFIG_PCI_MSI=y
CONFIG_PCI_LEGACY=y
# CONFIG_PCI_DEBUG is not set
CONFIG_HT_IRQ=y
CONFIG_ISA_DMA_API=y
CONFIG_ISA=y
# CONFIG_EISA is not set
# CONFIG_MCA is not set
CONFIG_SCx200=m
CONFIG_SCx200HR_TIMER=m
CONFIG_K8_NB=y
CONFIG_PCCARD=m
# CONFIG_PCMCIA_DEBUG is not set
CONFIG_PCMCIA=m
CONFIG_PCMCIA_LOAD_CIS=y
CONFIG_PCMCIA_IOCTL=y
CONFIG_CARDBUS=y

#
# PC-card bridges
#
CONFIG_YENTA=m
CONFIG_YENTA_O2=y
CONFIG_YENTA_RICOH=y
CONFIG_YENTA_TI=y
CONFIG_YENTA_ENE_TUNE=y
CONFIG_YENTA_TOSHIBA=y
CONFIG_PD6729=m
CONFIG_I82092=m
CONFIG_I82365=m
CONFIG_TCIC=m
CONFIG_PCMCIA_PROBE=y
CONFIG_PCCARD_NONSTATIC=m
CONFIG_HOTPLUG_PCI=m
CONFIG_HOTPLUG_PCI_FAKE=m
CONFIG_HOTPLUG_PCI_COMPAQ=m
# CONFIG_HOTPLUG_PCI_COMPAQ_NVRAM is not set
CONFIG_HOTPLUG_PCI_IBM=m
CONFIG_HOTPLUG_PCI_ACPI=m
CONFIG_HOTPLUG_PCI_ACPI_IBM=m
CONFIG_HOTPLUG_PCI_CPCI=y
CONFIG_HOTPLUG_PCI_CPCI_ZT5550=m
CONFIG_HOTPLUG_PCI_CPCI_GENERIC=m
CONFIG_HOTPLUG_PCI_SHPC=m

#
# Executable file formats / Emulations
#
CONFIG_BINFMT_ELF=y
CONFIG_BINFMT_AOUT=m
CONFIG_BINFMT_MISC=m

#
# Networking
#
CONFIG_NET=y

#
# Networking options
#
CONFIG_PACKET=y
CONFIG_PACKET_MMAP=y
CONFIG_UNIX=y
CONFIG_XFRM=y
CONFIG_XFRM_USER=m
# CONFIG_XFRM_SUB_POLICY is not set
# CONFIG_XFRM_MIGRATE is not set
CONFIG_NET_KEY=m
# CONFIG_NET_KEY_MIGRATE is not set
CONFIG_INET=y
CONFIG_IP_MULTICAST=y
CONFIG_IP_ADVANCED_ROUTER=y
CONFIG_ASK_IP_FIB_HASH=y
# CONFIG_IP_FIB_TRIE is not set
CONFIG_IP_FIB_HASH=y
CONFIG_IP_MULTIPLE_TABLES=y
CONFIG_IP_ROUTE_MULTIPATH=y
CONFIG_IP_ROUTE_VERBOSE=y
# CONFIG_IP_PNP is not set
CONFIG_NET_IPIP=m
CONFIG_NET_IPGRE=m
CONFIG_NET_IPGRE_BROADCAST=y
CONFIG_IP_MROUTE=y
CONFIG_IP_PIMSM_V1=y
CONFIG_IP_PIMSM_V2=y
# CONFIG_ARPD is not set
CONFIG_SYN_COOKIES=y
CONFIG_INET_AH=m
CONFIG_INET_ESP=m
CONFIG_INET_IPCOMP=m
CONFIG_INET_XFRM_TUNNEL=m
CONFIG_INET_TUNNEL=m
CONFIG_INET_XFRM_MODE_TRANSPORT=m
CONFIG_INET_XFRM_MODE_TUNNEL=m
CONFIG_INET_XFRM_MODE_BEET=m
CONFIG_INET_LRO=m
CONFIG_INET_DIAG=m
CONFIG_INET_TCP_DIAG=m
CONFIG_TCP_CONG_ADVANCED=y
CONFIG_TCP_CONG_BIC=y
CONFIG_TCP_CONG_CUBIC=m
CONFIG_TCP_CONG_WESTWOOD=m
CONFIG_TCP_CONG_HTCP=m
CONFIG_TCP_CONG_HSTCP=m
CONFIG_TCP_CONG_HYBLA=m
CONFIG_TCP_CONG_VEGAS=m
CONFIG_TCP_CONG_SCALABLE=m
CONFIG_TCP_CONG_LP=m
CONFIG_TCP_CONG_VENO=m
CONFIG_TCP_CONG_YEAH=m
CONFIG_TCP_CONG_ILLINOIS=m
CONFIG_DEFAULT_BIC=y
# CONFIG_DEFAULT_CUBIC is not set
# CONFIG_DEFAULT_HTCP is not set
# CONFIG_DEFAULT_VEGAS is not set
# CONFIG_DEFAULT_WESTWOOD is not set
# CONFIG_DEFAULT_RENO is not set
CONFIG_DEFAULT_TCP_CONG="bic"
# CONFIG_TCP_MD5SIG is not set
CONFIG_IP_VS=m
# CONFIG_IP_VS_DEBUG is not set
CONFIG_IP_VS_TAB_BITS=12

#
# IPVS transport protocol load balancing support
#
CONFIG_IP_VS_PROTO_TCP=y
CONFIG_IP_VS_PROTO_UDP=y
CONFIG_IP_VS_PROTO_ESP=y
CONFIG_IP_VS_PROTO_AH=y

#
# IPVS scheduler
#
CONFIG_IP_VS_RR=m
CONFIG_IP_VS_WRR=m
CONFIG_IP_VS_LC=m
CONFIG_IP_VS_WLC=m
CONFIG_IP_VS_LBLC=m
CONFIG_IP_VS_LBLCR=m
CONFIG_IP_VS_DH=m
CONFIG_IP_VS_SH=m
CONFIG_IP_VS_SED=m
CONFIG_IP_VS_NQ=m

#
# IPVS application helper
#
CONFIG_IP_VS_FTP=m
CONFIG_IPV6=m
CONFIG_IPV6_PRIVACY=y
# CONFIG_IPV6_ROUTER_PREF is not set
# CONFIG_IPV6_OPTIMISTIC_DAD is not set
CONFIG_INET6_AH=m
CONFIG_INET6_ESP=m
CONFIG_INET6_IPCOMP=m
# CONFIG_IPV6_MIP6 is not set
CONFIG_INET6_XFRM_TUNNEL=m
CONFIG_INET6_TUNNEL=m
CONFIG_INET6_XFRM_MODE_TRANSPORT=m
CONFIG_INET6_XFRM_MODE_TUNNEL=m
CONFIG_INET6_XFRM_MODE_BEET=m
CONFIG_INET6_XFRM_MODE_ROUTEOPTIMIZATION=m
CONFIG_IPV6_SIT=m
CONFIG_IPV6_TUNNEL=m
CONFIG_IPV6_MULTIPLE_TABLES=y
CONFIG_IPV6_SUBTREES=y
# CONFIG_NETLABEL is not set
CONFIG_NETWORK_SECMARK=y
CONFIG_NETFILTER=y
# CONFIG_NETFILTER_DEBUG is not set
CONFIG_BRIDGE_NETFILTER=y

#
# Core Netfilter Configuration
#
CONFIG_NETFILTER_NETLINK=m
CONFIG_NETFILTER_NETLINK_QUEUE=m
CONFIG_NETFILTER_NETLINK_LOG=m
CONFIG_NF_CONNTRACK_ENABLED=m
CONFIG_NF_CONNTRACK=m
CONFIG_NF_CT_ACCT=y
CONFIG_NF_CONNTRACK_MARK=y
CONFIG_NF_CONNTRACK_SECMARK=y
CONFIG_NF_CONNTRACK_EVENTS=y
CONFIG_NF_CT_PROTO_GRE=m
CONFIG_NF_CT_PROTO_SCTP=m
CONFIG_NF_CT_PROTO_UDPLITE=m
CONFIG_NF_CONNTRACK_AMANDA=m
CONFIG_NF_CONNTRACK_FTP=m
CONFIG_NF_CONNTRACK_H323=m
CONFIG_NF_CONNTRACK_IRC=m
CONFIG_NF_CONNTRACK_NETBIOS_NS=m
CONFIG_NF_CONNTRACK_PPTP=m
CONFIG_NF_CONNTRACK_SANE=m
CONFIG_NF_CONNTRACK_SIP=m
CONFIG_NF_CONNTRACK_TFTP=m
CONFIG_NF_CT_NETLINK=m
CONFIG_NETFILTER_XTABLES=m
CONFIG_NETFILTER_XT_TARGET_CLASSIFY=m
CONFIG_NETFILTER_XT_TARGET_CONNMARK=m
CONFIG_NETFILTER_XT_TARGET_DSCP=m
CONFIG_NETFILTER_XT_TARGET_MARK=m
CONFIG_NETFILTER_XT_TARGET_NFQUEUE=m
CONFIG_NETFILTER_XT_TARGET_NFLOG=m
CONFIG_NETFILTER_XT_TARGET_NOTRACK=m
CONFIG_NETFILTER_XT_TARGET_TRACE=m
CONFIG_NETFILTER_XT_TARGET_SECMARK=m
CONFIG_NETFILTER_XT_TARGET_CONNSECMARK=m
CONFIG_NETFILTER_XT_TARGET_TCPMSS=m
CONFIG_NETFILTER_XT_MATCH_COMMENT=m
CONFIG_NETFILTER_XT_MATCH_CONNBYTES=m
CONFIG_NETFILTER_XT_MATCH_CONNLIMIT=m
CONFIG_NETFILTER_XT_MATCH_CONNMARK=m
CONFIG_NETFILTER_XT_MATCH_CONNTRACK=m
CONFIG_NETFILTER_XT_MATCH_DCCP=m
CONFIG_NETFILTER_XT_MATCH_DSCP=m
CONFIG_NETFILTER_XT_MATCH_ESP=m
CONFIG_NETFILTER_XT_MATCH_HELPER=m
CONFIG_NETFILTER_XT_MATCH_LENGTH=m
CONFIG_NETFILTER_XT_MATCH_LIMIT=m
CONFIG_NETFILTER_XT_MATCH_MAC=m
CONFIG_NETFILTER_XT_MATCH_MARK=m
CONFIG_NETFILTER_XT_MATCH_POLICY=m
CONFIG_NETFILTER_XT_MATCH_MULTIPORT=m
CONFIG_NETFILTER_XT_MATCH_PHYSDEV=m
CONFIG_NETFILTER_XT_MATCH_PKTTYPE=m
CONFIG_NETFILTER_XT_MATCH_QUOTA=m
CONFIG_NETFILTER_XT_MATCH_REALM=m
CONFIG_NETFILTER_XT_MATCH_SCTP=m
CONFIG_NETFILTER_XT_MATCH_STATE=m
CONFIG_NETFILTER_XT_MATCH_STATISTIC=m
CONFIG_NETFILTER_XT_MATCH_STRING=m
CONFIG_NETFILTER_XT_MATCH_TCPMSS=m
CONFIG_NETFILTER_XT_MATCH_TIME=m
CONFIG_NETFILTER_XT_MATCH_U32=m
CONFIG_NETFILTER_XT_MATCH_HASHLIMIT=m

#
# IP: Netfilter Configuration
#
CONFIG_NF_CONNTRACK_IPV4=m
CONFIG_NF_CONNTRACK_PROC_COMPAT=y
CONFIG_IP_NF_QUEUE=m
CONFIG_IP_NF_IPTABLES=m
CONFIG_IP_NF_MATCH_IPRANGE=m
CONFIG_IP_NF_MATCH_TOS=m
CONFIG_IP_NF_MATCH_RECENT=m
CONFIG_IP_NF_MATCH_ECN=m
CONFIG_IP_NF_MATCH_AH=m
CONFIG_IP_NF_MATCH_TTL=m
CONFIG_IP_NF_MATCH_OWNER=m
CONFIG_IP_NF_MATCH_ADDRTYPE=m
CONFIG_IP_NF_FILTER=m
CONFIG_IP_NF_TARGET_REJECT=m
CONFIG_IP_NF_TARGET_LOG=m
CONFIG_IP_NF_TARGET_ULOG=m
CONFIG_NF_NAT=m
CONFIG_NF_NAT_NEEDED=y
CONFIG_IP_NF_TARGET_MASQUERADE=m
CONFIG_IP_NF_TARGET_REDIRECT=m
CONFIG_IP_NF_TARGET_NETMAP=m
CONFIG_IP_NF_TARGET_SAME=m
CONFIG_NF_NAT_SNMP_BASIC=m
CONFIG_NF_NAT_PROTO_GRE=m
CONFIG_NF_NAT_FTP=m
CONFIG_NF_NAT_IRC=m
CONFIG_NF_NAT_TFTP=m
CONFIG_NF_NAT_AMANDA=m
CONFIG_NF_NAT_PPTP=m
CONFIG_NF_NAT_H323=m
CONFIG_NF_NAT_SIP=m
CONFIG_IP_NF_MANGLE=m
CONFIG_IP_NF_TARGET_TOS=m
CONFIG_IP_NF_TARGET_ECN=m
CONFIG_IP_NF_TARGET_TTL=m
CONFIG_IP_NF_TARGET_CLUSTERIP=m
CONFIG_IP_NF_RAW=m
CONFIG_IP_NF_ARPTABLES=m
CONFIG_IP_NF_ARPFILTER=m
CONFIG_IP_NF_ARP_MANGLE=m

#
# IPv6: Netfilter Configuration (EXPERIMENTAL)
#
CONFIG_NF_CONNTRACK_IPV6=m
CONFIG_IP6_NF_QUEUE=m
CONFIG_IP6_NF_IPTABLES=m
CONFIG_IP6_NF_MATCH_RT=m
CONFIG_IP6_NF_MATCH_OPTS=m
CONFIG_IP6_NF_MATCH_FRAG=m
CONFIG_IP6_NF_MATCH_HL=m
CONFIG_IP6_NF_MATCH_OWNER=m
CONFIG_IP6_NF_MATCH_IPV6HEADER=m
CONFIG_IP6_NF_MATCH_AH=m
CONFIG_IP6_NF_MATCH_MH=m
CONFIG_IP6_NF_MATCH_EUI64=m
CONFIG_IP6_NF_FILTER=m
CONFIG_IP6_NF_TARGET_LOG=m
CONFIG_IP6_NF_TARGET_REJECT=m
CONFIG_IP6_NF_MANGLE=m
CONFIG_IP6_NF_TARGET_HL=m
CONFIG_IP6_NF_RAW=m

#
# DECnet: Netfilter Configuration
#
CONFIG_DECNET_NF_GRABULATOR=m

#
# Bridge: Netfilter Configuration
#
CONFIG_BRIDGE_NF_EBTABLES=m
CONFIG_BRIDGE_EBT_BROUTE=m
CONFIG_BRIDGE_EBT_T_FILTER=m
CONFIG_BRIDGE_EBT_T_NAT=m
CONFIG_BRIDGE_EBT_802_3=m
CONFIG_BRIDGE_EBT_AMONG=m
CONFIG_BRIDGE_EBT_ARP=m
CONFIG_BRIDGE_EBT_IP=m
CONFIG_BRIDGE_EBT_LIMIT=m
CONFIG_BRIDGE_EBT_MARK=m
CONFIG_BRIDGE_EBT_PKTTYPE=m
CONFIG_BRIDGE_EBT_STP=m
CONFIG_BRIDGE_EBT_VLAN=m
CONFIG_BRIDGE_EBT_ARPREPLY=m
CONFIG_BRIDGE_EBT_DNAT=m
CONFIG_BRIDGE_EBT_MARK_T=m
CONFIG_BRIDGE_EBT_REDIRECT=m
CONFIG_BRIDGE_EBT_SNAT=m
CONFIG_BRIDGE_EBT_LOG=m
CONFIG_BRIDGE_EBT_ULOG=m
CONFIG_IP_DCCP=m
CONFIG_INET_DCCP_DIAG=m
CONFIG_IP_DCCP_ACKVEC=y

#
# DCCP CCIDs Configuration (EXPERIMENTAL)
#
CONFIG_IP_DCCP_CCID2=m
# CONFIG_IP_DCCP_CCID2_DEBUG is not set
CONFIG_IP_DCCP_CCID3=m
CONFIG_IP_DCCP_TFRC_LIB=m
# CONFIG_IP_DCCP_CCID3_DEBUG is not set
CONFIG_IP_DCCP_CCID3_RTO=100

#
# DCCP Kernel Hacking
#
# CONFIG_IP_DCCP_DEBUG is not set
CONFIG_IP_SCTP=m
# CONFIG_SCTP_DBG_MSG is not set
# CONFIG_SCTP_DBG_OBJCNT is not set
# CONFIG_SCTP_HMAC_NONE is not set
# CONFIG_SCTP_HMAC_SHA1 is not set
CONFIG_SCTP_HMAC_MD5=y
CONFIG_TIPC=m
CONFIG_TIPC_ADVANCED=y
CONFIG_TIPC_ZONES=3
CONFIG_TIPC_CLUSTERS=1
CONFIG_TIPC_NODES=255
CONFIG_TIPC_SLAVE_NODES=0
CONFIG_TIPC_PORTS=8191
CONFIG_TIPC_LOG=0
# CONFIG_TIPC_DEBUG is not set
CONFIG_ATM=y
CONFIG_ATM_CLIP=y
# CONFIG_ATM_CLIP_NO_ICMP is not set
CONFIG_ATM_LANE=m
CONFIG_ATM_MPOA=m
CONFIG_ATM_BR2684=m
# CONFIG_ATM_BR2684_IPFILTER is not set
CONFIG_BRIDGE=m
CONFIG_VLAN_8021Q=m
CONFIG_DECNET=m
# CONFIG_DECNET_ROUTER is not set
CONFIG_LLC=y
CONFIG_LLC2=m
CONFIG_IPX=m
# CONFIG_IPX_INTERN is not set
CONFIG_ATALK=m
CONFIG_DEV_APPLETALK=m
CONFIG_LTPC=m
CONFIG_IPDDP=m
CONFIG_IPDDP_ENCAP=y
CONFIG_IPDDP_DECAP=y
CONFIG_X25=m
CONFIG_LAPB=m
CONFIG_ECONET=m
CONFIG_ECONET_AUNUDP=y
CONFIG_ECONET_NATIVE=y
CONFIG_WAN_ROUTER=m
CONFIG_NET_SCHED=y

#
# Queueing/Scheduling
#
CONFIG_NET_SCH_CBQ=m
CONFIG_NET_SCH_HTB=m
CONFIG_NET_SCH_HFSC=m
CONFIG_NET_SCH_ATM=m
CONFIG_NET_SCH_PRIO=m
CONFIG_NET_SCH_RR=m
CONFIG_NET_SCH_RED=m
CONFIG_NET_SCH_SFQ=m
CONFIG_NET_SCH_TEQL=m
CONFIG_NET_SCH_TBF=m
CONFIG_NET_SCH_GRED=m
CONFIG_NET_SCH_DSMARK=m
CONFIG_NET_SCH_NETEM=m
CONFIG_NET_SCH_INGRESS=m

#
# Classification
#
CONFIG_NET_CLS=y
CONFIG_NET_CLS_BASIC=m
CONFIG_NET_CLS_TCINDEX=m
CONFIG_NET_CLS_ROUTE4=m
CONFIG_NET_CLS_ROUTE=y
CONFIG_NET_CLS_FW=m
CONFIG_NET_CLS_U32=m
CONFIG_CLS_U32_PERF=y
CONFIG_CLS_U32_MARK=y
CONFIG_NET_CLS_RSVP=m
CONFIG_NET_CLS_RSVP6=m
CONFIG_NET_EMATCH=y
CONFIG_NET_EMATCH_STACK=32
CONFIG_NET_EMATCH_CMP=m
CONFIG_NET_EMATCH_NBYTE=m
CONFIG_NET_EMATCH_U32=m
CONFIG_NET_EMATCH_META=m
CONFIG_NET_EMATCH_TEXT=m
CONFIG_NET_CLS_ACT=y
CONFIG_NET_ACT_POLICE=m
CONFIG_NET_ACT_GACT=m
CONFIG_GACT_PROB=y
CONFIG_NET_ACT_MIRRED=m
CONFIG_NET_ACT_IPT=m
CONFIG_NET_ACT_NAT=m
CONFIG_NET_ACT_PEDIT=m
CONFIG_NET_ACT_SIMP=m
# CONFIG_NET_CLS_POLICE is not set
CONFIG_NET_CLS_IND=y
CONFIG_NET_SCH_FIFO=y

#
# Network testing
#
CONFIG_NET_PKTGEN=m
CONFIG_HAMRADIO=y

#
# Packet Radio protocols
#
CONFIG_AX25=m
# CONFIG_AX25_DAMA_SLAVE is not set
CONFIG_NETROM=m
CONFIG_ROSE=m

#
# AX.25 network device drivers
#
CONFIG_MKISS=m
CONFIG_6PACK=m
CONFIG_BPQETHER=m
CONFIG_SCC=m
# CONFIG_SCC_DELAY is not set
# CONFIG_SCC_TRXECHO is not set
CONFIG_BAYCOM_SER_FDX=m
CONFIG_BAYCOM_SER_HDX=m
CONFIG_BAYCOM_PAR=m
CONFIG_BAYCOM_EPP=m
CONFIG_IRDA=m

#
# IrDA protocols
#
CONFIG_IRLAN=m
CONFIG_IRNET=m
CONFIG_IRCOMM=m
# CONFIG_IRDA_ULTRA is not set

#
# IrDA options
#
CONFIG_IRDA_CACHE_LAST_LSAP=y
CONFIG_IRDA_FAST_RR=y
CONFIG_IRDA_DEBUG=y

#
# Infrared-port device drivers
#

#
# SIR device drivers
#
CONFIG_IRTTY_SIR=m

#
# Dongle support
#
CONFIG_DONGLE=y
CONFIG_ESI_DONGLE=m
CONFIG_ACTISYS_DONGLE=m
CONFIG_TEKRAM_DONGLE=m
CONFIG_TOIM3232_DONGLE=m
CONFIG_LITELINK_DONGLE=m
CONFIG_MA600_DONGLE=m
CONFIG_GIRBIL_DONGLE=m
CONFIG_MCP2120_DONGLE=m
CONFIG_OLD_BELKIN_DONGLE=m
CONFIG_ACT200L_DONGLE=m
CONFIG_KINGSUN_DONGLE=m
CONFIG_KSDAZZLE_DONGLE=m
CONFIG_KS959_DONGLE=m

#
# Old SIR device drivers
#

#
# Old Serial dongle support
#

#
# FIR device drivers
#
CONFIG_USB_IRDA=m
CONFIG_SIGMATEL_FIR=m
CONFIG_NSC_FIR=m
CONFIG_WINBOND_FIR=m
CONFIG_TOSHIBA_FIR=m
CONFIG_SMC_IRCC_FIR=m
CONFIG_ALI_FIR=m
CONFIG_VLSI_FIR=m
CONFIG_VIA_FIR=m
CONFIG_MCS_FIR=m
CONFIG_BT=m
CONFIG_BT_L2CAP=m
CONFIG_BT_SCO=m
CONFIG_BT_RFCOMM=m
CONFIG_BT_RFCOMM_TTY=y
CONFIG_BT_BNEP=m
CONFIG_BT_BNEP_MC_FILTER=y
CONFIG_BT_BNEP_PROTO_FILTER=y
CONFIG_BT_CMTP=m
CONFIG_BT_HIDP=m

#
# Bluetooth device drivers
#
CONFIG_BT_HCIUSB=m
CONFIG_BT_HCIUSB_SCO=y
CONFIG_BT_HCIBTSDIO=m
CONFIG_BT_HCIUART=m
CONFIG_BT_HCIUART_H4=y
CONFIG_BT_HCIUART_BCSP=y
CONFIG_BT_HCIUART_LL=y
CONFIG_BT_HCIBCM203X=m
CONFIG_BT_HCIBPA10X=m
CONFIG_BT_HCIBFUSB=m
CONFIG_BT_HCIDTL1=m
CONFIG_BT_HCIBT3C=m
CONFIG_BT_HCIBLUECARD=m
CONFIG_BT_HCIBTUART=m
CONFIG_BT_HCIVHCI=m
CONFIG_AF_RXRPC=m
# CONFIG_AF_RXRPC_DEBUG is not set
CONFIG_RXKAD=m
CONFIG_FIB_RULES=y

#
# Wireless
#
CONFIG_CFG80211=m
CONFIG_NL80211=y
CONFIG_WIRELESS_EXT=y
CONFIG_MAC80211=m
CONFIG_MAC80211_RCSIMPLE=y
CONFIG_MAC80211_LEDS=y
# CONFIG_MAC80211_DEBUGFS is not set
# CONFIG_MAC80211_DEBUG is not set
CONFIG_IEEE80211=m
# CONFIG_IEEE80211_DEBUG is not set
CONFIG_IEEE80211_CRYPT_WEP=m
CONFIG_IEEE80211_CRYPT_CCMP=m
CONFIG_IEEE80211_CRYPT_TKIP=m
CONFIG_IEEE80211_SOFTMAC=m
# CONFIG_IEEE80211_SOFTMAC_DEBUG is not set
CONFIG_RFKILL=m
CONFIG_RFKILL_INPUT=m
CONFIG_RFKILL_LEDS=y
CONFIG_NET_9P=m
CONFIG_NET_9P_FD=m
CONFIG_NET_9P_VIRTIO=m
# CONFIG_NET_9P_DEBUG is not set

#
# Device Drivers
#

#
# Generic Driver Options
#
CONFIG_UEVENT_HELPER_PATH="/sbin/hotplug"
CONFIG_STANDALONE=y
CONFIG_PREVENT_FIRMWARE_BUILD=y
CONFIG_FW_LOADER=m
# CONFIG_DEBUG_DRIVER is not set
# CONFIG_DEBUG_DEVRES is not set
# CONFIG_SYS_HYPERVISOR is not set
CONFIG_CONNECTOR=m
CONFIG_MTD=m
# CONFIG_MTD_DEBUG is not set
CONFIG_MTD_CONCAT=m
CONFIG_MTD_PARTITIONS=y
CONFIG_MTD_REDBOOT_PARTS=m
CONFIG_MTD_REDBOOT_DIRECTORY_BLOCK=-1
# CONFIG_MTD_REDBOOT_PARTS_UNALLOCATED is not set
# CONFIG_MTD_REDBOOT_PARTS_READONLY is not set

#
# User Modules And Translation Layers
#
CONFIG_MTD_CHAR=m
CONFIG_MTD_BLKDEVS=m
CONFIG_MTD_BLOCK=m
CONFIG_MTD_BLOCK_RO=m
CONFIG_FTL=m
CONFIG_NFTL=m
CONFIG_NFTL_RW=y
CONFIG_INFTL=m
CONFIG_RFD_FTL=m
CONFIG_SSFDC=m
CONFIG_MTD_OOPS=m

#
# RAM/ROM/Flash chip drivers
#
CONFIG_MTD_CFI=m
CONFIG_MTD_JEDECPROBE=m
CONFIG_MTD_GEN_PROBE=m
# CONFIG_MTD_CFI_ADV_OPTIONS is not set
CONFIG_MTD_MAP_BANK_WIDTH_1=y
CONFIG_MTD_MAP_BANK_WIDTH_2=y
CONFIG_MTD_MAP_BANK_WIDTH_4=y
# CONFIG_MTD_MAP_BANK_WIDTH_8 is not set
# CONFIG_MTD_MAP_BANK_WIDTH_16 is not set
# CONFIG_MTD_MAP_BANK_WIDTH_32 is not set
CONFIG_MTD_CFI_I1=y
CONFIG_MTD_CFI_I2=y
# CONFIG_MTD_CFI_I4 is not set
# CONFIG_MTD_CFI_I8 is not set
CONFIG_MTD_CFI_INTELEXT=m
CONFIG_MTD_CFI_AMDSTD=m
CONFIG_MTD_CFI_STAA=m
CONFIG_MTD_CFI_UTIL=m
CONFIG_MTD_RAM=m
CONFIG_MTD_ROM=m
CONFIG_MTD_ABSENT=m

#
# Mapping drivers for chip access
#
CONFIG_MTD_COMPLEX_MAPPINGS=y
CONFIG_MTD_PHYSMAP=m
CONFIG_MTD_PHYSMAP_START=0x8000000
CONFIG_MTD_PHYSMAP_LEN=0x4000000
CONFIG_MTD_PHYSMAP_BANKWIDTH=2
CONFIG_MTD_PNC2000=m
CONFIG_MTD_SC520CDP=m
CONFIG_MTD_NETSC520=m
CONFIG_MTD_TS5500=m
CONFIG_MTD_SBC_GXX=m
CONFIG_MTD_SCx200_DOCFLASH=m
# CONFIG_MTD_AMD76XROM is not set
# CONFIG_MTD_ICHXROM is not set
# CONFIG_MTD_ESB2ROM is not set
# CONFIG_MTD_CK804XROM is not set
# CONFIG_MTD_SCB2_FLASH is not set
CONFIG_MTD_NETtel=m
CONFIG_MTD_DILNETPC=m
CONFIG_MTD_DILNETPC_BOOTSIZE=0x80000
# CONFIG_MTD_L440GX is not set
CONFIG_MTD_PCI=m
CONFIG_MTD_INTEL_VR_NOR=m
CONFIG_MTD_PLATRAM=m

#
# Self-contained MTD device drivers
#
CONFIG_MTD_PMC551=m
# CONFIG_MTD_PMC551_BUGFIX is not set
# CONFIG_MTD_PMC551_DEBUG is not set
CONFIG_MTD_DATAFLASH=m
CONFIG_MTD_M25P80=m
CONFIG_MTD_SLRAM=m
CONFIG_MTD_PHRAM=m
CONFIG_MTD_MTDRAM=m
CONFIG_MTDRAM_TOTAL_SIZE=4096
CONFIG_MTDRAM_ERASE_SIZE=128
CONFIG_MTD_BLOCK2MTD=m

#
# Disk-On-Chip Device Drivers
#
CONFIG_MTD_DOC2000=m
CONFIG_MTD_DOC2001=m
CONFIG_MTD_DOC2001PLUS=m
CONFIG_MTD_DOCPROBE=m
CONFIG_MTD_DOCECC=m
# CONFIG_MTD_DOCPROBE_ADVANCED is not set
CONFIG_MTD_DOCPROBE_ADDRESS=0
CONFIG_MTD_NAND=m
# CONFIG_MTD_NAND_VERIFY_WRITE is not set
# CONFIG_MTD_NAND_ECC_SMC is not set
# CONFIG_MTD_NAND_MUSEUM_IDS is not set
CONFIG_MTD_NAND_IDS=m
CONFIG_MTD_NAND_DISKONCHIP=m
# CONFIG_MTD_NAND_DISKONCHIP_PROBE_ADVANCED is not set
CONFIG_MTD_NAND_DISKONCHIP_PROBE_ADDRESS=0
# CONFIG_MTD_NAND_DISKONCHIP_BBTWRITE is not set
CONFIG_MTD_NAND_CAFE=m
CONFIG_MTD_NAND_CS553X=m
# CONFIG_MTD_NAND_NANDSIM is not set
CONFIG_MTD_NAND_PLATFORM=m
CONFIG_MTD_ALAUDA=m
CONFIG_MTD_ONENAND=m
CONFIG_MTD_ONENAND_VERIFY_WRITE=y
# CONFIG_MTD_ONENAND_OTP is not set
CONFIG_MTD_ONENAND_2X_PROGRAM=y
CONFIG_MTD_ONENAND_SIM=m

#
# UBI - Unsorted block images
#
CONFIG_MTD_UBI=m
CONFIG_MTD_UBI_WL_THRESHOLD=4096
CONFIG_MTD_UBI_BEB_RESERVE=1
# CONFIG_MTD_UBI_GLUEBI is not set

#
# UBI debugging options
#
# CONFIG_MTD_UBI_DEBUG is not set
CONFIG_PARPORT=m
CONFIG_PARPORT_PC=m
CONFIG_PARPORT_SERIAL=m
CONFIG_PARPORT_PC_FIFO=y
# CONFIG_PARPORT_PC_SUPERIO is not set
CONFIG_PARPORT_PC_PCMCIA=m
# CONFIG_PARPORT_GSC is not set
CONFIG_PARPORT_AX88796=m
CONFIG_PARPORT_1284=y
CONFIG_PARPORT_NOT_PC=y
CONFIG_PNP=y
# CONFIG_PNP_DEBUG is not set

#
# Protocols
#
CONFIG_ISAPNP=y
CONFIG_PNPBIOS=y
CONFIG_PNPBIOS_PROC_FS=y
CONFIG_PNPACPI=y
CONFIG_BLK_DEV=y
CONFIG_BLK_DEV_FD=m
CONFIG_BLK_DEV_XD=m
CONFIG_PARIDE=m

#
# Parallel IDE high-level drivers
#
CONFIG_PARIDE_PD=m
CONFIG_PARIDE_PCD=m
CONFIG_PARIDE_PF=m
CONFIG_PARIDE_PT=m
CONFIG_PARIDE_PG=m

#
# Parallel IDE protocol modules
#
CONFIG_PARIDE_ATEN=m
CONFIG_PARIDE_BPCK=m
CONFIG_PARIDE_BPCK6=m
CONFIG_PARIDE_COMM=m
CONFIG_PARIDE_DSTR=m
CONFIG_PARIDE_FIT2=m
CONFIG_PARIDE_FIT3=m
CONFIG_PARIDE_EPAT=m
# CONFIG_PARIDE_EPATC8 is not set
CONFIG_PARIDE_EPIA=m
CONFIG_PARIDE_FRIQ=m
CONFIG_PARIDE_FRPW=m
CONFIG_PARIDE_KBIC=m
CONFIG_PARIDE_KTTI=m
CONFIG_PARIDE_ON20=m
CONFIG_PARIDE_ON26=m
CONFIG_BLK_CPQ_DA=m
CONFIG_BLK_CPQ_CISS_DA=m
CONFIG_CISS_SCSI_TAPE=y
CONFIG_BLK_DEV_DAC960=m
CONFIG_BLK_DEV_UMEM=m
# CONFIG_BLK_DEV_COW_COMMON is not set
CONFIG_BLK_DEV_LOOP=m
CONFIG_BLK_DEV_CRYPTOLOOP=m
CONFIG_BLK_DEV_NBD=m
CONFIG_BLK_DEV_SX8=m
# CONFIG_BLK_DEV_UB is not set
CONFIG_BLK_DEV_RAM=y
CONFIG_BLK_DEV_RAM_COUNT=16
CONFIG_BLK_DEV_RAM_SIZE=8192
CONFIG_BLK_DEV_RAM_BLOCKSIZE=1024
CONFIG_CDROM_PKTCDVD=m
CONFIG_CDROM_PKTCDVD_BUFFERS=8
# CONFIG_CDROM_PKTCDVD_WCACHE is not set
CONFIG_ATA_OVER_ETH=m
CONFIG_VIRTIO_BLK=m
CONFIG_MISC_DEVICES=y
CONFIG_IBM_ASM=m
CONFIG_PHANTOM=m
CONFIG_EEPROM_93CX6=m
CONFIG_SGI_IOC4=m
CONFIG_TIFM_CORE=m
CONFIG_TIFM_7XX1=m
CONFIG_ASUS_LAPTOP=m
CONFIG_FUJITSU_LAPTOP=m
CONFIG_MSI_LAPTOP=m
CONFIG_SONY_LAPTOP=m
# CONFIG_SONYPI_COMPAT is not set
CONFIG_THINKPAD_ACPI=m
# CONFIG_THINKPAD_ACPI_DEBUG is not set
CONFIG_THINKPAD_ACPI_BAY=y
CONFIG_IDE=m
CONFIG_BLK_DEV_IDE=m

#
# Please see Documentation/ide.txt for help/info on IDE drives
#
# CONFIG_BLK_DEV_IDE_SATA is not set
# CONFIG_BLK_DEV_HD_IDE is not set
CONFIG_BLK_DEV_IDEDISK=m
# CONFIG_IDEDISK_MULTI_MODE is not set
CONFIG_BLK_DEV_IDECS=m
CONFIG_BLK_DEV_DELKIN=m
CONFIG_BLK_DEV_IDECD=m
CONFIG_BLK_DEV_IDETAPE=m
CONFIG_BLK_DEV_IDEFLOPPY=m
# CONFIG_BLK_DEV_IDESCSI is not set
# CONFIG_BLK_DEV_IDEACPI is not set
# CONFIG_IDE_TASK_IOCTL is not set
CONFIG_IDE_PROC_FS=y

#
# IDE chipset support/bugfixes
#
CONFIG_IDE_GENERIC=m
# CONFIG_BLK_DEV_PLATFORM is not set
CONFIG_BLK_DEV_CMD640=y
# CONFIG_BLK_DEV_CMD640_ENHANCED is not set
CONFIG_BLK_DEV_IDEPNP=y

#
# PCI IDE chipsets support
#
CONFIG_BLK_DEV_IDEPCI=y
CONFIG_IDEPCI_SHARE_IRQ=y
# CONFIG_IDEPCI_PCIBUS_ORDER is not set
# CONFIG_BLK_DEV_OFFBOARD is not set
CONFIG_BLK_DEV_GENERIC=m
CONFIG_BLK_DEV_OPTI621=m
CONFIG_BLK_DEV_RZ1000=m
CONFIG_BLK_DEV_IDEDMA_PCI=y
CONFIG_BLK_DEV_AEC62XX=m
CONFIG_BLK_DEV_ALI15X3=m
# CONFIG_WDC_ALI15X3 is not set
CONFIG_BLK_DEV_AMD74XX=m
CONFIG_BLK_DEV_ATIIXP=m
CONFIG_BLK_DEV_CMD64X=m
CONFIG_BLK_DEV_TRIFLEX=m
CONFIG_BLK_DEV_CY82C693=m
CONFIG_BLK_DEV_CS5520=m
CONFIG_BLK_DEV_CS5530=m
CONFIG_BLK_DEV_CS5535=m
CONFIG_BLK_DEV_HPT34X=m
# CONFIG_HPT34X_AUTODMA is not set
CONFIG_BLK_DEV_HPT366=m
CONFIG_BLK_DEV_JMICRON=m
CONFIG_BLK_DEV_SC1200=m
CONFIG_BLK_DEV_PIIX=m
CONFIG_BLK_DEV_IT8213=m
CONFIG_BLK_DEV_IT821X=m
CONFIG_BLK_DEV_NS87415=m
CONFIG_BLK_DEV_PDC202XX_OLD=m
CONFIG_PDC202XX_BURST=y
CONFIG_BLK_DEV_PDC202XX_NEW=m
CONFIG_BLK_DEV_SVWKS=m
CONFIG_BLK_DEV_SIIMAGE=m
CONFIG_BLK_DEV_SIS5513=m
CONFIG_BLK_DEV_SLC90E66=m
CONFIG_BLK_DEV_TRM290=m
CONFIG_BLK_DEV_VIA82CXXX=m
CONFIG_BLK_DEV_TC86C001=m
# CONFIG_IDE_ARM is not set

#
# Other IDE chipsets support
#

#
# Note: most of these also require special kernel boot parameters
#
# CONFIG_BLK_DEV_4DRIVES is not set
# CONFIG_BLK_DEV_ALI14XX is not set
# CONFIG_BLK_DEV_DTC2278 is not set
# CONFIG_BLK_DEV_HT6560B is not set
# CONFIG_BLK_DEV_QD65XX is not set
# CONFIG_BLK_DEV_UMC8672 is not set
CONFIG_BLK_DEV_IDEDMA=y
CONFIG_IDE_ARCH_OBSOLETE_INIT=y
# CONFIG_BLK_DEV_HD is not set

#
# SCSI device support
#
CONFIG_RAID_ATTRS=m
CONFIG_SCSI=m
CONFIG_SCSI_DMA=y
CONFIG_SCSI_TGT=m
CONFIG_SCSI_NETLINK=y
CONFIG_SCSI_PROC_FS=y

#
# SCSI support type (disk, tape, CD-ROM)
#
CONFIG_BLK_DEV_SD=m
CONFIG_CHR_DEV_ST=m
CONFIG_CHR_DEV_OSST=m
CONFIG_BLK_DEV_SR=m
CONFIG_BLK_DEV_SR_VENDOR=y
CONFIG_CHR_DEV_SG=m
CONFIG_CHR_DEV_SCH=m

#
# Some SCSI devices (e.g. CD jukebox) support multiple LUNs
#
CONFIG_SCSI_MULTI_LUN=y
CONFIG_SCSI_CONSTANTS=y
CONFIG_SCSI_LOGGING=y
CONFIG_SCSI_SCAN_ASYNC=y
CONFIG_SCSI_WAIT_SCAN=m

#
# SCSI Transports
#
CONFIG_SCSI_SPI_ATTRS=m
CONFIG_SCSI_FC_ATTRS=m
CONFIG_SCSI_FC_TGT_ATTRS=y
CONFIG_SCSI_ISCSI_ATTRS=m
CONFIG_SCSI_SAS_ATTRS=m
CONFIG_SCSI_SAS_LIBSAS=m
CONFIG_SCSI_SAS_ATA=y
# CONFIG_SCSI_SAS_LIBSAS_DEBUG is not set
CONFIG_SCSI_SRP_ATTRS=m
CONFIG_SCSI_SRP_TGT_ATTRS=y
CONFIG_SCSI_LOWLEVEL=y
CONFIG_ISCSI_TCP=m
CONFIG_BLK_DEV_3W_XXXX_RAID=m
CONFIG_SCSI_3W_9XXX=m
CONFIG_SCSI_7000FASST=m
CONFIG_SCSI_ACARD=m
CONFIG_SCSI_AHA152X=m
CONFIG_SCSI_AHA1542=m
CONFIG_SCSI_AACRAID=m
CONFIG_SCSI_AIC7XXX=m
CONFIG_AIC7XXX_CMDS_PER_DEVICE=8
CONFIG_AIC7XXX_RESET_DELAY_MS=15000
CONFIG_AIC7XXX_DEBUG_ENABLE=y
CONFIG_AIC7XXX_DEBUG_MASK=0
CONFIG_AIC7XXX_REG_PRETTY_PRINT=y
CONFIG_SCSI_AIC7XXX_OLD=m
CONFIG_SCSI_AIC79XX=m
CONFIG_AIC79XX_CMDS_PER_DEVICE=32
CONFIG_AIC79XX_RESET_DELAY_MS=15000
CONFIG_AIC79XX_DEBUG_ENABLE=y
CONFIG_AIC79XX_DEBUG_MASK=0
CONFIG_AIC79XX_REG_PRETTY_PRINT=y
CONFIG_SCSI_AIC94XX=m
# CONFIG_AIC94XX_DEBUG is not set
CONFIG_SCSI_DPT_I2O=m
CONFIG_SCSI_ADVANSYS=m
CONFIG_SCSI_IN2000=m
CONFIG_SCSI_ARCMSR=m
# CONFIG_SCSI_ARCMSR_AER is not set
CONFIG_MEGARAID_NEWGEN=y
CONFIG_MEGARAID_MM=m
CONFIG_MEGARAID_MAILBOX=m
CONFIG_MEGARAID_LEGACY=m
CONFIG_MEGARAID_SAS=m
CONFIG_SCSI_HPTIOP=m
CONFIG_SCSI_BUSLOGIC=m
# CONFIG_SCSI_OMIT_FLASHPOINT is not set
CONFIG_SCSI_DMX3191D=m
CONFIG_SCSI_DTC3280=m
CONFIG_SCSI_EATA=m
CONFIG_SCSI_EATA_TAGGED_QUEUE=y
CONFIG_SCSI_EATA_LINKED_COMMANDS=y
CONFIG_SCSI_EATA_MAX_TAGS=16
CONFIG_SCSI_FUTURE_DOMAIN=m
CONFIG_SCSI_GDTH=m
CONFIG_SCSI_GENERIC_NCR5380=m
CONFIG_SCSI_GENERIC_NCR5380_MMIO=m
CONFIG_SCSI_GENERIC_NCR53C400=y
CONFIG_SCSI_IPS=m
CONFIG_SCSI_INITIO=m
# CONFIG_SCSI_INIA100 is not set
CONFIG_SCSI_PPA=m
CONFIG_SCSI_IMM=m
# CONFIG_SCSI_IZIP_EPP16 is not set
# CONFIG_SCSI_IZIP_SLOW_CTR is not set
CONFIG_SCSI_NCR53C406A=m
CONFIG_SCSI_STEX=m
CONFIG_SCSI_SYM53C8XX_2=m
CONFIG_SCSI_SYM53C8XX_DMA_ADDRESSING_MODE=1
CONFIG_SCSI_SYM53C8XX_DEFAULT_TAGS=16
CONFIG_SCSI_SYM53C8XX_MAX_TAGS=64
CONFIG_SCSI_SYM53C8XX_MMIO=y
CONFIG_SCSI_IPR=m
# CONFIG_SCSI_IPR_TRACE is not set
# CONFIG_SCSI_IPR_DUMP is not set
CONFIG_SCSI_PAS16=m
CONFIG_SCSI_PSI240I=m
CONFIG_SCSI_QLOGIC_FAS=m
CONFIG_SCSI_QLOGIC_1280=m
CONFIG_SCSI_QLA_FC=m
CONFIG_SCSI_QLA_ISCSI=m
CONFIG_SCSI_LPFC=m
# CONFIG_SCSI_SEAGATE is not set
CONFIG_SCSI_SYM53C416=m
CONFIG_SCSI_DC395x=m
CONFIG_SCSI_DC390T=m
CONFIG_SCSI_T128=m
CONFIG_SCSI_U14_34F=m
CONFIG_SCSI_U14_34F_TAGGED_QUEUE=y
CONFIG_SCSI_U14_34F_LINKED_COMMANDS=y
CONFIG_SCSI_U14_34F_MAX_TAGS=8
CONFIG_SCSI_ULTRASTOR=m
CONFIG_SCSI_NSP32=m
CONFIG_SCSI_DEBUG=m
CONFIG_SCSI_SRP=m
CONFIG_SCSI_LOWLEVEL_PCMCIA=y
CONFIG_PCMCIA_AHA152X=m
CONFIG_PCMCIA_FDOMAIN=m
CONFIG_PCMCIA_NINJA_SCSI=m
CONFIG_PCMCIA_QLOGIC=m
CONFIG_PCMCIA_SYM53C500=m
CONFIG_ATA=m
# CONFIG_ATA_NONSTANDARD is not set
CONFIG_ATA_ACPI=y
CONFIG_SATA_AHCI=m
CONFIG_SATA_SVW=m
CONFIG_ATA_PIIX=m
CONFIG_SATA_MV=m
CONFIG_SATA_NV=m
CONFIG_PDC_ADMA=m
CONFIG_SATA_QSTOR=m
CONFIG_SATA_PROMISE=m
CONFIG_SATA_SX4=m
CONFIG_SATA_SIL=m
CONFIG_SATA_SIL24=m
CONFIG_SATA_SIS=m
CONFIG_SATA_ULI=m
CONFIG_SATA_VIA=m
CONFIG_SATA_VITESSE=m
CONFIG_SATA_INIC162X=m
# CONFIG_PATA_ACPI is not set
# CONFIG_PATA_ALI is not set
# CONFIG_PATA_AMD is not set
CONFIG_PATA_ARTOP=m
# CONFIG_PATA_ATIIXP is not set
# CONFIG_PATA_CMD640_PCI is not set
# CONFIG_PATA_CMD64X is not set
# CONFIG_PATA_CS5520 is not set
# CONFIG_PATA_CS5530 is not set
# CONFIG_PATA_CS5535 is not set
# CONFIG_PATA_CS5536 is not set
# CONFIG_PATA_CYPRESS is not set
# CONFIG_PATA_EFAR is not set
CONFIG_ATA_GENERIC=m
# CONFIG_PATA_HPT366 is not set
# CONFIG_PATA_HPT37X is not set
# CONFIG_PATA_HPT3X2N is not set
# CONFIG_PATA_HPT3X3 is not set
# CONFIG_PATA_ISAPNP is not set
# CONFIG_PATA_IT821X is not set
# CONFIG_PATA_IT8213 is not set
# CONFIG_PATA_JMICRON is not set
# CONFIG_PATA_LEGACY is not set
# CONFIG_PATA_TRIFLEX is not set
CONFIG_PATA_MARVELL=m
# CONFIG_PATA_MPIIX is not set
# CONFIG_PATA_OLDPIIX is not set
# CONFIG_PATA_NETCELL is not set
# CONFIG_PATA_NS87410 is not set
# CONFIG_PATA_NS87415 is not set
# CONFIG_PATA_OPTI is not set
# CONFIG_PATA_OPTIDMA is not set
# CONFIG_PATA_PCMCIA is not set
# CONFIG_PATA_PDC_OLD is not set
# CONFIG_PATA_QDI is not set
# CONFIG_PATA_RADISYS is not set
# CONFIG_PATA_RZ1000 is not set
# CONFIG_PATA_SC1200 is not set
# CONFIG_PATA_SERVERWORKS is not set
# CONFIG_PATA_PDC2027X is not set
# CONFIG_PATA_SIL680 is not set
CONFIG_PATA_SIS=m
# CONFIG_PATA_VIA is not set
# CONFIG_PATA_WINBOND is not set
# CONFIG_PATA_WINBOND_VLB is not set
CONFIG_MD=y
CONFIG_BLK_DEV_MD=m
CONFIG_MD_LINEAR=m
CONFIG_MD_RAID0=m
CONFIG_MD_RAID1=m
CONFIG_MD_RAID10=m
CONFIG_MD_RAID456=m
CONFIG_MD_RAID5_RESHAPE=y
CONFIG_MD_MULTIPATH=m
CONFIG_MD_FAULTY=m
CONFIG_BLK_DEV_DM=m
# CONFIG_DM_DEBUG is not set
CONFIG_DM_CRYPT=m
CONFIG_DM_SNAPSHOT=m
CONFIG_DM_MIRROR=m
CONFIG_DM_ZERO=m
CONFIG_DM_MULTIPATH=m
CONFIG_DM_MULTIPATH_EMC=m
CONFIG_DM_MULTIPATH_RDAC=m
CONFIG_DM_MULTIPATH_HP=m
CONFIG_DM_DELAY=m
CONFIG_DM_UEVENT=y
CONFIG_FUSION=y
CONFIG_FUSION_SPI=m
CONFIG_FUSION_FC=m
CONFIG_FUSION_SAS=m
CONFIG_FUSION_MAX_SGE=40
CONFIG_FUSION_CTL=m
CONFIG_FUSION_LAN=m
# CONFIG_FUSION_LOGGING is not set

#
# IEEE 1394 (FireWire) support
#
CONFIG_FIREWIRE=m
CONFIG_FIREWIRE_OHCI=m
CONFIG_FIREWIRE_SBP2=m
# CONFIG_IEEE1394 is not set
CONFIG_I2O=m
CONFIG_I2O_LCT_NOTIFY_ON_CHANGES=y
CONFIG_I2O_EXT_ADAPTEC=y
CONFIG_I2O_CONFIG=m
CONFIG_I2O_CONFIG_OLD_IOCTL=y
CONFIG_I2O_BUS=m
CONFIG_I2O_BLOCK=m
CONFIG_I2O_SCSI=m
CONFIG_I2O_PROC=m
# CONFIG_MACINTOSH_DRIVERS is not set
CONFIG_NETDEVICES=y
CONFIG_NETDEVICES_MULTIQUEUE=y
CONFIG_IFB=m
CONFIG_DUMMY=m
CONFIG_BONDING=m
# CONFIG_MACVLAN is not set
CONFIG_EQUALIZER=m
CONFIG_TUN=m
CONFIG_VETH=m
CONFIG_NET_SB1000=m
CONFIG_ARCNET=m
CONFIG_ARCNET_1201=m
CONFIG_ARCNET_1051=m
CONFIG_ARCNET_RAW=m
CONFIG_ARCNET_CAP=m
CONFIG_ARCNET_COM90xx=m
CONFIG_ARCNET_COM90xxIO=m
CONFIG_ARCNET_RIM_I=m
CONFIG_ARCNET_COM20020=m
CONFIG_ARCNET_COM20020_ISA=m
CONFIG_ARCNET_COM20020_PCI=m
CONFIG_PHYLIB=m

#
# MII PHY device drivers
#
CONFIG_MARVELL_PHY=m
CONFIG_DAVICOM_PHY=m
CONFIG_QSEMI_PHY=m
CONFIG_LXT_PHY=m
CONFIG_CICADA_PHY=m
CONFIG_VITESSE_PHY=m
CONFIG_SMSC_PHY=m
CONFIG_BROADCOM_PHY=m
CONFIG_ICPLUS_PHY=m
CONFIG_FIXED_PHY=m
CONFIG_FIXED_MII_10_FDX=y
CONFIG_FIXED_MII_100_FDX=y
CONFIG_FIXED_MII_1000_FDX=y
CONFIG_FIXED_MII_AMNT=1
CONFIG_MDIO_BITBANG=m
CONFIG_NET_ETHERNET=y
CONFIG_MII=m
CONFIG_HAPPYMEAL=m
CONFIG_SUNGEM=m
CONFIG_CASSINI=m
CONFIG_NET_VENDOR_3COM=y
CONFIG_EL1=m
CONFIG_EL2=m
CONFIG_ELPLUS=m
CONFIG_EL16=m
CONFIG_EL3=m
CONFIG_3C515=m
CONFIG_VORTEX=m
CONFIG_TYPHOON=m
CONFIG_LANCE=m
CONFIG_NET_VENDOR_SMC=y
CONFIG_WD80x3=m
CONFIG_ULTRA=m
CONFIG_SMC9194=m
CONFIG_NET_VENDOR_RACAL=y
CONFIG_NI52=m
CONFIG_NI65=m
CONFIG_NET_TULIP=y
CONFIG_DE2104X=m
CONFIG_TULIP=m
# CONFIG_TULIP_MWI is not set
# CONFIG_TULIP_MMIO is not set
CONFIG_TULIP_NAPI=y
CONFIG_TULIP_NAPI_HW_MITIGATION=y
CONFIG_DE4X5=m
CONFIG_WINBOND_840=m
CONFIG_DM9102=m
CONFIG_ULI526X=m
CONFIG_PCMCIA_XIRCOM=m
CONFIG_AT1700=m
CONFIG_DEPCA=m
CONFIG_HP100=m
CONFIG_NET_ISA=y
CONFIG_E2100=m
CONFIG_EWRK3=m
CONFIG_EEXPRESS=m
CONFIG_EEXPRESS_PRO=m
CONFIG_HPLAN_PLUS=m
CONFIG_HPLAN=m
CONFIG_LP486E=m
CONFIG_ETH16I=m
CONFIG_NE2000=m
CONFIG_ZNET=m
CONFIG_SEEQ8005=m
# CONFIG_IBM_NEW_EMAC_ZMII is not set
# CONFIG_IBM_NEW_EMAC_RGMII is not set
# CONFIG_IBM_NEW_EMAC_TAH is not set
# CONFIG_IBM_NEW_EMAC_EMAC4 is not set
CONFIG_NET_PCI=y
CONFIG_PCNET32=m
CONFIG_PCNET32_NAPI=y
CONFIG_AMD8111_ETH=m
CONFIG_AMD8111E_NAPI=y
CONFIG_ADAPTEC_STARFIRE=m
CONFIG_ADAPTEC_STARFIRE_NAPI=y
CONFIG_AC3200=m
CONFIG_APRICOT=m
CONFIG_B44=m
CONFIG_B44_PCI_AUTOSELECT=y
CONFIG_B44_PCICORE_AUTOSELECT=y
CONFIG_B44_PCI=y
CONFIG_FORCEDETH=m
# CONFIG_FORCEDETH_NAPI is not set
CONFIG_CS89x0=m
CONFIG_EEPRO100=m
CONFIG_E100=m
CONFIG_FEALNX=m
CONFIG_NATSEMI=m
CONFIG_NE2K_PCI=m
CONFIG_8139CP=m
CONFIG_8139TOO=m
CONFIG_8139TOO_PIO=y
CONFIG_8139TOO_TUNE_TWISTER=y
CONFIG_8139TOO_8129=y
# CONFIG_8139_OLD_RX_RESET is not set
CONFIG_SIS900=m
CONFIG_EPIC100=m
CONFIG_SUNDANCE=m
# CONFIG_SUNDANCE_MMIO is not set
CONFIG_TLAN=m
CONFIG_VIA_RHINE=m
# CONFIG_VIA_RHINE_MMIO is not set
CONFIG_VIA_RHINE_NAPI=y
CONFIG_SC92031=m
# CONFIG_NET_POCKET is not set
CONFIG_NETDEV_1000=y
CONFIG_DL2K=m
CONFIG_E1000=m
CONFIG_E1000_NAPI=y
# CONFIG_E1000_DISABLE_PACKET_SPLIT is not set
CONFIG_E1000E=m
CONFIG_IP1000=m
CONFIG_NS83820=m
CONFIG_HAMACHI=m
CONFIG_YELLOWFIN=m
CONFIG_R8169=m
CONFIG_R8169_NAPI=y
CONFIG_R8169_VLAN=y
CONFIG_SIS190=m
CONFIG_SKGE=m
# CONFIG_SKGE_DEBUG is not set
CONFIG_SKY2=m
# CONFIG_SKY2_DEBUG is not set
# CONFIG_SK98LIN is not set
CONFIG_VIA_VELOCITY=m
CONFIG_TIGON3=m
CONFIG_QLA3XXX=m
CONFIG_ATL1=m
CONFIG_NETDEV_10000=y
CONFIG_CHELSIO_T1=m
CONFIG_CHELSIO_T1_1G=y
CONFIG_CHELSIO_T1_NAPI=y
CONFIG_CHELSIO_T3=m
CONFIG_IXGBE=m
CONFIG_IXGB=m
CONFIG_IXGB_NAPI=y
CONFIG_S2IO=m
CONFIG_S2IO_NAPI=y
CONFIG_MYRI10GE=m
CONFIG_NETXEN_NIC=m
CONFIG_NIU=m
CONFIG_MLX4_CORE=m
CONFIG_MLX4_DEBUG=y
CONFIG_TEHUTI=m
CONFIG_TR=y
CONFIG_IBMTR=m
CONFIG_IBMOL=m
CONFIG_IBMLS=m
CONFIG_TMS380TR=m
CONFIG_TMSPCI=m
CONFIG_SKISA=m
CONFIG_PROTEON=m
CONFIG_ABYSS=m

#
# Wireless LAN
#
CONFIG_WLAN_PRE80211=y
CONFIG_STRIP=m
CONFIG_ARLAN=m
CONFIG_WAVELAN=m
CONFIG_PCMCIA_WAVELAN=m
CONFIG_PCMCIA_NETWAVE=m
CONFIG_WLAN_80211=y
CONFIG_PCMCIA_RAYCS=m
CONFIG_IPW2100=m
CONFIG_IPW2100_MONITOR=y
# CONFIG_IPW2100_DEBUG is not set
CONFIG_IPW2200=m
CONFIG_IPW2200_MONITOR=y
CONFIG_IPW2200_RADIOTAP=y
CONFIG_IPW2200_PROMISCUOUS=y
CONFIG_IPW2200_QOS=y
# CONFIG_IPW2200_DEBUG is not set
CONFIG_LIBERTAS=m
CONFIG_LIBERTAS_USB=m
CONFIG_LIBERTAS_CS=m
CONFIG_LIBERTAS_SDIO=m
# CONFIG_LIBERTAS_DEBUG is not set
CONFIG_AIRO=m
CONFIG_HERMES=m
CONFIG_PLX_HERMES=m
CONFIG_TMD_HERMES=m
CONFIG_NORTEL_HERMES=m
CONFIG_PCI_HERMES=m
CONFIG_PCMCIA_HERMES=m
CONFIG_PCMCIA_SPECTRUM=m
CONFIG_ATMEL=m
CONFIG_PCI_ATMEL=m
CONFIG_PCMCIA_ATMEL=m
CONFIG_USB_ATMEL=m
CONFIG_AIRO_CS=m
CONFIG_PCMCIA_WL3501=m
CONFIG_PRISM54=m
CONFIG_USB_ZD1201=m
CONFIG_RTL8187=m
CONFIG_ADM8211=m
CONFIG_P54_COMMON=m
CONFIG_P54_USB=m
CONFIG_P54_PCI=m
CONFIG_ATH5K=m
CONFIG_IWLWIFI=y
# CONFIG_IWLWIFI_DEBUG is not set
CONFIG_IWLWIFI_SENSITIVITY=y
CONFIG_IWLWIFI_SPECTRUM_MEASUREMENT=y
CONFIG_IWLWIFI_QOS=y
CONFIG_IWL4965=m
CONFIG_IWL3945=m
CONFIG_HOSTAP=m
CONFIG_HOSTAP_FIRMWARE=y
# CONFIG_HOSTAP_FIRMWARE_NVRAM is not set
CONFIG_HOSTAP_PLX=m
CONFIG_HOSTAP_PCI=m
CONFIG_HOSTAP_CS=m
# CONFIG_BCM43XX is not set
CONFIG_B43=m
CONFIG_B43_PCI_AUTOSELECT=y
CONFIG_B43_PCICORE_AUTOSELECT=y
CONFIG_B43_PCMCIA=y
CONFIG_B43_LEDS=y
CONFIG_B43_RFKILL=y
# CONFIG_B43_DEBUG is not set
CONFIG_B43_DMA=y
CONFIG_B43_PIO=y
CONFIG_B43_DMA_AND_PIO_MODE=y
# CONFIG_B43_DMA_MODE is not set
# CONFIG_B43_PIO_MODE is not set
CONFIG_B43LEGACY=m
CONFIG_B43LEGACY_PCI_AUTOSELECT=y
CONFIG_B43LEGACY_PCICORE_AUTOSELECT=y
CONFIG_B43LEGACY_DEBUG=y
CONFIG_B43LEGACY_DMA=y
CONFIG_B43LEGACY_PIO=y
CONFIG_B43LEGACY_DMA_AND_PIO_MODE=y
# CONFIG_B43LEGACY_DMA_MODE is not set
# CONFIG_B43LEGACY_PIO_MODE is not set
CONFIG_ZD1211RW=m
# CONFIG_ZD1211RW_DEBUG is not set
CONFIG_RT2X00=m
CONFIG_RT2X00_LIB=m
CONFIG_RT2X00_LIB_PCI=m
CONFIG_RT2X00_LIB_USB=m
CONFIG_RT2X00_LIB_FIRMWARE=y
CONFIG_RT2X00_LIB_RFKILL=y
CONFIG_RT2400PCI=m
CONFIG_RT2400PCI_RFKILL=y
CONFIG_RT2500PCI=m
CONFIG_RT2500PCI_RFKILL=y
CONFIG_RT61PCI=m
CONFIG_RT61PCI_RFKILL=y
CONFIG_RT2500USB=m
CONFIG_RT73USB=m
# CONFIG_RT2X00_DEBUG is not set

#
# USB Network Adapters
#
CONFIG_USB_CATC=m
CONFIG_USB_KAWETH=m
CONFIG_USB_PEGASUS=m
CONFIG_USB_RTL8150=m
CONFIG_USB_USBNET=m
CONFIG_USB_NET_AX8817X=m
CONFIG_USB_NET_CDCETHER=m
CONFIG_USB_NET_DM9601=m
CONFIG_USB_NET_GL620A=m
CONFIG_USB_NET_NET1080=m
CONFIG_USB_NET_PLUSB=m
CONFIG_USB_NET_MCS7830=m
CONFIG_USB_NET_RNDIS_HOST=m
CONFIG_USB_NET_CDC_SUBSET=m
CONFIG_USB_ALI_M5632=y
CONFIG_USB_AN2720=y
CONFIG_USB_BELKIN=y
CONFIG_USB_ARMLINUX=y
CONFIG_USB_EPSON2888=y
CONFIG_USB_KC2190=y
CONFIG_USB_NET_ZAURUS=m
CONFIG_NET_PCMCIA=y
CONFIG_PCMCIA_3C589=m
CONFIG_PCMCIA_3C574=m
CONFIG_PCMCIA_FMVJ18X=m
CONFIG_PCMCIA_PCNET=m
CONFIG_PCMCIA_NMCLAN=m
CONFIG_PCMCIA_SMC91C92=m
CONFIG_PCMCIA_XIRC2PS=m
CONFIG_PCMCIA_AXNET=m
CONFIG_ARCNET_COM20020_CS=m
CONFIG_PCMCIA_IBMTR=m
CONFIG_WAN=y
CONFIG_HOSTESS_SV11=m
CONFIG_COSA=m
CONFIG_LANMEDIA=m
CONFIG_SEALEVEL_4021=m
CONFIG_HDLC=m
CONFIG_HDLC_RAW=m
CONFIG_HDLC_RAW_ETH=m
CONFIG_HDLC_CISCO=m
CONFIG_HDLC_FR=m
CONFIG_HDLC_PPP=m
CONFIG_HDLC_X25=m
CONFIG_PCI200SYN=m
CONFIG_WANXL=m
CONFIG_PC300=m
CONFIG_PC300_MLPPP=y

#
# Cyclades-PC300 MLPPP support is disabled.
#

#
# Refer to the file README.mlppp, provided by PC300 package.
#
# CONFIG_PC300TOO is not set
CONFIG_N2=m
CONFIG_C101=m
CONFIG_FARSYNC=m
CONFIG_DSCC4=m
CONFIG_DSCC4_PCISYNC=y
CONFIG_DSCC4_PCI_RST=y
CONFIG_DLCI=m
CONFIG_DLCI_MAX=8
CONFIG_SDLA=m
CONFIG_WAN_ROUTER_DRIVERS=m
CONFIG_CYCLADES_SYNC=m
CONFIG_CYCLOMX_X25=y
CONFIG_LAPBETHER=m
CONFIG_X25_ASY=m
CONFIG_SBNI=m
# CONFIG_SBNI_MULTILINE is not set
CONFIG_ATM_DRIVERS=y
CONFIG_ATM_DUMMY=m
CONFIG_ATM_TCP=m
CONFIG_ATM_LANAI=m
CONFIG_ATM_ENI=m
# CONFIG_ATM_ENI_DEBUG is not set
# CONFIG_ATM_ENI_TUNE_BURST is not set
CONFIG_ATM_FIRESTREAM=m
CONFIG_ATM_ZATM=m
# CONFIG_ATM_ZATM_DEBUG is not set
CONFIG_ATM_NICSTAR=m
# CONFIG_ATM_NICSTAR_USE_SUNI is not set
# CONFIG_ATM_NICSTAR_USE_IDT77105 is not set
CONFIG_ATM_IDT77252=m
# CONFIG_ATM_IDT77252_DEBUG is not set
# CONFIG_ATM_IDT77252_RCV_ALL is not set
CONFIG_ATM_IDT77252_USE_SUNI=y
CONFIG_ATM_HORIZON=m
# CONFIG_ATM_HORIZON_DEBUG is not set
CONFIG_ATM_IA=m
# CONFIG_ATM_IA_DEBUG is not set
CONFIG_ATM_FORE200E_MAYBE=m
CONFIG_ATM_HE=m
CONFIG_ATM_HE_USE_SUNI=y
CONFIG_FDDI=y
CONFIG_DEFXX=m
# CONFIG_DEFXX_MMIO is not set
CONFIG_SKFP=m
CONFIG_HIPPI=y
CONFIG_ROADRUNNER=m
# CONFIG_ROADRUNNER_LARGE_RINGS is not set
CONFIG_PLIP=m
CONFIG_PPP=m
CONFIG_PPP_MULTILINK=y
CONFIG_PPP_FILTER=y
CONFIG_PPP_ASYNC=m
CONFIG_PPP_SYNC_TTY=m
CONFIG_PPP_DEFLATE=m
CONFIG_PPP_BSDCOMP=m
CONFIG_PPP_MPPE=m
CONFIG_PPPOE=m
CONFIG_PPPOATM=m
CONFIG_PPPOL2TP=m
CONFIG_SLIP=m
CONFIG_SLIP_COMPRESSED=y
CONFIG_SLHC=m
CONFIG_SLIP_SMART=y
CONFIG_SLIP_MODE_SLIP6=y
CONFIG_NET_FC=y
CONFIG_SHAPER=m
CONFIG_NETCONSOLE=m
CONFIG_NETCONSOLE_DYNAMIC=y
CONFIG_NETPOLL=y
# CONFIG_NETPOLL_TRAP is not set
CONFIG_NET_POLL_CONTROLLER=y
CONFIG_VIRTIO_NET=m
CONFIG_ISDN=m
CONFIG_ISDN_I4L=m
CONFIG_ISDN_PPP=y
CONFIG_ISDN_PPP_VJ=y
CONFIG_ISDN_MPP=y
CONFIG_IPPP_FILTER=y
CONFIG_ISDN_PPP_BSDCOMP=m
CONFIG_ISDN_AUDIO=y
CONFIG_ISDN_TTY_FAX=y
CONFIG_ISDN_X25=y

#
# ISDN feature submodules
#
# CONFIG_ISDN_DIVERSION is not set

#
# ISDN4Linux hardware drivers
#

#
# Passive cards
#
CONFIG_ISDN_DRV_HISAX=m

#
# D-channel protocol features
#
CONFIG_HISAX_EURO=y
CONFIG_DE_AOC=y
# CONFIG_HISAX_NO_SENDCOMPLETE is not set
# CONFIG_HISAX_NO_LLC is not set
# CONFIG_HISAX_NO_KEYPAD is not set
CONFIG_HISAX_1TR6=y
CONFIG_HISAX_NI1=y
CONFIG_HISAX_MAX_CARDS=8

#
# HiSax supported cards
#
CONFIG_HISAX_16_0=y
CONFIG_HISAX_16_3=y
CONFIG_HISAX_TELESPCI=y
CONFIG_HISAX_S0BOX=y
CONFIG_HISAX_AVM_A1=y
CONFIG_HISAX_FRITZPCI=y
CONFIG_HISAX_AVM_A1_PCMCIA=y
CONFIG_HISAX_ELSA=y
CONFIG_HISAX_IX1MICROR2=y
CONFIG_HISAX_DIEHLDIVA=y
CONFIG_HISAX_ASUSCOM=y
CONFIG_HISAX_TELEINT=y
CONFIG_HISAX_HFCS=y
CONFIG_HISAX_SEDLBAUER=y
CONFIG_HISAX_SPORTSTER=y
CONFIG_HISAX_MIC=y
CONFIG_HISAX_NETJET=y
CONFIG_HISAX_NETJET_U=y
CONFIG_HISAX_NICCY=y
CONFIG_HISAX_ISURF=y
CONFIG_HISAX_HSTSAPHIR=y
CONFIG_HISAX_BKM_A4T=y
CONFIG_HISAX_SCT_QUADRO=y
CONFIG_HISAX_GAZEL=y
CONFIG_HISAX_HFC_PCI=y
CONFIG_HISAX_W6692=y
CONFIG_HISAX_HFC_SX=y
CONFIG_HISAX_ENTERNOW_PCI=y
# CONFIG_HISAX_DEBUG is not set

#
# HiSax PCMCIA card service modules
#
CONFIG_HISAX_SEDLBAUER_CS=m
CONFIG_HISAX_ELSA_CS=m
CONFIG_HISAX_AVM_A1_CS=m
CONFIG_HISAX_TELES_CS=m

#
# HiSax sub driver modules
#
CONFIG_HISAX_ST5481=m
CONFIG_HISAX_HFCUSB=m
CONFIG_HISAX_HFC4S8S=m
CONFIG_HISAX_FRITZ_PCIPNP=m
CONFIG_HISAX_HDLC=y

#
# Active cards
#
CONFIG_ISDN_DRV_ICN=m
CONFIG_ISDN_DRV_PCBIT=m
CONFIG_ISDN_DRV_SC=m
CONFIG_ISDN_DRV_ACT2000=m
CONFIG_ISDN_DRV_GIGASET=m
CONFIG_GIGASET_BASE=m
CONFIG_GIGASET_M105=m
CONFIG_GIGASET_M101=m
# CONFIG_GIGASET_DEBUG is not set
# CONFIG_GIGASET_UNDOCREQ is not set
CONFIG_ISDN_CAPI=m
CONFIG_ISDN_DRV_AVMB1_VERBOSE_REASON=y
CONFIG_CAPI_TRACE=y
CONFIG_ISDN_CAPI_MIDDLEWARE=y
CONFIG_ISDN_CAPI_CAPI20=m
CONFIG_ISDN_CAPI_CAPIFS_BOOL=y
CONFIG_ISDN_CAPI_CAPIFS=m
CONFIG_ISDN_CAPI_CAPIDRV=m

#
# CAPI hardware drivers
#
CONFIG_CAPI_AVM=y
CONFIG_ISDN_DRV_AVMB1_B1ISA=m
CONFIG_ISDN_DRV_AVMB1_B1PCI=m
CONFIG_ISDN_DRV_AVMB1_B1PCIV4=y
CONFIG_ISDN_DRV_AVMB1_T1ISA=m
CONFIG_ISDN_DRV_AVMB1_B1PCMCIA=m
CONFIG_ISDN_DRV_AVMB1_AVM_CS=m
CONFIG_ISDN_DRV_AVMB1_T1PCI=m
CONFIG_ISDN_DRV_AVMB1_C4=m
CONFIG_CAPI_EICON=y
CONFIG_ISDN_DIVAS=m
CONFIG_ISDN_DIVAS_BRIPCI=y
CONFIG_ISDN_DIVAS_PRIPCI=y
CONFIG_ISDN_DIVAS_DIVACAPI=m
CONFIG_ISDN_DIVAS_USERIDI=m
CONFIG_ISDN_DIVAS_MAINT=m
CONFIG_PHONE=m
CONFIG_PHONE_IXJ=m
CONFIG_PHONE_IXJ_PCMCIA=m

#
# Input device support
#
CONFIG_INPUT=y
CONFIG_INPUT_FF_MEMLESS=m
CONFIG_INPUT_POLLDEV=m

#
# Userland interfaces
#
CONFIG_INPUT_MOUSEDEV=y
CONFIG_INPUT_MOUSEDEV_PSAUX=y
CONFIG_INPUT_MOUSEDEV_SCREEN_X=1024
CONFIG_INPUT_MOUSEDEV_SCREEN_Y=768
CONFIG_INPUT_JOYDEV=m
CONFIG_INPUT_EVDEV=m
# CONFIG_INPUT_EVBUG is not set

#
# Input Device Drivers
#
CONFIG_INPUT_KEYBOARD=y
CONFIG_KEYBOARD_ATKBD=y
CONFIG_KEYBOARD_SUNKBD=m
CONFIG_KEYBOARD_LKKBD=m
CONFIG_KEYBOARD_XTKBD=m
CONFIG_KEYBOARD_NEWTON=m
CONFIG_KEYBOARD_STOWAWAY=m
CONFIG_INPUT_MOUSE=y
CONFIG_MOUSE_PS2=m
CONFIG_MOUSE_PS2_ALPS=y
CONFIG_MOUSE_PS2_LOGIPS2PP=y
CONFIG_MOUSE_PS2_SYNAPTICS=y
CONFIG_MOUSE_PS2_LIFEBOOK=y
CONFIG_MOUSE_PS2_TRACKPOINT=y
# CONFIG_MOUSE_PS2_TOUCHKIT is not set
CONFIG_MOUSE_SERIAL=m
CONFIG_MOUSE_APPLETOUCH=m
CONFIG_MOUSE_INPORT=m
# CONFIG_MOUSE_ATIXL is not set
CONFIG_MOUSE_LOGIBM=m
CONFIG_MOUSE_PC110PAD=m
CONFIG_MOUSE_VSXXXAA=m
CONFIG_INPUT_JOYSTICK=y
CONFIG_JOYSTICK_ANALOG=m
CONFIG_JOYSTICK_A3D=m
CONFIG_JOYSTICK_ADI=m
CONFIG_JOYSTICK_COBRA=m
CONFIG_JOYSTICK_GF2K=m
CONFIG_JOYSTICK_GRIP=m
CONFIG_JOYSTICK_GRIP_MP=m
CONFIG_JOYSTICK_GUILLEMOT=m
CONFIG_JOYSTICK_INTERACT=m
CONFIG_JOYSTICK_SIDEWINDER=m
CONFIG_JOYSTICK_TMDC=m
CONFIG_JOYSTICK_IFORCE=m
CONFIG_JOYSTICK_IFORCE_USB=y
CONFIG_JOYSTICK_IFORCE_232=y
CONFIG_JOYSTICK_WARRIOR=m
CONFIG_JOYSTICK_MAGELLAN=m
CONFIG_JOYSTICK_SPACEORB=m
CONFIG_JOYSTICK_SPACEBALL=m
CONFIG_JOYSTICK_STINGER=m
CONFIG_JOYSTICK_TWIDJOY=m
CONFIG_JOYSTICK_DB9=m
CONFIG_JOYSTICK_GAMECON=m
CONFIG_JOYSTICK_TURBOGRAFX=m
CONFIG_JOYSTICK_JOYDUMP=m
CONFIG_JOYSTICK_XPAD=m
CONFIG_JOYSTICK_XPAD_FF=y
CONFIG_JOYSTICK_XPAD_LEDS=y
CONFIG_INPUT_TABLET=y
CONFIG_TABLET_USB_ACECAD=m
CONFIG_TABLET_USB_AIPTEK=m
CONFIG_TABLET_USB_GTCO=m
CONFIG_TABLET_USB_KBTAB=m
CONFIG_TABLET_USB_WACOM=m
CONFIG_INPUT_TOUCHSCREEN=y
CONFIG_TOUCHSCREEN_ADS7846=m
CONFIG_TOUCHSCREEN_FUJITSU=m
CONFIG_TOUCHSCREEN_GUNZE=m
CONFIG_TOUCHSCREEN_ELO=m
CONFIG_TOUCHSCREEN_MTOUCH=m
CONFIG_TOUCHSCREEN_MK712=m
CONFIG_TOUCHSCREEN_PENMOUNT=m
CONFIG_TOUCHSCREEN_TOUCHRIGHT=m
CONFIG_TOUCHSCREEN_TOUCHWIN=m
CONFIG_TOUCHSCREEN_UCB1400=m
CONFIG_TOUCHSCREEN_USB_COMPOSITE=m
CONFIG_TOUCHSCREEN_USB_EGALAX=y
CONFIG_TOUCHSCREEN_USB_PANJIT=y
CONFIG_TOUCHSCREEN_USB_3M=y
CONFIG_TOUCHSCREEN_USB_ITM=y
CONFIG_TOUCHSCREEN_USB_ETURBO=y
CONFIG_TOUCHSCREEN_USB_GUNZE=y
CONFIG_TOUCHSCREEN_USB_DMC_TSC10=y
CONFIG_TOUCHSCREEN_USB_IRTOUCH=y
CONFIG_TOUCHSCREEN_USB_IDEALTEK=y
CONFIG_TOUCHSCREEN_USB_GENERAL_TOUCH=y
CONFIG_TOUCHSCREEN_USB_GOTOP=y
CONFIG_INPUT_MISC=y
CONFIG_INPUT_PCSPKR=m
CONFIG_INPUT_WISTRON_BTNS=m
CONFIG_INPUT_ATLAS_BTNS=m
CONFIG_INPUT_ATI_REMOTE=m
CONFIG_INPUT_ATI_REMOTE2=m
CONFIG_INPUT_KEYSPAN_REMOTE=m
CONFIG_INPUT_POWERMATE=m
CONFIG_INPUT_YEALINK=m
CONFIG_INPUT_UINPUT=m

#
# Hardware I/O ports
#
CONFIG_SERIO=y
CONFIG_SERIO_I8042=y
CONFIG_SERIO_SERPORT=m
CONFIG_SERIO_CT82C710=m
CONFIG_SERIO_PARKBD=m
CONFIG_SERIO_PCIPS2=m
CONFIG_SERIO_LIBPS2=y
CONFIG_SERIO_RAW=m
CONFIG_GAMEPORT=m
CONFIG_GAMEPORT_NS558=m
CONFIG_GAMEPORT_L4=m
CONFIG_GAMEPORT_EMU10K1=m
CONFIG_GAMEPORT_FM801=m

#
# Character devices
#
CONFIG_VT=y
CONFIG_VT_CONSOLE=y
CONFIG_HW_CONSOLE=y
# CONFIG_VT_HW_CONSOLE_BINDING is not set
CONFIG_SERIAL_NONSTANDARD=y
CONFIG_ROCKETPORT=m
CONFIG_CYCLADES=m
# CONFIG_CYZ_INTR is not set
# CONFIG_DIGIEPCA is not set
# CONFIG_ESPSERIAL is not set
# CONFIG_MOXA_INTELLIO is not set
CONFIG_MOXA_SMARTIO=m
CONFIG_MOXA_SMARTIO_NEW=m
# CONFIG_ISI is not set
CONFIG_SYNCLINK=m
CONFIG_SYNCLINKMP=m
CONFIG_SYNCLINK_GT=m
CONFIG_N_HDLC=m
# CONFIG_SPECIALIX is not set
CONFIG_SX=m
# CONFIG_RIO is not set
CONFIG_STALDRV=y

#
# Serial drivers
#
CONFIG_SERIAL_8250=y
CONFIG_SERIAL_8250_CONSOLE=y
CONFIG_FIX_EARLYCON_MEM=y
CONFIG_SERIAL_8250_PCI=y
CONFIG_SERIAL_8250_PNP=y
CONFIG_SERIAL_8250_CS=m
CONFIG_SERIAL_8250_NR_UARTS=32
CONFIG_SERIAL_8250_RUNTIME_UARTS=4
CONFIG_SERIAL_8250_EXTENDED=y
CONFIG_SERIAL_8250_MANY_PORTS=y
CONFIG_SERIAL_8250_FOURPORT=m
CONFIG_SERIAL_8250_ACCENT=m
CONFIG_SERIAL_8250_BOCA=m
CONFIG_SERIAL_8250_EXAR_ST16C554=m
CONFIG_SERIAL_8250_HUB6=m
CONFIG_SERIAL_8250_SHARE_IRQ=y
# CONFIG_SERIAL_8250_DETECT_IRQ is not set
CONFIG_SERIAL_8250_RSA=y

#
# Non-8250 serial port support
#
CONFIG_SERIAL_CORE=y
CONFIG_SERIAL_CORE_CONSOLE=y
CONFIG_SERIAL_JSM=m
CONFIG_UNIX98_PTYS=y
# CONFIG_LEGACY_PTYS is not set
CONFIG_PRINTER=m
# CONFIG_LP_CONSOLE is not set
CONFIG_PPDEV=m
CONFIG_HVC_DRIVER=y
CONFIG_VIRTIO_CONSOLE=y
CONFIG_IPMI_HANDLER=m
# CONFIG_IPMI_PANIC_EVENT is not set
CONFIG_IPMI_DEVICE_INTERFACE=m
CONFIG_IPMI_SI=m
CONFIG_IPMI_WATCHDOG=m
CONFIG_IPMI_POWEROFF=m
CONFIG_HW_RANDOM=y
CONFIG_HW_RANDOM_INTEL=m
CONFIG_HW_RANDOM_AMD=m
CONFIG_HW_RANDOM_GEODE=m
CONFIG_HW_RANDOM_VIA=m
CONFIG_NVRAM=m
CONFIG_RTC=m
CONFIG_GEN_RTC=m
CONFIG_GEN_RTC_X=y
CONFIG_DTLK=m
CONFIG_R3964=m
CONFIG_APPLICOM=m
CONFIG_SONYPI=m

#
# PCMCIA character devices
#
CONFIG_SYNCLINK_CS=m
CONFIG_CARDMAN_4000=m
CONFIG_CARDMAN_4040=m
CONFIG_MWAVE=m
CONFIG_SCx200_GPIO=m
CONFIG_PC8736x_GPIO=m
CONFIG_NSC_GPIO=m
CONFIG_CS5535_GPIO=m
CONFIG_RAW_DRIVER=m
CONFIG_MAX_RAW_DEVS=256
CONFIG_HPET=y
# CONFIG_HPET_RTC_IRQ is not set
CONFIG_HPET_MMAP=y
CONFIG_HANGCHECK_TIMER=m
CONFIG_TCG_TPM=m
CONFIG_TCG_TIS=m
CONFIG_TCG_NSC=m
CONFIG_TCG_ATMEL=m
CONFIG_TCG_INFINEON=m
CONFIG_TELCLOCK=m
CONFIG_DEVPORT=y
CONFIG_I2C=m
CONFIG_I2C_BOARDINFO=y
CONFIG_I2C_CHARDEV=m

#
# I2C Algorithms
#
CONFIG_I2C_ALGOBIT=m
CONFIG_I2C_ALGOPCF=m
CONFIG_I2C_ALGOPCA=m

#
# I2C Hardware Bus support
#
CONFIG_I2C_ALI1535=m
CONFIG_I2C_ALI1563=m
CONFIG_I2C_ALI15X3=m
CONFIG_I2C_AMD756=m
CONFIG_I2C_AMD756_S4882=m
CONFIG_I2C_AMD8111=m
CONFIG_I2C_I801=m
CONFIG_I2C_I810=m
CONFIG_I2C_PIIX4=m
CONFIG_I2C_NFORCE2=m
CONFIG_I2C_OCORES=m
CONFIG_I2C_PARPORT=m
CONFIG_I2C_PARPORT_LIGHT=m
CONFIG_I2C_PROSAVAGE=m
CONFIG_I2C_SAVAGE4=m
CONFIG_I2C_SIMTEC=m
CONFIG_SCx200_I2C=m
CONFIG_SCx200_I2C_SCL=12
CONFIG_SCx200_I2C_SDA=13
CONFIG_SCx200_ACB=m
CONFIG_I2C_SIS5595=m
CONFIG_I2C_SIS630=m
CONFIG_I2C_SIS96X=m
CONFIG_I2C_TAOS_EVM=m
CONFIG_I2C_STUB=m
CONFIG_I2C_TINY_USB=m
CONFIG_I2C_VIA=m
CONFIG_I2C_VIAPRO=m
CONFIG_I2C_VOODOO3=m
CONFIG_I2C_PCA_ISA=m

#
# Miscellaneous I2C Chip support
#
CONFIG_SENSORS_DS1337=m
CONFIG_SENSORS_DS1374=m
CONFIG_DS1682=m
CONFIG_SENSORS_EEPROM=m
CONFIG_SENSORS_PCF8574=m
CONFIG_SENSORS_PCA9539=m
CONFIG_SENSORS_PCF8591=m
CONFIG_SENSORS_MAX6875=m
CONFIG_SENSORS_TSL2550=m
# CONFIG_I2C_DEBUG_CORE is not set
# CONFIG_I2C_DEBUG_ALGO is not set
# CONFIG_I2C_DEBUG_BUS is not set
# CONFIG_I2C_DEBUG_CHIP is not set

#
# SPI support
#
CONFIG_SPI=y
# CONFIG_SPI_DEBUG is not set
CONFIG_SPI_MASTER=y

#
# SPI Master Controller Drivers
#
CONFIG_SPI_BITBANG=m
CONFIG_SPI_BUTTERFLY=m
CONFIG_SPI_LM70_LLP=m

#
# SPI Protocol Masters
#
CONFIG_SPI_AT25=m
# CONFIG_SPI_SPIDEV is not set
CONFIG_SPI_TLE62X0=m
CONFIG_W1=m
CONFIG_W1_CON=y

#
# 1-wire Bus Masters
#
CONFIG_W1_MASTER_MATROX=m
CONFIG_W1_MASTER_DS2490=m
CONFIG_W1_MASTER_DS2482=m

#
# 1-wire Slaves
#
CONFIG_W1_SLAVE_THERM=m
CONFIG_W1_SLAVE_SMEM=m
CONFIG_W1_SLAVE_DS2433=m
# CONFIG_W1_SLAVE_DS2433_CRC is not set
CONFIG_W1_SLAVE_DS2760=m
CONFIG_POWER_SUPPLY=y
# CONFIG_POWER_SUPPLY_DEBUG is not set
CONFIG_PDA_POWER=m
CONFIG_BATTERY_DS2760=m
CONFIG_HWMON=y
CONFIG_HWMON_VID=m
CONFIG_SENSORS_ABITUGURU=m
CONFIG_SENSORS_ABITUGURU3=m
CONFIG_SENSORS_AD7418=m
CONFIG_SENSORS_ADM1021=m
CONFIG_SENSORS_ADM1025=m
CONFIG_SENSORS_ADM1026=m
CONFIG_SENSORS_ADM1029=m
CONFIG_SENSORS_ADM1031=m
CONFIG_SENSORS_ADM9240=m
CONFIG_SENSORS_ADT7470=m
CONFIG_SENSORS_K8TEMP=m
CONFIG_SENSORS_ASB100=m
CONFIG_SENSORS_ATXP1=m
CONFIG_SENSORS_DS1621=m
CONFIG_SENSORS_I5K_AMB=m
CONFIG_SENSORS_F71805F=m
CONFIG_SENSORS_F71882FG=m
CONFIG_SENSORS_F75375S=m
CONFIG_SENSORS_FSCHER=m
CONFIG_SENSORS_FSCPOS=m
CONFIG_SENSORS_FSCHMD=m
CONFIG_SENSORS_GL518SM=m
CONFIG_SENSORS_GL520SM=m
CONFIG_SENSORS_CORETEMP=m
CONFIG_SENSORS_IBMPEX=m
CONFIG_SENSORS_IT87=m
CONFIG_SENSORS_LM63=m
CONFIG_SENSORS_LM70=m
CONFIG_SENSORS_LM75=m
CONFIG_SENSORS_LM77=m
CONFIG_SENSORS_LM78=m
CONFIG_SENSORS_LM80=m
CONFIG_SENSORS_LM83=m
CONFIG_SENSORS_LM85=m
CONFIG_SENSORS_LM87=m
CONFIG_SENSORS_LM90=m
CONFIG_SENSORS_LM92=m
CONFIG_SENSORS_LM93=m
CONFIG_SENSORS_MAX1619=m
CONFIG_SENSORS_MAX6650=m
CONFIG_SENSORS_PC87360=m
CONFIG_SENSORS_PC87427=m
CONFIG_SENSORS_SIS5595=m
CONFIG_SENSORS_DME1737=m
CONFIG_SENSORS_SMSC47M1=m
CONFIG_SENSORS_SMSC47M192=m
CONFIG_SENSORS_SMSC47B397=m
CONFIG_SENSORS_THMC50=m
CONFIG_SENSORS_VIA686A=m
CONFIG_SENSORS_VT1211=m
CONFIG_SENSORS_VT8231=m
CONFIG_SENSORS_W83781D=m
CONFIG_SENSORS_W83791D=m
CONFIG_SENSORS_W83792D=m
CONFIG_SENSORS_W83793=m
CONFIG_SENSORS_W83L785TS=m
CONFIG_SENSORS_W83627HF=m
CONFIG_SENSORS_W83627EHF=m
CONFIG_SENSORS_HDAPS=m
CONFIG_SENSORS_APPLESMC=m
# CONFIG_HWMON_DEBUG_CHIP is not set
CONFIG_WATCHDOG=y
# CONFIG_WATCHDOG_NOWAYOUT is not set

#
# Watchdog Device Drivers
#
CONFIG_SOFT_WATCHDOG=m
CONFIG_ACQUIRE_WDT=m
CONFIG_ADVANTECH_WDT=m
CONFIG_ALIM1535_WDT=m
CONFIG_ALIM7101_WDT=m
CONFIG_SC520_WDT=m
CONFIG_EUROTECH_WDT=m
CONFIG_IB700_WDT=m
CONFIG_IBMASR=m
CONFIG_WAFER_WDT=m
CONFIG_I6300ESB_WDT=m
CONFIG_ITCO_WDT=m
# CONFIG_ITCO_VENDOR_SUPPORT is not set
CONFIG_IT8712F_WDT=m
CONFIG_SC1200_WDT=m
CONFIG_SCx200_WDT=m
CONFIG_PC87413_WDT=m
CONFIG_60XX_WDT=m
CONFIG_SBC8360_WDT=m
CONFIG_SBC7240_WDT=m
CONFIG_CPU5_WDT=m
CONFIG_SMSC37B787_WDT=m
CONFIG_W83627HF_WDT=m
CONFIG_W83697HF_WDT=m
CONFIG_W83877F_WDT=m
CONFIG_W83977F_WDT=m
CONFIG_MACHZ_WDT=m
CONFIG_SBC_EPX_C3_WATCHDOG=m

#
# ISA-based Watchdog Cards
#
CONFIG_PCWATCHDOG=m
CONFIG_MIXCOMWD=m
CONFIG_WDT=m
CONFIG_WDT_501=y

#
# PCI-based Watchdog Cards
#
CONFIG_PCIPCWATCHDOG=m
CONFIG_WDTPCI=m
CONFIG_WDT_501_PCI=y

#
# USB-based Watchdog Cards
#
CONFIG_USBPCWATCHDOG=m

#
# Sonics Silicon Backplane
#
CONFIG_SSB_POSSIBLE=y
CONFIG_SSB=m
CONFIG_SSB_PCIHOST_POSSIBLE=y
CONFIG_SSB_PCIHOST=y
CONFIG_SSB_PCMCIAHOST_POSSIBLE=y
CONFIG_SSB_PCMCIAHOST=y
# CONFIG_SSB_DEBUG is not set
CONFIG_SSB_DRIVER_PCICORE_POSSIBLE=y
CONFIG_SSB_DRIVER_PCICORE=y

#
# Multifunction device drivers
#
CONFIG_MFD_SM501=m

#
# Multimedia devices
#
CONFIG_VIDEO_DEV=m
CONFIG_VIDEO_V4L1=y
CONFIG_VIDEO_V4L1_COMPAT=y
CONFIG_VIDEO_V4L2=y
CONFIG_VIDEO_CAPTURE_DRIVERS=y
# CONFIG_VIDEO_ADV_DEBUG is not set
CONFIG_VIDEO_HELPER_CHIPS_AUTO=y
CONFIG_VIDEO_TVAUDIO=m
CONFIG_VIDEO_TDA7432=m
CONFIG_VIDEO_TDA9840=m
CONFIG_VIDEO_TDA9875=m
CONFIG_VIDEO_TEA6415C=m
CONFIG_VIDEO_TEA6420=m
CONFIG_VIDEO_MSP3400=m
CONFIG_VIDEO_CS53L32A=m
CONFIG_VIDEO_WM8775=m
CONFIG_VIDEO_WM8739=m
CONFIG_VIDEO_VP27SMPX=m
CONFIG_VIDEO_BT819=m
CONFIG_VIDEO_BT856=m
CONFIG_VIDEO_KS0127=m
CONFIG_VIDEO_OV7670=m
CONFIG_VIDEO_SAA7110=m
CONFIG_VIDEO_SAA7111=m
CONFIG_VIDEO_SAA7114=m
CONFIG_VIDEO_SAA711X=m
CONFIG_VIDEO_TVP5150=m
CONFIG_VIDEO_VPX3220=m
CONFIG_VIDEO_CX25840=m
CONFIG_VIDEO_CX2341X=m
CONFIG_VIDEO_SAA7127=m
CONFIG_VIDEO_SAA7185=m
CONFIG_VIDEO_ADV7170=m
CONFIG_VIDEO_ADV7175=m
CONFIG_VIDEO_UPD64031A=m
CONFIG_VIDEO_UPD64083=m
CONFIG_VIDEO_VIVI=m
CONFIG_VIDEO_BT848=m
CONFIG_VIDEO_BT848_DVB=y
CONFIG_VIDEO_SAA6588=m
CONFIG_VIDEO_PMS=m
CONFIG_VIDEO_BWQCAM=m
CONFIG_VIDEO_CQCAM=m
CONFIG_VIDEO_W9966=m
CONFIG_VIDEO_CPIA=m
CONFIG_VIDEO_CPIA_PP=m
CONFIG_VIDEO_CPIA_USB=m
CONFIG_VIDEO_CPIA2=m
CONFIG_VIDEO_SAA5246A=m
CONFIG_VIDEO_SAA5249=m
CONFIG_TUNER_3036=m
CONFIG_VIDEO_STRADIS=m
CONFIG_VIDEO_ZORAN_ZR36060=m
CONFIG_VIDEO_ZORAN=m
CONFIG_VIDEO_ZORAN_BUZ=m
CONFIG_VIDEO_ZORAN_DC10=m
CONFIG_VIDEO_ZORAN_DC30=m
CONFIG_VIDEO_ZORAN_LML33=m
CONFIG_VIDEO_ZORAN_LML33R10=m
CONFIG_VIDEO_ZORAN_AVS6EYES=m
CONFIG_VIDEO_MEYE=m
CONFIG_VIDEO_SAA7134=m
CONFIG_VIDEO_SAA7134_ALSA=m
CONFIG_VIDEO_SAA7134_OSS=m
CONFIG_VIDEO_SAA7134_DVB=m
CONFIG_VIDEO_MXB=m
CONFIG_VIDEO_DPC=m
CONFIG_VIDEO_HEXIUM_ORION=m
CONFIG_VIDEO_HEXIUM_GEMINI=m
CONFIG_VIDEO_CX88=m
CONFIG_VIDEO_CX88_ALSA=m
CONFIG_VIDEO_CX88_BLACKBIRD=m
CONFIG_VIDEO_CX88_DVB=m
CONFIG_VIDEO_CX88_VP3054=m
CONFIG_VIDEO_CX23885=m
CONFIG_VIDEO_IVTV=m
CONFIG_VIDEO_FB_IVTV=m
CONFIG_VIDEO_CAFE_CCIC=m
CONFIG_V4L_USB_DRIVERS=y
CONFIG_VIDEO_PVRUSB2=m
CONFIG_VIDEO_PVRUSB2_29XXX=y
CONFIG_VIDEO_PVRUSB2_24XXX=y
CONFIG_VIDEO_PVRUSB2_SYSFS=y
# CONFIG_VIDEO_PVRUSB2_DEBUGIFC is not set
CONFIG_VIDEO_EM28XX=m
CONFIG_VIDEO_USBVISION=m
CONFIG_VIDEO_USBVIDEO=m
CONFIG_USB_VICAM=m
CONFIG_USB_IBMCAM=m
CONFIG_USB_KONICAWC=m
CONFIG_USB_QUICKCAM_MESSENGER=m
CONFIG_USB_ET61X251=m
CONFIG_VIDEO_OVCAMCHIP=m
# CONFIG_USB_W9968CF is not set
CONFIG_USB_OV511=m
CONFIG_USB_SE401=m
CONFIG_USB_SN9C102=m
CONFIG_USB_STV680=m
CONFIG_USB_ZC0301=m
CONFIG_USB_PWC=m
# CONFIG_USB_PWC_DEBUG is not set
CONFIG_USB_ZR364XX=m
CONFIG_RADIO_ADAPTERS=y
CONFIG_RADIO_CADET=m
CONFIG_RADIO_RTRACK=m
CONFIG_RADIO_RTRACK2=m
CONFIG_RADIO_AZTECH=m
CONFIG_RADIO_GEMTEK=m
CONFIG_RADIO_GEMTEK_PCI=m
CONFIG_RADIO_MAXIRADIO=m
CONFIG_RADIO_MAESTRO=m
CONFIG_RADIO_SF16FMI=m
CONFIG_RADIO_SF16FMR2=m
CONFIG_RADIO_TERRATEC=m
CONFIG_RADIO_TRUST=m
CONFIG_RADIO_TYPHOON=m
CONFIG_RADIO_TYPHOON_PROC_FS=y
CONFIG_RADIO_ZOLTRIX=m
CONFIG_USB_DSBR=m
CONFIG_DVB_CORE=m
CONFIG_DVB_CORE_ATTACH=y
CONFIG_DVB_CAPTURE_DRIVERS=y

#
# Supported SAA7146 based PCI Adapters
#
CONFIG_DVB_AV7110=m
CONFIG_DVB_AV7110_OSD=y
CONFIG_DVB_BUDGET=m
CONFIG_DVB_BUDGET_CI=m
CONFIG_DVB_BUDGET_AV=m
CONFIG_DVB_BUDGET_PATCH=m

#
# Supported USB Adapters
#
CONFIG_DVB_USB=m
# CONFIG_DVB_USB_DEBUG is not set
CONFIG_DVB_USB_A800=m
CONFIG_DVB_USB_DIBUSB_MB=m
CONFIG_DVB_USB_DIBUSB_MB_FAULTY=y
CONFIG_DVB_USB_DIBUSB_MC=m
CONFIG_DVB_USB_DIB0700=m
CONFIG_DVB_USB_UMT_010=m
CONFIG_DVB_USB_CXUSB=m
CONFIG_DVB_USB_M920X=m
CONFIG_DVB_USB_GL861=m
CONFIG_DVB_USB_AU6610=m
CONFIG_DVB_USB_DIGITV=m
CONFIG_DVB_USB_VP7045=m
CONFIG_DVB_USB_VP702X=m
CONFIG_DVB_USB_GP8PSK=m
CONFIG_DVB_USB_NOVA_T_USB2=m
CONFIG_DVB_USB_TTUSB2=m
CONFIG_DVB_USB_DTT200U=m
CONFIG_DVB_USB_OPERA1=m
CONFIG_DVB_USB_AF9005=m
CONFIG_DVB_USB_AF9005_REMOTE=m
CONFIG_DVB_TTUSB_DEC=m
CONFIG_DVB_CINERGYT2=m
# CONFIG_DVB_CINERGYT2_TUNING is not set

#
# Supported FlexCopII (B2C2) Adapters
#
CONFIG_DVB_B2C2_FLEXCOP=m
CONFIG_DVB_B2C2_FLEXCOP_PCI=m
CONFIG_DVB_B2C2_FLEXCOP_USB=m
# CONFIG_DVB_B2C2_FLEXCOP_DEBUG is not set

#
# Supported BT878 Adapters
#
CONFIG_DVB_BT8XX=m

#
# Supported Pluto2 Adapters
#
CONFIG_DVB_PLUTO2=m

#
# Supported DVB Frontends
#

#
# Customise DVB Frontends
#
# CONFIG_DVB_FE_CUSTOMISE is not set

#
# DVB-S (satellite) frontends
#
CONFIG_DVB_STV0299=m
CONFIG_DVB_CX24110=m
CONFIG_DVB_CX24123=m
CONFIG_DVB_TDA8083=m
CONFIG_DVB_MT312=m
CONFIG_DVB_VES1X93=m
CONFIG_DVB_S5H1420=m
CONFIG_DVB_TDA10086=m

#
# DVB-T (terrestrial) frontends
#
CONFIG_DVB_SP8870=m
CONFIG_DVB_SP887X=m
CONFIG_DVB_CX22700=m
CONFIG_DVB_CX22702=m
CONFIG_DVB_L64781=m
CONFIG_DVB_TDA1004X=m
CONFIG_DVB_NXT6000=m
CONFIG_DVB_MT352=m
CONFIG_DVB_ZL10353=m
CONFIG_DVB_DIB3000MB=m
CONFIG_DVB_DIB3000MC=m
CONFIG_DVB_DIB7000M=m
CONFIG_DVB_DIB7000P=m

#
# DVB-C (cable) frontends
#
CONFIG_DVB_VES1820=m
CONFIG_DVB_TDA10021=m
CONFIG_DVB_TDA10023=m
CONFIG_DVB_STV0297=m

#
# ATSC (North American/Korean Terrestrial/Cable DTV) frontends
#
CONFIG_DVB_NXT200X=m
CONFIG_DVB_OR51211=m
CONFIG_DVB_OR51132=m
CONFIG_DVB_BCM3510=m
CONFIG_DVB_LGDT330X=m
CONFIG_DVB_S5H1409=m

#
# Tuners/PLL support
#
CONFIG_DVB_PLL=m
CONFIG_DVB_TDA826X=m
CONFIG_DVB_TDA827X=m
CONFIG_DVB_TUNER_QT1010=m
CONFIG_DVB_TUNER_MT2060=m
CONFIG_DVB_TUNER_MT2266=m
CONFIG_DVB_TUNER_MT2131=m
CONFIG_DVB_TUNER_DIB0070=m

#
# Miscellaneous devices
#
CONFIG_DVB_LNBP21=m
CONFIG_DVB_ISL6421=m
CONFIG_DVB_TUA6100=m
CONFIG_VIDEO_SAA7146=m
CONFIG_VIDEO_SAA7146_VV=m
CONFIG_VIDEO_TUNER=m
# CONFIG_VIDEO_TUNER_CUSTOMIZE is not set
CONFIG_TUNER_MT20XX=m
CONFIG_TUNER_TDA8290=m
CONFIG_TUNER_TEA5761=m
CONFIG_TUNER_TEA5767=m
CONFIG_TUNER_SIMPLE=m
CONFIG_VIDEOBUF_GEN=m
CONFIG_VIDEOBUF_DMA_SG=m
CONFIG_VIDEOBUF_VMALLOC=m
CONFIG_VIDEOBUF_DVB=m
CONFIG_VIDEO_BTCX=m
CONFIG_VIDEO_IR_I2C=m
CONFIG_VIDEO_IR=m
CONFIG_VIDEO_TVEEPROM=m
CONFIG_DAB=y
CONFIG_USB_DABUSB=m

#
# Graphics support
#
CONFIG_AGP=m
CONFIG_AGP_ALI=m
CONFIG_AGP_ATI=m
CONFIG_AGP_AMD=m
CONFIG_AGP_AMD64=m
CONFIG_AGP_INTEL=m
CONFIG_AGP_NVIDIA=m
CONFIG_AGP_SIS=m
CONFIG_AGP_SWORKS=m
CONFIG_AGP_VIA=m
CONFIG_AGP_EFFICEON=m
CONFIG_DRM=m
CONFIG_DRM_TDFX=m
CONFIG_DRM_R128=m
CONFIG_DRM_RADEON=m
CONFIG_DRM_I810=m
CONFIG_DRM_I830=m
CONFIG_DRM_I915=m
CONFIG_DRM_MGA=m
CONFIG_DRM_SIS=m
CONFIG_DRM_VIA=m
CONFIG_DRM_SAVAGE=m
CONFIG_VGASTATE=m
CONFIG_VIDEO_OUTPUT_CONTROL=m
CONFIG_FB=y
CONFIG_FIRMWARE_EDID=y
CONFIG_FB_DDC=m
CONFIG_FB_CFB_FILLRECT=y
CONFIG_FB_CFB_COPYAREA=y
CONFIG_FB_CFB_IMAGEBLIT=y
# CONFIG_FB_CFB_REV_PIXELS_IN_BYTE is not set
CONFIG_FB_SYS_FILLRECT=m
CONFIG_FB_SYS_COPYAREA=m
CONFIG_FB_SYS_IMAGEBLIT=m
CONFIG_FB_SYS_FOPS=m
CONFIG_FB_DEFERRED_IO=y
CONFIG_FB_SVGALIB=m
# CONFIG_FB_MACMODES is not set
CONFIG_FB_BACKLIGHT=y
CONFIG_FB_MODE_HELPERS=y
CONFIG_FB_TILEBLITTING=y

#
# Frame buffer hardware drivers
#
CONFIG_FB_CIRRUS=m
CONFIG_FB_PM2=m
CONFIG_FB_PM2_FIFO_DISCONNECT=y
CONFIG_FB_CYBER2000=m
CONFIG_FB_ARC=m
# CONFIG_FB_ASILIANT is not set
# CONFIG_FB_IMSTT is not set
CONFIG_FB_VGA16=m
# CONFIG_FB_UVESA is not set
CONFIG_FB_VESA=y
CONFIG_FB_EFI=y
# CONFIG_FB_IMAC is not set
CONFIG_FB_HECUBA=m
CONFIG_FB_HGA=m
# CONFIG_FB_HGA_ACCEL is not set
CONFIG_FB_S1D13XXX=m
CONFIG_FB_NVIDIA=m
CONFIG_FB_NVIDIA_I2C=y
# CONFIG_FB_NVIDIA_DEBUG is not set
CONFIG_FB_NVIDIA_BACKLIGHT=y
# CONFIG_FB_RIVA is not set
CONFIG_FB_I810=m
# CONFIG_FB_I810_GTF is not set
CONFIG_FB_LE80578=m
CONFIG_FB_CARILLO_RANCH=m
CONFIG_FB_INTEL=m
# CONFIG_FB_INTEL_DEBUG is not set
CONFIG_FB_INTEL_I2C=y
CONFIG_FB_MATROX=m
CONFIG_FB_MATROX_MILLENIUM=y
CONFIG_FB_MATROX_MYSTIQUE=y
CONFIG_FB_MATROX_G=y
CONFIG_FB_MATROX_I2C=m
CONFIG_FB_MATROX_MAVEN=m
CONFIG_FB_MATROX_MULTIHEAD=y
CONFIG_FB_RADEON=m
CONFIG_FB_RADEON_I2C=y
CONFIG_FB_RADEON_BACKLIGHT=y
# CONFIG_FB_RADEON_DEBUG is not set
CONFIG_FB_ATY128=m
CONFIG_FB_ATY128_BACKLIGHT=y
CONFIG_FB_ATY=m
CONFIG_FB_ATY_CT=y
CONFIG_FB_ATY_GENERIC_LCD=y
CONFIG_FB_ATY_GX=y
CONFIG_FB_ATY_BACKLIGHT=y
CONFIG_FB_S3=m
CONFIG_FB_SAVAGE=m
CONFIG_FB_SAVAGE_I2C=y
# CONFIG_FB_SAVAGE_ACCEL is not set
CONFIG_FB_SIS=m
CONFIG_FB_SIS_300=y
CONFIG_FB_SIS_315=y
CONFIG_FB_NEOMAGIC=m
CONFIG_FB_KYRO=m
CONFIG_FB_3DFX=m
# CONFIG_FB_3DFX_ACCEL is not set
CONFIG_FB_VOODOO1=m
CONFIG_FB_VT8623=m
CONFIG_FB_CYBLA=m
CONFIG_FB_TRIDENT=m
# CONFIG_FB_TRIDENT_ACCEL is not set
CONFIG_FB_ARK=m
CONFIG_FB_PM3=m
CONFIG_FB_GEODE=y
CONFIG_FB_GEODE_LX=m
CONFIG_FB_GEODE_GX=m
# CONFIG_FB_GEODE_GX_SET_FBSIZE is not set
CONFIG_FB_GEODE_GX1=m
CONFIG_FB_SM501=m
CONFIG_FB_VIRTUAL=m
CONFIG_BACKLIGHT_LCD_SUPPORT=y
# CONFIG_LCD_CLASS_DEVICE is not set
CONFIG_BACKLIGHT_CLASS_DEVICE=y
# CONFIG_BACKLIGHT_CORGI is not set
CONFIG_BACKLIGHT_PROGEAR=m

#
# Display device support
#
CONFIG_DISPLAY_SUPPORT=m

#
# Display hardware drivers
#

#
# Console display driver support
#
CONFIG_VGA_CONSOLE=y
# CONFIG_VGACON_SOFT_SCROLLBACK is not set
CONFIG_VIDEO_SELECT=y
CONFIG_MDA_CONSOLE=m
CONFIG_DUMMY_CONSOLE=y
CONFIG_FRAMEBUFFER_CONSOLE=y
# CONFIG_FRAMEBUFFER_CONSOLE_DETECT_PRIMARY is not set
CONFIG_FRAMEBUFFER_CONSOLE_ROTATION=y
# CONFIG_FONTS is not set
CONFIG_FONT_8x8=y
CONFIG_FONT_8x16=y
# CONFIG_LOGO is not set

#
# Sound
#
CONFIG_SOUND=m

#
# Advanced Linux Sound Architecture
#
CONFIG_SND=m
CONFIG_SND_TIMER=m
CONFIG_SND_PCM=m
CONFIG_SND_HWDEP=m
CONFIG_SND_RAWMIDI=m
CONFIG_SND_SEQUENCER=m
CONFIG_SND_SEQ_DUMMY=m
CONFIG_SND_OSSEMUL=y
CONFIG_SND_MIXER_OSS=m
CONFIG_SND_PCM_OSS=m
CONFIG_SND_PCM_OSS_PLUGINS=y
CONFIG_SND_SEQUENCER_OSS=y
CONFIG_SND_RTCTIMER=m
CONFIG_SND_SEQ_RTCTIMER_DEFAULT=y
# CONFIG_SND_DYNAMIC_MINORS is not set
CONFIG_SND_SUPPORT_OLD_API=y
CONFIG_SND_VERBOSE_PROCFS=y
# CONFIG_SND_VERBOSE_PRINTK is not set
# CONFIG_SND_DEBUG is not set

#
# Generic devices
#
CONFIG_SND_MPU401_UART=m
CONFIG_SND_OPL3_LIB=m
CONFIG_SND_OPL4_LIB=m
CONFIG_SND_VX_LIB=m
CONFIG_SND_AC97_CODEC=m
CONFIG_SND_DUMMY=m
CONFIG_SND_VIRMIDI=m
CONFIG_SND_MTPAV=m
CONFIG_SND_MTS64=m
CONFIG_SND_SERIAL_U16550=m
CONFIG_SND_MPU401=m
CONFIG_SND_PORTMAN2X4=m
CONFIG_SND_AD1848_LIB=m
CONFIG_SND_CS4231_LIB=m
CONFIG_SND_SB_COMMON=m
CONFIG_SND_SB8_DSP=m
CONFIG_SND_SB16_DSP=m

#
# ISA devices
#
CONFIG_SND_ADLIB=m
CONFIG_SND_AD1816A=m
CONFIG_SND_AD1848=m
CONFIG_SND_ALS100=m
CONFIG_SND_AZT2320=m
CONFIG_SND_CMI8330=m
CONFIG_SND_CS4231=m
CONFIG_SND_CS4232=m
CONFIG_SND_CS4236=m
CONFIG_SND_DT019X=m
CONFIG_SND_ES968=m
CONFIG_SND_ES1688=m
CONFIG_SND_ES18XX=m
CONFIG_SND_SC6000=m
CONFIG_SND_GUS_SYNTH=m
CONFIG_SND_GUSCLASSIC=m
CONFIG_SND_GUSEXTREME=m
CONFIG_SND_GUSMAX=m
CONFIG_SND_INTERWAVE=m
CONFIG_SND_INTERWAVE_STB=m
CONFIG_SND_OPL3SA2=m
CONFIG_SND_OPTI92X_AD1848=m
CONFIG_SND_OPTI92X_CS4231=m
CONFIG_SND_OPTI93X=m
CONFIG_SND_MIRO=m
CONFIG_SND_SB8=m
CONFIG_SND_SB16=m
CONFIG_SND_SBAWE=m
CONFIG_SND_SB16_CSP=y
CONFIG_SND_SB16_CSP_FIRMWARE_IN_KERNEL=y
CONFIG_SND_SGALAXY=m
CONFIG_SND_SSCAPE=m
CONFIG_SND_WAVEFRONT=m
CONFIG_SND_WAVEFRONT_FIRMWARE_IN_KERNEL=y

#
# PCI devices
#
CONFIG_SND_AD1889=m
CONFIG_SND_ALS300=m
CONFIG_SND_ALS4000=m
CONFIG_SND_ALI5451=m
CONFIG_SND_ATIIXP=m
CONFIG_SND_ATIIXP_MODEM=m
CONFIG_SND_AU8810=m
CONFIG_SND_AU8820=m
CONFIG_SND_AU8830=m
CONFIG_SND_AZT3328=m
CONFIG_SND_BT87X=m
# CONFIG_SND_BT87X_OVERCLOCK is not set
CONFIG_SND_CA0106=m
CONFIG_SND_CMIPCI=m
CONFIG_SND_CS4281=m
CONFIG_SND_CS5530=m
CONFIG_SND_CS5535AUDIO=m
CONFIG_SND_DARLA20=m
CONFIG_SND_GINA20=m
CONFIG_SND_LAYLA20=m
CONFIG_SND_DARLA24=m
CONFIG_SND_GINA24=m
CONFIG_SND_LAYLA24=m
CONFIG_SND_MONA=m
CONFIG_SND_MIA=m
CONFIG_SND_ECHO3G=m
CONFIG_SND_INDIGO=m
CONFIG_SND_INDIGOIO=m
CONFIG_SND_INDIGODJ=m
CONFIG_SND_EMU10K1=m
CONFIG_SND_EMU10K1X=m
CONFIG_SND_ENS1370=m
CONFIG_SND_ENS1371=m
CONFIG_SND_ES1938=m
CONFIG_SND_ES1968=m
CONFIG_SND_FM801=m
CONFIG_SND_FM801_TEA575X_BOOL=y
CONFIG_SND_FM801_TEA575X=m
CONFIG_SND_HDA_INTEL=m
# CONFIG_SND_HDA_HWDEP is not set
CONFIG_SND_HDA_CODEC_REALTEK=y
CONFIG_SND_HDA_CODEC_ANALOG=y
CONFIG_SND_HDA_CODEC_SIGMATEL=y
CONFIG_SND_HDA_CODEC_VIA=y
CONFIG_SND_HDA_CODEC_ATIHDMI=y
CONFIG_SND_HDA_CODEC_CONEXANT=y
CONFIG_SND_HDA_CODEC_CMEDIA=y
CONFIG_SND_HDA_CODEC_SI3054=y
CONFIG_SND_HDA_GENERIC=y
CONFIG_SND_HDA_POWER_SAVE=y
CONFIG_SND_HDA_POWER_SAVE_DEFAULT=0
CONFIG_SND_HDSP=m
CONFIG_SND_HDSPM=m
CONFIG_SND_ICE1712=m
CONFIG_SND_ICE1724=m
CONFIG_SND_INTEL8X0=m
CONFIG_SND_INTEL8X0M=m
CONFIG_SND_KORG1212=m
CONFIG_SND_MAESTRO3=m
CONFIG_SND_MIXART=m
CONFIG_SND_NM256=m
CONFIG_SND_PCXHR=m
CONFIG_SND_RIPTIDE=m
CONFIG_SND_RME32=m
CONFIG_SND_RME96=m
CONFIG_SND_RME9652=m
CONFIG_SND_SONICVIBES=m
CONFIG_SND_TRIDENT=m
CONFIG_SND_VIA82XX=m
CONFIG_SND_VIA82XX_MODEM=m
CONFIG_SND_VX222=m
CONFIG_SND_YMFPCI=m
CONFIG_SND_AC97_POWER_SAVE=y
CONFIG_SND_AC97_POWER_SAVE_DEFAULT=0

#
# SPI devices
#

#
# USB devices
#
CONFIG_SND_USB_AUDIO=m
CONFIG_SND_USB_USX2Y=m
CONFIG_SND_USB_CAIAQ=m
CONFIG_SND_USB_CAIAQ_INPUT=y

#
# PCMCIA devices
#
CONFIG_SND_VXPOCKET=m
CONFIG_SND_PDAUDIOCF=m

#
# System on Chip audio support
#
# CONFIG_SND_SOC is not set

#
# SoC Audio support for SuperH
#

#
# Open Sound System
#
CONFIG_SOUND_PRIME=m
CONFIG_SOUND_TRIDENT=m
# CONFIG_SOUND_MSNDCLAS is not set
# CONFIG_SOUND_MSNDPIN is not set
CONFIG_SOUND_OSS=m
# CONFIG_SOUND_TRACEINIT is not set
# CONFIG_SOUND_DMAP is not set
CONFIG_SOUND_SSCAPE=m
CONFIG_SOUND_VMIDI=m
CONFIG_SOUND_TRIX=m
CONFIG_SOUND_MSS=m
CONFIG_SOUND_MPU401=m
CONFIG_SOUND_PAS=m
CONFIG_SOUND_PSS=m
CONFIG_PSS_MIXER=y
CONFIG_SOUND_SB=m
CONFIG_SOUND_YM3812=m
CONFIG_SOUND_UART6850=m
CONFIG_SOUND_AEDSP16=m
CONFIG_SC6600=y
CONFIG_SC6600_JOY=y
CONFIG_SC6600_CDROM=4
CONFIG_SC6600_CDROMBASE=0x0
# CONFIG_AEDSP16_MSS is not set
# CONFIG_AEDSP16_SBPRO is not set
CONFIG_SOUND_KAHLUA=m
CONFIG_AC97_BUS=m
CONFIG_HID_SUPPORT=y
CONFIG_HID=m
# CONFIG_HID_DEBUG is not set
CONFIG_HIDRAW=y

#
# USB Input Devices
#
CONFIG_USB_HID=m
CONFIG_USB_HIDINPUT_POWERBOOK=y
# CONFIG_HID_FF is not set
CONFIG_USB_HIDDEV=y

#
# USB HID Boot Protocol drivers
#
CONFIG_USB_KBD=m
CONFIG_USB_MOUSE=m
CONFIG_USB_SUPPORT=y
CONFIG_USB_ARCH_HAS_HCD=y
CONFIG_USB_ARCH_HAS_OHCI=y
CONFIG_USB_ARCH_HAS_EHCI=y
CONFIG_USB=m
# CONFIG_USB_DEBUG is not set

#
# Miscellaneous USB options
#
CONFIG_USB_DEVICEFS=y
CONFIG_USB_DEVICE_CLASS=y
# CONFIG_USB_DYNAMIC_MINORS is not set
CONFIG_USB_SUSPEND=y
# CONFIG_USB_PERSIST is not set
# CONFIG_USB_OTG is not set

#
# USB Host Controller Drivers
#
CONFIG_USB_EHCI_HCD=m
CONFIG_USB_EHCI_SPLIT_ISO=y
CONFIG_USB_EHCI_ROOT_HUB_TT=y
CONFIG_USB_EHCI_TT_NEWSCHED=y
CONFIG_USB_ISP116X_HCD=m
CONFIG_USB_OHCI_HCD=m
# CONFIG_USB_OHCI_HCD_SSB is not set
# CONFIG_USB_OHCI_BIG_ENDIAN_DESC is not set
# CONFIG_USB_OHCI_BIG_ENDIAN_MMIO is not set
CONFIG_USB_OHCI_LITTLE_ENDIAN=y
CONFIG_USB_UHCI_HCD=m
CONFIG_USB_U132_HCD=m
CONFIG_USB_SL811_HCD=m
CONFIG_USB_SL811_CS=m
CONFIG_USB_R8A66597_HCD=m

#
# USB Device Class drivers
#
CONFIG_USB_ACM=m
CONFIG_USB_PRINTER=m

#
# NOTE: USB_STORAGE enables SCSI, and 'SCSI disk support'
#

#
# may also be needed; see USB_STORAGE Help for more information
#
CONFIG_USB_STORAGE=m
# CONFIG_USB_STORAGE_DEBUG is not set
CONFIG_USB_STORAGE_DATAFAB=y
CONFIG_USB_STORAGE_FREECOM=y
CONFIG_USB_STORAGE_ISD200=y
CONFIG_USB_STORAGE_DPCM=y
CONFIG_USB_STORAGE_USBAT=y
CONFIG_USB_STORAGE_SDDR09=y
CONFIG_USB_STORAGE_SDDR55=y
CONFIG_USB_STORAGE_JUMPSHOT=y
CONFIG_USB_STORAGE_ALAUDA=y
CONFIG_USB_STORAGE_KARMA=y
# CONFIG_USB_LIBUSUAL is not set

#
# USB Imaging devices
#
CONFIG_USB_MDC800=m
CONFIG_USB_MICROTEK=m
CONFIG_USB_MON=y

#
# USB port drivers
#
CONFIG_USB_USS720=m

#
# USB Serial Converter support
#
CONFIG_USB_SERIAL=m
CONFIG_USB_SERIAL_GENERIC=y
CONFIG_USB_SERIAL_AIRCABLE=m
CONFIG_USB_SERIAL_AIRPRIME=m
CONFIG_USB_SERIAL_ARK3116=m
CONFIG_USB_SERIAL_BELKIN=m
CONFIG_USB_SERIAL_CH341=m
# CONFIG_USB_SERIAL_WHITEHEAT is not set
CONFIG_USB_SERIAL_DIGI_ACCELEPORT=m
CONFIG_USB_SERIAL_CP2101=m
CONFIG_USB_SERIAL_CYPRESS_M8=m
CONFIG_USB_SERIAL_EMPEG=m
CONFIG_USB_SERIAL_FTDI_SIO=m
CONFIG_USB_SERIAL_FUNSOFT=m
CONFIG_USB_SERIAL_VISOR=m
CONFIG_USB_SERIAL_IPAQ=m
CONFIG_USB_SERIAL_IR=m
# CONFIG_USB_SERIAL_EDGEPORT is not set
# CONFIG_USB_SERIAL_EDGEPORT_TI is not set
CONFIG_USB_SERIAL_GARMIN=m
CONFIG_USB_SERIAL_IPW=m
CONFIG_USB_SERIAL_KEYSPAN_PDA=m
CONFIG_USB_SERIAL_KLSI=m
CONFIG_USB_SERIAL_KOBIL_SCT=m
CONFIG_USB_SERIAL_MCT_U232=m
CONFIG_USB_SERIAL_MOS7720=m
CONFIG_USB_SERIAL_MOS7840=m
CONFIG_USB_SERIAL_NAVMAN=m
CONFIG_USB_SERIAL_PL2303=m
CONFIG_USB_SERIAL_OTI6858=m
CONFIG_USB_SERIAL_HP4X=m
CONFIG_USB_SERIAL_SAFE=m
# CONFIG_USB_SERIAL_SAFE_PADDED is not set
CONFIG_USB_SERIAL_SIERRAWIRELESS=m
# CONFIG_USB_SERIAL_TI is not set
CONFIG_USB_SERIAL_CYBERJACK=m
CONFIG_USB_SERIAL_XIRCOM=m
CONFIG_USB_SERIAL_OPTION=m
CONFIG_USB_SERIAL_OMNINET=m
CONFIG_USB_SERIAL_DEBUG=m
CONFIG_USB_EZUSB=y

#
# USB Miscellaneous drivers
#
CONFIG_USB_ADUTUX=m
CONFIG_USB_AUERSWALD=m
CONFIG_USB_RIO500=m
CONFIG_USB_LEGOTOWER=m
CONFIG_USB_LCD=m
CONFIG_USB_BERRY_CHARGE=m
CONFIG_USB_LED=m
CONFIG_USB_CYPRESS_CY7C63=m
CONFIG_USB_CYTHERM=m
CONFIG_USB_PHIDGET=m
CONFIG_USB_PHIDGETKIT=m
CONFIG_USB_PHIDGETMOTORCONTROL=m
CONFIG_USB_PHIDGETSERVO=m
CONFIG_USB_IDMOUSE=m
CONFIG_USB_FTDI_ELAN=m
CONFIG_USB_APPLEDISPLAY=m
CONFIG_USB_SISUSBVGA=m
CONFIG_USB_SISUSBVGA_CON=y
CONFIG_USB_LD=m
CONFIG_USB_TRANCEVIBRATOR=m
CONFIG_USB_IOWARRIOR=m
CONFIG_USB_TEST=m

#
# USB DSL modem support
#
CONFIG_USB_ATM=m
CONFIG_USB_SPEEDTOUCH=m
CONFIG_USB_CXACRU=m
CONFIG_USB_UEAGLEATM=m
CONFIG_USB_XUSBATM=m

#
# USB Gadget Support
#
CONFIG_USB_GADGET=m
# CONFIG_USB_GADGET_DEBUG is not set
# CONFIG_USB_GADGET_DEBUG_FILES is not set
# CONFIG_USB_GADGET_DEBUG_FS is not set
CONFIG_USB_GADGET_SELECTED=y
# CONFIG_USB_GADGET_AMD5536UDC is not set
# CONFIG_USB_GADGET_ATMEL_USBA is not set
# CONFIG_USB_GADGET_FSL_USB2 is not set
CONFIG_USB_GADGET_NET2280=y
CONFIG_USB_NET2280=m
# CONFIG_USB_GADGET_PXA2XX is not set
# CONFIG_USB_GADGET_M66592 is not set
# CONFIG_USB_GADGET_GOKU is not set
# CONFIG_USB_GADGET_LH7A40X is not set
# CONFIG_USB_GADGET_OMAP is not set
# CONFIG_USB_GADGET_S3C2410 is not set
# CONFIG_USB_GADGET_AT91 is not set
# CONFIG_USB_GADGET_DUMMY_HCD is not set
CONFIG_USB_GADGET_DUALSPEED=y
CONFIG_USB_ZERO=m
CONFIG_USB_ETH=m
CONFIG_USB_ETH_RNDIS=y
CONFIG_USB_GADGETFS=m
CONFIG_USB_FILE_STORAGE=m
# CONFIG_USB_FILE_STORAGE_TEST is not set
CONFIG_USB_G_SERIAL=m
CONFIG_USB_MIDI_GADGET=m
CONFIG_MMC=m
# CONFIG_MMC_DEBUG is not set
# CONFIG_MMC_UNSAFE_RESUME is not set

#
# MMC/SD Card Drivers
#
CONFIG_MMC_BLOCK=m
CONFIG_MMC_BLOCK_BOUNCE=y
CONFIG_SDIO_UART=m

#
# MMC/SD Host Controller Drivers
#
CONFIG_MMC_SDHCI=m
CONFIG_MMC_RICOH_MMC=m
CONFIG_MMC_WBSD=m
CONFIG_MMC_TIFM_SD=m
CONFIG_NEW_LEDS=y
CONFIG_LEDS_CLASS=m

#
# LED drivers
#
CONFIG_LEDS_NET48XX=m
CONFIG_LEDS_WRAP=m

#
# LED Triggers
#
CONFIG_LEDS_TRIGGERS=y
CONFIG_LEDS_TRIGGER_TIMER=m
CONFIG_LEDS_TRIGGER_IDE_DISK=y
CONFIG_LEDS_TRIGGER_HEARTBEAT=m
CONFIG_INFINIBAND=m
CONFIG_INFINIBAND_USER_MAD=m
CONFIG_INFINIBAND_USER_ACCESS=m
CONFIG_INFINIBAND_USER_MEM=y
CONFIG_INFINIBAND_ADDR_TRANS=y
CONFIG_INFINIBAND_MTHCA=m
CONFIG_INFINIBAND_MTHCA_DEBUG=y
CONFIG_INFINIBAND_AMSO1100=m
# CONFIG_INFINIBAND_AMSO1100_DEBUG is not set
CONFIG_INFINIBAND_CXGB3=m
# CONFIG_INFINIBAND_CXGB3_DEBUG is not set
CONFIG_MLX4_INFINIBAND=m
CONFIG_INFINIBAND_IPOIB=m
# CONFIG_INFINIBAND_IPOIB_CM is not set
CONFIG_INFINIBAND_IPOIB_DEBUG=y
# CONFIG_INFINIBAND_IPOIB_DEBUG_DATA is not set
CONFIG_INFINIBAND_SRP=m
CONFIG_INFINIBAND_ISER=m
CONFIG_EDAC=y

#
# Reporting subsystems
#
# CONFIG_EDAC_DEBUG is not set
CONFIG_EDAC_MM_EDAC=m
CONFIG_EDAC_AMD76X=m
CONFIG_EDAC_E7XXX=m
CONFIG_EDAC_E752X=m
CONFIG_EDAC_I82875P=m
CONFIG_EDAC_I82975X=m
CONFIG_EDAC_I3000=m
CONFIG_EDAC_I82860=m
CONFIG_EDAC_R82600=m
CONFIG_EDAC_I5000=m
CONFIG_RTC_LIB=m
CONFIG_RTC_CLASS=m

#
# RTC interfaces
#
CONFIG_RTC_INTF_SYSFS=y
CONFIG_RTC_INTF_PROC=y
CONFIG_RTC_INTF_DEV=y
# CONFIG_RTC_INTF_DEV_UIE_EMUL is not set
# CONFIG_RTC_DRV_TEST is not set

#
# I2C RTC drivers
#
CONFIG_RTC_DRV_DS1307=m
CONFIG_RTC_DRV_DS1374=m
CONFIG_RTC_DRV_DS1672=m
CONFIG_RTC_DRV_MAX6900=m
CONFIG_RTC_DRV_RS5C372=m
CONFIG_RTC_DRV_ISL1208=m
CONFIG_RTC_DRV_X1205=m
CONFIG_RTC_DRV_PCF8563=m
CONFIG_RTC_DRV_PCF8583=m
CONFIG_RTC_DRV_M41T80=m
# CONFIG_RTC_DRV_M41T80_WDT is not set

#
# SPI RTC drivers
#
CONFIG_RTC_DRV_RS5C348=m
CONFIG_RTC_DRV_MAX6902=m

#
# Platform RTC drivers
#
CONFIG_RTC_DRV_CMOS=m
CONFIG_RTC_DRV_DS1553=m
CONFIG_RTC_DRV_STK17TA8=m
CONFIG_RTC_DRV_DS1742=m
CONFIG_RTC_DRV_M48T86=m
CONFIG_RTC_DRV_M48T59=m
CONFIG_RTC_DRV_V3020=m

#
# on-CPU RTC drivers
#
# CONFIG_DMADEVICES is not set
# CONFIG_AUXDISPLAY is not set
CONFIG_VIRTUALIZATION=y
CONFIG_KVM=m
CONFIG_KVM_INTEL=m
CONFIG_KVM_AMD=m
CONFIG_LGUEST=m

#
# Userspace I/O
#
CONFIG_UIO=m
CONFIG_UIO_CIF=m
CONFIG_VIRTIO=y
CONFIG_VIRTIO_RING=y

#
# Firmware Drivers
#
CONFIG_EDD=m
CONFIG_EFI_VARS=m
CONFIG_DELL_RBU=m
CONFIG_DCDBAS=m
CONFIG_DMIID=y

#
# File systems
#
CONFIG_EXT2_FS=m
CONFIG_EXT2_FS_XATTR=y
CONFIG_EXT2_FS_POSIX_ACL=y
CONFIG_EXT2_FS_SECURITY=y
# CONFIG_EXT2_FS_XIP is not set
CONFIG_EXT3_FS=m
CONFIG_EXT3_FS_XATTR=y
CONFIG_EXT3_FS_POSIX_ACL=y
CONFIG_EXT3_FS_SECURITY=y
CONFIG_EXT4DEV_FS=m
CONFIG_EXT4DEV_FS_XATTR=y
CONFIG_EXT4DEV_FS_POSIX_ACL=y
CONFIG_EXT4DEV_FS_SECURITY=y
CONFIG_JBD=m
# CONFIG_JBD_DEBUG is not set
CONFIG_JBD2=m
# CONFIG_JBD2_DEBUG is not set
CONFIG_FS_MBCACHE=m
CONFIG_REISERFS_FS=m
# CONFIG_REISERFS_CHECK is not set
# CONFIG_REISERFS_PROC_INFO is not set
CONFIG_REISERFS_FS_XATTR=y
CONFIG_REISERFS_FS_POSIX_ACL=y
CONFIG_REISERFS_FS_SECURITY=y
CONFIG_JFS_FS=m
CONFIG_JFS_POSIX_ACL=y
CONFIG_JFS_SECURITY=y
# CONFIG_JFS_DEBUG is not set
# CONFIG_JFS_STATISTICS is not set
CONFIG_FS_POSIX_ACL=y
CONFIG_XFS_FS=m
CONFIG_XFS_QUOTA=y
CONFIG_XFS_SECURITY=y
CONFIG_XFS_POSIX_ACL=y
CONFIG_XFS_RT=y
CONFIG_GFS2_FS=m
CONFIG_GFS2_FS_LOCKING_NOLOCK=m
CONFIG_GFS2_FS_LOCKING_DLM=m
CONFIG_OCFS2_FS=m
CONFIG_OCFS2_DEBUG_MASKLOG=y
# CONFIG_OCFS2_DEBUG_FS is not set
CONFIG_MINIX_FS=m
CONFIG_ROMFS_FS=m
CONFIG_INOTIFY=y
CONFIG_INOTIFY_USER=y
CONFIG_QUOTA=y
CONFIG_QUOTA_NETLINK_INTERFACE=y
CONFIG_PRINT_QUOTA_WARNING=y
CONFIG_QFMT_V1=m
CONFIG_QFMT_V2=m
CONFIG_QUOTACTL=y
CONFIG_DNOTIFY=y
CONFIG_AUTOFS_FS=m
CONFIG_AUTOFS4_FS=m
CONFIG_FUSE_FS=m
CONFIG_GENERIC_ACL=y

#
# CD-ROM/DVD Filesystems
#
CONFIG_ISO9660_FS=m
CONFIG_JOLIET=y
CONFIG_ZISOFS=y
CONFIG_UDF_FS=m
CONFIG_UDF_NLS=y

#
# DOS/FAT/NT Filesystems
#
CONFIG_FAT_FS=m
CONFIG_MSDOS_FS=m
CONFIG_VFAT_FS=m
CONFIG_FAT_DEFAULT_CODEPAGE=437
CONFIG_FAT_DEFAULT_IOCHARSET="iso8859-1"
CONFIG_NTFS_FS=m
# CONFIG_NTFS_DEBUG is not set
CONFIG_NTFS_RW=y

#
# Pseudo filesystems
#
CONFIG_PROC_FS=y
CONFIG_PROC_KCORE=y
CONFIG_PROC_SYSCTL=y
CONFIG_SYSFS=y
CONFIG_TMPFS=y
CONFIG_TMPFS_POSIX_ACL=y
CONFIG_HUGETLBFS=y
CONFIG_HUGETLB_PAGE=y
CONFIG_CONFIGFS_FS=m

#
# Miscellaneous filesystems
#
CONFIG_ADFS_FS=m
# CONFIG_ADFS_FS_RW is not set
CONFIG_AFFS_FS=m
CONFIG_ECRYPT_FS=m
CONFIG_HFS_FS=m
CONFIG_HFSPLUS_FS=m
CONFIG_BEFS_FS=m
# CONFIG_BEFS_DEBUG is not set
CONFIG_BFS_FS=m
CONFIG_EFS_FS=m
CONFIG_JFFS2_FS=m
CONFIG_JFFS2_FS_DEBUG=0
CONFIG_JFFS2_FS_WRITEBUFFER=y
# CONFIG_JFFS2_FS_WBUF_VERIFY is not set
# CONFIG_JFFS2_SUMMARY is not set
CONFIG_JFFS2_FS_XATTR=y
CONFIG_JFFS2_FS_POSIX_ACL=y
CONFIG_JFFS2_FS_SECURITY=y
# CONFIG_JFFS2_COMPRESSION_OPTIONS is not set
CONFIG_JFFS2_ZLIB=y
# CONFIG_JFFS2_LZO is not set
CONFIG_JFFS2_RTIME=y
# CONFIG_JFFS2_RUBIN is not set
CONFIG_CRAMFS=m
CONFIG_VXFS_FS=m
CONFIG_HPFS_FS=m
CONFIG_QNX4FS_FS=m
CONFIG_SYSV_FS=m
CONFIG_UFS_FS=m
# CONFIG_UFS_FS_WRITE is not set
# CONFIG_UFS_DEBUG is not set
CONFIG_NETWORK_FILESYSTEMS=y
CONFIG_NFS_FS=m
CONFIG_NFS_V3=y
CONFIG_NFS_V3_ACL=y
CONFIG_NFS_V4=y
# CONFIG_NFS_DIRECTIO is not set
CONFIG_NFSD=m
CONFIG_NFSD_V2_ACL=y
CONFIG_NFSD_V3=y
CONFIG_NFSD_V3_ACL=y
CONFIG_NFSD_V4=y
CONFIG_NFSD_TCP=y
CONFIG_LOCKD=m
CONFIG_LOCKD_V4=y
CONFIG_EXPORTFS=m
CONFIG_NFS_ACL_SUPPORT=m
CONFIG_NFS_COMMON=y
CONFIG_SUNRPC=m
CONFIG_SUNRPC_GSS=m
CONFIG_SUNRPC_XPRT_RDMA=m
CONFIG_SUNRPC_BIND34=y
CONFIG_RPCSEC_GSS_KRB5=m
CONFIG_RPCSEC_GSS_SPKM3=m
# CONFIG_SMB_FS is not set
CONFIG_CIFS=m
# CONFIG_CIFS_STATS is not set
# CONFIG_CIFS_WEAK_PW_HASH is not set
CONFIG_CIFS_XATTR=y
CONFIG_CIFS_POSIX=y
# CONFIG_CIFS_DEBUG2 is not set
# CONFIG_CIFS_EXPERIMENTAL is not set
CONFIG_NCP_FS=m
# CONFIG_NCPFS_PACKET_SIGNING is not set
# CONFIG_NCPFS_IOCTL_LOCKING is not set
# CONFIG_NCPFS_STRONG is not set
CONFIG_NCPFS_NFS_NS=y
CONFIG_NCPFS_OS2_NS=y
# CONFIG_NCPFS_SMALLDOS is not set
CONFIG_NCPFS_NLS=y
CONFIG_NCPFS_EXTRAS=y
CONFIG_CODA_FS=m
# CONFIG_CODA_FS_OLD_API is not set
CONFIG_AFS_FS=m
# CONFIG_AFS_DEBUG is not set
CONFIG_9P_FS=m

#
# Partition Types
#
CONFIG_PARTITION_ADVANCED=y
CONFIG_ACORN_PARTITION=y
# CONFIG_ACORN_PARTITION_CUMANA is not set
# CONFIG_ACORN_PARTITION_EESOX is not set
CONFIG_ACORN_PARTITION_ICS=y
# CONFIG_ACORN_PARTITION_ADFS is not set
# CONFIG_ACORN_PARTITION_POWERTEC is not set
CONFIG_ACORN_PARTITION_RISCIX=y
CONFIG_OSF_PARTITION=y
CONFIG_AMIGA_PARTITION=y
CONFIG_ATARI_PARTITION=y
CONFIG_MAC_PARTITION=y
CONFIG_MSDOS_PARTITION=y
CONFIG_BSD_DISKLABEL=y
CONFIG_MINIX_SUBPARTITION=y
CONFIG_SOLARIS_X86_PARTITION=y
CONFIG_UNIXWARE_DISKLABEL=y
CONFIG_LDM_PARTITION=y
# CONFIG_LDM_DEBUG is not set
CONFIG_SGI_PARTITION=y
CONFIG_ULTRIX_PARTITION=y
CONFIG_SUN_PARTITION=y
CONFIG_KARMA_PARTITION=y
CONFIG_EFI_PARTITION=y
# CONFIG_SYSV68_PARTITION is not set
CONFIG_NLS=y
CONFIG_NLS_DEFAULT="iso8859-1"
CONFIG_NLS_CODEPAGE_437=m
CONFIG_NLS_CODEPAGE_737=m
CONFIG_NLS_CODEPAGE_775=m
CONFIG_NLS_CODEPAGE_850=m
CONFIG_NLS_CODEPAGE_852=m
CONFIG_NLS_CODEPAGE_855=m
CONFIG_NLS_CODEPAGE_857=m
CONFIG_NLS_CODEPAGE_860=m
CONFIG_NLS_CODEPAGE_861=m
CONFIG_NLS_CODEPAGE_862=m
CONFIG_NLS_CODEPAGE_863=m
CONFIG_NLS_CODEPAGE_864=m
CONFIG_NLS_CODEPAGE_865=m
CONFIG_NLS_CODEPAGE_866=m
CONFIG_NLS_CODEPAGE_869=m
CONFIG_NLS_CODEPAGE_936=m
CONFIG_NLS_CODEPAGE_950=m
CONFIG_NLS_CODEPAGE_932=m
CONFIG_NLS_CODEPAGE_949=m
CONFIG_NLS_CODEPAGE_874=m
CONFIG_NLS_ISO8859_8=m
CONFIG_NLS_CODEPAGE_1250=m
CONFIG_NLS_CODEPAGE_1251=m
CONFIG_NLS_ASCII=m
CONFIG_NLS_ISO8859_1=m
CONFIG_NLS_ISO8859_2=m
CONFIG_NLS_ISO8859_3=m
CONFIG_NLS_ISO8859_4=m
CONFIG_NLS_ISO8859_5=m
CONFIG_NLS_ISO8859_6=m
CONFIG_NLS_ISO8859_7=m
CONFIG_NLS_ISO8859_9=m
CONFIG_NLS_ISO8859_13=m
CONFIG_NLS_ISO8859_14=m
CONFIG_NLS_ISO8859_15=m
CONFIG_NLS_KOI8_R=m
CONFIG_NLS_KOI8_U=m
CONFIG_NLS_UTF8=m
CONFIG_DLM=m
CONFIG_DLM_DEBUG=y
CONFIG_INSTRUMENTATION=y
CONFIG_PROFILING=y
CONFIG_OPROFILE=m
# CONFIG_KPROBES is not set
# CONFIG_MARKERS is not set

#
# Kernel hacking
#
CONFIG_TRACE_IRQFLAGS_SUPPORT=y
# CONFIG_PRINTK_TIME is not set
CONFIG_ENABLE_WARN_DEPRECATED=y
CONFIG_ENABLE_MUST_CHECK=y
CONFIG_MAGIC_SYSRQ=y
CONFIG_UNUSED_SYMBOLS=y
CONFIG_DEBUG_FS=y
# CONFIG_HEADERS_CHECK is not set
CONFIG_DEBUG_KERNEL=y
# CONFIG_DEBUG_SHIRQ is not set
CONFIG_DETECT_SOFTLOCKUP=y
# CONFIG_SCHED_DEBUG is not set
# CONFIG_SCHEDSTATS is not set
CONFIG_TIMER_STATS=y
# CONFIG_DEBUG_SLAB is not set
# CONFIG_DEBUG_RT_MUTEXES is not set
# CONFIG_RT_MUTEX_TESTER is not set
# CONFIG_DEBUG_SPINLOCK is not set
# CONFIG_DEBUG_MUTEXES is not set
# CONFIG_DEBUG_LOCK_ALLOC is not set
# CONFIG_PROVE_LOCKING is not set
# CONFIG_LOCK_STAT is not set
# CONFIG_DEBUG_SPINLOCK_SLEEP is not set
# CONFIG_DEBUG_LOCKING_API_SELFTESTS is not set
# CONFIG_DEBUG_KOBJECT is not set
# CONFIG_DEBUG_HIGHMEM is not set
CONFIG_DEBUG_BUGVERBOSE=y
# CONFIG_DEBUG_INFO is not set
# CONFIG_DEBUG_VM is not set
# CONFIG_DEBUG_LIST is not set
# CONFIG_DEBUG_SG is not set
# CONFIG_FRAME_POINTER is not set
# CONFIG_FORCED_INLINING is not set
# CONFIG_BOOT_PRINTK_DELAY is not set
# CONFIG_RCU_TORTURE_TEST is not set
# CONFIG_FAULT_INJECTION is not set
# CONFIG_SAMPLES is not set
CONFIG_EARLY_PRINTK=y
# CONFIG_DEBUG_STACKOVERFLOW is not set
# CONFIG_DEBUG_STACK_USAGE is not set

#
# Page alloc debug is incompatible with Software Suspend on i386
#
# CONFIG_DEBUG_RODATA is not set
# CONFIG_4KSTACKS is not set
CONFIG_X86_FIND_SMP_CONFIG=y
CONFIG_X86_MPPARSE=y
CONFIG_DOUBLEFAULT=y

#
# Security options
#
CONFIG_KEYS=y
# CONFIG_KEYS_DEBUG_PROC_KEYS is not set
CONFIG_SECURITY=y
CONFIG_SECURITY_NETWORK=y
CONFIG_SECURITY_NETWORK_XFRM=y
CONFIG_SECURITY_CAPABILITIES=y
CONFIG_SECURITY_FILE_CAPABILITIES=y
CONFIG_SECURITY_SELINUX=y
CONFIG_SECURITY_SELINUX_BOOTPARAM=y
CONFIG_SECURITY_SELINUX_BOOTPARAM_VALUE=0
CONFIG_SECURITY_SELINUX_DISABLE=y
CONFIG_SECURITY_SELINUX_DEVELOP=y
CONFIG_SECURITY_SELINUX_AVC_STATS=y
CONFIG_SECURITY_SELINUX_CHECKREQPROT_VALUE=1
# CONFIG_SECURITY_SELINUX_ENABLE_SECMARK_DEFAULT is not set
# CONFIG_SECURITY_SELINUX_POLICYDB_VERSION_MAX is not set
CONFIG_XOR_BLOCKS=m
CONFIG_ASYNC_CORE=m
CONFIG_ASYNC_MEMCPY=m
CONFIG_ASYNC_XOR=m
CONFIG_CRYPTO=y
CONFIG_CRYPTO_ALGAPI=y
CONFIG_CRYPTO_AEAD=m
CONFIG_CRYPTO_BLKCIPHER=m
CONFIG_CRYPTO_HASH=y
CONFIG_CRYPTO_MANAGER=y
CONFIG_CRYPTO_HMAC=y
CONFIG_CRYPTO_XCBC=m
CONFIG_CRYPTO_NULL=m
CONFIG_CRYPTO_MD4=m
CONFIG_CRYPTO_MD5=y
CONFIG_CRYPTO_SHA1=m
CONFIG_CRYPTO_SHA256=m
CONFIG_CRYPTO_SHA512=m
CONFIG_CRYPTO_WP512=m
CONFIG_CRYPTO_TGR192=m
CONFIG_CRYPTO_GF128MUL=m
CONFIG_CRYPTO_ECB=m
CONFIG_CRYPTO_CBC=m
CONFIG_CRYPTO_PCBC=m
CONFIG_CRYPTO_LRW=m
CONFIG_CRYPTO_XTS=m
# CONFIG_CRYPTO_CRYPTD is not set
CONFIG_CRYPTO_DES=m
CONFIG_CRYPTO_FCRYPT=m
CONFIG_CRYPTO_BLOWFISH=m
CONFIG_CRYPTO_TWOFISH=m
CONFIG_CRYPTO_TWOFISH_COMMON=m
CONFIG_CRYPTO_TWOFISH_586=m
CONFIG_CRYPTO_SERPENT=m
CONFIG_CRYPTO_AES=m
CONFIG_CRYPTO_AES_586=m
CONFIG_CRYPTO_CAST5=m
CONFIG_CRYPTO_CAST6=m
CONFIG_CRYPTO_TEA=m
CONFIG_CRYPTO_ARC4=m
CONFIG_CRYPTO_KHAZAD=m
CONFIG_CRYPTO_ANUBIS=m
CONFIG_CRYPTO_SEED=m
CONFIG_CRYPTO_DEFLATE=m
CONFIG_CRYPTO_MICHAEL_MIC=m
CONFIG_CRYPTO_CRC32C=m
CONFIG_CRYPTO_CAMELLIA=m
CONFIG_CRYPTO_TEST=m
CONFIG_CRYPTO_AUTHENC=m
CONFIG_CRYPTO_HW=y
CONFIG_CRYPTO_DEV_PADLOCK=m
CONFIG_CRYPTO_DEV_PADLOCK_AES=m
CONFIG_CRYPTO_DEV_PADLOCK_SHA=m
CONFIG_CRYPTO_DEV_GEODE=m

#
# Library routines
#
CONFIG_BITREVERSE=y
CONFIG_CRC_CCITT=m
CONFIG_CRC16=m
CONFIG_CRC_ITU_T=m
CONFIG_CRC32=y
CONFIG_CRC7=m
CONFIG_LIBCRC32C=m
CONFIG_AUDIT_GENERIC=y
CONFIG_ZLIB_INFLATE=m
CONFIG_ZLIB_DEFLATE=m
CONFIG_GENERIC_ALLOCATOR=y
CONFIG_REED_SOLOMON=m
CONFIG_REED_SOLOMON_DEC16=y
CONFIG_TEXTSEARCH=y
CONFIG_TEXTSEARCH_KMP=m
CONFIG_TEXTSEARCH_BM=m
CONFIG_TEXTSEARCH_FSM=m
CONFIG_PLIST=y
CONFIG_HAS_IOMEM=y
CONFIG_HAS_IOPORT=y
CONFIG_HAS_DMA=y
CONFIG_CHECK_SIGNATURE=y

SysRq : Show State
  task                PC stack   pid father
init          S f7c41b38     0     1      0
       f7c3f7b0 00000082 00000002 f7c41b38 f7c41b30 00000000 33e47d83 00000236 
       f7c3f918 c2010940 00000000 00082722 f7c41b5c c04c6ec0 000000fd 00000001 
       00000000 00000000 f7c41b5c 00082c03 0000000b f7c41f9c c02bbe7f 0000000b 
Call Trace:
 [<c02bbe7f>] schedule_timeout+0x70/0x8d
 [<c012c215>] process_timeout+0x0/0x5
 [<c02bbe7a>] schedule_timeout+0x6b/0x8d
 [<c0182b33>] do_select+0x372/0x3c9
 [<c0183121>] __pollwait+0x0/0xac
 [<c011f451>] default_wake_function+0x0/0x8
 [<f896776d>] do_get_write_access+0x2f9/0x332 [jbd]
 [<f8a976c2>] __ext3_get_inode_loc+0x10f/0x2dd [ext3]
 [<c01bd73a>] security_sock_rcv_skb+0xc/0xd
 [<c0292100>] tcp_v4_rcv+0x463/0x887
 [<f89677c7>] journal_get_write_access+0x21/0x26 [jbd]
 [<c025923b>] __alloc_skb+0x49/0xf5
 [<c0259c9b>] __netdev_alloc_skb+0x1c/0x35
 [<f889adfc>] e1000_alloc_rx_buffers+0x1cc/0x296 [e1000]
 [<c025d47c>] netif_receive_skb+0x2e4/0x350
 [<f889b7ad>] e1000_clean_rx_irq+0x422/0x452 [e1000]
 [<f889b38b>] e1000_clean_rx_irq+0x0/0x452 [e1000]
 [<f8898fd7>] e1000_clean+0x1e3/0x20d [e1000]
 [<c0186791>] __d_lookup+0x96/0xd9
 [<c017dee1>] do_lookup+0x4f/0x140
 [<c0185f7c>] dput+0x15/0xdc
 [<c017fda9>] __link_path_walk+0xa23/0xb46
 [<c0182e0f>] core_sys_select+0x285/0x2a2
 [<c01801f8>] do_path_lookup+0x162/0x1c4
 [<c017f1c2>] getname+0x59/0xad
 [<c017a4c8>] cp_new_stat64+0xfc/0x10e
 [<c0183271>] sys_select+0xa4/0x187
 [<c0103e56>] sysenter_past_esp+0x6b/0xa1
 =======================
kthreadd      S 00000086     0     2      0
       f7c3f1d0 00000046 00000003 00000086 dfac9e54 dfac9e98 e00667ec 0000012f 
       f7c3f338 c2010940 00000000 dfac9ea0 0000032c 00000000 00000286 00000000 
       c011ee96 00000000 c0349d58 000015d1 dfac9e80 00000000 c0134e37 c0134dd6 
Call Trace:
 [<c011ee96>] complete+0x36/0x44
 [<c0134e37>] kthreadd+0x61/0xf5
 [<c0134dd6>] kthreadd+0x0/0xf5
 [<c0104b07>] kernel_thread_helper+0x7/0x10
 =======================
migration/0   S 00000096     0     3      2
       f7c3e610 00000046 00000250 00000096 f0999f30 f0999f64 50b71309 00000237 
       f7c3e778 c2010940 00000000 f0999f6c 00000000 00000000 00000296 00000000 
       c011ee96 00000000 c2010d58 c012145b c2010940 00000000 c012159a 00000000 
Call Trace:
 [<c011ee96>] complete+0x36/0x44
 [<c012145b>] migration_thread+0x0/0x1c4
 [<c012159a>] migration_thread+0x13f/0x1c4
 [<c011ee96>] complete+0x36/0x44
 [<c012145b>] migration_thread+0x0/0x1c4
 [<c0134fae>] kthread+0x38/0x5e
 [<c0134f76>] kthread+0x0/0x5e
 [<c0104b07>] kernel_thread_helper+0x7/0x10
 =======================
ksoftirqd/0   S f7c69fb8     0     4      2
       f7c3e030 00000046 00000002 f7c69fb8 f7c69fb0 00000000 00000003 c01330f4 
       f7c3e198 c2010940 00000000 0008259f c012921e 00000001 000000ff 00000000 
       00000000 00000000 00000000 c0129113 00000000 00000000 c0129135 00000000 
Call Trace:
 [<c01330f4>] __rcu_process_callbacks+0xfa/0x174
 [<c012921e>] tasklet_action+0x58/0xb8
 [<c0129113>] ksoftirqd+0x0/0xa4
 [<c0129135>] ksoftirqd+0x22/0xa4
 [<c0134fae>] kthread+0x38/0x5e
 [<c0134f76>] kthread+0x0/0x5e
 [<c0104b07>] kernel_thread_helper+0x7/0x10
 =======================
watchdog/0    S f7c6dfb8     0     5      2
       f7c6b7f0 00000046 00000002 f7c6dfb8 f7c6dfb0 00000000 c011dac1 df72d50a 
       f7c6b958 c2010940 00000000 0008274a 00000246 00000000 000000fd 00000001 
       00000000 00000000 00000000 c01556a2 00000000 00000000 c01556dd 00000063 
Call Trace:
 [<c011dac1>] __update_rq_clock+0x1a/0xf3
 [<c01556a2>] watchdog+0x0/0x4a
 [<c01556dd>] watchdog+0x3b/0x4a
 [<c0134fae>] kthread+0x38/0x5e
 [<c0134f76>] kthread+0x0/0x5e
 [<c0104b07>] kernel_thread_helper+0x7/0x10
 =======================
migration/1   S 00000096     0     6      2
       f7c6b210 00000046 00000003 00000096 f05fff30 f05fff64 37f5ffba 00000237 
       f7c6b378 c2018940 00000001 f05fff6c 00000000 00000000 00000296 00000000 
       c011ee96 00000000 c2018d58 c012145b c2018940 00000000 c012159a 00000000 
Call Trace:
 [<c011ee96>] complete+0x36/0x44
 [<c012145b>] migration_thread+0x0/0x1c4
 [<c012159a>] migration_thread+0x13f/0x1c4
 [<c011ee96>] complete+0x36/0x44
 [<c012145b>] migration_thread+0x0/0x1c4
 [<c0134fae>] kthread+0x38/0x5e
 [<c0134f76>] kthread+0x0/0x5e
 [<c0104b07>] kernel_thread_helper+0x7/0x10
 =======================
ksoftirqd/1   S 00000282     0     7      2
       f7c6ac30 00000046 00000000 00000282 c2015ee0 00000000 36b8173e 00000237 
       f7c6ad98 c2018940 00000001 00000005 00000000 00000000 c0368a68 00000046 
       00000246 c0129113 00000001 c0129113 00000000 00000000 c0129135 00000001 
Call Trace:
 [<c0129113>] ksoftirqd+0x0/0xa4
 [<c0129113>] ksoftirqd+0x0/0xa4
 [<c0129135>] ksoftirqd+0x22/0xa4
 [<c0134fae>] kthread+0x38/0x5e
 [<c0134f76>] kthread+0x0/0x5e
 [<c0104b07>] kernel_thread_helper+0x7/0x10
 =======================
watchdog/1    S f7c75fb8     0     8      2
       f7c6a650 00000046 00000002 f7c75fb8 f7c75fb0 00000000 c011dac1 e4ae4558 
       f7c6a7b8 c2018940 00000001 00082757 00000246 00000000 000000ff 00000000 
       00000000 00000000 00000001 c01556a2 00000000 00000000 c01556dd 00000063 
Call Trace:
 [<c011dac1>] __update_rq_clock+0x1a/0xf3
 [<c01556a2>] watchdog+0x0/0x4a
 [<c01556dd>] watchdog+0x3b/0x4a
 [<c0134fae>] kthread+0x38/0x5e
 [<c0134f76>] kthread+0x0/0x5e
 [<c0104b07>] kernel_thread_helper+0x7/0x10
 =======================
events/0      S c200d9c0     0     9      2
       f7c77830 00000046 00016dd6 c200d9c0 00000002 f7c79f9c 7e3c70da 00000237 
       f7c77998 c2010940 00000000 0008274a 14076365 00000000 000000ff 00000000 
       00000000 00016dd6 f7c4bec0 c01326e3 f7c79fd0 00000000 c013276b 00000000 
Call Trace:
 [<c01326e3>] worker_thread+0x0/0xc5
 [<c013276b>] worker_thread+0x88/0xc5
 [<c0135075>] autoremove_wake_function+0x0/0x35
 [<c0134fae>] kthread+0x38/0x5e
 [<c0134f76>] kthread+0x0/0x5e
 [<c0104b07>] kernel_thread_helper+0x7/0x10
 =======================
events/1      R running      0    10      2
khelper       S 00000060     0    11      2
       f7c77250 00000046 c0104b00 00000060 00000286 00000000 5f1147fa 0000012e 
       f7c773b8 c2018940 00000001 c0131996 000005f9 00000000 c0131ecc 00000001 
       00000246 c0135188 f7c4be40 c01326e3 f7c9bfd0 00000000 c013276b 00000000 
Call Trace:
 [<c0104b00>] kernel_thread_helper+0x0/0x10
 [<c0131996>] __call_usermodehelper+0x30/0x4b
 [<c0131ecc>] run_workqueue+0xdc/0x109
 [<c0135188>] prepare_to_wait+0x12/0x49
 [<c01326e3>] worker_thread+0x0/0xc5
 [<c013276b>] worker_thread+0x88/0xc5
 [<c0135075>] autoremove_wake_function+0x0/0x35
 [<c0134fae>] kthread+0x38/0x5e
 [<c0134f76>] kthread+0x0/0x5e
 [<c0104b07>] kernel_thread_helper+0x7/0x10
 =======================
kblockd/0     S f7ce7fa0     0    43      2
       f7cd8230 00000046 00000002 f7ce7fa0 f7ce7f98 00000000 498b2be3 00000237 
       f7cd8398 c2010940 00000000 f74191f8 00000000 00000000 c0131ecc 00000000 
       00000246 c0135188 f7c7d840 c01326e3 f7ce7fd0 00000000 c013276b 00000000 
Call Trace:
 [<c0131ecc>] run_workqueue+0xdc/0x109
 [<c0135188>] prepare_to_wait+0x12/0x49
 [<c01326e3>] worker_thread+0x0/0xc5
 [<c013276b>] worker_thread+0x88/0xc5
 [<c0135075>] autoremove_wake_function+0x0/0x35
 [<c0134fae>] kthread+0x38/0x5e
 [<c0134f76>] kthread+0x0/0x5e
 [<c0104b07>] kernel_thread_helper+0x7/0x10
 =======================
kblockd/1     S f7ce9fa0     0    44      2
       f7c76c70 00000046 00000002 f7ce9fa0 f7ce9f98 00000000 37459602 00000214 
       f7c76dd8 c2018940 00000001 f74191f8 00007cc0 00000000 c0131ecc 00000000 
       00000246 c0135188 f7c7d800 c01326e3 f7ce9fd0 00000000 c013276b 00000000 
Call Trace:
 [<c0131ecc>] run_workqueue+0xdc/0x109
 [<c0135188>] prepare_to_wait+0x12/0x49
 [<c01326e3>] worker_thread+0x0/0xc5
 [<c013276b>] worker_thread+0x88/0xc5
 [<c0135075>] autoremove_wake_function+0x0/0x35
 [<c0134fae>] kthread+0x38/0x5e
 [<c0134f76>] kthread+0x0/0x5e
 [<c0104b07>] kernel_thread_helper+0x7/0x10
 =======================
kacpid        S f7d11fa0     0    47      2
       f7d0f7b0 00000046 00000002 f7d11fa0 f7d11f98 00000000 f7d0f7b0 c0344160 
       f7d0f918 c2010940 00000000 fffedb65 f7d11fb8 00000000 000000ff 00000000 
       00000000 00000000 f7c7d600 c01326e3 f7d11fd0 00000000 c013276b 00000000 
Call Trace:
 [<c01326e3>] worker_thread+0x0/0xc5
 [<c013276b>] worker_thread+0x88/0xc5
 [<c0135075>] autoremove_wake_function+0x0/0x35
 [<c0134fae>] kthread+0x38/0x5e
 [<c0134f76>] kthread+0x0/0x5e
 [<c0104b07>] kernel_thread_helper+0x7/0x10
 =======================
kacpi_notify  S f7d15fa0     0    48      2
       f7d137f0 00000046 00000002 f7d15fa0 f7d15f98 00000000 f7d137f0 c0344160 
       f7d13958 c2010940 00000000 fffedb67 f7d15fb8 00000000 000000ff 00000000 
       00000000 00000000 f7c4bd80 c01326e3 f7d15fd0 00000000 c013276b 00000000 
Call Trace:
 [<c01326e3>] worker_thread+0x0/0xc5
 [<c013276b>] worker_thread+0x88/0xc5
 [<c0135075>] autoremove_wake_function+0x0/0x35
 [<c0134fae>] kthread+0x38/0x5e
 [<c0134f76>] kthread+0x0/0x5e
 [<c0104b07>] kernel_thread_helper+0x7/0x10
 =======================
kseriod       S c035ca68     0   126      2
       f7cd8810 00000046 000007fb c035ca68 f7d6bf7c c02bacf2 072393ba 00000003 
       f7cd8978 c2010940 00000000 00000000 00023232 00000000 c035ca68 00000000 
       00000246 c0135188 f7d6bfb4 c024613f f7d6bfc8 00000246 c02463d8 c2010940 
Call Trace:
 [<c02bacf2>] klist_next+0x24/0x6c
 [<c0135188>] prepare_to_wait+0x12/0x49
 [<c024613f>] serio_thread+0x0/0x311
 [<c02463d8>] serio_thread+0x299/0x311
 [<c0135075>] autoremove_wake_function+0x0/0x35
 [<c024613f>] serio_thread+0x0/0x311
 [<c0134fae>] kthread+0x38/0x5e
 [<c0134f76>] kthread+0x0/0x5e
 [<c0104b07>] kernel_thread_helper+0x7/0x10
 =======================
pdflush       S f7dbdf98     0   165      2
       f7d54cf0 00000046 00000002 f7dbdf98 f7dbdf90 00000000 c01601fa 00000000 
       f7d54e58 c2010940 00000000 fffedc41 c011d6ab c2010960 000000ff 00000000 
       00000000 00000000 00000001 f7dbdfc4 00000000 00000000 c01602c7 f7c41f48 
Call Trace:
 [<c01601fa>] pdflush+0x0/0x1d2
 [<c011d6ab>] enqueue_task+0x52/0x5d
 [<c01602c7>] pdflush+0xcd/0x1d2
 [<c01601fa>] pdflush+0x0/0x1d2
 [<c0134fae>] kthread+0x38/0x5e
 [<c0134f76>] kthread+0x0/0x5e
 [<c0104b07>] kernel_thread_helper+0x7/0x10
 =======================
pdflush       S f7dbff98     0   166      2
       f7d12c30 00000046 00000002 f7dbff98 f7dbff90 00000000 00082a7e 00000000 
       f7d12d98 c2010940 00000000 00082598 000003ed 00000000 000000ff 00000000 
       00000000 00000000 00000001 f7dbffc4 00000000 00000000 c01602c7 f7c41f48 
Call Trace:
 [<c01602c7>] pdflush+0xcd/0x1d2
 [<c01601fa>] pdflush+0x0/0x1d2
 [<c0134fae>] kthread+0x38/0x5e
 [<c0134f76>] kthread+0x0/0x5e
 [<c0104b07>] kernel_thread_helper+0x7/0x10
 =======================
kswapd0       S f7dc1f40     0   167      2
       f7d552d0 00000046 00000002 f7dc1f40 f7dc1f38 00000000 c0162b51 f7dc1fb4 
       f7d55438 c2010940 00000000 fffedc41 00000000 00000000 000000ff 00000000 
       00000000 00000000 f7d552d0 c0162b51 f7dc1fb4 c034e460 c0162c0d f7d554e0 
Call Trace:
 [<c0162b51>] kswapd+0x0/0x40a
 [<c0162b51>] kswapd+0x0/0x40a
 [<c0162c0d>] kswapd+0xbc/0x40a
 [<c0103039>] __switch_to+0x9d/0x11c
 [<c02bbc1a>] schedule+0x588/0x5ec
 [<c0135075>] autoremove_wake_function+0x0/0x35
 [<c0162b51>] kswapd+0x0/0x40a
 [<c0134fae>] kthread+0x38/0x5e
 [<c0134f76>] kthread+0x0/0x5e
 [<c0104b07>] kernel_thread_helper+0x7/0x10
 =======================
aio/0         S f7d79fa0     0   168      2
       f7d54710 00000046 00000002 f7d79fa0 f7d79f98 00000000 f7d54710 c0344160 
       f7d54878 c2010940 00000000 fffedc43 f7d79fb8 00000000 000000ff 00000000 
       00000000 00000000 f7ce0240 c01326e3 f7d79fd0 00000000 c013276b 00000000 
Call Trace:
 [<c01326e3>] worker_thread+0x0/0xc5
 [<c013276b>] worker_thread+0x88/0xc5
 [<c0135075>] autoremove_wake_function+0x0/0x35
 [<c0134fae>] kthread+0x38/0x5e
 [<c0134f76>] kthread+0x0/0x5e
 [<c0104b07>] kernel_thread_helper+0x7/0x10
 =======================
aio/1         S 00000000     0   169      2
       f7d12650 00000046 f7d13420 00000000 f7d12650 00000000 352ee0b6 00000000 
       f7d127b8 c2018940 00000001 f7d73fc0 00001bd3 00000000 00000001 00000001 
       00000246 c0135188 f7d16fc0 c01326e3 f7d73fd0 00000000 c013276b 00000000 
Call Trace:
 [<c0135188>] prepare_to_wait+0x12/0x49
 [<c01326e3>] worker_thread+0x0/0xc5
 [<c013276b>] worker_thread+0x88/0xc5
 [<c0135075>] autoremove_wake_function+0x0/0x35
 [<c0134fae>] kthread+0x38/0x5e
 [<c0134f76>] kthread+0x0/0x5e
 [<c0104b07>] kernel_thread_helper+0x7/0x10
 =======================
ksuspend_usbd S f74fdfa0     0   567      2
       f7fd79b0 00000046 00000002 f74fdfa0 f74fdf98 00000000 049bfc26 00000001 
       f7fd7b18 c2010940 00000000 fffee0b3 f88595d3 00000000 000000ff 00000000 
       00000000 00000000 f7ff4900 c01326e3 f74fdfd0 00000000 c013276b 00000000 
Call Trace:
 [<f88595d3>] usb_autosuspend_work+0x0/0xc [usbcore]
 [<c01326e3>] worker_thread+0x0/0xc5
 [<c013276b>] worker_thread+0x88/0xc5
 [<c0135075>] autoremove_wake_function+0x0/0x35
 [<c0134fae>] kthread+0x38/0x5e
 [<c0134f76>] kthread+0x0/0x5e
 [<c0104b07>] kernel_thread_helper+0x7/0x10
 =======================
khubd         S c20159c0     0   590      2
       f7fe2030 00000046 00000b14 c20159c0 00000002 f7527f3c b3400da2 00000000 
       f7fe2198 c2018940 00000001 fffede71 e7dda0f8 ffffffff 000000ff 00000000 
       00000000 00000b14 f8871588 00000000 f7527fbc 00000000 f8855571 f7527fc0 
Call Trace:
 [<f8855571>] hub_thread+0xa34/0xad8 [usbcore]
 [<c0103039>] __switch_to+0x9d/0x11c
 [<c02bbc1a>] schedule+0x588/0x5ec
 [<c0135075>] autoremove_wake_function+0x0/0x35
 [<f8854b3d>] hub_thread+0x0/0xad8 [usbcore]
 [<c0134fae>] kthread+0x38/0x5e
 [<c0134f76>] kthread+0x0/0x5e
 [<c0104b07>] kernel_thread_helper+0x7/0x10
 =======================
scsi_tgtd/0   S 00000000     0   647      2
       f741ed30 00000046 f7c3f3e0 00000000 f741ed30 00000000 8609bb4a 00000000 
       f741ee98 c2010940 00000000 00000092 000011d8 00000000 6f645cd3 00000000 
       00000246 c0135188 f7fb4280 c01326e3 f7535fd0 00000000 c013276b 00000000 
Call Trace:
 [<c0135188>] prepare_to_wait+0x12/0x49
 [<c01326e3>] worker_thread+0x0/0xc5
 [<c013276b>] worker_thread+0x88/0xc5
 [<c0135075>] autoremove_wake_function+0x0/0x35
 [<c0134fae>] kthread+0x38/0x5e
 [<c0134f76>] kthread+0x0/0x5e
 [<c0104b07>] kernel_thread_helper+0x7/0x10
 =======================
scsi_tgtd/1   S 00000000     0   660      2
       f7d1e690 00000046 f7fe2240 00000000 f7d1e690 00000000 708eb084 00000000 
       f7d1e7f8 c2018940 00000001 00000092 00726adb 00000000 867da4d5 00000000 
       00000246 c0135188 f74acf40 c01326e3 f7529fd0 00000000 c013276b 00000000 
Call Trace:
 [<c0135188>] prepare_to_wait+0x12/0x49
 [<c01326e3>] worker_thread+0x0/0xc5
 [<c013276b>] worker_thread+0x88/0xc5
 [<c0135075>] autoremove_wake_function+0x0/0x35
 [<c0134fae>] kthread+0x38/0x5e
 [<c0134f76>] kthread+0x0/0x5e
 [<c0104b07>] kernel_thread_helper+0x7/0x10
 =======================
scsi_eh_0     S f7567f64     0   738      2
       f7406cb0 00000046 00000002 f7567f64 f7567f5c 00000000 00000000 00000001 
       f7406e18 c2018940 00000001 fffede50 00000000 00000000 000000ff 00000000 
       00000000 00000000 f7d52000 f7d52000 00000000 00000000 f882cc62 f7406cb0 
Call Trace:
 [<f882cc62>] scsi_error_handler+0x46/0x455 [scsi_mod]
 [<c02bbc1a>] schedule+0x588/0x5ec
 [<f882cc1c>] scsi_error_handler+0x0/0x455 [scsi_mod]
 [<c0134fae>] kthread+0x38/0x5e
 [<c0134f76>] kthread+0x0/0x5e
 [<c0104b07>] kernel_thread_helper+0x7/0x10
 =======================
qla2xxx_0_dpc S f7517f98     0   752      2
       f7fe2bf0 00000046 00000002 f7517f98 f7517f90 00000000 f7d522b8 040800e0 
       f7fe2d58 c2010940 00000000 fffedf94 f7d52278 00000100 000000ff 00000000 
       00000000 00000000 f7d52278 f891d5f5 f7d52278 00000000 f891d626 f7451d38 
Call Trace:
 [<f891d5f5>] qla2x00_do_dpc+0x0/0x459 [qla2xxx]
 [<f891d626>] qla2x00_do_dpc+0x31/0x459 [qla2xxx]
 [<f891d5f5>] qla2x00_do_dpc+0x0/0x459 [qla2xxx]
 [<c0134fae>] kthread+0x38/0x5e
 [<c0134f76>] kthread+0x0/0x5e
 [<c0104b07>] kernel_thread_helper+0x7/0x10
 =======================
scsi_wq_0     S c200d9c0     0   753      2
       f7cb4d30 00000046 00000afb c200d9c0 00000002 f7623f9c 1520edb6 00000001 
       f7cb4e98 c2010940 00000000 fffedf9a 1710f1a6 00000000 000000ff 00000000 
       00000000 00000afb f7ff4e00 c01326e3 f7623fd0 00000000 c013276b 00000000 
Call Trace:
 [<c01326e3>] worker_thread+0x0/0xc5
 [<c013276b>] worker_thread+0x88/0xc5
 [<c0135075>] autoremove_wake_function+0x0/0x35
 [<c0134fae>] kthread+0x38/0x5e
 [<c0134f76>] kthread+0x0/0x5e
 [<c0104b07>] kernel_thread_helper+0x7/0x10
 =======================
fc_wq_0       S 00000000     0   754      2
       f7412130 00000046 f7fca400 00000000 f7412130 00000000 d72ba61d 00000000 
       f7412298 c2010940 00000000 00000092 000009b2 00000000 d72b84b3 00000000 
       00000246 c0135188 f7ff4640 c01326e3 f75b7fd0 00000000 c013276b 00000000 
Call Trace:
 [<c0135188>] prepare_to_wait+0x12/0x49
 [<c01326e3>] worker_thread+0x0/0xc5
 [<c013276b>] worker_thread+0x88/0xc5
 [<c0135075>] autoremove_wake_function+0x0/0x35
 [<c0134fae>] kthread+0x38/0x5e
 [<c0134f76>] kthread+0x0/0x5e
 [<c0104b07>] kernel_thread_helper+0x7/0x10
 =======================
fc_dl_0       S 00000000     0   755      2
       f741f310 00000046 f7fca400 00000000 f741f310 00000000 d72cfc9a 00000000 
       f741f478 c2010940 00000000 00000092 00000c7a 00000000 d72bcc2a 00000000 
       00000246 c0135188 f7ff4940 c01326e3 f751ffd0 00000000 c013276b 00000000 
Call Trace:
 [<c0135188>] prepare_to_wait+0x12/0x49
 [<c01326e3>] worker_thread+0x0/0xc5
 [<c013276b>] worker_thread+0x88/0xc5
 [<c0135075>] autoremove_wake_function+0x0/0x35
 [<c0134fae>] kthread+0x38/0x5e
 [<c0134f76>] kthread+0x0/0x5e
 [<c0104b07>] kernel_thread_helper+0x7/0x10
 =======================
kjournald     S f7471f94     0  1265      2
       f7407870 00000046 00000002 f7471f94 f7471f8c 00000000 f703d800 00000003 
       f74079d8 c2010940 00000000 00082650 00000001 00000286 000000fd 00000001 
       00000000 00000000 f74c8e14 f74c8e00 f7471fcc 00000000 f896bab2 00000000 
Call Trace:
 [<f896bab2>] kjournald+0x15e/0x1d4 [jbd]
 [<c0135075>] autoremove_wake_function+0x0/0x35
 [<f896b954>] kjournald+0x0/0x1d4 [jbd]
 [<c0134fae>] kthread+0x38/0x5e
 [<c0134f76>] kthread+0x0/0x5e
 [<c0104b07>] kernel_thread_helper+0x7/0x10
 =======================
udevd         S f76afb38     0  1464      1
       f7d61310 00000082 00000002 f76afb38 f76afb30 00000000 14f30f21 0000012f 
       f7d61478 c2018940 00000001 0003d589 00000000 00000000 000000ff 00000000 
       00000000 00000000 7fffffff f7d66080 00000008 f76aff9c c02bbe22 000000ff 
Call Trace:
 [<c02bbe22>] schedule_timeout+0x13/0x8d
 [<c0104978>] apic_timer_interrupt+0x28/0x30
 [<c01351ce>] remove_wait_queue+0xf/0x34
 [<c0135234>] add_wait_queue+0x12/0x32
 [<c019b319>] inotify_poll+0x3a/0x40
 [<c0182b33>] do_select+0x372/0x3c9
 [<c0183121>] __pollwait+0x0/0xac
 [<c011f451>] default_wake_function+0x0/0x8
 [<c011f451>] default_wake_function+0x0/0x8
 [<c011f451>] default_wake_function+0x0/0x8
 [<c011f451>] default_wake_function+0x0/0x8
 [<c011da1a>] update_curr+0x62/0xef
 [<c0121c33>] task_tick_fair+0x11/0x42
 [<c0115958>] lapic_next_event+0xc/0x10
 [<c013bc15>] clockevents_program_event+0xe0/0xee
 [<c01e1be5>] number+0x159/0x22f
 [<c025a825>] skb_copy_datagram_iovec+0x53/0x1d3
 [<c01e2506>] vsnprintf+0x442/0x47e
 [<c0113c7d>] flush_tlb_page+0x3e/0x62
 [<c01657d2>] do_wp_page+0x1e0/0x4c8
 [<c0113c7d>] flush_tlb_page+0x3e/0x62
 [<c0167849>] handle_mm_fault+0x609/0x688
 [<c01e1be5>] number+0x159/0x22f
 [<c0182e0f>] core_sys_select+0x285/0x2a2
 [<c0113c7d>] flush_tlb_page+0x3e/0x62
 [<c01657d2>] do_wp_page+0x1e0/0x4c8
 [<c0189d92>] mntput_no_expire+0x11/0x66
 [<c017ff75>] link_path_walk+0xa9/0xb3
 [<c0167849>] handle_mm_fault+0x609/0x688
 [<c011f451>] default_wake_function+0x0/0x8
 [<c017dc8b>] permission+0xa3/0xef
 [<c018625e>] shrink_dcache_parent+0x22/0xc0
 [<c01351ce>] remove_wait_queue+0xf/0x34
 [<c01271e7>] do_wait+0x9b1/0xa47
 [<c01832a3>] sys_select+0xd6/0x187
 [<c01272ae>] sys_wait4+0x31/0x34
 [<c0103e56>] sysenter_past_esp+0x6b/0xa1
 =======================
portmap       S c2016540     0  2538      1
       f7cd93d0 00000082 c2016560 c2016540 00000000 c025f8ec 33dcc7c7 00000236 
       f7cd9538 c2018940 00000001 c2016554 00001089 00000000 f705bb80 00000038 
       00000000 00082225 7fffffff ffffffff f74643c0 00000000 c02bbe22 00000246 
Call Trace:
 [<c025f8ec>] process_backlog+0x6e/0xc9
 [<c02bbe22>] schedule_timeout+0x13/0x8d
 [<c0135234>] add_wait_queue+0x12/0x32
 [<c0135234>] add_wait_queue+0x12/0x32
 [<c028269b>] tcp_poll+0x19/0x120
 [<c0295009>] udp_poll+0x10/0xd5
 [<c01826c0>] do_sys_poll+0x222/0x2dc
 [<c0183121>] __pollwait+0x0/0xac
 [<c011f451>] default_wake_function+0x0/0x8
 [<c011f451>] default_wake_function+0x0/0x8
 [<c02bce5e>] _spin_lock_bh+0x8/0x18
 [<c0255991>] release_sock+0x12/0x8e
 [<c02965ab>] udp_sendmsg+0x4b1/0x5a7
 [<c029b7b1>] inet_sendmsg+0x3b/0x45
 [<c0253cbf>] sock_sendmsg+0xc9/0xe4
 [<c0135075>] autoremove_wake_function+0x0/0x35
 [<c0135075>] autoremove_wake_function+0x0/0x35
 [<c0253e6e>] sys_sendmsg+0x194/0x1f9
 [<c025498c>] sys_recvmsg+0x150/0x1d2
 [<c012c574>] mod_timer+0x19/0x36
 [<c0255abf>] sk_reset_timer+0xc/0x16
 [<c028d8fa>] __tcp_push_pending_frames+0x72d/0x7d2
 [<c0177915>] do_sync_read+0xc7/0x10a
 [<c02bce5e>] _spin_lock_bh+0x8/0x18
 [<c02550c9>] sys_socketcall+0x240/0x261
 [<c0189d92>] mntput_no_expire+0x11/0x66
 [<c01830ee>] sys_poll+0x3a/0x6d
 [<c0103e56>] sysenter_past_esp+0x6b/0xa1
 =======================
syslogd       S 00001000     0  2662      1
       f7d2a0f0 00000086 f8a976c2 00001000 f896776d c20f8b00 67e0d33d 00000237 
       f7d2a258 c2010940 00000000 f70ffb60 00000000 00000000 0074800d f78b8158 
       00000000 f7949ba8 7fffffff f745f980 00000001 f70fff9c c02bbe22 f7949d68 
Call Trace:
 [<f8a976c2>] __ext3_get_inode_loc+0x10f/0x2dd [ext3]
 [<f896776d>] do_get_write_access+0x2f9/0x332 [jbd]
 [<c02bbe22>] schedule_timeout+0x13/0x8d
 [<f8aa2dca>] __ext3_journal_dirty_metadata+0x16/0x3a [ext3]
 [<c01351ce>] remove_wait_queue+0xf/0x34
 [<c0135234>] add_wait_queue+0x12/0x32
 [<c025aae4>] datagram_poll+0x14/0xb1
 [<c0182b33>] do_select+0x372/0x3c9
 [<c0183121>] __pollwait+0x0/0xac
 [<c011f451>] default_wake_function+0x0/0x8
 [<f8a976c2>] __ext3_get_inode_loc+0x10f/0x2dd [ext3]
 [<f8aa2dca>] __ext3_journal_dirty_metadata+0x16/0x3a [ext3]
 [<f89677c7>] journal_get_write_access+0x21/0x26 [jbd]
 [<f8a9754d>] ext3_mark_iloc_dirty+0x27b/0x2e1 [ext3]
 [<f8a9791e>] ext3_mark_inode_dirty+0x20/0x27 [ext3]
 [<c011ef21>] __wake_up+0x32/0x42
 [<f8967468>] journal_stop+0x15d/0x169 [jbd]
 [<f8a9e98b>] __ext3_journal_stop+0x19/0x34 [ext3]
 [<f8a996d1>] ext3_ordered_write_end+0xf4/0x122 [ext3]
 [<c015af0f>] generic_file_buffered_write+0x1ac/0x5a1
 [<c018db92>] generic_getxattr+0x3e/0x44
 [<c018db54>] generic_getxattr+0x0/0x44
 [<c015b795>] __generic_file_aio_write_nolock+0x491/0x4f0
 [<c0182e0f>] core_sys_select+0x285/0x2a2
 [<f8a96018>] ext3_file_write+0x24/0x8f [ext3]
 [<c0177707>] do_sync_readv_writev+0xc1/0xfe
 [<c0135075>] autoremove_wake_function+0x0/0x35
 [<c01039a3>] do_notify_resume+0x50c/0x60c
 [<c01775bc>] rw_copy_check_uvector+0x50/0xaa
 [<c0177e57>] do_readv_writev+0xb5/0x180
 [<c017d114>] pipe_write+0x0/0x3e6
 [<c01832a3>] sys_select+0xd6/0x187
 [<c012d479>] recalc_sigpending+0xb/0x30
 [<c012d53f>] sigprocmask+0xa1/0xc7
 [<c012f059>] sys_rt_sigprocmask+0x4b/0xc7
 [<c0103e56>] sysenter_past_esp+0x6b/0xa1
 =======================
klogd         R running      0  2668      1
sshd          S f7787b38     0  2770      1
       f7ffa690 00200082 00000002 f7787b38 f7787b30 00000000 00000000 f78b8040 
       f7ffa7f8 c2010940 00000000 ffff0872 f896776d c018fec4 000000ff 00000000 
       00000000 00000000 7fffffff f762ac00 00000004 f7787f9c c02bbe22 00001000 
Call Trace:
 [<f896776d>] do_get_write_access+0x2f9/0x332 [jbd]
 [<c018fec4>] __mark_inode_dirty+0x24/0x144
 [<c02bbe22>] schedule_timeout+0x13/0x8d
 [<f8a95389>] ext3_new_blocks+0x4c6/0x5cd [ext3]
 [<c0135234>] add_wait_queue+0x12/0x32
 [<c028269b>] tcp_poll+0x19/0x120
 [<c018244a>] free_poll_entry+0xe/0x16
 [<c0182b33>] do_select+0x372/0x3c9
 [<c0183121>] __pollwait+0x0/0xac
 [<c011f451>] default_wake_function+0x0/0x8
 [<c011f451>] default_wake_function+0x0/0x8
 [<f896776d>] do_get_write_access+0x2f9/0x332 [jbd]
 [<f8a976c2>] __ext3_get_inode_loc+0x10f/0x2dd [ext3]
 [<c0193024>] __find_get_block_slow+0x3a/0x11a
 [<f8aa2dca>] __ext3_journal_dirty_metadata+0x16/0x3a [ext3]
 [<f89677c7>] journal_get_write_access+0x21/0x26 [jbd]
 [<f8a9754d>] ext3_mark_iloc_dirty+0x27b/0x2e1 [ext3]
 [<f8a9791e>] ext3_mark_inode_dirty+0x20/0x27 [ext3]
 [<f8a9e98b>] __ext3_journal_stop+0x19/0x34 [ext3]
 [<c018fec4>] __mark_inode_dirty+0x24/0x144
 [<c0193aa6>] block_write_end+0x4d/0x55
 [<f8967468>] journal_stop+0x15d/0x169 [jbd]
 [<f8a97c47>] ext3_generic_write_end+0x72/0x7c [ext3]
 [<f8a9e98b>] __ext3_journal_stop+0x19/0x34 [ext3]
 [<f8a996d1>] ext3_ordered_write_end+0xf4/0x122 [ext3]
 [<c015af0f>] generic_file_buffered_write+0x1ac/0x5a1
 [<c025923b>] __alloc_skb+0x49/0xf5
 [<c0182e0f>] core_sys_select+0x285/0x2a2
 [<c015e72d>] __alloc_pages+0x59/0x2d5
 [<c011d152>] kunmap_atomic+0x66/0x95
 [<c0113c7d>] flush_tlb_page+0x3e/0x62
 [<c01657d2>] do_wp_page+0x1e0/0x4c8
 [<c0167849>] handle_mm_fault+0x609/0x688
 [<c011ef21>] __wake_up+0x32/0x42
 [<c0258720>] skb_dequeue+0x39/0x3f
 [<c01832a3>] sys_select+0xd6/0x187
 [<c0189d92>] mntput_no_expire+0x11/0x66
 [<c01761b4>] filp_close+0x51/0x58
 [<c0103e56>] sysenter_past_esp+0x6b/0xa1
 [<c02b0000>] unix_create1+0xbb/0xfa
 =======================
rpc.statd     S f77fbb38     0  2804      1
       f7407290 00000086 00000002 f77fbb38 f77fbb30 00000000 00000001 c20159c0 
       f74073f8 c2018940 00000001 ffff0254 c2015a08 00000000 000000ff 00000000 
       00000000 00000000 7fffffff f7c54cc0 00000008 f77fbf9c c02bbe22 00000246 
Call Trace:
 [<c02bbe22>] schedule_timeout+0x13/0x8d
 [<c0135234>] add_wait_queue+0x12/0x32
 [<c0135234>] add_wait_queue+0x12/0x32
 [<c028269b>] tcp_poll+0x19/0x120
 [<c0295009>] udp_poll+0x10/0xd5
 [<c0182b33>] do_select+0x372/0x3c9
 [<c0183121>] __pollwait+0x0/0xac
 [<c011f451>] default_wake_function+0x0/0x8
 [<c011f451>] default_wake_function+0x0/0x8
 [<c011f451>] default_wake_function+0x0/0x8
 [<c0183121>] __pollwait+0x0/0xac
 [<c011f451>] default_wake_function+0x0/0x8
 [<c012908f>] local_bh_enable+0x83/0x91
 [<c025fc69>] dev_queue_xmit+0x287/0x2ae
 [<c027bbc0>] ip_cork_release+0x19/0x76
 [<c027bf59>] ip_push_pending_frames+0x33c/0x346
 [<c027d512>] ip_generic_getfrag+0x0/0x96
 [<c029545c>] udp_push_pending_frames+0x2b7/0x31e
 [<c02bce5e>] _spin_lock_bh+0x8/0x18
 [<c0255991>] release_sock+0x12/0x8e
 [<c025a395>] memcpy_toiovec+0x27/0x4a
 [<c025a825>] skb_copy_datagram_iovec+0x53/0x1d3
 [<c025abf6>] skb_recv_datagram+0x75/0x1a3
 [<c0259185>] skb_release_all+0xa3/0xfa
 [<c0296c5c>] udp_recvmsg+0x183/0x1d0
 [<c0255375>] sock_common_recvmsg+0x3e/0x54
 [<c0253bdb>] sock_recvmsg+0xe5/0x100
 [<c0135075>] autoremove_wake_function+0x0/0x35
 [<c0182e0f>] core_sys_select+0x285/0x2a2
 [<c0254824>] move_addr_to_user+0x50/0x68
 [<c0254b16>] sys_recvfrom+0x108/0x12b
 [<c02547a9>] sys_bind+0x6e/0x99
 [<c029b618>] inet_create+0x1eb/0x27e
 [<c02bce5e>] _spin_lock_bh+0x8/0x18
 [<c029c43f>] inet_sock_destruct+0x16a/0x1af
 [<c02bce5e>] _spin_lock_bh+0x8/0x18
 [<c01832a3>] sys_select+0xd6/0x187
 [<c0189d92>] mntput_no_expire+0x11/0x66
 [<c01761b4>] filp_close+0x51/0x58
 [<c0103e56>] sysenter_past_esp+0x6b/0xa1
 =======================
rpciod/0      S f713dfa0     0  2809      2
       f7d1f830 00000046 00000002 f713dfa0 f713df98 00000000 f8c70647 00000000 
       f7d1f998 c2010940 00000000 0003d596 f79fe500 f770c240 000000ff 00000000 
       00000000 00000000 f770c240 c01326e3 f713dfd0 00000000 c013276b 00000000 
Call Trace:
 [<f8c70647>] xs_udp_connect_worker4+0x0/0xda [sunrpc]
 [<c01326e3>] worker_thread+0x0/0xc5
 [<c013276b>] worker_thread+0x88/0xc5
 [<c0135075>] autoremove_wake_function+0x0/0x35
 [<c0134fae>] kthread+0x38/0x5e
 [<c0134f76>] kthread+0x0/0x5e
 [<c0104b07>] kernel_thread_helper+0x7/0x10
 =======================
rpciod/1      S f713ffa0     0  2810      2
       f741f8f0 00000046 00000002 f713ffa0 f713ff98 00000000 f8c70647 00000000 
       f741fa58 c2018940 00000001 0003d597 f79fe500 f770c280 000000ff 00000000 
       00000000 00000000 f770c280 c01326e3 f713ffd0 00000000 c013276b 00000000 
Call Trace:
 [<f8c70647>] xs_udp_connect_worker4+0x0/0xda [sunrpc]
 [<c01326e3>] worker_thread+0x0/0xc5
 [<c013276b>] worker_thread+0x88/0xc5
 [<c0135075>] autoremove_wake_function+0x0/0x35
 [<c0134fae>] kthread+0x38/0x5e
 [<c0134f76>] kthread+0x0/0x5e
 [<c0104b07>] kernel_thread_helper+0x7/0x10
 =======================
rpc.idmapd    S f711df10     0  2826      1
       f7fd6230 00000086 00000002 f711df10 f711df08 00000000 edab2ccb 00000235 
       f7fd6398 c2018940 00000001 000825c7 f711df34 f7c70000 000000ff 00000000 
       00000000 00000000 f711df34 00082a71 000003e7 00000202 c02bbe7f 00000001 
Call Trace:
 [<c02bbe7f>] schedule_timeout+0x70/0x8d
 [<c012c215>] process_timeout+0x0/0x5
 [<c02bbe7a>] schedule_timeout+0x6b/0x8d
 [<c019bbc7>] sys_epoll_wait+0x150/0x3be
 [<c01391c4>] do_gettimeofday+0x31/0xce
 [<c011f451>] default_wake_function+0x0/0x8
 [<c0103e56>] sysenter_past_esp+0x6b/0xa1
 [<c02b0000>] unix_create1+0xbb/0xfa
 =======================
getty         S f715feac     0  3141      1
       f7c760b0 00000082 f715fea4 f715feac f715fea4 00000000 00000000 c0234dd1 
       f7c76218 c2018940 00000001 ffff04a8 00000020 00000008 000000ff 00000000 
       00000000 00000400 7fffffff f7011000 f715ff40 bf8fdd6b c02bbe22 c2015134 
Call Trace:
 [<c0234dd1>] do_con_write+0x1774/0x17cd
 [<c02bbe22>] schedule_timeout+0x13/0x8d
 [<c015dfeb>] __pagevec_free+0x14/0x1a
 [<c0160aa9>] release_pages+0x13e/0x146
 [<c01f58f7>] vgacon_set_cursor_size+0xe1/0xf9
 [<c0135234>] add_wait_queue+0x12/0x32
 [<c022b644>] read_chan+0x310/0x58c
 [<c011f451>] default_wake_function+0x0/0x8
 [<c022b334>] read_chan+0x0/0x58c
 [<c0228938>] tty_read+0x64/0xac
 [<c02288d4>] tty_read+0x0/0xac
 [<c017819b>] vfs_read+0x9f/0x14b
 [<c0178604>] sys_read+0x41/0x67
 [<c0103e56>] sysenter_past_esp+0x6b/0xa1
 [<c02b0000>] unix_create1+0xbb/0xfa
 =======================
getty         S 00000000     0  3142      1
       f7cc01b0 00000082 ffffffff 00000000 c0231d4a f74cba00 e72cb073 00000009 
       f7cc0318 c2010940 00000000 f71d5edc 0005d7d6 00000000 f7197800 f71af000 
       2034eda0 00000008 7fffffff f71af000 f71d5f40 bf8fdd6b c02bbe22 c200d134 
Call Trace:
 [<c0231d4a>] notify_update+0x1f/0x22
 [<c02bbe22>] schedule_timeout+0x13/0x8d
 [<c015dfeb>] __pagevec_free+0x14/0x1a
 [<c0160aa9>] release_pages+0x13e/0x146
 [<c0135234>] add_wait_queue+0x12/0x32
 [<c022b644>] read_chan+0x310/0x58c
 [<c011f451>] default_wake_function+0x0/0x8
 [<c022b334>] read_chan+0x0/0x58c
 [<c0228938>] tty_read+0x64/0xac
 [<c02288d4>] tty_read+0x0/0xac
 [<c017819b>] vfs_read+0x9f/0x14b
 [<c0178604>] sys_read+0x41/0x67
 [<c0103e56>] sysenter_past_esp+0x6b/0xa1
 [<c02b0000>] unix_create1+0xbb/0xfa
 =======================
getty         S f71c7eac     0  3143      1
       f7d0e030 00000082 00000002 f71c7eac f71c7ea4 00000000 00000000 00000286 
       f7d0e198 c2010940 00000000 ffff04aa c04ec260 00000001 000000ff 00000000 
       00000000 00000000 7fffffff f740f800 f71c7f40 bfc608cb c02bbe22 f7fa3e58 
Call Trace:
 [<c02bbe22>] schedule_timeout+0x13/0x8d
 [<c02266db>] tty_wakeup+0x4c/0x50
 [<c012921e>] tasklet_action+0x58/0xb8
 [<c0135234>] add_wait_queue+0x12/0x32
 [<c022b644>] read_chan+0x310/0x58c
 [<c011f451>] default_wake_function+0x0/0x8
 [<c022b334>] read_chan+0x0/0x58c
 [<c0228938>] tty_read+0x64/0xac
 [<c02288d4>] tty_read+0x0/0xac
 [<c017819b>] vfs_read+0x9f/0x14b
 [<c0178604>] sys_read+0x41/0x67
 [<c0103e56>] sysenter_past_esp+0x6b/0xa1
 [<c02b0000>] unix_create1+0xbb/0xfa
 =======================
sshd          S f71cfb38     0  3487   2770
       f7d618f0 00000082 00000002 f71cfb38 f71cfb30 00000000 a26a51cf 00000237 
       f7d61a58 c2010940 00000000 000827aa 000087bf 00000000 00000003 c03560b0 
       c03560b0 00000000 7fffffff f7433900 00000008 f71cff9c c02bbe22 00000003 
Call Trace:
 [<c02bbe22>] schedule_timeout+0x13/0x8d
 [<c0226639>] tty_ldisc_deref+0x55/0x64
 [<c02274c4>] tty_poll+0x53/0x60
 [<c0182b33>] do_select+0x372/0x3c9
 [<c0183121>] __pollwait+0x0/0xac
 [<c011f451>] default_wake_function+0x0/0x8
 [<c011f451>] default_wake_function+0x0/0x8
 [<c011f451>] default_wake_function+0x0/0x8
 [<c011f451>] default_wake_function+0x0/0x8
 [<c026c797>] __qdisc_run+0x9e/0x164
 [<c025fc69>] dev_queue_xmit+0x287/0x2ae
 [<c027d2ab>] ip_finish_output+0x1d3/0x20b
 [<c027df20>] ip_queue_xmit+0x31e/0x361
 [<f8898fd7>] e1000_clean+0x1e3/0x20d [e1000]
 [<c028be87>] tcp_transmit_skb+0x661/0x694
 [<c012c32a>] lock_timer_base+0x19/0x35
 [<c012c43e>] __mod_timer+0x9a/0xa4
 [<c0255abf>] sk_reset_timer+0xc/0x16
 [<c028d8fa>] __tcp_push_pending_frames+0x72d/0x7d2
 [<c02bce5e>] _spin_lock_bh+0x8/0x18
 [<c0255991>] release_sock+0x12/0x8e
 [<c02839c2>] tcp_sendmsg+0x927/0xa18
 [<c0182e0f>] core_sys_select+0x285/0x2a2
 [<c02535de>] sock_aio_write+0xe3/0xef
 [<c017780b>] do_sync_write+0xc7/0x10a
 [<c0135075>] autoremove_wake_function+0x0/0x35
 [<c022b334>] read_chan+0x0/0x58c
 [<c01832a3>] sys_select+0xd6/0x187
 [<c017866b>] sys_write+0x41/0x67
 [<c0103e56>] sysenter_past_esp+0x6b/0xa1
 =======================
bash          R running      0  4005   3487
gfs2_scand    S c200d9c0     0  4328      2
       f7fd6810 00000046 000161a5 c200d9c0 00000002 f7205f70 7e71c2c0 00000237 
       f7fd6978 c2010940 00000000 0008274a 13ffabdb 00000000 000000ff 00000000 
       00000000 000161a5 f7205f98 00082c1f 00000000 00000000 c02bbe7f 00000000 
Call Trace:
 [<c02bbe7f>] schedule_timeout+0x70/0x8d
 [<c012c215>] process_timeout+0x0/0x5
 [<c02bbe7a>] schedule_timeout+0x6b/0x8d
 [<f8d1e73c>] gfs2_scand+0x0/0x5b [gfs2]
 [<f8d1e78a>] gfs2_scand+0x4e/0x5b [gfs2]
 [<c0134fae>] kthread+0x38/0x5e
 [<c0134f76>] kthread+0x0/0x5e
 [<c0104b07>] kernel_thread_helper+0x7/0x10
 =======================
glock_workque S f71f1fa0     0  4331      2
       f7fd73d0 00000046 00000002 f71f1fa0 f71f1f98 00000000 f7fd73d0 f7490040 
       f7fd7538 c2010940 00000000 0000dd5d f71f1fb8 00000000 000000ff 00000000 
       00000000 00000000 f71c8e00 c01326e3 f71f1fd0 00000000 c013276b 00000000 
Call Trace:
 [<c01326e3>] worker_thread+0x0/0xc5
 [<c013276b>] worker_thread+0x88/0xc5
 [<c0135075>] autoremove_wake_function+0x0/0x35
 [<c0134fae>] kthread+0x38/0x5e
 [<c0134f76>] kthread+0x0/0x5e
 [<c0104b07>] kernel_thread_helper+0x7/0x10
 =======================
glock_workque S f7127fa0     0  4332      2
       f7d2b290 00000046 00000002 f7127fa0 f7127f98 00000000 f7d2b290 f7424580 
       f7d2b3f8 c2018940 00000001 0000dd6b f7127fb8 00000000 000000ff 00000000 
       00000000 00000000 f71c8fc0 c01326e3 f7127fd0 00000000 c013276b 00000000 
Call Trace:
 [<c01326e3>] worker_thread+0x0/0xc5
 [<c013276b>] worker_thread+0x88/0xc5
 [<c0135075>] autoremove_wake_function+0x0/0x35
 [<c0134fae>] kthread+0x38/0x5e
 [<c0134f76>] kthread+0x0/0x5e
 [<c0104b07>] kernel_thread_helper+0x7/0x10
 =======================
ccsd          S c200df80     0  4342      1
       f7412710 00000086 c012bf83 c200df80 00000002 c0138050 67dce113 00000237 
       f7412878 c2010940 00000000 0000000a 00000000 00000000 00000046 00000000 
       00000000 00000001 7fffffff f7729500 00000009 f716ff9c c02bbe22 00000246 
Call Trace:
 [<c012bf83>] run_timer_softirq+0x30/0x195
 [<c0138050>] hrtimer_interrupt+0x198/0x1c0
 [<c02bbe22>] schedule_timeout+0x13/0x8d
 [<c0135234>] add_wait_queue+0x12/0x32
 [<c0135234>] add_wait_queue+0x12/0x32
 [<c02af0ca>] unix_poll+0x17/0x8b
 [<c0182b33>] do_select+0x372/0x3c9
 [<c0183121>] __pollwait+0x0/0xac
 [<c011f451>] default_wake_function+0x0/0x8
 [<c011f451>] default_wake_function+0x0/0x8
 [<c011f451>] default_wake_function+0x0/0x8
 [<c011d140>] kunmap_atomic+0x54/0x95
 [<c011d152>] kunmap_atomic+0x66/0x95
 [<c01099ca>] sched_clock+0x8/0x18
 [<c011dac1>] __update_rq_clock+0x1a/0xf3
 [<c011da1a>] update_curr+0x62/0xef
 [<c0121c33>] task_tick_fair+0x11/0x42
 [<c011e0cf>] enqueue_entity+0x2b/0x3d
 [<c011da1a>] update_curr+0x62/0xef
 [<c0103096>] __switch_to+0xfa/0x11c
 [<c02bbc1a>] schedule+0x588/0x5ec
 [<c02bbe22>] schedule_timeout+0x13/0x8d
 [<c025923b>] __alloc_skb+0x49/0xf5
 [<c0255c2d>] sock_alloc_send_skb+0x6e/0x196
 [<c0257159>] sock_def_readable+0x12/0x63
 [<c02b0b4a>] unix_stream_sendmsg+0x24c/0x30b
 [<c0182e0f>] core_sys_select+0x285/0x2a2
 [<c02535de>] sock_aio_write+0xe3/0xef
 [<c011ef21>] __wake_up+0x32/0x42
 [<c017780b>] do_sync_write+0xc7/0x10a
 [<c011ef21>] __wake_up+0x32/0x42
 [<c01832a3>] sys_select+0xd6/0x187
 [<c0189d92>] mntput_no_expire+0x11/0x66
 [<c01761b4>] filp_close+0x51/0x58
 [<c0103e56>] sysenter_past_esp+0x6b/0xa1
 =======================
ccsd          S 00000020     0  4343      1
       f7d2acb0 00000086 c028c04c 00000020 00000000 f1028080 f7f1e368 00000232 
       f7d2ae18 c2010940 00000000 5cb5d57b 00020fdd 00000000 f71ee130 c029018c 
       00000034 c011ec17 7fffffff f7729080 0000000a f77a3f9c c02bbe22 f0dafbf8 
Call Trace:
 [<c028c04c>] tcp_send_ack+0xe8/0xec
 [<c029018c>] tcp_v4_do_rcv+0x2b/0x348
 [<c011ec17>] task_rq_lock+0x3b/0x5e
 [<c02bbe22>] schedule_timeout+0x13/0x8d
 [<c0135234>] add_wait_queue+0x12/0x32
 [<c0135234>] add_wait_queue+0x12/0x32
 [<c02af0ca>] unix_poll+0x17/0x8b
 [<c0182b33>] do_select+0x372/0x3c9
 [<c0183121>] __pollwait+0x0/0xac
 [<c011f451>] default_wake_function+0x0/0x8
 [<c011f451>] default_wake_function+0x0/0x8
 [<c0255abf>] sk_reset_timer+0xc/0x16
 [<c028b082>] tcp_rcv_established+0x5c9/0x62b
 [<c025f393>] net_rx_action+0x9f/0x198
 [<c029018c>] tcp_v4_do_rcv+0x2b/0x348
 [<c02924b1>] tcp_v4_rcv+0x814/0x887
 [<c025fc69>] dev_queue_xmit+0x287/0x2ae
 [<c0279c78>] ip_local_deliver_finish+0x113/0x1b6
 [<c0279b46>] ip_rcv_finish+0x272/0x291
 [<f8a976c2>] __ext3_get_inode_loc+0x10f/0x2dd [ext3]
 [<c025d47c>] netif_receive_skb+0x2e4/0x350
 [<c025f8ec>] process_backlog+0x6e/0xc9
 [<c025f393>] net_rx_action+0x9f/0x198
 [<c028abba>] tcp_rcv_established+0x101/0x62b
 [<c012908f>] local_bh_enable+0x83/0x91
 [<c025fc69>] dev_queue_xmit+0x287/0x2ae
 [<c027d2ab>] ip_finish_output+0x1d3/0x20b
 [<c027df20>] ip_queue_xmit+0x31e/0x361
 [<c0182e0f>] core_sys_select+0x285/0x2a2
 [<c028be87>] tcp_transmit_skb+0x661/0x694
 [<f8967468>] journal_stop+0x15d/0x169 [jbd]
 [<c012c574>] mod_timer+0x19/0x36
 [<c0255abf>] sk_reset_timer+0xc/0x16
 [<c028d8fa>] __tcp_push_pending_frames+0x72d/0x7d2
 [<c0160aa9>] release_pages+0x13e/0x146
 [<c02bce5e>] _spin_lock_bh+0x8/0x18
 [<c0284881>] tcp_close+0x527/0x546
 [<c01832a3>] sys_select+0xd6/0x187
 [<c0189d92>] mntput_no_expire+0x11/0x66
 [<c01761b4>] filp_close+0x51/0x58
 [<c0103e56>] sysenter_past_esp+0x6b/0xa1
 =======================
aisexec       S c200d9c0     0  4347      1
       f7d60750 00000082 00000d04 c200d9c0 00000002 f7141bd4 9e30a1b7 00000237 
       f7d608b8 c2010940 00000000 0008282a 14826f0a 00000000 000000ff 00000000 
       00000000 00000d04 f7141bfc 000827f8 f7c52080 00000000 c02bbe7f 00000246 
Call Trace:
 [<c02bbe7f>] schedule_timeout+0x70/0x8d
 [<c0135234>] add_wait_queue+0x12/0x32
 [<c012c215>] process_timeout+0x0/0x5
 [<c02bbe7a>] schedule_timeout+0x6b/0x8d
 [<c01826c0>] do_sys_poll+0x222/0x2dc
 [<c0183121>] __pollwait+0x0/0xac
 [<c011f451>] default_wake_function+0x0/0x8
 [<c011f451>] default_wake_function+0x0/0x8
 [<c011f451>] default_wake_function+0x0/0x8
 [<c011f451>] default_wake_function+0x0/0x8
 [<c011f451>] default_wake_function+0x0/0x8
 [<c011f451>] default_wake_function+0x0/0x8
 [<c011f451>] default_wake_function+0x0/0x8
 [<c011f451>] default_wake_function+0x0/0x8
 [<c011f451>] default_wake_function+0x0/0x8
 [<c011f451>] default_wake_function+0x0/0x8
 [<c011f451>] default_wake_function+0x0/0x8
 [<c011f451>] default_wake_function+0x0/0x8
 [<c0135075>] autoremove_wake_function+0x0/0x35
 [<c0135075>] autoremove_wake_function+0x0/0x35
 [<c0254824>] move_addr_to_user+0x50/0x68
 [<c02549fa>] sys_recvmsg+0x1be/0x1d2
 [<c025600d>] sk_free+0xa9/0xb6
 [<c01391c4>] do_gettimeofday+0x31/0xce
 [<c01830ee>] sys_poll+0x3a/0x6d
 [<c0103e56>] sysenter_past_esp+0x6b/0xa1
 =======================
aisexec       S f78b8158     0  4348      1
       f7d60170 00000082 001a0007 f78b8158 00000000 f78edb70 eb8fde28 0000007a 
       f7d602d8 c2010940 00000000 00000000 00000000 00000000 f78b80b0 f78edb70 
       c1042160 00000000 7fffffff ffffffff 00000000 00000000 c02bbe22 001a000e 
Call Trace:
 [<c02bbe22>] schedule_timeout+0x13/0x8d
 [<c01930fa>] __find_get_block_slow+0x110/0x11a
 [<c01826c0>] do_sys_poll+0x222/0x2dc
 [<c0183121>] __pollwait+0x0/0xac
 [<c0193472>] __find_get_block+0x176/0x180
 [<c019349f>] __getblk+0x23/0x27e
 [<c0186791>] __d_lookup+0x96/0xd9
 [<c0174be1>] cache_alloc_refill+0x58/0x476
 [<c02af8af>] unix_find_other+0x11a/0x16c
 [<c025923b>] __alloc_skb+0x49/0xf5
 [<c02b13e2>] unix_write_space+0xf/0x63
 [<c025743d>] sock_wfree+0x21/0x36
 [<c0259185>] skb_release_all+0xa3/0xfa
 [<c02afd2e>] unix_dgram_sendmsg+0x42d/0x467
 [<c0253cbf>] sock_sendmsg+0xc9/0xe4
 [<c0159f56>] find_lock_page+0x19/0x7f
 [<c015bf92>] filemap_fault+0x213/0x384
 [<c015e72d>] __alloc_pages+0x59/0x2d5
 [<c017dc8b>] permission+0xa3/0xef
 [<c0113c7d>] flush_tlb_page+0x3e/0x62
 [<c01655b1>] __do_fault+0x32d/0x36e
 [<c011f447>] try_to_wake_up+0x2b7/0x2c1
 [<c016750f>] handle_mm_fault+0x2cf/0x688
 [<c011dfcb>] pick_next_task_fair+0x1f/0x2d
 [<c011da1a>] update_curr+0x62/0xef
 [<c011bf8f>] do_page_fault+0x1f7/0x5a8
 [<c011d6d2>] activate_task+0x1c/0x28
 [<c0120a91>] sched_setscheduler+0x25b/0x2ae
 [<c01830ee>] sys_poll+0x3a/0x6d
 [<c0103e56>] sysenter_past_esp+0x6b/0xa1
 =======================
aisexec       S f7167e1c     0  4349      1
       f7d2b870 00000082 00000002 f7167e1c f7167e14 00000000 c0169120 08185100 
       f7d2b9d8 c2010940 00000000 0000ded5 00000000 00000000 000000ff 00000000 
       00000000 00000000 f741a774 f7167e9c c04d8870 08185100 c013d69a c034f728 
Call Trace:
 [<c0169120>] find_extend_vma+0x12/0x49
 [<c013d69a>] futex_wait+0x192/0x2a1
 [<c011d140>] kunmap_atomic+0x54/0x95
 [<c011d152>] kunmap_atomic+0x66/0x95
 [<c0113c7d>] flush_tlb_page+0x3e/0x62
 [<c011ec17>] task_rq_lock+0x3b/0x5e
 [<c011f447>] try_to_wake_up+0x2b7/0x2c1
 [<c011f451>] default_wake_function+0x0/0x8
 [<c013e611>] do_futex+0x69/0x957
 [<c011df66>] set_next_entity+0x11/0x38
 [<c0189d92>] mntput_no_expire+0x11/0x66
 [<c013efc1>] sys_futex+0xc2/0xd4
 [<c0103e56>] sysenter_past_esp+0x6b/0xa1
 =======================
aisexec       S c200d9c0     0  4353      1
       f7cb5310 00000082 00016832 c200d9c0 00000002 f71fdbd4 28699197 0000012f 
       f7cb5478 c2010940 00000000 0003d032 001f1993 00000000 000000ff 00000000 
       00000000 00016832 7fffffff ffffffff f7cc4680 00000000 c02bbe22 00000000 
Call Trace:
 [<c02bbe22>] schedule_timeout+0x13/0x8d
 [<c0135234>] add_wait_queue+0x12/0x32
 [<c02af0ca>] unix_poll+0x17/0x8b
 [<c01826c0>] do_sys_poll+0x222/0x2dc
 [<c0183121>] __pollwait+0x0/0xac
 [<c011f451>] default_wake_function+0x0/0x8
 [<c011f447>] try_to_wake_up+0x2b7/0x2c1
 [<c011d4e6>] __wake_up_common+0x32/0x5c
 [<c013508a>] autoremove_wake_function+0x15/0x35
 [<c011d4e6>] __wake_up_common+0x32/0x5c
 [<c011ef21>] __wake_up+0x32/0x42
 [<c0257180>] sock_def_readable+0x39/0x63
 [<c02b0b4a>] unix_stream_sendmsg+0x24c/0x30b
 [<c0253cbf>] sock_sendmsg+0xc9/0xe4
 [<c0135075>] autoremove_wake_function+0x0/0x35
 [<c0135075>] autoremove_wake_function+0x0/0x35
 [<c0253ebf>] sys_sendmsg+0x1e5/0x1f9
 [<c02549fa>] sys_recvmsg+0x1be/0x1d2
 [<c011f447>] try_to_wake_up+0x2b7/0x2c1
 [<c01099ca>] sched_clock+0x8/0x18
 [<c0103039>] __switch_to+0x9d/0x11c
 [<c02bce5e>] _spin_lock_bh+0x8/0x18
 [<c02bce5e>] _spin_lock_bh+0x8/0x18
 [<c0255991>] release_sock+0x12/0x8e
 [<c02570cf>] sock_setsockopt+0x47e/0x496
 [<c01099ca>] sched_clock+0x8/0x18
 [<c0103039>] __switch_to+0x9d/0x11c
 [<c02550c9>] sys_socketcall+0x240/0x261
 [<c01830ee>] sys_poll+0x3a/0x6d
 [<c0103e56>] sysenter_past_esp+0x6b/0xa1
 =======================
aisexec       S c200e540     0  4354      1
       f7d12070 00000082 c200e560 c200e540 00000000 c025f8ec 284caf3c 0000012f 
       f7d121d8 c2010940 00000000 c200e554 000082c7 00000000 f7fb9000 f7fb9000 
       f753e980 0003d297 7fffffff ffffffff f7cc4c80 00000000 c02bbe22 00000000 
Call Trace:
 [<c025f8ec>] process_backlog+0x6e/0xc9
 [<c02bbe22>] schedule_timeout+0x13/0x8d
 [<c0135234>] add_wait_queue+0x12/0x32
 [<c02af0ca>] unix_poll+0x17/0x8b
 [<c01826c0>] do_sys_poll+0x222/0x2dc
 [<c0183121>] __pollwait+0x0/0xac
 [<c011f451>] default_wake_function+0x0/0x8
 [<c011f447>] try_to_wake_up+0x2b7/0x2c1
 [<c02bce5e>] _spin_lock_bh+0x8/0x18
 [<c013508a>] autoremove_wake_function+0x15/0x35
 [<c011d4e6>] __wake_up_common+0x32/0x5c
 [<c011ef21>] __wake_up+0x32/0x42
 [<c0257180>] sock_def_readable+0x39/0x63
 [<c02b0b4a>] unix_stream_sendmsg+0x24c/0x30b
 [<c0253cbf>] sock_sendmsg+0xc9/0xe4
 [<c0135075>] autoremove_wake_function+0x0/0x35
 [<c0135075>] autoremove_wake_function+0x0/0x35
 [<c02bbc1a>] schedule+0x588/0x5ec
 [<c0253ebf>] sys_sendmsg+0x1e5/0x1f9
 [<c02549fa>] sys_recvmsg+0x1be/0x1d2
 [<c011d4e6>] __wake_up_common+0x32/0x5c
 [<c013d37f>] get_futex_key+0x6e/0x122
 [<c013da8b>] futex_wake+0xa6/0xb0
 [<c013e624>] do_futex+0x7c/0x957
 [<c02570cf>] sock_setsockopt+0x47e/0x496
 [<c01099ca>] sched_clock+0x8/0x18
 [<c0103039>] __switch_to+0x9d/0x11c
 [<c02bbc1a>] schedule+0x588/0x5ec
 [<c01830ee>] sys_poll+0x3a/0x6d
 [<c0103e56>] sysenter_past_esp+0x6b/0xa1
 =======================
aisexec       S f76d7bd8     0  4361      1
       f7cb4170 00000082 00000002 f76d7bd8 f76d7bd0 00000000 3bed7aa8 0000012f 
       f7cb42d8 c2018940 00000001 0000e0b7 00000000 00000000 000000ff 00000000 
       00000000 00000000 7fffffff ffffffff f7d1a840 00000000 c02bbe22 00000000 
Call Trace:
 [<c02bbe22>] schedule_timeout+0x13/0x8d
 [<c0135234>] add_wait_queue+0x12/0x32
 [<c02af0ca>] unix_poll+0x17/0x8b
 [<c01826c0>] do_sys_poll+0x222/0x2dc
 [<c0183121>] __pollwait+0x0/0xac
 [<c011f451>] default_wake_function+0x0/0x8
 [<c011f447>] try_to_wake_up+0x2b7/0x2c1
 [<c011d4e6>] __wake_up_common+0x32/0x5c
 [<c013508a>] autoremove_wake_function+0x15/0x35
 [<c011d4e6>] __wake_up_common+0x32/0x5c
 [<c011ef21>] __wake_up+0x32/0x42
 [<c0257180>] sock_def_readable+0x39/0x63
 [<c02b0b4a>] unix_stream_sendmsg+0x24c/0x30b
 [<c0253cbf>] sock_sendmsg+0xc9/0xe4
 [<c0135075>] autoremove_wake_function+0x0/0x35
 [<c0135075>] autoremove_wake_function+0x0/0x35
 [<c0253ebf>] sys_sendmsg+0x1e5/0x1f9
 [<c02549fa>] sys_recvmsg+0x1be/0x1d2
 [<c01e1be5>] number+0x159/0x22f
 [<c011e0f7>] enqueue_task_fair+0x16/0x24
 [<c011d6d2>] activate_task+0x1c/0x28
 [<c011f447>] try_to_wake_up+0x2b7/0x2c1
 [<c02bce5e>] _spin_lock_bh+0x8/0x18
 [<c02bce5e>] _spin_lock_bh+0x8/0x18
 [<c0255991>] release_sock+0x12/0x8e
 [<c02570cf>] sock_setsockopt+0x47e/0x496
 [<c01099ca>] sched_clock+0x8/0x18
 [<c02550c9>] sys_socketcall+0x240/0x261
 [<c01830ee>] sys_poll+0x3a/0x6d
 [<c0103e56>] sysenter_past_esp+0x6b/0xa1
 =======================
aisexec       S c2016540     0  4362      1
       f7cb4750 00000082 c2016560 c2016540 00000000 c025f8ec 4f86a901 0000012f 
       f7cb48b8 c2010940 00000000 c2016554 000009ee 00000000 f7fb9000 f7fb9000 
       f708a380 0003d33c 7fffffff ffffffff f7d1af00 00000000 c02bbe22 00000001 
Call Trace:
 [<c025f8ec>] process_backlog+0x6e/0xc9
 [<c02bbe22>] schedule_timeout+0x13/0x8d
 [<c0135234>] add_wait_queue+0x12/0x32
 [<c02af0ca>] unix_poll+0x17/0x8b
 [<c01826c0>] do_sys_poll+0x222/0x2dc
 [<c0183121>] __pollwait+0x0/0xac
 [<c011f451>] default_wake_function+0x0/0x8
 [<c011f447>] try_to_wake_up+0x2b7/0x2c1
 [<c02bce5e>] _spin_lock_bh+0x8/0x18
 [<c013508a>] autoremove_wake_function+0x15/0x35
 [<c011d4e6>] __wake_up_common+0x32/0x5c
 [<c011ef21>] __wake_up+0x32/0x42
 [<c0257180>] sock_def_readable+0x39/0x63
 [<c02b0b4a>] unix_stream_sendmsg+0x24c/0x30b
 [<c0253cbf>] sock_sendmsg+0xc9/0xe4
 [<c0135075>] autoremove_wake_function+0x0/0x35
 [<c0135075>] autoremove_wake_function+0x0/0x35
 [<c011da1a>] update_curr+0x62/0xef
 [<c01099ca>] sched_clock+0x8/0x18
 [<c011d6ab>] enqueue_task+0x52/0x5d
 [<c011d6d2>] activate_task+0x1c/0x28
 [<c011f447>] try_to_wake_up+0x2b7/0x2c1
 [<c011d4e6>] __wake_up_common+0x32/0x5c
 [<c011ef21>] __wake_up+0x32/0x42
 [<c013d7e4>] wake_futex+0x3b/0x45
 [<c013da8b>] futex_wake+0xa6/0xb0
 [<c013e624>] do_futex+0x7c/0x957
 [<c02570cf>] sock_setsockopt+0x47e/0x496
 [<c01099ca>] sched_clock+0x8/0x18
 [<c0103039>] __switch_to+0x9d/0x11c
 [<c02bbc1a>] schedule+0x588/0x5ec
 [<c013efc1>] sys_futex+0xc2/0xd4
 [<c01830ee>] sys_poll+0x3a/0x6d
 [<c0103e56>] sysenter_past_esp+0x6b/0xa1
 =======================
aisexec       S c200d9c0     0  4363      1
       f7cb58f0 00000082 0002b572 c200d9c0 00000002 f71edbd4 69d6f449 0000007b 
       f7cb5a58 c2010940 00000000 0000e0b7 14cd9b81 00000000 000000ff 00000000 
       00000000 0002b572 7fffffff ffffffff f7d1a3c0 00000000 c02bbe22 00000001 
Call Trace:
 [<c02bbe22>] schedule_timeout+0x13/0x8d
 [<c0135234>] add_wait_queue+0x12/0x32
 [<c02af0ca>] unix_poll+0x17/0x8b
 [<c01826c0>] do_sys_poll+0x222/0x2dc
 [<c0183121>] __pollwait+0x0/0xac
 [<c011f451>] default_wake_function+0x0/0x8
 [<c011f447>] try_to_wake_up+0x2b7/0x2c1
 [<c013508a>] autoremove_wake_function+0x15/0x35
 [<c013508a>] autoremove_wake_function+0x15/0x35
 [<c011d4e6>] __wake_up_common+0x32/0x5c
 [<c011ef21>] __wake_up+0x32/0x42
 [<c0257180>] sock_def_readable+0x39/0x63
 [<c02b0b4a>] unix_stream_sendmsg+0x24c/0x30b
 [<c0253cbf>] sock_sendmsg+0xc9/0xe4
 [<c0135075>] autoremove_wake_function+0x0/0x35
 [<c0135075>] autoremove_wake_function+0x0/0x35
 [<c02bbc1a>] schedule+0x588/0x5ec
 [<c0169120>] find_extend_vma+0x12/0x49
 [<c013d37f>] get_futex_key+0x6e/0x122
 [<c011d6ab>] enqueue_task+0x52/0x5d
 [<c011d6d2>] activate_task+0x1c/0x28
 [<c011f447>] try_to_wake_up+0x2b7/0x2c1
 [<c011d4e6>] __wake_up_common+0x32/0x5c
 [<c011ef21>] __wake_up+0x32/0x42
 [<c013d7e4>] wake_futex+0x3b/0x45
 [<c013da8b>] futex_wake+0xa6/0xb0
 [<c013e624>] do_futex+0x7c/0x957
 [<c02570cf>] sock_setsockopt+0x47e/0x496
 [<c01099ca>] sched_clock+0x8/0x18
 [<c013efc1>] sys_futex+0xc2/0xd4
 [<c01830ee>] sys_poll+0x3a/0x6d
 [<c0103e56>] sysenter_past_esp+0x6b/0xa1
 =======================
aisexec       S f7225bd8     0  4364      1
       f7cc0d70 00000082 00000002 f7225bd8 f7225bd0 00000000 000000e6 00000001 
       f7cc0ed8 c2010940 00000000 0000e0b7 c020d6f9 f7c2e5c4 000000ff 00000000 
       00000000 00000000 7fffffff ffffffff f743fa80 00000000 c02bbe22 00000000 
Call Trace:
 [<c020d6f9>] acpi_ex_pci_config_space_handler+0x0/0x5c
 [<c02bbe22>] schedule_timeout+0x13/0x8d
 [<c0135234>] add_wait_queue+0x12/0x32
 [<c02af0ca>] unix_poll+0x17/0x8b
 [<c01826c0>] do_sys_poll+0x222/0x2dc
 [<c0183121>] __pollwait+0x0/0xac
 [<c011f451>] default_wake_function+0x0/0x8
 [<c011f447>] try_to_wake_up+0x2b7/0x2c1
 [<c011d4e6>] __wake_up_common+0x32/0x5c
 [<c013508a>] autoremove_wake_function+0x15/0x35
 [<c011d4e6>] __wake_up_common+0x32/0x5c
 [<c011ef21>] __wake_up+0x32/0x42
 [<c0257180>] sock_def_readable+0x39/0x63
 [<c02b0b4a>] unix_stream_sendmsg+0x24c/0x30b
 [<c0253cbf>] sock_sendmsg+0xc9/0xe4
 [<c0135075>] autoremove_wake_function+0x0/0x35
 [<c0135075>] autoremove_wake_function+0x0/0x35
 [<c0253ebf>] sys_sendmsg+0x1e5/0x1f9
 [<c02549fa>] sys_recvmsg+0x1be/0x1d2
 [<c011f447>] try_to_wake_up+0x2b7/0x2c1
 [<c01202b2>] finish_task_switch+0x25/0x81
 [<c02bce5e>] _spin_lock_bh+0x8/0x18
 [<c02bce5e>] _spin_lock_bh+0x8/0x18
 [<c0255991>] release_sock+0x12/0x8e
 [<c02570cf>] sock_setsockopt+0x47e/0x496
 [<c01099ca>] sched_clock+0x8/0x18
 [<c02550c9>] sys_socketcall+0x240/0x261
 [<c01830ee>] sys_poll+0x3a/0x6d
 [<c0103e56>] sysenter_past_esp+0x6b/0xa1
 =======================
aisexec       S f740e480     0  4365      1
       f7cc1930 00000082 f7419158 f740e480 f7419168 00011210 a5b3d03e 0000007b 
       f7cc1a98 c2010940 00000000 f7237c00 000f350f 00000000 f7419158 00000000 
       c01d5d4e 00000004 7fffffff ffffffff f743f300 00000000 c02bbe22 f7617380 
Call Trace:
 [<c01d5d4e>] get_request+0x20e/0x2bb
 [<c02bbe22>] schedule_timeout+0x13/0x8d
 [<c0135234>] add_wait_queue+0x12/0x32
 [<c02af0ca>] unix_poll+0x17/0x8b
 [<c01826c0>] do_sys_poll+0x222/0x2dc
 [<c0183121>] __pollwait+0x0/0xac
 [<c011f451>] default_wake_function+0x0/0x8
 [<c011f447>] try_to_wake_up+0x2b7/0x2c1
 [<c013508a>] autoremove_wake_function+0x15/0x35
 [<c011d4e6>] __wake_up_common+0x32/0x5c
 [<c013508a>] autoremove_wake_function+0x15/0x35
 [<c011d4e6>] __wake_up_common+0x32/0x5c
 [<c011ef21>] __wake_up+0x32/0x42
 [<c0257180>] sock_def_readable+0x39/0x63
 [<c02b0b4a>] unix_stream_sendmsg+0x24c/0x30b
 [<c0253cbf>] sock_sendmsg+0xc9/0xe4
 [<c0135075>] autoremove_wake_function+0x0/0x35
 [<c0159dfc>] sync_page+0x0/0x40
 [<c0135075>] autoremove_wake_function+0x0/0x35
 [<c0159dee>] __lock_page+0x58/0x5e
 [<c0253ebf>] sys_sendmsg+0x1e5/0x1f9
 [<c02549fa>] sys_recvmsg+0x1be/0x1d2
 [<c011d4e6>] __wake_up_common+0x32/0x5c
 [<c011eed9>] __wake_up_sync+0x35/0x4b
 [<c02bce5e>] _spin_lock_bh+0x8/0x18
 [<c011da1a>] update_curr+0x62/0xef
 [<c02bce5e>] _spin_lock_bh+0x8/0x18
 [<c0255991>] release_sock+0x12/0x8e
 [<c02570cf>] sock_setsockopt+0x47e/0x496
 [<c011dfcb>] pick_next_task_fair+0x1f/0x2d
 [<c01099ca>] sched_clock+0x8/0x18
 [<c0103039>] __switch_to+0x9d/0x11c
 [<c02bbc1a>] schedule+0x588/0x5ec
 [<c01830ee>] sys_poll+0x3a/0x6d
 [<c0103e56>] sysenter_past_esp+0x6b/0xa1
 =======================
aisexec       S c200e540     0  4366      1
       f7fe37b0 00000082 c200e560 c200e540 00000000 c025f8ec a5a2c89c 0000007b 
       f7fe3918 c2010940 00000000 c200e554 0000b1c9 00000000 f7fb9000 f7fb9000 
       f7c56c80 0000e1b3 7fffffff ffffffff f7cdc0c0 00000000 c02bbe22 00000000 
Call Trace:
 [<c025f8ec>] process_backlog+0x6e/0xc9
 [<c02bbe22>] schedule_timeout+0x13/0x8d
 [<c0135234>] add_wait_queue+0x12/0x32
 [<c02af0ca>] unix_poll+0x17/0x8b
 [<c01826c0>] do_sys_poll+0x222/0x2dc
 [<c0183121>] __pollwait+0x0/0xac
 [<c011f451>] default_wake_function+0x0/0x8
 [<c011f447>] try_to_wake_up+0x2b7/0x2c1
 [<c02bce5e>] _spin_lock_bh+0x8/0x18
 [<c013508a>] autoremove_wake_function+0x15/0x35
 [<c011d4e6>] __wake_up_common+0x32/0x5c
 [<c011ef21>] __wake_up+0x32/0x42
 [<c0257180>] sock_def_readable+0x39/0x63
 [<c02b0b4a>] unix_stream_sendmsg+0x24c/0x30b
 [<c0253cbf>] sock_sendmsg+0xc9/0xe4
 [<c0135075>] autoremove_wake_function+0x0/0x35
 [<c0135075>] autoremove_wake_function+0x0/0x35
 [<c0253ebf>] sys_sendmsg+0x1e5/0x1f9
 [<c02549fa>] sys_recvmsg+0x1be/0x1d2
 [<c011f447>] try_to_wake_up+0x2b7/0x2c1
 [<c012d30e>] __sigqueue_alloc+0x33/0x59
 [<c011da1a>] update_curr+0x62/0xef
 [<c02bce5e>] _spin_lock_bh+0x8/0x18
 [<c011da1a>] update_curr+0x62/0xef
 [<c02bce5e>] _spin_lock_bh+0x8/0x18
 [<c0255991>] release_sock+0x12/0x8e
 [<c02570cf>] sock_setsockopt+0x47e/0x496
 [<c011dfcb>] pick_next_task_fair+0x1f/0x2d
 [<c01099ca>] sched_clock+0x8/0x18
 [<c0103039>] __switch_to+0x9d/0x11c
 [<c02bbc1a>] schedule+0x588/0x5ec
 [<c01830ee>] sys_poll+0x3a/0x6d
 [<c0103e56>] sysenter_past_esp+0x6b/0xa1
 =======================
aisexec       S f7159bd8     0  4496      1
       f7ffb250 00000082 00000002 f7159bd8 f7159bd0 00000000 9e539f00 0000012b 
       f7ffb3b8 c2018940 00000001 0003c411 000031fe 00000000 000000ff 00000000 
       00000000 00000000 7fffffff ffffffff f7d18bc0 00000000 c02bbe22 00000000 
Call Trace:
 [<c02bbe22>] schedule_timeout+0x13/0x8d
 [<c0135234>] add_wait_queue+0x12/0x32
 [<c02af0ca>] unix_poll+0x17/0x8b
 [<c01826c0>] do_sys_poll+0x222/0x2dc
 [<c0183121>] __pollwait+0x0/0xac
 [<c011f451>] default_wake_function+0x0/0x8
 [<c011f447>] try_to_wake_up+0x2b7/0x2c1
 [<c011d4e6>] __wake_up_common+0x32/0x5c
 [<c013508a>] autoremove_wake_function+0x15/0x35
 [<c011d4e6>] __wake_up_common+0x32/0x5c
 [<c011ef21>] __wake_up+0x32/0x42
 [<c0257180>] sock_def_readable+0x39/0x63
 [<c02b0b4a>] unix_stream_sendmsg+0x24c/0x30b
 [<c0253cbf>] sock_sendmsg+0xc9/0xe4
 [<c0135075>] autoremove_wake_function+0x0/0x35
 [<c0135075>] autoremove_wake_function+0x0/0x35
 [<c0253ebf>] sys_sendmsg+0x1e5/0x1f9
 [<c02549fa>] sys_recvmsg+0x1be/0x1d2
 [<c012d30e>] __sigqueue_alloc+0x33/0x59
 [<c011eed9>] __wake_up_sync+0x35/0x4b
 [<c02bce5e>] _spin_lock_bh+0x8/0x18
 [<c011da1a>] update_curr+0x62/0xef
 [<c02bce5e>] _spin_lock_bh+0x8/0x18
 [<c0255991>] release_sock+0x12/0x8e
 [<c02570cf>] sock_setsockopt+0x47e/0x496
 [<c011dfcb>] pick_next_task_fair+0x1f/0x2d
 [<c01099ca>] sched_clock+0x8/0x18
 [<c0103039>] __switch_to+0x9d/0x11c
 [<c02550c9>] sys_socketcall+0x240/0x261
 [<c01830ee>] sys_poll+0x3a/0x6d
 [<c0103e56>] sysenter_past_esp+0x6b/0xa1
 =======================
aisexec       S c200d9c0     0  4498      1
       f7ffac70 00000082 0002b572 c200d9c0 00000002 f7181bd4 b2d4e5a4 0000012b 
       f7ffadd8 c2010940 00000000 0003c411 148872bf 00000000 000000ff 00000000 
       00000000 0002b572 7fffffff ffffffff f7cb65c0 00000000 c02bbe22 00000000 
Call Trace:
 [<c02bbe22>] schedule_timeout+0x13/0x8d
 [<c0135234>] add_wait_queue+0x12/0x32
 [<c02af0ca>] unix_poll+0x17/0x8b
 [<c01826c0>] do_sys_poll+0x222/0x2dc
 [<c0183121>] __pollwait+0x0/0xac
 [<c011f451>] default_wake_function+0x0/0x8
 [<c011f447>] try_to_wake_up+0x2b7/0x2c1
 [<c013508a>] autoremove_wake_function+0x15/0x35
 [<c011d4e6>] __wake_up_common+0x32/0x5c
 [<c011ef21>] __wake_up+0x32/0x42
 [<c0257180>] sock_def_readable+0x39/0x63
 [<c02b0b4a>] unix_stream_sendmsg+0x24c/0x30b
 [<c0253cbf>] sock_sendmsg+0xc9/0xe4
 [<c0135075>] autoremove_wake_function+0x0/0x35
 [<c0135075>] autoremove_wake_function+0x0/0x35
 [<c011d6ab>] enqueue_task+0x52/0x5d
 [<c011d6d2>] activate_task+0x1c/0x28
 [<c011f447>] try_to_wake_up+0x2b7/0x2c1
 [<c011d4e6>] __wake_up_common+0x32/0x5c
 [<c011ef21>] __wake_up+0x32/0x42
 [<c013d7e4>] wake_futex+0x3b/0x45
 [<c013da8b>] futex_wake+0xa6/0xb0
 [<c013e624>] do_futex+0x7c/0x957
 [<c02570cf>] sock_setsockopt+0x47e/0x496
 [<c013efc1>] sys_futex+0xc2/0xd4
 [<c01830ee>] sys_poll+0x3a/0x6d
 [<c0103e56>] sysenter_past_esp+0x6b/0xa1
 =======================
aisexec       S c200d9c0     0  5266      1
       f7250230 00000082 00016434 c200d9c0 00000002 f7393bd4 7364a80d 0000012e 
       f7250398 c2010940 00000000 0003cf9d 00000000 00000000 000000ff 00000000 
       00000000 00016434 7fffffff ffffffff f7d1a780 00000000 c02bbe22 00000202 
Call Trace:
 [<c02bbe22>] schedule_timeout+0x13/0x8d
 [<c0159dee>] __lock_page+0x58/0x5e
 [<c0135234>] add_wait_queue+0x12/0x32
 [<c02af0ca>] unix_poll+0x17/0x8b
 [<c01826c0>] do_sys_poll+0x222/0x2dc
 [<c0183121>] __pollwait+0x0/0xac
 [<c011f451>] default_wake_function+0x0/0x8
 [<c011f447>] try_to_wake_up+0x2b7/0x2c1
 [<c013508a>] autoremove_wake_function+0x15/0x35
 [<c013508a>] autoremove_wake_function+0x15/0x35
 [<c011d4e6>] __wake_up_common+0x32/0x5c
 [<c011ef21>] __wake_up+0x32/0x42
 [<c0257180>] sock_def_readable+0x39/0x63
 [<c02b0b4a>] unix_stream_sendmsg+0x24c/0x30b
 [<c0253cbf>] sock_sendmsg+0xc9/0xe4
 [<c011df66>] set_next_entity+0x11/0x38
 [<c0135075>] autoremove_wake_function+0x0/0x35
 [<c0159dfc>] sync_page+0x0/0x40
 [<c0135075>] autoremove_wake_function+0x0/0x35
 [<c0159dee>] __lock_page+0x58/0x5e
 [<c0253ebf>] sys_sendmsg+0x1e5/0x1f9
 [<c02549fa>] sys_recvmsg+0x1be/0x1d2
 [<c012d30e>] __sigqueue_alloc+0x33/0x59
 [<c011da1a>] update_curr+0x62/0xef
 [<c02bce5e>] _spin_lock_bh+0x8/0x18
 [<c011da1a>] update_curr+0x62/0xef
 [<c02bce5e>] _spin_lock_bh+0x8/0x18
 [<c0255991>] release_sock+0x12/0x8e
 [<c02570cf>] sock_setsockopt+0x47e/0x496
 [<c011dfcb>] pick_next_task_fair+0x1f/0x2d
 [<c01099ca>] sched_clock+0x8/0x18
 [<c0103039>] __switch_to+0x9d/0x11c
 [<c02bbc1a>] schedule+0x588/0x5ec
 [<c01830ee>] sys_poll+0x3a/0x6d
 [<c0103e56>] sysenter_past_esp+0x6b/0xa1
 =======================
aisexec       S c200e540     0  5268      1
       f74138b0 00000082 c200e560 c200e540 00000000 c025f8ec 735d498c 0000012e 
       f7413a18 c2010940 00000000 c200e554 0000f2e9 00000000 f7fb9000 f7fb9000 
       f773ae80 0003cf9d 7fffffff ffffffff f753c6c0 00000000 c02bbe22 00000000 
Call Trace:
 [<c025f8ec>] process_backlog+0x6e/0xc9
 [<c02bbe22>] schedule_timeout+0x13/0x8d
 [<c0135234>] add_wait_queue+0x12/0x32
 [<c02af0ca>] unix_poll+0x17/0x8b
 [<c01826c0>] do_sys_poll+0x222/0x2dc
 [<c0183121>] __pollwait+0x0/0xac
 [<c011f451>] default_wake_function+0x0/0x8
 [<c011f447>] try_to_wake_up+0x2b7/0x2c1
 [<c02bce5e>] _spin_lock_bh+0x8/0x18
 [<c013508a>] autoremove_wake_function+0x15/0x35
 [<c011d4e6>] __wake_up_common+0x32/0x5c
 [<c011ef21>] __wake_up+0x32/0x42
 [<c0257180>] sock_def_readable+0x39/0x63
 [<c02b0b4a>] unix_stream_sendmsg+0x24c/0x30b
 [<c0253cbf>] sock_sendmsg+0xc9/0xe4
 [<c011df66>] set_next_entity+0x11/0x38
 [<c0135075>] autoremove_wake_function+0x0/0x35
 [<c0135075>] autoremove_wake_function+0x0/0x35
 [<c0159dee>] __lock_page+0x58/0x5e
 [<c0253ebf>] sys_sendmsg+0x1e5/0x1f9
 [<c02549fa>] sys_recvmsg+0x1be/0x1d2
 [<c011da1a>] update_curr+0x62/0xef
 [<c02bce5e>] _spin_lock_bh+0x8/0x18
 [<c011da1a>] update_curr+0x62/0xef
 [<c02bce5e>] _spin_lock_bh+0x8/0x18
 [<c0255991>] release_sock+0x12/0x8e
 [<c02570cf>] sock_setsockopt+0x47e/0x496
 [<c011dfcb>] pick_next_task_fair+0x1f/0x2d
 [<c01099ca>] sched_clock+0x8/0x18
 [<c0103039>] __switch_to+0x9d/0x11c
 [<c02bbc1a>] schedule+0x588/0x5ec
 [<c01830ee>] sys_poll+0x3a/0x6d
 [<c0103e56>] sysenter_past_esp+0x6b/0xa1
 =======================
aisexec       S c200d9c0     0  5282      1
       f741e170 00000082 00016832 c200d9c0 00000002 f727dbd4 971fd024 0000012e 
       f741e2d8 c2010940 00000000 0003d032 14989283 00000000 000000ff 00000000 
       00000000 00016832 7fffffff ffffffff f753c180 00000000 c02bbe22 00000202 
Call Trace:
 [<c02bbe22>] schedule_timeout+0x13/0x8d
 [<c0135234>] add_wait_queue+0x12/0x32
 [<c02af0ca>] unix_poll+0x17/0x8b
 [<c01826c0>] do_sys_poll+0x222/0x2dc
 [<c0183121>] __pollwait+0x0/0xac
 [<c011f451>] default_wake_function+0x0/0x8
 [<c011f447>] try_to_wake_up+0x2b7/0x2c1
 [<c013508a>] autoremove_wake_function+0x15/0x35
 [<c013508a>] autoremove_wake_function+0x15/0x35
 [<c011d4e6>] __wake_up_common+0x32/0x5c
 [<c011ef21>] __wake_up+0x32/0x42
 [<c0257180>] sock_def_readable+0x39/0x63
 [<c02b0b4a>] unix_stream_sendmsg+0x24c/0x30b
 [<c0253cbf>] sock_sendmsg+0xc9/0xe4
 [<c0135075>] autoremove_wake_function+0x0/0x35
 [<c0135075>] autoremove_wake_function+0x0/0x35
 [<c0253ebf>] sys_sendmsg+0x1e5/0x1f9
 [<c02549fa>] sys_recvmsg+0x1be/0x1d2
 [<c012d30e>] __sigqueue_alloc+0x33/0x59
 [<c011da1a>] update_curr+0x62/0xef
 [<c02bce5e>] _spin_lock_bh+0x8/0x18
 [<c011da1a>] update_curr+0x62/0xef
 [<c02bce5e>] _spin_lock_bh+0x8/0x18
 [<c0255991>] release_sock+0x12/0x8e
 [<c02570cf>] sock_setsockopt+0x47e/0x496
 [<c011dfcb>] pick_next_task_fair+0x1f/0x2d
 [<c01099ca>] sched_clock+0x8/0x18
 [<c0103039>] __switch_to+0x9d/0x11c
 [<c02bbc1a>] schedule+0x588/0x5ec
 [<c01830ee>] sys_poll+0x3a/0x6d
 [<c0103e56>] sysenter_past_esp+0x6b/0xa1
 =======================
aisexec       S c200e540     0  5285      1
       f7269250 00000082 c200e560 c200e540 00000000 c025f8ec 9706f1bd 0000012e 
       f72693b8 c2010940 00000000 c200e554 0000db1f 00000000 f7fb9000 f7fb9000 
       f75ae780 0003d033 7fffffff ffffffff f7439500 00000000 c02bbe22 00000000 
Call Trace:
 [<c025f8ec>] process_backlog+0x6e/0xc9
 [<c02bbe22>] schedule_timeout+0x13/0x8d
 [<c0135234>] add_wait_queue+0x12/0x32
 [<c02af0ca>] unix_poll+0x17/0x8b
 [<c01826c0>] do_sys_poll+0x222/0x2dc
 [<c0183121>] __pollwait+0x0/0xac
 [<c011f451>] default_wake_function+0x0/0x8
 [<c011f447>] try_to_wake_up+0x2b7/0x2c1
 [<c02bce5e>] _spin_lock_bh+0x8/0x18
 [<c013508a>] autoremove_wake_function+0x15/0x35
 [<c011d4e6>] __wake_up_common+0x32/0x5c
 [<c011ef21>] __wake_up+0x32/0x42
 [<c0257180>] sock_def_readable+0x39/0x63
 [<c02b0b4a>] unix_stream_sendmsg+0x24c/0x30b
 [<c0253cbf>] sock_sendmsg+0xc9/0xe4
 [<c011df66>] set_next_entity+0x11/0x38
 [<c0135075>] autoremove_wake_function+0x0/0x35
 [<c0159dfc>] sync_page+0x0/0x40
 [<c0135075>] autoremove_wake_function+0x0/0x35
 [<c0159dee>] __lock_page+0x58/0x5e
 [<c0253ebf>] sys_sendmsg+0x1e5/0x1f9
 [<c02549fa>] sys_recvmsg+0x1be/0x1d2
 [<c012d30e>] __sigqueue_alloc+0x33/0x59
 [<c011da1a>] update_curr+0x62/0xef
 [<c02bce5e>] _spin_lock_bh+0x8/0x18
 [<c011da1a>] update_curr+0x62/0xef
 [<c02bce5e>] _spin_lock_bh+0x8/0x18
 [<c0255991>] release_sock+0x12/0x8e
 [<c02570cf>] sock_setsockopt+0x47e/0x496
 [<c011dfcb>] pick_next_task_fair+0x1f/0x2d
 [<c01099ca>] sched_clock+0x8/0x18
 [<c0103039>] __switch_to+0x9d/0x11c
 [<c02bbc1a>] schedule+0x588/0x5ec
 [<c01830ee>] sys_poll+0x3a/0x6d
 [<c0103e56>] sysenter_past_esp+0x6b/0xa1
 =======================
aisexec       S 00000000     0  5364      1
       f73cb290 00000082 00000000 00000000 00000000 00000000 277b9dbd 0000012f 
       f73cb3f8 c2010940 00000000 00000000 001c13f2 00000000 00000000 00000000 
       00000000 00000000 7fffffff ffffffff f746d0c0 00000000 c02bbe22 00000000 
Call Trace:
 [<c02bbe22>] schedule_timeout+0x13/0x8d
 [<c0135234>] add_wait_queue+0x12/0x32
 [<c02af0ca>] unix_poll+0x17/0x8b
 [<c01826c0>] do_sys_poll+0x222/0x2dc
 [<c0183121>] __pollwait+0x0/0xac
 [<c011f451>] default_wake_function+0x0/0x8
 [<c011f447>] try_to_wake_up+0x2b7/0x2c1
 [<c013508a>] autoremove_wake_function+0x15/0x35
 [<c013508a>] autoremove_wake_function+0x15/0x35
 [<c011d4e6>] __wake_up_common+0x32/0x5c
 [<c011ef21>] __wake_up+0x32/0x42
 [<c0257180>] sock_def_readable+0x39/0x63
 [<c02b0b4a>] unix_stream_sendmsg+0x24c/0x30b
 [<c0253cbf>] sock_sendmsg+0xc9/0xe4
 [<c0135075>] autoremove_wake_function+0x0/0x35
 [<c0135075>] autoremove_wake_function+0x0/0x35
 [<c0115958>] lapic_next_event+0xc/0x10
 [<c013bc15>] clockevents_program_event+0xe0/0xee
 [<c0253ebf>] sys_sendmsg+0x1e5/0x1f9
 [<c02549fa>] sys_recvmsg+0x1be/0x1d2
 [<c02bce5e>] _spin_lock_bh+0x8/0x18
 [<c02bce5e>] _spin_lock_bh+0x8/0x18
 [<c0255991>] release_sock+0x12/0x8e
 [<c02570cf>] sock_setsockopt+0x47e/0x496
 [<c01099ca>] sched_clock+0x8/0x18
 [<c0103039>] __switch_to+0x9d/0x11c
 [<c02bbc1a>] schedule+0x588/0x5ec
 [<c01830ee>] sys_poll+0x3a/0x6d
 [<c0103e56>] sysenter_past_esp+0x6b/0xa1
 =======================
aisexec       S c200e540     0  5365      1
       f73ca0f0 00000082 c200e560 c200e540 00000000 c025f8ec 27590f8b 0000012f 
       f73ca258 c2010940 00000000 c200e554 0000c51b 00000000 f7fb9000 f7fb9000 
       f7fdf180 0003d293 7fffffff ffffffff f7442500 00000000 c02bbe22 00000000 
Call Trace:
 [<c025f8ec>] process_backlog+0x6e/0xc9
 [<c02bbe22>] schedule_timeout+0x13/0x8d
 [<c0135234>] add_wait_queue+0x12/0x32
 [<c02af0ca>] unix_poll+0x17/0x8b
 [<c01826c0>] do_sys_poll+0x222/0x2dc
 [<c0183121>] __pollwait+0x0/0xac
 [<c011f451>] default_wake_function+0x0/0x8
 [<c011f447>] try_to_wake_up+0x2b7/0x2c1
 [<c02bce5e>] _spin_lock_bh+0x8/0x18
 [<c013508a>] autoremove_wake_function+0x15/0x35
 [<c011d4e6>] __wake_up_common+0x32/0x5c
 [<c011ef21>] __wake_up+0x32/0x42
 [<c0257180>] sock_def_readable+0x39/0x63
 [<c02b0b4a>] unix_stream_sendmsg+0x24c/0x30b
 [<c0253cbf>] sock_sendmsg+0xc9/0xe4
 [<c0135075>] autoremove_wake_function+0x0/0x35
 [<c011d140>] kunmap_atomic+0x54/0x95
 [<c011d152>] kunmap_atomic+0x66/0x95
 [<c015e60e>] get_page_from_freelist+0x30a/0x387
 [<c0253ebf>] sys_sendmsg+0x1e5/0x1f9
 [<c0165253>] vm_normal_page+0xd/0x3e
 [<c0165c81>] follow_page+0x16f/0x1c7
 [<c0167b59>] get_user_pages+0x291/0x2fd
 [<c01099ca>] sched_clock+0x8/0x18
 [<c0103039>] __switch_to+0x9d/0x11c
 [<c02bbc1a>] schedule+0x588/0x5ec
 [<c01830ee>] sys_poll+0x3a/0x6d
 [<c0103e56>] sysenter_past_esp+0x6b/0xa1
 =======================
aisexec       S 00000000     0  5374      1
       f7cd99b0 00000082 00000000 00000000 00000000 00000000 2841a22d 0000012f 
       f7cd9b18 c2010940 00000000 00000000 00181e1a 00000000 00000000 00000000 
       00000000 00000000 7fffffff ffffffff f7465140 00000000 c02bbe22 00000000 
Call Trace:
 [<c02bbe22>] schedule_timeout+0x13/0x8d
 [<c0135234>] add_wait_queue+0x12/0x32
 [<c02af0ca>] unix_poll+0x17/0x8b
 [<c01826c0>] do_sys_poll+0x222/0x2dc
 [<c0183121>] __pollwait+0x0/0xac
 [<c011f451>] default_wake_function+0x0/0x8
 [<c011f447>] try_to_wake_up+0x2b7/0x2c1
 [<c013508a>] autoremove_wake_function+0x15/0x35
 [<c011d4e6>] __wake_up_common+0x32/0x5c
 [<c013508a>] autoremove_wake_function+0x15/0x35
 [<c011d4e6>] __wake_up_common+0x32/0x5c
 [<c011ef21>] __wake_up+0x32/0x42
 [<c0257180>] sock_def_readable+0x39/0x63
 [<c02b0b4a>] unix_stream_sendmsg+0x24c/0x30b
 [<c0253cbf>] sock_sendmsg+0xc9/0xe4
 [<c0135075>] autoremove_wake_function+0x0/0x35
 [<c0135075>] autoremove_wake_function+0x0/0x35
 [<c0253ebf>] sys_sendmsg+0x1e5/0x1f9
 [<c02549fa>] sys_recvmsg+0x1be/0x1d2
 [<c02bce5e>] _spin_lock_bh+0x8/0x18
 [<c02bce5e>] _spin_lock_bh+0x8/0x18
 [<c0255991>] release_sock+0x12/0x8e
 [<c02570cf>] sock_setsockopt+0x47e/0x496
 [<c01099ca>] sched_clock+0x8/0x18
 [<c0103039>] __switch_to+0x9d/0x11c
 [<c02bbc1a>] schedule+0x588/0x5ec
 [<c01830ee>] sys_poll+0x3a/0x6d
 [<c0103e56>] sysenter_past_esp+0x6b/0xa1
 =======================
aisexec       S c200e540     0  5376      1
       f7264610 00000082 c200e560 c200e540 00000000 c025f8ec 28220b0f 0000012f 
       f7264778 c2010940 00000000 c200e554 0000a4ef 00000000 f7fb9000 f7fb9000 
       f753e880 0003d296 7fffffff ffffffff f7433c00 00000000 c02bbe22 00000000 
Call Trace:
 [<c025f8ec>] process_backlog+0x6e/0xc9
 [<c02bbe22>] schedule_timeout+0x13/0x8d
 [<c0135234>] add_wait_queue+0x12/0x32
 [<c02af0ca>] unix_poll+0x17/0x8b
 [<c01826c0>] do_sys_poll+0x222/0x2dc
 [<c0183121>] __pollwait+0x0/0xac
 [<c011f451>] default_wake_function+0x0/0x8
 [<c011f447>] try_to_wake_up+0x2b7/0x2c1
 [<c02bce5e>] _spin_lock_bh+0x8/0x18
 [<c013508a>] autoremove_wake_function+0x15/0x35
 [<c011d4e6>] __wake_up_common+0x32/0x5c
 [<c011ef21>] __wake_up+0x32/0x42
 [<c0257180>] sock_def_readable+0x39/0x63
 [<c02b0b4a>] unix_stream_sendmsg+0x24c/0x30b
 [<c0253cbf>] sock_sendmsg+0xc9/0xe4
 [<c0135075>] autoremove_wake_function+0x0/0x35
 [<c0135075>] autoremove_wake_function+0x0/0x35
 [<c0253ebf>] sys_sendmsg+0x1e5/0x1f9
 [<c02549fa>] sys_recvmsg+0x1be/0x1d2
 [<c02bce5e>] _spin_lock_bh+0x8/0x18
 [<c02bce5e>] _spin_lock_bh+0x8/0x18
 [<c0255991>] release_sock+0x12/0x8e
 [<c02570cf>] sock_setsockopt+0x47e/0x496
 [<c01099ca>] sched_clock+0x8/0x18
 [<c0103039>] __switch_to+0x9d/0x11c
 [<c02bbc1a>] schedule+0x588/0x5ec
 [<c01830ee>] sys_poll+0x3a/0x6d
 [<c0103e56>] sysenter_past_esp+0x6b/0xa1
 =======================
groupd        S c200d9c0     0  4351      1
       f7d13210 00000082 00000d79 c200d9c0 00000002 f74b3bd4 284f89cd 0000012f 
       f7d13378 c2010940 00000000 0003d032 00000000 00000000 000000ff 00000000 
       00000000 00000d79 7fffffff ffffffff f7ccac00 00000000 c02bbe22 00000001 
Call Trace:
 [<c02bbe22>] schedule_timeout+0x13/0x8d
 [<c011dda8>] balance_tasks+0x4d/0xf2
 [<c0135234>] add_wait_queue+0x12/0x32
 [<c02af0ca>] unix_poll+0x17/0x8b
 [<c01826c0>] do_sys_poll+0x222/0x2dc
 [<c0183121>] __pollwait+0x0/0xac
 [<c011f451>] default_wake_function+0x0/0x8
 [<c011f451>] default_wake_function+0x0/0x8
 [<c011f451>] default_wake_function+0x0/0x8
 [<c011f451>] default_wake_function+0x0/0x8
 [<c011f451>] default_wake_function+0x0/0x8
 [<c011f451>] default_wake_function+0x0/0x8
 [<c011f451>] default_wake_function+0x0/0x8
 [<c011f451>] default_wake_function+0x0/0x8
 [<c011f451>] default_wake_function+0x0/0x8
 [<c011f451>] default_wake_function+0x0/0x8
 [<c011f451>] default_wake_function+0x0/0x8
 [<c011f451>] default_wake_function+0x0/0x8
 [<c011d4e6>] __wake_up_common+0x32/0x5c
 [<c011ef21>] __wake_up+0x32/0x42
 [<c0257180>] sock_def_readable+0x39/0x63
 [<c02b0b4a>] unix_stream_sendmsg+0x24c/0x30b
 [<c02535de>] sock_aio_write+0xe3/0xef
 [<c0135075>] autoremove_wake_function+0x0/0x35
 [<c01780c2>] vfs_write+0x113/0x14d
 [<c01830ee>] sys_poll+0x3a/0x6d
 [<c0103e56>] sysenter_past_esp+0x6b/0xa1
 =======================
fenced        S f715bbd8     0  4355      1
       f7d2a6d0 00000082 00000002 f715bbd8 f715bbd0 00000000 a581433e 0000007b 
       f7d2a838 c2010940 00000000 0000e88b 00000000 00000000 000000ff 00000000 
       00000000 00000000 7fffffff ffffffff f7d1a900 00000000 c02bbe22 c01de09c 
Call Trace:
 [<c02bbe22>] schedule_timeout+0x13/0x8d
 [<c01de09c>] __next_cpu+0x12/0x21
 [<c011e4ee>] find_busiest_group+0x216/0x60d
 [<c011dda8>] balance_tasks+0x4d/0xf2
 [<c0135234>] add_wait_queue+0x12/0x32
 [<c02af0ca>] unix_poll+0x17/0x8b
 [<c01826c0>] do_sys_poll+0x222/0x2dc
 [<c0183121>] __pollwait+0x0/0xac
 [<c011f451>] default_wake_function+0x0/0x8
 [<c011f451>] default_wake_function+0x0/0x8
 [<c011f451>] default_wake_function+0x0/0x8
 [<c011f451>] default_wake_function+0x0/0x8
 [<c011f447>] try_to_wake_up+0x2b7/0x2c1
 [<c01099ca>] sched_clock+0x8/0x18
 [<c0121cc8>] check_preempt_wakeup+0x1e/0x7a
 [<c011f447>] try_to_wake_up+0x2b7/0x2c1
 [<c011d4e6>] __wake_up_common+0x32/0x5c
 [<c011eed9>] __wake_up_sync+0x35/0x4b
 [<c02b140d>] unix_write_space+0x3a/0x63
 [<c025743d>] sock_wfree+0x21/0x36
 [<c0259185>] skb_release_all+0xa3/0xfa
 [<c02b053e>] unix_stream_recvmsg+0x3aa/0x4bd
 [<c0189d92>] mntput_no_expire+0x11/0x66
 [<c0113c7d>] flush_tlb_page+0x3e/0x62
 [<c02536df>] sock_aio_read+0xf5/0x101
 [<c01657d2>] do_wp_page+0x1e0/0x4c8
 [<c0167849>] handle_mm_fault+0x609/0x688
 [<c0258720>] skb_dequeue+0x39/0x3f
 [<c0258b10>] skb_queue_purge+0x11/0x17
 [<c02b155f>] unix_sock_destructor+0xe/0xd2
 [<c0256004>] sk_free+0xa0/0xb6
 [<c0258720>] skb_dequeue+0x39/0x3f
 [<c0185d43>] d_kill+0x37/0x46
 [<c0185f7c>] dput+0x15/0xdc
 [<c01789be>] __fput+0x122/0x14c
 [<c0189d92>] mntput_no_expire+0x11/0x66
 [<c01830ee>] sys_poll+0x3a/0x6d
 [<c0103e56>] sysenter_past_esp+0x6b/0xa1
 [<c02b0000>] unix_create1+0xbb/0xfa
 =======================
dlm_controld  S c20159c0     0  4357      1
       f7c76690 00000082 00000761 c20159c0 00000002 f71ebbd4 c8037da6 0000012f 
       f7c767f8 c2018940 00000001 0003d589 ec641c75 ffffffff 000000ff 00000000 
       00000000 00000761 7fffffff ffffffff f7433780 00000000 c02bbe22 f7433780 
Call Trace:
 [<c02bbe22>] schedule_timeout+0x13/0x8d
 [<c0135234>] add_wait_queue+0x12/0x32
 [<c02af0ca>] unix_poll+0x17/0x8b
 [<c01826c0>] do_sys_poll+0x222/0x2dc
 [<c0183121>] __pollwait+0x0/0xac
 [<c011f451>] default_wake_function+0x0/0x8
 [<c011f451>] default_wake_function+0x0/0x8
 [<c011f451>] default_wake_function+0x0/0x8
 [<c011f451>] default_wake_function+0x0/0x8
 [<c011d7c8>] task_tick_rt+0xb/0x4c
 [<c0115958>] lapic_next_event+0xc/0x10
 [<c013bc15>] clockevents_program_event+0xe0/0xee
 [<c025a395>] memcpy_toiovec+0x27/0x4a
 [<c025a825>] skb_copy_datagram_iovec+0x53/0x1d3
 [<c011ef21>] __wake_up+0x32/0x42
 [<c02729db>] netlink_recvmsg+0x262/0x281
 [<c0253bdb>] sock_recvmsg+0xe5/0x100
 [<c02b140d>] unix_write_space+0x3a/0x63
 [<c0135075>] autoremove_wake_function+0x0/0x35
 [<c02536df>] sock_aio_read+0xf5/0x101
 [<c011e0f7>] enqueue_task_fair+0x16/0x24
 [<c0177915>] do_sync_read+0xc7/0x10a
 [<c0135075>] autoremove_wake_function+0x0/0x35
 [<c0254b70>] sys_recv+0x37/0x3b
 [<c0255025>] sys_socketcall+0x19c/0x261
 [<c01830ee>] sys_poll+0x3a/0x6d
 [<c0103e56>] sysenter_past_esp+0x6b/0xa1
 =======================
gfs_controld  S c20159c0     0  4359      1
       f7cc1350 00000086 0001621a c20159c0 00000002 f7203bd4 c80342b4 0000012f 
       f7cc14b8 c2018940 00000001 0003d589 ec63ed5b ffffffff 000000ff 00000000 
       00000000 0001621a 7fffffff ffffffff f7d1a6c0 00000000 c02bbe22 00000001 
Call Trace:
 [<c02bbe22>] schedule_timeout+0x13/0x8d
 [<c0135234>] add_wait_queue+0x12/0x32
 [<c0135234>] add_wait_queue+0x12/0x32
 [<c01826c0>] do_sys_poll+0x222/0x2dc
 [<c0183121>] __pollwait+0x0/0xac
 [<c011f451>] default_wake_function+0x0/0x8
 [<c011f451>] default_wake_function+0x0/0x8
 [<c011f451>] default_wake_function+0x0/0x8
 [<c011f451>] default_wake_function+0x0/0x8
 [<c011f451>] default_wake_function+0x0/0x8
 [<c011f451>] default_wake_function+0x0/0x8
 [<c025a395>] memcpy_toiovec+0x27/0x4a
 [<c025a825>] skb_copy_datagram_iovec+0x53/0x1d3
 [<c011ef21>] __wake_up+0x32/0x42
 [<c02729db>] netlink_recvmsg+0x262/0x281
 [<c0135075>] autoremove_wake_function+0x0/0x35
 [<c0253bdb>] sock_recvmsg+0xe5/0x100
 [<c0135075>] autoremove_wake_function+0x0/0x35
 [<c0253e6e>] sys_sendmsg+0x194/0x1f9
 [<c025495c>] sys_recvmsg+0x120/0x1d2
 [<c011e0f7>] enqueue_task_fair+0x16/0x24
 [<c0258720>] skb_dequeue+0x39/0x3f
 [<c0258b10>] skb_queue_purge+0x11/0x17
 [<c0256004>] sk_free+0xa0/0xb6
 [<c0254b70>] sys_recv+0x37/0x3b
 [<c0255025>] sys_socketcall+0x19c/0x261
 [<c01830ee>] sys_poll+0x3a/0x6d
 [<c0103e56>] sysenter_past_esp+0x6b/0xa1
 =======================
clurgmgrd     S c20159c0     0  4487      1
       f7fe31d0 00000086 00000818 c20159c0 00000002 f70f1f1c f7fd6e20 00000000 
       f7fe3338 c2018940 00000001 0003c412 97619d64 c200d99c 000000ff 00000000 
       00000000 00000818 00001188 00000001 f7fe31c8 00000000 c012719a 00000246 
Call Trace:
 [<c012719a>] do_wait+0x964/0xa47
 [<c012ce5f>] do_sigaction+0x8a/0x136
 [<c011f451>] default_wake_function+0x0/0x8
 [<c01272ae>] sys_wait4+0x31/0x34
 [<c01272d8>] sys_waitpid+0x27/0x2b
 [<c0103e56>] sysenter_past_esp+0x6b/0xa1
 [<c02b0000>] unix_create1+0xbb/0xfa
 =======================
clurgmgrd     S f70c1b38     0  4488   4487
       f7fd6df0 00000082 00000002 f70c1b38 f70c1b30 00000000 3cef85c3 00000237 
       f7fd6f58 c2010940 00000000 f70c1b5c 00000000 00000000 00000286 c012c43e 
       00000000 00000286 f70c1b5c 00082fef 0000000d f70c1f9c c02bbe7f f726edc4 
Call Trace:
 [<c012c43e>] __mod_timer+0x9a/0xa4
 [<c02bbe7f>] schedule_timeout+0x70/0x8d
 [<c012c215>] process_timeout+0x0/0x5
 [<c02bbe7a>] schedule_timeout+0x6b/0x8d
 [<c0182b33>] do_select+0x372/0x3c9
 [<c0183121>] __pollwait+0x0/0xac
 [<c011f451>] default_wake_function+0x0/0x8
 [<c011f451>] default_wake_function+0x0/0x8
 [<c011da1a>] update_curr+0x62/0xef
 [<c011e0c1>] enqueue_entity+0x1d/0x3d
 [<c011e0f7>] enqueue_task_fair+0x16/0x24
 [<c01930fa>] __find_get_block_slow+0x110/0x11a
 [<c01657d2>] do_wp_page+0x1e0/0x4c8
 [<c011da1a>] update_curr+0x62/0xef
 [<c011da1a>] update_curr+0x62/0xef
 [<c011da1a>] update_curr+0x62/0xef
 [<c0103039>] __switch_to+0x9d/0x11c
 [<c02bbc1a>] schedule+0x588/0x5ec
 [<c0189d92>] mntput_no_expire+0x11/0x66
 [<c02bbe22>] schedule_timeout+0x13/0x8d
 [<c02b13e2>] unix_write_space+0xf/0x63
 [<c025743d>] sock_wfree+0x21/0x36
 [<c0259185>] skb_release_all+0xa3/0xfa
 [<c02b053e>] unix_stream_recvmsg+0x3aa/0x4bd
 [<c0182e0f>] core_sys_select+0x285/0x2a2
 [<c015d83d>] __rmqueue+0x13/0x174
 [<c0132d7c>] alloc_pid+0x211/0x2c4
 [<c011da1a>] update_curr+0x62/0xef
 [<c011da1a>] update_curr+0x62/0xef
 [<c0103039>] __switch_to+0x9d/0x11c
 [<c0183271>] sys_select+0xa4/0x187
 [<c0103e56>] sysenter_past_esp+0x6b/0xa1
 [<c02b0000>] unix_create1+0xbb/0xfa
 =======================
clurgmgrd     S f73b3b38     0  5151   4487
       f7250df0 00000082 00000002 f73b3b38 f73b3b30 00000000 36648b42 00000237 
       f7250f58 c2018940 00000001 f73b3b5c 000195c9 00000000 00000286 c012c43e 
       00000000 00000286 f73b3b5c 00082856 00000006 f73b3f9c c02bbe7f 00000000 
Call Trace:
 [<c012c43e>] __mod_timer+0x9a/0xa4
 [<c02bbe7f>] schedule_timeout+0x70/0x8d
 [<c012c215>] process_timeout+0x0/0x5
 [<c02bbe7a>] schedule_timeout+0x6b/0x8d
 [<c0182b33>] do_select+0x372/0x3c9
 [<c0183121>] __pollwait+0x0/0xac
 [<c011f451>] default_wake_function+0x0/0x8
 [<c011f451>] default_wake_function+0x0/0x8
 [<c01930fa>] __find_get_block_slow+0x110/0x11a
 [<c0189d92>] mntput_no_expire+0x11/0x66
 [<c017ff75>] link_path_walk+0xa9/0xb3
 [<c0115357>] apic_wait_icr_idle+0xe/0x15
 [<c0113e45>] native_flush_tlb_others+0x68/0x95
 [<c0113c7d>] flush_tlb_page+0x3e/0x62
 [<c01657d2>] do_wp_page+0x1e0/0x4c8
 [<c0258a78>] __kfree_skb+0x8/0x63
 [<f88971f2>] e1000_unmap_and_free_tx_resource+0x1b/0x23 [e1000]
 [<f8898b9d>] e1000_clean_tx_irq+0xbc/0x2c5 [e1000]
 [<c0167849>] handle_mm_fault+0x609/0x688
 [<f889b38b>] e1000_clean_rx_irq+0x0/0x452 [e1000]
 [<f8898fd7>] e1000_clean+0x1e3/0x20d [e1000]
 [<c011bf8f>] do_page_fault+0x1f7/0x5a8
 [<c01066f6>] do_IRQ+0x5a/0x70
 [<c011bd98>] do_page_fault+0x0/0x5a8
 [<c02bd0a2>] error_code+0x72/0x78
 [<c02b00d8>] unix_accept+0x24/0xe0
 [<c0182e0f>] core_sys_select+0x285/0x2a2
 [<c015e72d>] __alloc_pages+0x59/0x2d5
 [<c011d152>] kunmap_atomic+0x66/0x95
 [<c0113c7d>] flush_tlb_page+0x3e/0x62
 [<c01657d2>] do_wp_page+0x1e0/0x4c8
 [<c017d80b>] pipe_read+0x2e0/0x338
 [<f88971f2>] e1000_unmap_and_free_tx_resource+0x1b/0x23 [e1000]
 [<f8898b9d>] e1000_clean_tx_irq+0xbc/0x2c5 [e1000]
 [<c0177915>] do_sync_read+0xc7/0x10a
 [<c0167849>] handle_mm_fault+0x609/0x688
 [<c0135075>] autoremove_wake_function+0x0/0x35
 [<f8898fd7>] e1000_clean+0x1e3/0x20d [e1000]
 [<c0183271>] sys_select+0xa4/0x187
 [<c0103e56>] sysenter_past_esp+0x6b/0xa1
 =======================
clurgmgrd     S f725fe1c     0  5152   4487
       f7d558b0 00000082 00000002 f725fe1c f725fe14 00000000 c01374ba 00000001 
       f7d55a18 c2010940 00000000 00082610 00000286 c0137b92 000000fd 00000001 
       00000000 00000000 f757b074 f725ff98 f725fe48 0807ae70 c013d6f2 00000000 
Call Trace:
 [<c01374ba>] enqueue_hrtimer+0xd7/0xe2
 [<c0137b92>] hrtimer_start+0x100/0x10c
 [<c013d6f2>] futex_wait+0x1ea/0x2a1
 [<c013766f>] hrtimer_wakeup+0x0/0x18
 [<c013d6e6>] futex_wait+0x1de/0x2a1
 [<c011f451>] default_wake_function+0x0/0x8
 [<c013e611>] do_futex+0x69/0x957
 [<c012c32a>] lock_timer_base+0x19/0x35
 [<c012c43e>] __mod_timer+0x9a/0xa4
 [<c0139c2c>] getnstimeofday+0x30/0xb8
 [<c0137d73>] ktime_get_ts+0x16/0x44
 [<c013efc1>] sys_futex+0xc2/0xd4
 [<c0103e56>] sysenter_past_esp+0x6b/0xa1
 [<c02b0000>] unix_create1+0xbb/0xfa
 =======================
clurgmgrd     S b73c9bf8     0 23130   4487
       f0a058b0 00000082 b7d3494c b73c9bf8 000000f0 ffffffda 5db68e13 00000237 
       f0a05a18 c2010940 00000000 f7ffcb7c 00000000 00000000 b7d3494c f757b074 
       c2010974 c01bd464 00005af2 00000001 f7d558a8 00000000 c012719a 00000246 
Call Trace:
 [<c01bd464>] security_task_wait+0xc/0xd
 [<c012719a>] do_wait+0x964/0xa47
 [<c0123d23>] do_fork+0x120/0x1cc
 [<c011f451>] default_wake_function+0x0/0x8
 [<c01272ae>] sys_wait4+0x31/0x34
 [<c01272d8>] sys_waitpid+0x27/0x2b
 [<c0103e56>] sysenter_past_esp+0x6b/0xa1
 [<c02b0000>] unix_create1+0xbb/0xfa
 =======================
clurgmgrd     S 7db76065     0 23131   4487
       f0a04cf0 00000082 c16eeaac 7db76065 7db76065 ffffffda 5d728a38 00000237 
       f0a04e58 c2010940 00000000 f7ffcb78 00000000 00000000 b7d3494c c200d920 
       c2010974 c01bd464 00005af0 00000001 f0a058a8 00000000 c012719a 00000246 
Call Trace:
 [<c01bd464>] security_task_wait+0xc/0xd
 [<c012719a>] do_wait+0x964/0xa47
 [<c0123d23>] do_fork+0x120/0x1cc
 [<c011f451>] default_wake_function+0x0/0x8
 [<c01272ae>] sys_wait4+0x31/0x34
 [<c01272d8>] sys_waitpid+0x27/0x2b
 [<c0103e56>] sysenter_past_esp+0x6b/0xa1
 [<c02b0000>] unix_create1+0xbb/0xfa
 =======================
dlm_astd      S 00000000     0  4489      2
       f7d6d930 00000046 c011d4e6 00000000 00000003 f7fc3994 3caea2de 00000237 
       f7d6da98 c2018940 00000001 000013d0 00001ad2 00000000 f09b1ec0 f7fc3800 
       f881e7f5 00000292 00000000 f8a4a145 f881e7f5 00000000 f8a4a16c 00000000 
Call Trace:
 [<c011d4e6>] __wake_up_common+0x32/0x5c
 [<f881e7f5>] gdlm_bast+0x0/0x90 [lock_dlm]
 [<f8a4a145>] dlm_astd+0x0/0x13e [dlm]
 [<f881e7f5>] gdlm_bast+0x0/0x90 [lock_dlm]
 [<f8a4a16c>] dlm_astd+0x27/0x13e [dlm]
 [<f8a4a145>] dlm_astd+0x0/0x13e [dlm]
 [<c0134fae>] kthread+0x38/0x5e
 [<c0134f76>] kthread+0x0/0x5e
 [<c0104b07>] kernel_thread_helper+0x7/0x10
 =======================
dlm_scand     S f716df74     0  4490      2
       f7d6c1b0 00000046 00000002 f716df74 f716df6c 00000000 dfa174b8 f8a4af41 
       f7d6c318 c2010940 00000000 0008276a f716df98 c04c6ec0 000000fd 00000001 
       00000000 00000000 f716df98 00082c42 00000000 00000000 c02bbe7f 00000282 
Call Trace:
 [<f8a4af41>] search_bucket+0x2d/0x47 [dlm]
 [<c02bbe7f>] schedule_timeout+0x70/0x8d
 [<c012c215>] process_timeout+0x0/0x5
 [<c02bbe7a>] schedule_timeout+0x6b/0x8d
 [<f8a52aa8>] dlm_scand+0x0/0x57 [dlm]
 [<f8a52af2>] dlm_scand+0x4a/0x57 [dlm]
 [<c0134fae>] kthread+0x38/0x5e
 [<c0134f76>] kthread+0x0/0x5e
 [<c0104b07>] kernel_thread_helper+0x7/0x10
 =======================
dlm_recv/0    S 00000000     0  4491      2
       f7d6d350 00000046 f7fd7000 00000000 f7d6d350 00000000 b2a74cd3 0000012b 
       f7d6d4b8 c2010940 00000000 00000092 00000a91 00000000 b2a727cf 0000012b 
       00000246 c0135188 f7795640 c01326e3 f7211fd0 00000000 c013276b 00000000 
Call Trace:
 [<c0135188>] prepare_to_wait+0x12/0x49
 [<c01326e3>] worker_thread+0x0/0xc5
 [<c013276b>] worker_thread+0x88/0xc5
 [<c0135075>] autoremove_wake_function+0x0/0x35
 [<c0134fae>] kthread+0x38/0x5e
 [<c0134f76>] kthread+0x0/0x5e
 [<c0104b07>] kernel_thread_helper+0x7/0x10
 =======================
dlm_recv/1    S c20159c0     0  4492      2
       f7d6c790 00000046 00000897 c20159c0 00000002 f719df9c f7d6c790 f711e900 
       f7d6c8f8 c2018940 00000001 0003c412 f7c43fb0 f70c1d00 000000ff 00000000 
       00000000 00000897 f7fb4140 c01326e3 f719dfd0 00000000 c013276b 00000000 
Call Trace:
 [<c01326e3>] worker_thread+0x0/0xc5
 [<c013276b>] worker_thread+0x88/0xc5
 [<c0135075>] autoremove_wake_function+0x0/0x35
 [<c0134fae>] kthread+0x38/0x5e
 [<c0134f76>] kthread+0x0/0x5e
 [<c0104b07>] kernel_thread_helper+0x7/0x10
 =======================
dlm_send      S 00000000     0  4493      2
       f7ffa0b0 00000046 f7fd7000 00000000 f7ffa0b0 00000000 b2a83987 0000012b 
       f7ffa218 c2010940 00000000 00000092 0000083f 00000000 b2a7bde8 0000012b 
       00000246 c0135188 f70a4b40 c01326e3 f7715fd0 00000000 c013276b 00000000 
Call Trace:
 [<c0135188>] prepare_to_wait+0x12/0x49
 [<c01326e3>] worker_thread+0x0/0xc5
 [<c013276b>] worker_thread+0x88/0xc5
 [<c0135075>] autoremove_wake_function+0x0/0x35
 [<c0134fae>] kthread+0x38/0x5e
 [<c0134f76>] kthread+0x0/0x5e
 [<c0104b07>] kernel_thread_helper+0x7/0x10
 =======================
dlm_recoverd  S c20159c0     0  4494      2
       f7ffb830 00000046 0002b7f0 c20159c0 00000002 f71e7f88 9e5e3c67 0000012b 
       f7ffb998 c2018940 00000001 0003c412 eb7b0536 ffffffff 000000ff 00000000 
       00000000 0002b7f0 00000000 f705f000 00000001 00000000 f8a56bf0 00000000 
Call Trace:
 [<f8a56bf0>] dlm_recoverd+0x49/0x4cc [dlm]
 [<f8a56ba7>] dlm_recoverd+0x0/0x4cc [dlm]
 [<c0134fae>] kthread+0x38/0x5e
 [<c0134f76>] kthread+0x0/0x5e
 [<c0104b07>] kernel_thread_helper+0x7/0x10
 =======================
lock_dlm1     S 00000000     0  5278      2
       f741e750 00000046 c011d4e6 00000000 00000003 f0fc7e78 3cae9d88 00000237 
       f741e8b8 c2018940 00000001 00000000 00000000 00000000 f8945000 00000286 
       f8ca47d3 00000246 f7fc3950 f7fc3800 f7381fc8 f0f99c40 f881f357 00000000 
Call Trace:
 [<c011d4e6>] __wake_up_common+0x32/0x5c
 [<f8ca47d3>] gfs_glock_cb+0xae/0x143 [gfs]
 [<f881f357>] gdlm_thread+0xcd/0x600 [lock_dlm]
 [<c02bbc1a>] schedule+0x588/0x5ec
 [<c011f451>] default_wake_function+0x0/0x8
 [<f881f891>] gdlm_thread1+0x0/0xa [lock_dlm]
 [<c0134fae>] kthread+0x38/0x5e
 [<c0134f76>] kthread+0x0/0x5e
 [<c0104b07>] kernel_thread_helper+0x7/0x10
 =======================
lock_dlm2     S 00000000     0  5279      2
       f7264bf0 00000046 c011d4e6 00000000 00000003 f0fc7ddc 3cae9832 00000237 
       f7264d58 c2018940 00000001 00000000 00000000 00000000 f8945000 00000286 
       f8ca47d3 00000246 f7fc3950 f7fc3800 f725dfc8 f09b1ec0 f881f357 00000000 
Call Trace:
 [<c011d4e6>] __wake_up_common+0x32/0x5c
 [<f8ca47d3>] gfs_glock_cb+0xae/0x143 [gfs]
 [<f881f357>] gdlm_thread+0xcd/0x600 [lock_dlm]
 [<c02bbc1a>] schedule+0x588/0x5ec
 [<c011f451>] default_wake_function+0x0/0x8
 [<f881f88a>] gdlm_thread2+0x0/0x7 [lock_dlm]
 [<c0134fae>] kthread+0x38/0x5e
 [<c0134f76>] kthread+0x0/0x5e
 [<c0104b07>] kernel_thread_helper+0x7/0x10
 =======================
dlm_recoverd  S c20159c0     0  5280      2
       f7cd8df0 00000046 00000cfb c20159c0 00000002 f73cff88 82b864b4 0000012e 
       f7cd8f58 c2018940 00000001 0003d030 eb7f2c46 ffffffff 000000ff 00000000 
       00000000 00000cfb 00000000 f77b1400 00000001 00000000 f8a56bf0 00000000 
Call Trace:
 [<f8a56bf0>] dlm_recoverd+0x49/0x4cc [dlm]
 [<f8a56ba7>] dlm_recoverd+0x0/0x4cc [dlm]
 [<c0134fae>] kthread+0x38/0x5e
 [<c0134f76>] kthread+0x0/0x5e
 [<c0104b07>] kernel_thread_helper+0x7/0x10
 =======================
gfs_scand     S f7253f74     0  5286      2
       f7d60d30 00000046 00000002 f7253f74 f7253f6c 00000000 f89529ec f8ca4928 
       f7d60e98 c2010940 00000000 000825af f7253f98 c04c6ec0 000000fd 00000001 
       00000000 00000000 f7253f98 00082a91 00000000 00000000 c02bbe7f f8ca4928 
Call Trace:
 [<f8ca4928>] scan_glock+0x0/0x129 [gfs]
 [<c02bbe7f>] schedule_timeout+0x70/0x8d
 [<f8ca4928>] scan_glock+0x0/0x129 [gfs]
 [<c012c215>] process_timeout+0x0/0x5
 [<c02bbe7a>] schedule_timeout+0x6b/0x8d
 [<f8c98569>] gfs_scand+0x0/0x3d [gfs]
 [<f8c98599>] gfs_scand+0x30/0x3d [gfs]
 [<c0134fae>] kthread+0x38/0x5e
 [<c0134f76>] kthread+0x0/0x5e
 [<c0104b07>] kernel_thread_helper+0x7/0x10
 =======================
gfs_glockd    S c200d9c0     0  5288      2
       f7256c30 00000046 000005d0 c200d9c0 f0e8c930 f0e8c81c 551630e2 00000237 
       f7256d98 c2010940 00000000 f0a94660 000e59d5 00000000 00000000 f8ca342f 
       00000246 c0135188 f8945000 f8c984c1 f73d5fd0 00000000 f8c98545 00000000 
Call Trace:
 [<f8ca342f>] unlock_on_glock+0x18/0x1f [gfs]
 [<c0135188>] prepare_to_wait+0x12/0x49
 [<f8c984c1>] gfs_glockd+0x0/0xa8 [gfs]
 [<f8c98545>] gfs_glockd+0x84/0xa8 [gfs]
 [<c0135075>] autoremove_wake_function+0x0/0x35
 [<c0134fae>] kthread+0x38/0x5e
 [<c0134f76>] kthread+0x0/0x5e
 [<c0104b07>] kernel_thread_helper+0x7/0x10
 =======================
gfs_recoverd  S f6febf74     0  5292      2
       f7d1f250 00000046 00000002 f6febf74 f6febf6c 00000000 f3932c31 00000182 
       f7d1f3b8 c2010940 00000000 0007f16b f6febf98 c04c6ec0 000000fd 00000001 
       00000000 00000000 f6febf98 00082bc2 00000000 00000000 c02bbe7f f6febfb8 
Call Trace:
 [<c02bbe7f>] schedule_timeout+0x70/0x8d
 [<c012c215>] process_timeout+0x0/0x5
 [<c02bbe7a>] schedule_timeout+0x6b/0x8d
 [<f8c985a6>] gfs_recoverd+0x0/0x3d [gfs]
 [<f8c985d6>] gfs_recoverd+0x30/0x3d [gfs]
 [<c0134fae>] kthread+0x38/0x5e
 [<c0134f76>] kthread+0x0/0x5e
 [<c0104b07>] kernel_thread_helper+0x7/0x10
 =======================
gfs_logd      S f6fedf3c     0  5293      2
       f7d0ebf0 00000046 00000002 f6fedf3c f6fedf34 00000000 c200d9c0 00000000 
       f7d0ed58 c2010940 00000000 0008276a f6fedf60 c04c6ec0 000000ff 00000000 
       00000000 00000000 f6fedf60 00082855 f8945000 00000000 c02bbe7f 03916d40 
Call Trace:
 [<c02bbe7f>] schedule_timeout+0x70/0x8d
 [<c012c215>] process_timeout+0x0/0x5
 [<c02bbe7a>] schedule_timeout+0x6b/0x8d
 [<f8c98675>] gfs_logd+0x92/0xa8 [gfs]
 [<f8c985e3>] gfs_logd+0x0/0xa8 [gfs]
 [<c0134fae>] kthread+0x38/0x5e
 [<c0134f76>] kthread+0x0/0x5e
 [<c0104b07>] kernel_thread_helper+0x7/0x10
 =======================
gfs_quotad    S f6feff54     0  5294      2
       f73cb870 00000046 00000002 f6feff54 f6feff4c 00000000 7e3c9079 00000237 
       f73cb9d8 c2010940 00000000 f6feff78 14077efa 00000000 00000286 c012c43e 
       00000000 00000286 f6feff78 00082c1f f8945000 0007f15b c02bbe7f f8cb93f3 
Call Trace:
 [<c012c43e>] __mod_timer+0x9a/0xa4
 [<c02bbe7f>] schedule_timeout+0x70/0x8d
 [<f8cb93f3>] quota_unlock+0x14/0x79 [gfs]
 [<c012c215>] process_timeout+0x0/0x5
 [<c02bbe7a>] schedule_timeout+0x6b/0x8d
 [<f8c987d1>] gfs_quotad+0x146/0x15d [gfs]
 [<f8c9868b>] gfs_quotad+0x0/0x15d [gfs]
 [<c0134fae>] kthread+0x38/0x5e
 [<c0134f76>] kthread+0x0/0x5e
 [<c0104b07>] kernel_thread_helper+0x7/0x10
 =======================
gfs_inoded    S f6ff1f74     0  5295      2
       f7257210 00000046 00000002 f6ff1f74 f6ff1f6c 00000000 15a59ebd 00000235 
       f7257378 c2010940 00000000 f6ff1f98 00000ec5 00000000 00000286 c012c43e 
       00000000 00000286 f6ff1f98 00082bc9 00000000 00000000 c02bbe7f 00000000 
Call Trace:
 [<c012c43e>] __mod_timer+0x9a/0xa4
 [<c02bbe7f>] schedule_timeout+0x70/0x8d
 [<c02bcb3e>] call_rwsem_down_write_failed+0x6/0x8
 [<c012c215>] process_timeout+0x0/0x5
 [<c02bbe7a>] schedule_timeout+0x6b/0x8d
 [<f8c98484>] gfs_inoded+0x0/0x3d [gfs]
 [<f8c984b4>] gfs_inoded+0x30/0x3d [gfs]
 [<c0134fae>] kthread+0x38/0x5e
 [<c0134f76>] kthread+0x0/0x5e
 [<c0104b07>] kernel_thread_helper+0x7/0x10
 =======================
lock_dlm1     S f64389a8     0  5369      2
       f7256070 00000046 000000c0 f64389a8 f0ef2140 f8bd2000 fcfe4bc3 00000233 
       f72561d8 c2010940 00000000 f8bd2000 00000000 00000000 f8bd2000 f724bfb8 
       f8ca47d3 00000246 f74a3350 f74a3200 f724bfc8 f61a69c0 f881f357 00000000 
Call Trace:
 [<f8ca47d3>] gfs_glock_cb+0xae/0x143 [gfs]
 [<f881f357>] gdlm_thread+0xcd/0x600 [lock_dlm]
 [<c02bbc1a>] schedule+0x588/0x5ec
 [<c011f451>] default_wake_function+0x0/0x8
 [<f881f891>] gdlm_thread1+0x0/0xa [lock_dlm]
 [<c0134fae>] kthread+0x38/0x5e
 [<c0134f76>] kthread+0x0/0x5e
 [<c0104b07>] kernel_thread_helper+0x7/0x10
 =======================
lock_dlm2     S f64d0e40     0  5370      2
       dfa0b8f0 00000046 000000c0 f64d0e40 f080cfc0 f8bd2000 fcfe41f2 00000233 
       dfa0ba58 c2010940 00000000 f8bd2000 00003977 00000000 f8bd2000 f723ffb8 
       f8ca47d3 00000246 f74a3350 f74a3200 f723ffc8 f6942c40 f881f357 00000000 
Call Trace:
 [<f8ca47d3>] gfs_glock_cb+0xae/0x143 [gfs]
 [<f881f357>] gdlm_thread+0xcd/0x600 [lock_dlm]
 [<c02bbc1a>] schedule+0x588/0x5ec
 [<c011f451>] default_wake_function+0x0/0x8
 [<f881f88a>] gdlm_thread2+0x0/0x7 [lock_dlm]
 [<c0134fae>] kthread+0x38/0x5e
 [<c0134f76>] kthread+0x0/0x5e
 [<c0104b07>] kernel_thread_helper+0x7/0x10
 =======================
dlm_recoverd  S 00000001     0  5372      2
       dfa078b0 00000046 f71e50a0 00000001 f71e5000 f8a5164d 286f333c 0000012f 
       dfa07a18 c2010940 00000000 f768ffe0 00012930 00000000 f71e5000 f8a562da 
       f8a51735 000000ff 00000000 f71e5000 00000001 00000000 f8a56bf0 00000000 
Call Trace:
 [<f8a5164d>] dlm_recover_waiters_post+0x304/0x30e [dlm]
 [<f8a562da>] wait_status+0x8b/0xd8 [dlm]
 [<f8a51735>] dlm_grant_after_purge+0x1f/0xb5 [dlm]
 [<f8a56bf0>] dlm_recoverd+0x49/0x4cc [dlm]
 [<f8a56ba7>] dlm_recoverd+0x0/0x4cc [dlm]
 [<c0134fae>] kthread+0x38/0x5e
 [<c0134f76>] kthread+0x0/0x5e
 [<c0104b07>] kernel_thread_helper+0x7/0x10
 =======================
gfs_scand     S f7151f74     0  5380      2
       f70be1b0 00000046 00000002 f7151f74 f7151f6c 00000000 4079ac3a 00000236 
       f70be318 c2010940 00000000 0008274a f7151f98 c04c6ec0 000000fd 00000001 
       00000000 00000000 f7151f98 00082c20 00000000 00000000 c02bbe7f f8ca4928 
Call Trace:
 [<c02bbe7f>] schedule_timeout+0x70/0x8d
 [<f8ca4928>] scan_glock+0x0/0x129 [gfs]
 [<c012c215>] process_timeout+0x0/0x5
 [<c02bbe7a>] schedule_timeout+0x6b/0x8d
 [<f8c98569>] gfs_scand+0x0/0x3d [gfs]
 [<f8c98599>] gfs_scand+0x30/0x3d [gfs]
 [<c0134fae>] kthread+0x38/0x5e
 [<c0134f76>] kthread+0x0/0x5e
 [<c0104b07>] kernel_thread_helper+0x7/0x10
 =======================
gfs_glockd    S f080cfc0     0  5385      2
       f72519b0 00000046 f64d0e40 f080cfc0 f8cd43c0 f8ca2a54 fcfd871e 00000233 
       f7251b18 c2010940 00000000 f64d0e40 00001f60 00000000 00000000 f8ca342f 
       00000246 c0135188 f8bd2000 f8c984c1 dfa0ffd0 00000000 f8c98545 00000000 
Call Trace:
 [<f8ca2a54>] run_queue+0x159/0x30f [gfs]
 [<f8ca342f>] unlock_on_glock+0x18/0x1f [gfs]
 [<c0135188>] prepare_to_wait+0x12/0x49
 [<f8c984c1>] gfs_glockd+0x0/0xa8 [gfs]
 [<f8c98545>] gfs_glockd+0x84/0xa8 [gfs]
 [<c0135075>] autoremove_wake_function+0x0/0x35
 [<c0134fae>] kthread+0x38/0x5e
 [<c0134f76>] kthread+0x0/0x5e
 [<c0104b07>] kernel_thread_helper+0x7/0x10
 =======================
gfs_recoverd  S dfaa5f74     0  5459      2
       f7d54130 00000046 00000002 dfaa5f74 dfaa5f6c 00000000 e14aeda8 000001d6 
       f7d54298 c2010940 00000000 0007f26b dfaa5f98 c04c6ec0 000000ff 00000000 
       00000000 00000000 dfaa5f98 00082c84 00000000 00000000 c02bbe7f dfaa5fb8 
Call Trace:
 [<c02bbe7f>] schedule_timeout+0x70/0x8d
 [<c012c215>] process_timeout+0x0/0x5
 [<c02bbe7a>] schedule_timeout+0x6b/0x8d
 [<f8c985a6>] gfs_recoverd+0x0/0x3d [gfs]
 [<f8c985d6>] gfs_recoverd+0x30/0x3d [gfs]
 [<c0134fae>] kthread+0x38/0x5e
 [<c0134f76>] kthread+0x0/0x5e
 [<c0104b07>] kernel_thread_helper+0x7/0x10
 =======================
gfs_logd      S dfaa7f3c     0  5460      2
       dfa6c030 00000046 00000002 dfaa7f3c dfaa7f34 00000000 85639b11 00000237 
       dfa6c198 c2010940 00000000 dfaa7f60 00001491 00000000 00000286 c012c43e 
       00000000 00000286 dfaa7f60 00082855 f8bd2000 00000000 c02bbe7f f8bd2000 
Call Trace:
 [<c012c43e>] __mod_timer+0x9a/0xa4
 [<c02bbe7f>] schedule_timeout+0x70/0x8d
 [<c012c215>] process_timeout+0x0/0x5
 [<c02bbe7a>] schedule_timeout+0x6b/0x8d
 [<f8c98675>] gfs_logd+0x92/0xa8 [gfs]
 [<f8c985e3>] gfs_logd+0x0/0xa8 [gfs]
 [<c0134fae>] kthread+0x38/0x5e
 [<c0134f76>] kthread+0x0/0x5e
 [<c0104b07>] kernel_thread_helper+0x7/0x10
 =======================
gfs_quotad    S dfaa9f54     0  5461      2
       f70bed70 00000046 00000002 dfaa9f54 dfaa9f4c 00000000 5e9f6b82 00000204 
       f70beed8 c2010940 00000000 0008282a dfaa9f78 c04c6ec0 000000fd 00000001 
       00000000 00000000 dfaa9f78 00082ca5 f8bd2000 0007f209 c02bbe7f 00000282 
Call Trace:
 [<c02bbe7f>] schedule_timeout+0x70/0x8d
 [<c012c215>] process_timeout+0x0/0x5
 [<c02bbe7a>] schedule_timeout+0x6b/0x8d
 [<f8c987d1>] gfs_quotad+0x146/0x15d [gfs]
 [<f8c9868b>] gfs_quotad+0x0/0x15d [gfs]
 [<c0134fae>] kthread+0x38/0x5e
 [<c0134f76>] kthread+0x0/0x5e
 [<c0104b07>] kernel_thread_helper+0x7/0x10
 =======================
gfs_inoded    S dfaabf74     0  5462      2
       f7d0e610 00000046 00000002 dfaabf74 dfaabf6c 00000000 5d311e61 00000204 
       f7d0e778 c2010940 00000000 00081e59 dfaabf98 c04c6ec0 000000ff 00000000 
       00000000 00000000 dfaabf98 00082c87 00000000 00000000 c02bbe7f dfaabf8c 
Call Trace:
 [<c02bbe7f>] schedule_timeout+0x70/0x8d
 [<c012c215>] process_timeout+0x0/0x5
 [<c02bbe7a>] schedule_timeout+0x6b/0x8d
 [<f8c98484>] gfs_inoded+0x0/0x3d [gfs]
 [<f8c984b4>] gfs_inoded+0x30/0x3d [gfs]
 [<c0134fae>] kthread+0x38/0x5e
 [<c0134f76>] kthread+0x0/0x5e
 [<c0104b07>] kernel_thread_helper+0x7/0x10
 =======================
lockd         S f68dbeec     0  5584      2
       f7412cf0 00000046 00000002 f68dbeec f68dbee4 00000000 f7a24800 f691b2c0 
       f7412e58 c2010940 00000000 0003d596 f8c7555f 00000000 000000ff 00000000 
       00000000 00000000 7fffffff f6fdc000 f770c604 f68dbf6c c02bbe22 0000012f 
Call Trace:
 [<f8c7555f>] svc_udp_recvfrom+0x175/0x367 [sunrpc]
 [<c02bbe22>] schedule_timeout+0x13/0x8d
 [<f8c74c80>] svc_sock_release+0xdd/0x149 [sunrpc]
 [<c0135234>] add_wait_queue+0x12/0x32
 [<f8c7642c>] svc_recv+0x23d/0x3b9 [sunrpc]
 [<c0121b59>] sched_move_task+0xbf/0xc5
 [<c011f451>] default_wake_function+0x0/0x8
 [<f8bfc334>] lockd+0x111/0x225 [lockd]
 [<c01212f6>] schedule_tail+0x18/0x52
 [<c0103d8a>] ret_from_fork+0x6/0x1c
 [<f8bfc223>] lockd+0x0/0x225 [lockd]
 [<f8bfc223>] lockd+0x0/0x225 [lockd]
 [<c0104b07>] kernel_thread_helper+0x7/0x10
 =======================
nfsd4         S f68ddfa0     0  5585      2
       f72513d0 00000046 00000002 f68ddfa0 f68ddf98 00000000 674aa5e9 00000216 
       f7251538 c2010940 00000000 0007f46b f8db0f74 00000000 000000ff 00000000 
       00000000 00000000 f71efec0 c01326e3 f68ddfd0 00000000 c013276b 00000000 
Call Trace:
 [<f8db0f74>] laundromat_main+0x0/0x1d8 [nfsd]
 [<c01326e3>] worker_thread+0x0/0xc5
 [<c013276b>] worker_thread+0x88/0xc5
 [<c0135075>] autoremove_wake_function+0x0/0x35
 [<c0134fae>] kthread+0x38/0x5e
 [<c0134f76>] kthread+0x0/0x5e
 [<c0104b07>] kernel_thread_helper+0x7/0x10
 =======================
nfsd          D c20159c0     0  5586      2
       f7269830 00000046 000001a7 c20159c0 00000002 f6999b58 40e26f3d 000001df 
       f7269998 c2018940 00000001 0006b57b ec672099 ffffffff 000000ff 00000000 
       00000000 000001a7 7fffffff f6999cf0 f6999bd4 7fffffff c02bbe22 00008000 
Call Trace:
 [<c02bbe22>] schedule_timeout+0x13/0x8d
 [<c015b8e6>] generic_file_aio_write_nolock+0x3f/0x92
 [<c02bb53d>] wait_for_common+0x16/0x123
 [<c02bb5dd>] wait_for_common+0xb6/0x123
 [<c011f451>] default_wake_function+0x0/0x8
 [<f8ca2d12>] glock_wait_internal+0x108/0x249 [gfs]
 [<f8ca31bf>] gfs_glock_nq+0x36c/0x3a5 [gfs]
 [<f8ca3210>] gfs_glock_nq_init+0x18/0x2b [gfs]
 [<f8ca451a>] gfs_glock_nq_num+0x3f/0x88 [gfs]
 [<f8cb25c8>] gfs_get_dentry+0xa3/0x2ba [gfs]
 [<c025a825>] skb_copy_datagram_iovec+0x53/0x1d3
 [<c026c797>] __qdisc_run+0x9e/0x164
 [<c02bce5e>] _spin_lock_bh+0x8/0x18
 [<c0259185>] skb_release_all+0xa3/0xfa
 [<c02bce5e>] _spin_lock_bh+0x8/0x18
 [<c0255991>] release_sock+0x12/0x8e
 [<c028424e>] tcp_recvmsg+0x630/0x73c
 [<f8cb2925>] gfs_fh_to_dentry+0x69/0x6f [gfs]
 [<f880f4bd>] exportfs_decode_fh+0x29/0x1a7 [exportfs]
 [<c011da1a>] update_curr+0x62/0xef
 [<f8c79a0f>] cache_check+0x59/0x3bd [sunrpc]
 [<c011e0cf>] enqueue_entity+0x2b/0x3d
 [<f8da227c>] exp_get_by_name+0x43/0x52 [nfsd]
 [<f8c7a827>] sunrpc_cache_lookup+0x3e/0xf4 [sunrpc]
 [<f8c79a0f>] cache_check+0x59/0x3bd [sunrpc]
 [<c012fac2>] set_current_groups+0x14d/0x159
 [<f8da41e8>] nfsd_setuser+0x125/0x175 [nfsd]
 [<f8d9e407>] nfsd_setuser_and_check_port+0x4f/0x57 [nfsd]
 [<c011ef21>] __wake_up+0x32/0x42
 [<f8da24ea>] exp_find+0x5b/0x63 [nfsd]
 [<f8da2520>] rqst_exp_find+0x2e/0xa5 [nfsd]
 [<f8d9eb11>] fh_verify+0x1e8/0x47f [nfsd]
 [<f8d9e86f>] nfsd_acceptable+0x0/0xba [nfsd]
 [<c011df2e>] load_balance_start_fair+0x0/0x5
 [<c011da1a>] update_curr+0x62/0xef
 [<f8d9fbb8>] nfsd_open+0x28/0x163 [nfsd]
 [<f8d9fee8>] nfsd_write+0x90/0xe7 [nfsd]
 [<f8c7a827>] sunrpc_cache_lookup+0x3e/0xf4 [sunrpc]
 [<f8da6486>] nfsd3_proc_write+0x109/0x123 [nfsd]
 [<f8d9c20e>] nfsd_dispatch+0xd3/0x1a0 [nfsd]
 [<f8c76c29>] svcauth_unix_set_client+0x135/0x163 [sunrpc]
 [<f8c7385e>] svc_process+0x3be/0x670 [sunrpc]
 [<f8c76530>] svc_recv+0x341/0x3b9 [sunrpc]
 [<f8d9c76c>] nfsd+0x17f/0x28f [nfsd]
 [<f8d9c5ed>] nfsd+0x0/0x28f [nfsd]
 [<c0104b07>] kernel_thread_helper+0x7/0x10
 =======================
nfsd          D 00000282     0  5587      2
       f7cc0790 00000046 c013c948 00000282 f75a7000 00000000 40e1585d 000001df 
       f7cc08f8 c2018940 00000001 f708a280 00002876 00000000 c027d2ab 1e702200 
       f69d1900 f778c4dc 7fffffff f69d9cf0 f69d9bd4 7fffffff c02bbe22 00000200 
Call Trace:
 [<c013c948>] tick_program_event+0x33/0x52
 [<c027d2ab>] ip_finish_output+0x1d3/0x20b
 [<c02bbe22>] schedule_timeout+0x13/0x8d
 [<c0115e82>] smp_apic_timer_interrupt+0x71/0x7d
 [<f89285ce>] qla2x00_start_scsi+0x2df/0x311 [qla2xxx]
 [<c0104978>] apic_timer_interrupt+0x28/0x30
 [<c02bb5dd>] wait_for_common+0xb6/0x123
 [<c011f451>] default_wake_function+0x0/0x8
 [<f8ca2d12>] glock_wait_internal+0x108/0x249 [gfs]
 [<f8ca31bf>] gfs_glock_nq+0x36c/0x3a5 [gfs]
 [<f8ca3210>] gfs_glock_nq_init+0x18/0x2b [gfs]
 [<f8ca451a>] gfs_glock_nq_num+0x3f/0x88 [gfs]
 [<f8cb25c8>] gfs_get_dentry+0xa3/0x2ba [gfs]
 [<c025a825>] skb_copy_datagram_iovec+0x53/0x1d3
 [<c026c797>] __qdisc_run+0x9e/0x164
 [<c02bce5e>] _spin_lock_bh+0x8/0x18
 [<c02559d1>] release_sock+0x52/0x8e
 [<c028424e>] tcp_recvmsg+0x630/0x73c
 [<f8cb2925>] gfs_fh_to_dentry+0x69/0x6f [gfs]
 [<f880f4bd>] exportfs_decode_fh+0x29/0x1a7 [exportfs]
 [<c011da1a>] update_curr+0x62/0xef
 [<f8c79a0f>] cache_check+0x59/0x3bd [sunrpc]
 [<c011e0cf>] enqueue_entity+0x2b/0x3d
 [<f8da227c>] exp_get_by_name+0x43/0x52 [nfsd]
 [<f8c7a827>] sunrpc_cache_lookup+0x3e/0xf4 [sunrpc]
 [<f8c79a0f>] cache_check+0x59/0x3bd [sunrpc]
 [<c012fac2>] set_current_groups+0x14d/0x159
 [<f8da41e8>] nfsd_setuser+0x125/0x175 [nfsd]
 [<f8d9e407>] nfsd_setuser_and_check_port+0x4f/0x57 [nfsd]
 [<c011ef21>] __wake_up+0x32/0x42
 [<f8da24ea>] exp_find+0x5b/0x63 [nfsd]
 [<f8da2520>] rqst_exp_find+0x2e/0xa5 [nfsd]
 [<f8d9eb11>] fh_verify+0x1e8/0x47f [nfsd]
 [<f8d9e86f>] nfsd_acceptable+0x0/0xba [nfsd]
 [<f8d9fbb8>] nfsd_open+0x28/0x163 [nfsd]
 [<f8d9fee8>] nfsd_write+0x90/0xe7 [nfsd]
 [<f8c7a827>] sunrpc_cache_lookup+0x3e/0xf4 [sunrpc]
 [<f8da6486>] nfsd3_proc_write+0x109/0x123 [nfsd]
 [<f8d9c20e>] nfsd_dispatch+0xd3/0x1a0 [nfsd]
 [<f8c76c29>] svcauth_unix_set_client+0x135/0x163 [sunrpc]
 [<f8c7385e>] svc_process+0x3be/0x670 [sunrpc]
 [<f8c76530>] svc_recv+0x341/0x3b9 [sunrpc]
 [<f8d9c76c>] nfsd+0x17f/0x28f [nfsd]
 [<f8d9c5ed>] nfsd+0x0/0x28f [nfsd]
 [<c0104b07>] kernel_thread_helper+0x7/0x10
 =======================
nfsd          R running      0  5589      2
nfsd          D f6ab7d6c     0  5590      2
       f7268c70 00000046 f6ab7c40 f6ab7d6c f7ae47b8 c16cab00 40e232cd 000001df 
       f7268dd8 c2018940 00000001 00000001 00002641 00000000 00000001 c011e0cf 
       c2015920 f7269830 7fffffff f6ab7cf0 f6ab7bd4 7fffffff c02bbe22 f7269830 
Call Trace:
 [<c011e0cf>] enqueue_entity+0x2b/0x3d
 [<c02bbe22>] schedule_timeout+0x13/0x8d
 [<c011d6d2>] activate_task+0x1c/0x28
 [<c011f447>] try_to_wake_up+0x2b7/0x2c1
 [<c02bb5dd>] wait_for_common+0xb6/0x123
 [<c011f451>] default_wake_function+0x0/0x8
 [<f8ca2d12>] glock_wait_internal+0x108/0x249 [gfs]
 [<f8ca31bf>] gfs_glock_nq+0x36c/0x3a5 [gfs]
 [<f8ca3210>] gfs_glock_nq_init+0x18/0x2b [gfs]
 [<f8ca451a>] gfs_glock_nq_num+0x3f/0x88 [gfs]
 [<f8cb25c8>] gfs_get_dentry+0xa3/0x2ba [gfs]
 [<c025a825>] skb_copy_datagram_iovec+0x53/0x1d3
 [<c026c797>] __qdisc_run+0x9e/0x164
 [<c02bce5e>] _spin_lock_bh+0x8/0x18
 [<c0255991>] release_sock+0x12/0x8e
 [<c028424e>] tcp_recvmsg+0x630/0x73c
 [<f8cb2925>] gfs_fh_to_dentry+0x69/0x6f [gfs]
 [<f880f4bd>] exportfs_decode_fh+0x29/0x1a7 [exportfs]
 [<c011da1a>] update_curr+0x62/0xef
 [<f8c79a0f>] cache_check+0x59/0x3bd [sunrpc]
 [<c011e0cf>] enqueue_entity+0x2b/0x3d
 [<f8da227c>] exp_get_by_name+0x43/0x52 [nfsd]
 [<f8c7a827>] sunrpc_cache_lookup+0x3e/0xf4 [sunrpc]
 [<f8c79a0f>] cache_check+0x59/0x3bd [sunrpc]
 [<c012fac2>] set_current_groups+0x14d/0x159
 [<f8da41e8>] nfsd_setuser+0x125/0x175 [nfsd]
 [<f8d9e407>] nfsd_setuser_and_check_port+0x4f/0x57 [nfsd]
 [<c011ef21>] __wake_up+0x32/0x42
 [<f8da24ea>] exp_find+0x5b/0x63 [nfsd]
 [<f8da2520>] rqst_exp_find+0x2e/0xa5 [nfsd]
 [<f8d9eb11>] fh_verify+0x1e8/0x47f [nfsd]
 [<f8d9e86f>] nfsd_acceptable+0x0/0xba [nfsd]
 [<c011df2e>] load_balance_start_fair+0x0/0x5
 [<c011df29>] load_balance_next_fair+0x0/0x5
 [<f8d9fbb8>] nfsd_open+0x28/0x163 [nfsd]
 [<f8d9fee8>] nfsd_write+0x90/0xe7 [nfsd]
 [<f8c7a827>] sunrpc_cache_lookup+0x3e/0xf4 [sunrpc]
 [<f8da6486>] nfsd3_proc_write+0x109/0x123 [nfsd]
 [<f8d9c20e>] nfsd_dispatch+0xd3/0x1a0 [nfsd]
 [<f8c76c29>] svcauth_unix_set_client+0x135/0x163 [sunrpc]
 [<f8c7385e>] svc_process+0x3be/0x670 [sunrpc]
 [<f8c76530>] svc_recv+0x341/0x3b9 [sunrpc]
 [<f8d9c76c>] nfsd+0x17f/0x28f [nfsd]
 [<f8d9c5ed>] nfsd+0x0/0x28f [nfsd]
 [<c0104b07>] kernel_thread_helper+0x7/0x10
 =======================
nfsd          D f6af7d6c     0  5591      2
       f7264030 00000046 f6af7c40 f6af7d6c f7ae47b8 c16cab00 40dfd904 000001df 
       f7264198 c2018940 00000001 00000000 00002e66 00000000 f6af7e14 00000005 
       f8c989c4 0062ed3c 7fffffff f6af7cf0 f6af7bd4 7fffffff c02bbe22 00000000 
Call Trace:
 [<f8c989c4>] gfs_dgetblk+0x26/0x2b [gfs]
 [<c02bbe22>] schedule_timeout+0x13/0x8d
 [<c015b8e6>] generic_file_aio_write_nolock+0x3f/0x92
 [<c02bb53d>] wait_for_common+0x16/0x123
 [<c02bb5dd>] wait_for_common+0xb6/0x123
 [<c011f451>] default_wake_function+0x0/0x8
 [<f8ca2d12>] glock_wait_internal+0x108/0x249 [gfs]
 [<f8ca31bf>] gfs_glock_nq+0x36c/0x3a5 [gfs]
 [<f8ca3210>] gfs_glock_nq_init+0x18/0x2b [gfs]
 [<f8ca451a>] gfs_glock_nq_num+0x3f/0x88 [gfs]
 [<f8cb25c8>] gfs_get_dentry+0xa3/0x2ba [gfs]
 [<c025a825>] skb_copy_datagram_iovec+0x53/0x1d3
 [<c026c797>] __qdisc_run+0x9e/0x164
 [<c0259185>] skb_release_all+0xa3/0xfa
 [<c02bce5e>] _spin_lock_bh+0x8/0x18
 [<c0255991>] release_sock+0x12/0x8e
 [<c028424e>] tcp_recvmsg+0x630/0x73c
 [<c025fc69>] dev_queue_xmit+0x287/0x2ae
 [<f8cb2925>] gfs_fh_to_dentry+0x69/0x6f [gfs]
 [<f880f4bd>] exportfs_decode_fh+0x29/0x1a7 [exportfs]
 [<c011da1a>] update_curr+0x62/0xef
 [<f8c79a0f>] cache_check+0x59/0x3bd [sunrpc]
 [<c011e0cf>] enqueue_entity+0x2b/0x3d
 [<f8da227c>] exp_get_by_name+0x43/0x52 [nfsd]
 [<f8c7a827>] sunrpc_cache_lookup+0x3e/0xf4 [sunrpc]
 [<f8c79a0f>] cache_check+0x59/0x3bd [sunrpc]
 [<c012fac2>] set_current_groups+0x14d/0x159
 [<f8da41e8>] nfsd_setuser+0x125/0x175 [nfsd]
 [<f8d9e407>] nfsd_setuser_and_check_port+0x4f/0x57 [nfsd]
 [<c011ef21>] __wake_up+0x32/0x42
 [<f8da24ea>] exp_find+0x5b/0x63 [nfsd]
 [<f8da2520>] rqst_exp_find+0x2e/0xa5 [nfsd]
 [<f8d9eb11>] fh_verify+0x1e8/0x47f [nfsd]
 [<f8d9e86f>] nfsd_acceptable+0x0/0xba [nfsd]
 [<c011da1a>] update_curr+0x62/0xef
 [<f8d9fbb8>] nfsd_open+0x28/0x163 [nfsd]
 [<f8d9fee8>] nfsd_write+0x90/0xe7 [nfsd]
 [<f8c7a827>] sunrpc_cache_lookup+0x3e/0xf4 [sunrpc]
 [<f8da6486>] nfsd3_proc_write+0x109/0x123 [nfsd]
 [<f8d9c20e>] nfsd_dispatch+0xd3/0x1a0 [nfsd]
 [<f8c76c29>] svcauth_unix_set_client+0x135/0x163 [sunrpc]
 [<f8c7385e>] svc_process+0x3be/0x670 [sunrpc]
 [<f8c76530>] svc_recv+0x341/0x3b9 [sunrpc]
 [<f8d9c76c>] nfsd+0x17f/0x28f [nfsd]
 [<f8d9c5ed>] nfsd+0x0/0x28f [nfsd]
 [<c0104b07>] kernel_thread_helper+0x7/0x10
 =======================
nfsexport.sh  S 7aee7065     0 23280  23131
       f0c4b7b0 00000082 c16d5e4c 7aee7065 7aee7065 c200d980 5f756026 00000237 
       f0c4b918 c2010940 00000000 f744b080 00000000 00000000 00000000 c200d920 
       c2010974 c01bd464 ffffffff 00000001 f0c4b7a8 00000000 c012719a 00000246 
Call Trace:
 [<c01bd464>] security_task_wait+0xc/0xd
 [<c012719a>] do_wait+0x964/0xa47
 [<c012ce5f>] do_sigaction+0x8a/0x136
 [<c0123d23>] do_fork+0x120/0x1cc
 [<c011f451>] default_wake_function+0x0/0x8
 [<c01272ae>] sys_wait4+0x31/0x34
 [<c01272d8>] sys_waitpid+0x27/0x2b
 [<c0103e56>] sysenter_past_esp+0x6b/0xa1
 [<c02b0000>] unix_create1+0xbb/0xfa
 =======================
nfsexport.sh  S 7bfb2065     0 23282  23130
       f05d1870 00000086 c161076c 7bfb2065 7bfb2065 c200d980 5f81f760 00000237 
       f05d19d8 c2010940 00000000 f74f4080 0000dc82 00000000 00000000 c200d920 
       c2010974 c01bd464 ffffffff 00000001 f05d1868 00000000 c012719a c0103039 
Call Trace:
 [<c01bd464>] security_task_wait+0xc/0xd
 [<c012719a>] do_wait+0x964/0xa47
 [<c0103039>] __switch_to+0x9d/0x11c
 [<c012ce5f>] do_sigaction+0x8a/0x136
 [<c0123d23>] do_fork+0x120/0x1cc
 [<c011f451>] default_wake_function+0x0/0x8
 [<c01272ae>] sys_wait4+0x31/0x34
 [<c01272d8>] sys_waitpid+0x27/0x2b
 [<c0103e56>] sysenter_past_esp+0x6b/0xa1
 [<c02b0000>] unix_create1+0xbb/0xfa
 =======================
nfsexport.sh  S 7b566065     0 23298  23280
       f6b653d0 00000086 c1608b2c 7b566065 7b566065 c200d980 688d37c7 00000237 
       f6b65538 c2010940 00000000 f76bb080 00000000 00000000 00000000 c200d920 
       c2010974 c01bd464 ffffffff 00000001 f6b653c8 00000000 c012719a c0103039 
Call Trace:
 [<c01bd464>] security_task_wait+0xc/0xd
 [<c012719a>] do_wait+0x964/0xa47
 [<c0103039>] __switch_to+0x9d/0x11c
 [<c012ce5f>] do_sigaction+0x8a/0x136
 [<c0123d23>] do_fork+0x120/0x1cc
 [<c011f451>] default_wake_function+0x0/0x8
 [<c01272ae>] sys_wait4+0x31/0x34
 [<c01272d8>] sys_waitpid+0x27/0x2b
 [<c0103e56>] sysenter_past_esp+0x6b/0xa1
 =======================
nfsexport.sh  S f05e5f20     0 23300  23282
       f6b64810 00000082 00000002 f05e5f20 f05e5f18 00000000 f6b4c680 00000001 
       f6b64978 c2010940 00000000 000826c1 a66f21b9 c200d99c 000000fd 00000001 
       00000000 00000000 ffffffff 00000001 f6b64808 00000000 c012719a c0103039 
Call Trace:
 [<c012719a>] do_wait+0x964/0xa47
 [<c0103039>] __switch_to+0x9d/0x11c
 [<c012ce5f>] do_sigaction+0x8a/0x136
 [<c0123d23>] do_fork+0x120/0x1cc
 [<c011f451>] default_wake_function+0x0/0x8
 [<c01272ae>] sys_wait4+0x31/0x34
 [<c01272d8>] sys_waitpid+0x27/0x2b
 [<c0103e56>] sysenter_past_esp+0x6b/0xa1
 =======================
sleep         S c200e044     0 23354  23298
       f6b4cc30 00000086 f6b53f38 c200e044 c200dfb8 00000000 687b0076 00000237 
       f6b4cd98 c2010940 00000000 00000237 00000000 00000000 f70c4900 c200dfb8 
       00000000 00000286 f6b53f38 00000001 00000001 00000000 c02bc21a 00000001 
Call Trace:
 [<c02bc21a>] do_nanosleep+0x48/0x73
 [<c0137bd7>] hrtimer_nanosleep+0x39/0xb7
 [<c013766f>] hrtimer_wakeup+0x0/0x18
 [<c02bc20f>] do_nanosleep+0x3d/0x73
 [<c0137ce0>] sys_nanosleep+0x8b/0x96
 [<c016a3b3>] sys_brk+0xc5/0xcd
 [<c0103e56>] sysenter_past_esp+0x6b/0xa1
 [<c02b0000>] unix_create1+0xbb/0xfa
 =======================
sleep         S f6b53f3c     0 23355  23300
       f6b4c650 00000086 f6b55f38 f6b53f3c c200dfb8 00000000 688c5aad 00000237 
       f6b4c7b8 c2010940 00000000 00000237 00000000 00000000 f70c4ac0 c200dfb8 
       00000000 00000286 f6b55f38 00000001 00000001 00000000 c02bc21a 00000001 
Call Trace:
 [<c02bc21a>] do_nanosleep+0x48/0x73
 [<c0137bd7>] hrtimer_nanosleep+0x39/0xb7
 [<c013766f>] hrtimer_wakeup+0x0/0x18
 [<c02bc20f>] do_nanosleep+0x3d/0x73
 [<c0137ce0>] sys_nanosleep+0x8b/0x96
 [<c016a3b3>] sys_brk+0xc5/0xcd
 [<c0103e56>] sysenter_past_esp+0x6b/0xa1
 [<c02b0000>] unix_create1+0xbb/0xfa
 =======================
Clocksource tsc unstable (delta = 9374030724 ns)
Time: acpi_pm clocksource has been installed.

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 189 bytes
Desc: Digital signature
URL: <http://listman.redhat.com/archives/linux-cluster/attachments/20080212/3c0979f1/attachment.sig>

From p_pavlos at freemail.gr  Wed Feb 13 10:33:47 2008
From: p_pavlos at freemail.gr (Pavlos Parissis)
Date: Wed, 13 Feb 2008 12:33:47 +0200
Subject: [Linux-cluster] Netmask bit set to 32 in service ip
Message-ID: <20080213123347.ad6mnbk1coo44kwo@easymail-app.hol.gr>

Hi,

I have a question which may sounds stupid.
why the netmask for the service ip is set to 32 while the IP belongs  
to a network with different netmask?

Regards,
Pavlos


: bond0: <BROADCAST,MULTICAST,MASTER,UP> mtu 1500 qdisc noqueue
     link/ether 00:19:bb:3b:6c:b1 brd ff:ff:ff:ff:ff:ff
     inet 10.10.21.133/26 brd 10.10.21.191 scope global bond0
     inet 10.10.21.138/32 scope global bond0 <<================= service ip
3: bond1: <BROADCAST,MULTICAST,MASTER,UP> mtu 1500 qdisc noqueue
     link/ether 00:1a:4b:ff:9c:e8 brd ff:ff:ff:ff:ff:ff
     inet 10.10.21.69/27 brd 10.10.21.95 scope global bond1
     inet 10.10.21.71/32 scope global bond1 <<================= service ip
4: bond2: <BROADCAST,MULTICAST,MASTER,UP> mtu 1500 qdisc noqueue
     link/ether 00:1a:4b:ff:9c:ea brd ff:ff:ff:ff:ff:ff
     inet 10.10.21.228/27 brd 10.10.21.255 scope global bond2
5: eth0: <BROADCAST,MULTICAST,SLAVE,UP> mtu 1500 qdisc pfifo_fast  
master bond0 qlen 1000
     link/ether 00:19:bb:3b:6c:b1 brd ff:ff:ff:ff:ff:ff
6: eth1: <BROADCAST,MULTICAST,SLAVE,UP> mtu 1500 qdisc pfifo_fast  
master bond0 qlen 1000
     link/ether 00:19:bb:3b:6c:b1 brd ff:ff:ff:ff:ff:ff
7: eth2: <BROADCAST,MULTICAST,SLAVE,UP> mtu 1500 qdisc pfifo_fast  
master bond1 qlen 1000
     link/ether 00:1a:4b:ff:9c:e8 brd ff:ff:ff:ff:ff:ff
8: eth3: <BROADCAST,MULTICAST,SLAVE,UP> mtu 1500 qdisc pfifo_fast  
master bond1 qlen 1000
     link/ether 00:1a:4b:ff:9c:e8 brd ff:ff:ff:ff:ff:ff
9: eth4: <BROADCAST,MULTICAST,SLAVE,UP> mtu 1500 qdisc pfifo_fast  
master bond2 qlen 1000
     link/ether 00:1a:4b:ff:9c:ea brd ff:ff:ff:ff:ff:ff
10: eth5: <BROADCAST,MULTICAST,SLAVE,UP> mtu 1500 qdisc pfifo_fast  
master bond2 qlen 1000
     link/ether 00:1a:4b:ff:9c:ea brd ff:ff:ff:ff:ff:ff
11: eth6: <BROADCAST,MULTICAST> mtu 1500 qdisc noop qlen 1000
     link/ether 00:19:bb:3b:18:38 brd ff:ff:ff:ff:ff:ff
12: eth7: <BROADCAST,MULTICAST> mtu 1500 qdisc noop qlen 1000
     link/ether 00:19:bb:3b:18:3a brd ff:ff:ff:ff:ff:ff
ocsi2# grep ' 10.10.21.138' /etc/cluster/cluster.conf
ocsi2# grep '10.10.21.138' /etc/cluster/cluster.conf
       <ip monitor_link="1" address="10.10.21.138"/>



ocsi2# cat /etc/cluster/cluster.conf
<?xml version="1.0" encoding="UTF-8"?>
<cluster config_version="52" name="NGP-Cluster">
   <clusternodes>
     <clusternode votes="1" name="ocsi1-cluster">
       <fence>
         <method name="hardware">
           <device hostname="ocsi1-ilo" name="ilo"/>
         </method>
         <method name="last_resort">
           <device ipaddr="ocsi1-cluster" name="last_resort"/>
         </method>
       </fence>
     </clusternode>
     <clusternode votes="1" name="ocsi2-cluster">
       <fence>
         <method name="hardware">
           <device hostname="ocsi2-ilo" name="ilo"/>
         </method>
         <method name="last_resort">
           <device ipaddr="ocsi2-cluster" name="last_resort"/>
         </method>
       </fence>
     </clusternode>
     <clusternode votes="1" name="ocsi3-cluster">
       <fence>
         <method name="hardware">
           <device hostname="ocsi3-ilo" name="ilo"/>
         </method>
         <method name="last_resort">
           <device ipaddr="ocsi3-cluster" name="last_resort"/>
         </method>
       </fence>
     </clusternode>
   </clusternodes>
   <fencedevices>
     <fencedevice passwd="admin123" action="off" login="admin"  
name="ilo" agent="fence_ilo"/>
     <fencedevice name="last_resort" agent="fence_manual"/>
   </fencedevices>
   <rm log_facility="local3" log_level="4">
     <failoverdomains>
       <failoverdomain restricted="1" ordered="1" name="FirstDomain">
         <failoverdomainnode priority="0" name="ocsi2-cluster"/>
         <failoverdomainnode priority="1" name="ocsi1-cluster"/>
       </failoverdomain>
       <failoverdomain restricted="1" ordered="1" name="SecondDomain">
         <failoverdomainnode priority="0" name="ocsi3-cluster"/>
         <failoverdomainnode priority="1" name="ocsi1-cluster"/>
       </failoverdomain>
     </failoverdomains>
     <resources/>
     <service domain="SecondDomain" name="ppr2" autostart="1"  
recovery="relocate">
       <script name="ppr2" file="/usr/local/wsb/scripts/rhc_ppr2"/>
       <ip monitor_link="1" address="10.10.21.72"/>
       <fs device="/dev/sdd1" mountpoint="/usr/omg_ppr2" fstype="ext3"  
force_unmount="1" name="/usr/omg_ppr2"/>
       <ip monitor_link="1" address="10.10.21.141"/>
     </service>
     <service domain="FirstDomain" name="ppr1" autostart="1"  
recovery="relocate">
       <script name="ppr1" file="/usr/local/wsb/scripts/rhc_test1"/>
       <ip monitor_link="1" address="10.10.21.71"/>
       <fs device="/dev/sdd1" mountpoint="/usr/omg_ppr" fstype="ext3"  
force_unmount="1" name="/usr/omg_ppr"/>
       <ip monitor_link="1" address="10.10.21.138"/>
     </service>
   </rm>
   <quorumd votes="2" log_level="4" tko="10" interval="1"  
label="priquorum" log_facility="local3" device="/dev/sdc"/>
   <fence_daemon clean_start="1"/>
</cluster>




From marcos at digitaltecnologia.info  Wed Feb 13 14:19:47 2008
From: marcos at digitaltecnologia.info (Marcos Ferreira da Silva)
Date: Wed, 13 Feb 2008 09:19:47 -0500
Subject: [Linux-cluster] openais problem
Message-ID: <e1ce4452f7f349db9bcf48f1bd5b637e@Mail61.safesecureweb.com>

I have two node cluster.

I start node 1.
When I start node2 this join to cluster and appear this at log messages:

Feb 13 11:13:27 vserver1 openais[28108]: [TOTEM] FAILED TO RECEIVE 
Feb 13 11:13:27 vserver1 openais[28108]: [TOTEM] entering GATHER state from 6. 

[root at vserver2 ~]# clustat  
Member Status: Quorate

  Member Name                        ID   Status
  ------ ----                        ---- ------
  vserver1.teste.br                    1 Offline
  vserver2.teste.br                    2 Online, Local, rgmanager

The firewall is stopped.

[root at vserver2 ~]# cat /etc/hosts
# Do not remove the following line, or various programs
# that require network functionality will fail.
127.0.0.1               localhost.localdomain localhost
::1                     localhost6.localdomain6 localhost6
192.168.200.200         vserver1.teste.br teste1
192.168.200.201         vserver2.teste.br teste2

My cluster.conf:

<?xml version="1.0"?>
<cluster config_version="47" name="cluster1">
        <fence_daemon clean_start="0" post_fail_delay="0" post_join_delay="30"/>
        <fence_xvmd family="ipv4" key_file="/etc/cluster/fence_xvm.key" auth="none" hash="none"  />
        <clusternodes>
                <clusternode name="vserver1.teset.br" nodeid="1" votes="1">
                        <fence>
                                <method name="1">
                                        <device domain="admin" name="xvm"/>
                                </method>
                        </fence>
                </clusternode>
                <clusternode name="vserver2.teset.br" nodeid="2" votes="1">
                        <fence>
                                <method name="1">
                                        <device domain="intranetteste" name="xvm"/>
                                </method>
                        </fence>
                </clusternode>
        </clusternodes>
        <cman expected_votes="1" two_node="1"/>
        <fencedevices>
                <fencedevice agent="fence_xvm" key_file="/etc/cluster/fence_xvm.key" auth="none" hash="none" name="xvm"/>
        </fencedevices>
        <rm>
                <failoverdomains/>
                <resources/>
    <vm autostart="0" name="admin" path="/etc/xen"/>
    <vm autostart="0" name="intranetteste" path="/etc/xen"/>
        </rm>
        <totem token="21000"/>
</cluster>

------------------------------
Marcos Ferreira da Silva
Digital Tecnologia
Uberlandia-MG
(34) 9154-0150 / 3226-2534





From dist-list at LEXUM.UMontreal.CA  Wed Feb 13 15:12:06 2008
From: dist-list at LEXUM.UMontreal.CA (FM)
Date: Wed, 13 Feb 2008 10:12:06 -0500
Subject: [Linux-cluster] From piranha + system-config-cluster to Conga
Message-ID: <47B308C6.7@lexum.umontreal.ca>

Hello,
We are using RH 4.6  + GFS + cluster suite for several years now.

The new way to manage it with conga seems to be more easy then the old way.

Can we move from piranha + system-config-cluster easily ?




From rpeterso at redhat.com  Wed Feb 13 15:18:42 2008
From: rpeterso at redhat.com (Bob Peterson)
Date: Wed, 13 Feb 2008 09:18:42 -0600
Subject: [Linux-cluster] no version for "gfs2_unmount_lockproto"
In-Reply-To: <87bq6lp8nv.fsf@szonett.ki.iif.hu>
References: <878x1q59hl.fsf@szonett.ki.iif.hu>
	<1202841274.2701.15.camel@technetium.msp.redhat.com>
	<87skzxq2wm.fsf@szonett.ki.iif.hu>
	<1202856202.2701.43.camel@technetium.msp.redhat.com>
	<87bq6lp8nv.fsf@szonett.ki.iif.hu>
Message-ID: <1202915922.2701.69.camel@technetium.msp.redhat.com>

On Wed, 2008-02-13 at 09:23 +0100, Ferenc Wagner wrote:
> Thanks!  This patch indeed fixed the hang.  But of course not the
> mount:
> 
> Trying to join cluster "lock_dlm", "pilot:test"
> Joined cluster. Now mounting FS...
> GFS: fsid=pilot:test.4294967295: can't mount journal #4294967295
> GFS: fsid=pilot:test.4294967295: there are only 6 journals (0 - 5)

Hi Ferenc,

The "4294967295" is really a -1 which is a bad return code on the
mount.  So it should be a process of elimination to find out what
went wrong.  Several possibilities of what can be going wrong come
to mind:

1. Is it possible that your file system has a different cluster
   name ("pilot") from the the cluster name in your cluster.conf file?
2. Perhaps there is another gfs file system with the same name "test"
   already mounted?
3. Perhaps it can't find the locking protocol, lock_dlm (I hope)?
   Make sure lock_dlm shows up in lsmod.
4. Perhaps gfs can't find the rest of the cluster infrastructure?
   Check to make sure you did "service cman start" and have
   aisexec running on the system having the problem.  Also, check
   /var/log/messages for messages pertaining to cluster problems.

It sounds to me like we should have a better error message for
whatever went wrong.  Let's figure that out first and then we can
go about improving the error messages with a bugzilla if needed.
We have improved the error messages considerably from earlier.
I don't know what version of the gfs2-utils you have, but that
will contain the common mount helper (/sbin/mount.gfs2 is a hard
link to /sbin/mount.gfs) that does some of this error processing
when mounts fail.  So a newer version of the mount helper may be
better at pointing out what it doesn't like about your file system.

> # gfs_tool jindex /dev/mapper/gfs-test 
> gfs_tool: /dev/mapper/gfs-test is not a GFS file/filesystem
> 
> Scary.  What may be the problem?  The other node is using this
> volume...  Can even unmount/remount it.  Though in dmesg it says:

I wouldn't call it scary at all.  It sounds like gfs_tool may be
somewhat confused about the mount point.  Try using the mount
point that was used on the mount command, not the /dev/mapper
mount point and see if that helps.  I've actually been
working on making a better version of that code too--both kernel
and userland--that improves how gfs_tool finds mount points.
For RHEL5, they're bugzillas 431951 (gfs_tool) and 431952 (kernel)
respectively.  Those changes have not been shipped yet, due to
code freeze, but patches are in the bugzilla records.

As for all the kernel dmesgs you noted, that's perfectly normal.
When you mount a gfs file system, it runs through all the journals
regardless, checking if they are clean or need to be replayed,
so that's all those kernel messages mean.  They're not locked
(well, they are, but only for a couple seconds).

Regards,

Bob Peterson
Red Hat GFS




From adrian.bridgett at opsera.com  Wed Feb 13 15:36:27 2008
From: adrian.bridgett at opsera.com (Adrian Bridgett)
Date: Wed, 13 Feb 2008 15:36:27 +0000
Subject: [Linux-cluster] GFS2 loses data under kernel 2.6.24...
Message-ID: <1202916987.25809.6.camel@abridgett-pc>

I've just been doing some GFSv2 testing and saw this under stock 2.6.24.
In fact what we saw was that files under 4K were fine, those over 4K
were truncated to 0bytes on the other node.

I tried that patch - no change (after mkfs too).

I then tried 2.6.25-rc1.  Did mkfs, mount (okay), mount on the 2nd box
hung, then "ls" on the first box also hung.  I rebooted and tried again
(mkfs, etc) - this time it was all okay and the files were all fine on
the 2nd box.

All just FYI (but comments still appreciated ;-))

Thanks,

Adrian
-- 
Adrian Bridgett
Infrastructure and Network Architect


Mobile:  +44 (0) 777 377 8251     Tel :   +44 (0) 1189 294202 
Skype:   abridgett     Email:  adrian.bridgett at opsera.com
www.opsera.com

Opsera Limited | Unit 69 Suttons Business Park
Reading | Berkshire | RG6 1AZ | UK

This e-mail is confidential, intended only for the named recipient(s)
above and may contain information that is privileged and confidential.
If you receive this message in error, or are not the named recipient(s),
please notify the sender at the phone number above, do not copy this
message, do not disclose its contents to anyone, and delete this e-mail
message from your computer. Although Opsera routinely screens for
viruses, addressees should scan this e-mail and any attachments for
viruses. Opsera makes no representation or warranty as to the absence of
viruses in this e-mail or any attachments.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://listman.redhat.com/archives/linux-cluster/attachments/20080213/547e9a74/attachment.htm>

From wferi at niif.hu  Wed Feb 13 16:22:11 2008
From: wferi at niif.hu (Ferenc Wagner)
Date: Wed, 13 Feb 2008 17:22:11 +0100
Subject: [Linux-cluster] no version for "gfs2_unmount_lockproto"
In-Reply-To: <1202915922.2701.69.camel@technetium.msp.redhat.com> (Bob
	Peterson's message of "Wed, 13 Feb 2008 09:18:42 -0600")
References: <878x1q59hl.fsf@szonett.ki.iif.hu>
	<1202841274.2701.15.camel@technetium.msp.redhat.com>
	<87skzxq2wm.fsf@szonett.ki.iif.hu>
	<1202856202.2701.43.camel@technetium.msp.redhat.com>
	<87bq6lp8nv.fsf@szonett.ki.iif.hu>
	<1202915922.2701.69.camel@technetium.msp.redhat.com>
Message-ID: <87y79oomh8.fsf@szonett.ki.iif.hu>

Bob Peterson <rpeterso at redhat.com> writes:

> On Wed, 2008-02-13 at 09:23 +0100, Ferenc Wagner wrote:
>
>> Thanks!  This patch indeed fixed the hang.  But of course not the
>> mount:
>> 
>> Trying to join cluster "lock_dlm", "pilot:test"
>> Joined cluster. Now mounting FS...
>> GFS: fsid=pilot:test.4294967295: can't mount journal #4294967295
>> GFS: fsid=pilot:test.4294967295: there are only 6 journals (0 - 5)

Hi Bob,

Thanks for looking into this.  Find my answers below.

> The "4294967295" is really a -1 which is a bad return code on the
> mount.

Aha.  I expected something like that, though it looks more like a
journal number in the output.  Nevermind.

> So it should be a process of elimination to find out what went
> wrong.  Several possibilities of what can be going wrong come to
> mind:
>
> 1. Is it possible that your file system has a different cluster
>    name ("pilot") from the the cluster name in your cluster.conf file?

No: <cluster name="pilot" config_version="3"> in the config.

> 2. Perhaps there is another gfs file system with the same name "test"
>    already mounted?

No, there isn't.  I rebooted the node several times, and it does not
start the cluster infrastructure automatically.

> 3. Perhaps it can't find the locking protocol, lock_dlm (I hope)?
>    Make sure lock_dlm shows up in lsmod.

It does:

# lsmod | grep lock
lock_nolock             3456  0 
lock_dlm               21260  1 
gfs2                  333228  3 gfs,lock_nolock,lock_dlm
dlm                   108564  10 lock_dlm

> 4. Perhaps gfs can't find the rest of the cluster infrastructure?
>    Check to make sure you did "service cman start"

I did cman_tool join, which started aisexec.

>    and have aisexec running on the system having the problem.

Yes, it's still running.

>    Also, check /var/log/messages for messages pertaining to cluster
>    problems.

Starts with usual stuff, then:

openais[4504]: [MAIN ] AIS Executive Service RELEASE 'subrev 1358 version 0.80.3' 
  <lots of component loads>
openais[4504]: [TOTEM] Token Timeout (10000 ms) retransmit timeout (495 ms) 
  <lots of technical data>
openais[4504]: [TOTEM] entering GATHER state from 15.
openais[4504]: [SERV ] Initialising service handler 'openais extended virtual synchrony service' 
  <lots of similar lines>
openais[4504]: [CMAN ] CMAN 2.01.00 (built Feb 12 2008 22:08:05) started 
openais[4504]: [SYNC ] Not using a virtual synchrony filter. 
openais[4504]: [TOTEM] Creating commit token because I am the rep. 
  <some state transitions>
openais[4504]: [TOTEM] entering OPERATIONAL state. 
openais[4504]: [CMAN ] quorum regained, resuming activity 
openais[4504]: [CLM  ] got nodejoin message <IP of node1>
openais[4504]: [CLM  ] got nodejoin message <IP of node3>
openais[4504]: [CPG  ] got joinlist message from node 3 
ccsd[4500]: Initial status:: Quorate 

*Here* comes something possibly interesting, after fence_tool join:

fenced[4543]: fencing deferred to prior member

Though it doesn't look like node3 (which has the filesystem mounted)
would want to fence node1 (which has this message in its syslog).  Is
there a command available to find out the current fencing status or
history?

Then comes the usual error message:

kernel: dlm: Using TCP for communications
kernel: dlm: connecting to 3
kernel: dlm: got connection from 3
clvmd: Cluster LVM daemon started - connected to CMAN
kernel: Trying to join cluster "lock_dlm", "pilot:test"
kernel: Joined cluster. Now mounting FS...
kernel: GFS: fsid=pilot:test.4294967295: can't mount journal #4294967295
kernel: GFS: fsid=pilot:test.4294967295: there are only 6 journals (0 - 5)

> It sounds to me like we should have a better error message for
> whatever went wrong.  Let's figure that out first and then we can
> go about improving the error messages with a bugzilla if needed.

Sounds like a plan.  Good error messages always help a lot.

> We have improved the error messages considerably from earlier.
> I don't know what version of the gfs2-utils you have, but that
> will contain the common mount helper (/sbin/mount.gfs2 is a hard
> link to /sbin/mount.gfs) that does some of this error processing
> when mounts fail.  So a newer version of the mount helper may be
> better at pointing out what it doesn't like about your file system.

Maybe, but I'm using cluster-2.01.00, and have bad experience with CVS
versions, like dependence on bleeding edge kernel and device mapper.

>> # gfs_tool jindex /dev/mapper/gfs-test 
>> gfs_tool: /dev/mapper/gfs-test is not a GFS file/filesystem
>> 
>> Scary.  What may be the problem?  The other node is using this
>> volume...  Can even unmount/remount it.  Though in dmesg it says:
>
> I wouldn't call it scary at all.  It sounds like gfs_tool may be
> somewhat confused about the mount point.  Try using the mount
> point that was used on the mount command, not the /dev/mapper
> mount point and see if that helps.

Well, it helps on the node which has the filesystem mounted.  Of
course not on the other.  Is gfs_tool supposed to work on mounted
filesystems only?  Probably so.

> I've actually been working on making a better version of that code
> too--both kernel and userland--that improves how gfs_tool finds
> mount points.  For RHEL5, they're bugzillas 431951 (gfs_tool) and
> 431952 (kernel) respectively.  Those changes have not been shipped
> yet, due to code freeze, but patches are in the bugzilla records.

Do you think I should apply them?  It doesn't sound like they would
help with this problem.

> As for all the kernel dmesgs you noted, that's perfectly normal.
> When you mount a gfs file system, it runs through all the journals
> regardless, checking if they are clean or need to be replayed,
> so that's all those kernel messages mean.  They're not locked
> (well, they are, but only for a couple seconds).

Thanks for the clarification.  And what does that deferred fencing
mean?
-- 
Regards,
Feri.



From asim.husanovic at gmail.com  Wed Feb 13 16:35:58 2008
From: asim.husanovic at gmail.com (Asim Husanovic)
Date: Wed, 13 Feb 2008 17:35:58 +0100
Subject: [Linux-cluster] RHEL 5 standard installation
Message-ID: <3c1234d0802130835y1a2a788cwa0b05c2cb18f5c66@mail.gmail.com>

Hi

I install RHEL 5 standard installation

# uname -a
Linux yildiz.hermes.si 2.6.18-8.el5 #1 SMP Fri Jan 26 14:15:21 EST
2007 i686 i68   6 i386 GNU/Linux

with:

gfs-utils-0.1.11-1.el5
cman-2.0.60-1.el5
system-config-cluster-1.0.39-1.0
rgmanager-2.0.23-1
gnbd-1.1.5-1.el5
openais-0.80.2-1.el5
gfs2-utils-0.1.25-1.el5
lvm2-cluster-2.02.16-3.el5
kmod-gfs-0.1.16-5.2.6.18_8.el5
perl-Net-Telnet-3.03-5

# fdisk -l

Disk /dev/sda: 21.4 GB, 21474836480 bytes
255 heads, 63 sectors/track, 2610 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

   Device Boot      Start         End      Blocks   Id  System
/dev/sda1   *           1          13      104391   83  Linux
/dev/sda2              14        2610    20860402+  8e  Linux LVM

Disk /dev/sdb: 8589 MB, 8589934592 bytes
255 heads, 63 sectors/track, 1044 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

   Device Boot      Start         End      Blocks   Id  System
/dev/sdb1               1        1044     8385898+  8e  Linux LVM

Disk /dev/sdc: 8589 MB, 8589934592 bytes
255 heads, 63 sectors/track, 1044 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

   Device Boot      Start         End      Blocks   Id  System
/dev/sdc1               1        1044     8385898+  8e  Linux LVM

# vgdisplay -v /dev/VG_SHARE
    Using volume group(s) on command line
    Finding volume group "VG_SHARE"
  --- Volume group ---
  VG Name               VG_SHARE
  System ID
  Format                lvm2
  Metadata Areas        2
  Metadata Sequence No  3
  VG Access             read/write
  VG Status             resizable
  MAX LV                0
  Cur LV                1
  Open LV               0
  Max PV                0
  Cur PV                2
  Act PV                2
  VG Size               15.99 GB
  PE Size               4.00 MB
  Total PE              4094
  Alloc PE / Size       1002 / 3.91 GB
  Free  PE / Size       3092 / 12.08 GB
  VG UUID               MrlGGd-jg7O-OfZa-rxIm-9CUC-PyJ8-tgDITt

  --- Logical volume ---
  LV Name                /dev/VG_SHARE/LV_SHARE
  VG Name                VG_SHARE
  LV UUID                sjwBZq-8HL6-CnjK-iqGo-mkQk-vHvy-6Vkjbx
  LV Write Access        read/write
  LV Status              available
  # open                 0
  LV Size                3.91 GB
  Current LE             1002
  Segments               1
  Allocation             inherit
  Read ahead sectors     0
  Block device           253:2

  --- Physical volumes ---
  PV Name               /dev/sdb1
  PV UUID               rEgx77-JfwD-zazd-S1lZ-GaX0-STbY-532TD2
  PV Status             allocatable
  Total PE / Free PE    2047 / 1045

  PV Name               /dev/sdc1
  PV UUID               J1MUR6-chsV-sqqV-uAG5-jxBD-CJEv-ufooJs
  PV Status             allocatable
  Total PE / Free PE    2047 / 2047

# service cman start
Starting cluster:
   Loading modules... done
   Mounting configfs... done
   Starting ccsd... done
   Starting cman... failed

                                                           [FAILED]

# tail -f /var/log/messages
Feb 12 14:36:58 yildiz ccsd[2921]: Starting ccsd 2.0.60:
Feb 12 14:36:58 yildiz ccsd[2921]:  Built: Jan 23 2007 12:42:25
Feb 12 14:36:58 yildiz ccsd[2921]:  Copyright (C) Red Hat, Inc.  2004
All rights reserved.
Feb 12 14:36:58 yildiz ccsd[2921]: cluster.conf (cluster name =
RHEL5_CS, version = 1) found.
Feb 12 14:36:58 yildiz ccsd[2921]: Remote copy of cluster.conf is from
quorate node.
Feb 12 14:36:58 yildiz ccsd[2921]:  Local version # : 1
Feb 12 14:36:58 yildiz ccsd[2921]:  Remote version #: 1
Feb 12 14:36:58 yildiz ccsd[2921]: Remote copy of cluster.conf is from
quorate node.
Feb 12 14:36:58 yildiz ccsd[2921]:  Local version # : 1
Feb 12 14:36:58 yildiz ccsd[2921]:  Remote version #: 1
Feb 12 14:36:58 yildiz ccsd[2921]: Remote copy of cluster.conf is from
quorate node.
Feb 12 14:36:58 yildiz ccsd[2921]:  Local version # : 1
Feb 12 14:36:58 yildiz ccsd[2921]:  Remote version #: 1
Feb 12 14:36:58 yildiz ccsd[2921]: Remote copy of cluster.conf is from
quorate node.
Feb 12 14:36:58 yildiz ccsd[2921]:  Local version # : 1
Feb 12 14:36:58 yildiz ccsd[2921]:  Remote version #: 1
Feb 12 14:36:58 yildiz openais[2927]: [MAIN ] AIS Executive Service
RELEASE 'subrev 1324 version 0.80.2'
Feb 12 14:36:58 yildiz openais[2927]: [MAIN ] Copyright (C) 2002-2006
MontaVista Software, Inc and contributors.
Feb 12 14:36:58 yildiz openais[2927]: [MAIN ] Copyright (C) 2006 Red Hat, Inc.
Feb 12 14:36:58 yildiz openais[2927]: [MAIN ] AIS Executive Service:
started and ready to provide service.
Feb 12 14:36:58 yildiz openais[2927]: [MAIN ] Using default multicast
address of 239.192.76.169
Feb 12 14:36:58 yildiz openais[2927]: [MAIN ] openais component
openais_cpg loaded.
Feb 12 14:36:58 yildiz openais[2927]: [MAIN ] Registering service
handler 'openais cluster closed process group service v1.01'
Feb 12 14:36:58 yildiz openais[2927]: [MAIN ] openais component
openais_cfg loaded.
Feb 12 14:36:58 yildiz openais[2927]: [MAIN ] Registering service
handler 'openais configuration service'
Feb 12 14:36:58 yildiz openais[2927]: [MAIN ] openais component
openais_msg loaded.
Feb 12 14:36:58 yildiz openais[2927]: [MAIN ] Registering service
handler 'openais message service B.01.01'
Feb 12 14:36:58 yildiz openais[2927]: [MAIN ] openais component
openais_lck loaded.
Feb 12 14:36:58 yildiz openais[2927]: [MAIN ] Registering service
handler 'openais distributed locking service B.01.01'
Feb 12 14:36:58 yildiz openais[2927]: [MAIN ] openais component
openais_evt loaded.
Feb 12 14:36:58 yildiz openais[2927]: [MAIN ] Registering service
handler 'openais event service B.01.01'
Feb 12 14:36:58 yildiz openais[2927]: [MAIN ] openais component
openais_ckpt loaded.
Feb 12 14:36:58 yildiz openais[2927]: [MAIN ] Registering service
handler 'openais checkpoint service B.01.01'
Feb 12 14:36:58 yildiz openais[2927]: [MAIN ] openais component
openais_amf loaded.
Feb 12 14:36:58 yildiz openais[2927]: [MAIN ] Registering service
handler 'openais availability management framework B.01.01'
Feb 12 14:36:58 yildiz openais[2927]: [MAIN ] openais component
openais_clm loaded.
Feb 12 14:36:58 yildiz openais[2927]: [MAIN ] Registering service
handler 'openais cluster membership service B.01.01'
Feb 12 14:36:58 yildiz openais[2927]: [MAIN ] openais component
openais_evs loaded.
Feb 12 14:36:58 yildiz openais[2927]: [MAIN ] Registering service
handler 'openais extended virtual synchrony service'
Feb 12 14:36:58 yildiz openais[2927]: [MAIN ] openais component
openais_cman loaded.
Feb 12 14:36:58 yildiz openais[2927]: [MAIN ] Registering service
handler 'openais CMAN membership service 2.01'
Feb 12 14:36:58 yildiz openais[2927]: [TOTEM] Token Timeout (10000 ms)
retransmit timeout (495 ms)
Feb 12 14:36:58 yildiz openais[2927]: [TOTEM] token hold (386 ms)
retransmits before loss (20 retrans)
Feb 12 14:36:58 yildiz openais[2927]: [TOTEM] join (60 ms) send_join
(0 ms) consensus (4800 ms) merge (200 ms)
Feb 12 14:36:58 yildiz openais[2927]: [TOTEM] downcheck (1000 ms) fail
to recv const (50 msgs)
Feb 12 14:36:58 yildiz openais[2927]: [TOTEM] seqno unchanged const
(30 rotations) Maximum network MTU 1500
Feb 12 14:36:58 yildiz openais[2927]: [TOTEM] window size per rotation
(50 messages) maximum messages per rotation (17 messages)
Feb 12 14:36:58 yildiz openais[2927]: [TOTEM] send threads (0 threads)
Feb 12 14:36:58 yildiz openais[2927]: [TOTEM] RRP token expired timeout (495 ms)
Feb 12 14:36:58 yildiz openais[2927]: [TOTEM] RRP token problem
counter (2000 ms)
Feb 12 14:36:58 yildiz openais[2927]: [TOTEM] RRP threshold (10 problem count)
Feb 12 14:36:58 yildiz openais[2927]: [TOTEM] RRP mode set to none.
Feb 12 14:36:58 yildiz openais[2927]: [TOTEM] heartbeat_failures_allowed (0)
Feb 12 14:36:58 yildiz openais[2927]: [TOTEM] max_network_delay (50 ms)
Feb 12 14:36:58 yildiz openais[2927]: [TOTEM] HeartBeat is Disabled.
To enable set heartbeat_failures_allowed > 0
Feb 12 14:36:58 yildiz openais[2927]: [TOTEM] Receive multicast socket
recv buffer size (219136 bytes).
Feb 12 14:36:58 yildiz openais[2927]: [TOTEM] Transmit multicast
socket send buffer size (219136 bytes).
Feb 12 14:36:59 yildiz openais[2927]: [TOTEM] The network interface
[172.16.40.11] is now up.
Feb 12 14:36:59 yildiz openais[2927]: [TOTEM] Created or loaded
sequence id 0.172.16.40.11 for this ring.
Feb 12 14:36:59 yildiz openais[2927]: [TOTEM] entering GATHER state from 15.
Feb 12 14:36:59 yildiz openais[2927]: [SERV ] Initialising service
handler 'openais extended virtual synchrony service'
Feb 12 14:36:59 yildiz openais[2927]: [SERV ] Initialising service
handler 'openais cluster membership service B.01.01'
Feb 12 14:36:59 yildiz openais[2927]: [SERV ] Initialising service
handler 'openais availability management framework B.01.01'
Feb 12 14:36:59 yildiz openais[2927]: [SERV ] Initialising service
handler 'openais checkpoint service B.01.01'
Feb 12 14:36:59 yildiz openais[2927]: [SERV ] Initialising service
handler 'openais event service B.01.01'
Feb 12 14:36:59 yildiz openais[2927]: [SERV ] Initialising service
handler 'openais distributed locking service B.01.01'
Feb 12 14:36:59 yildiz openais[2927]: [SERV ] Initialising service
handler 'openais message service B.01.01'
Feb 12 14:36:59 yildiz openais[2927]: [SERV ] Initialising service
handler 'openais configuration service'
Feb 12 14:36:59 yildiz openais[2927]: [SERV ] Initialising service
handler 'openais cluster closed process group service v1.01'
Feb 12 14:36:59 yildiz openais[2927]: [SERV ] Initialising service
handler 'openais CMAN membership service 2.01'
Feb 12 14:36:59 yildiz openais[2927]: [CMAN ] CMAN 2.0.60 (built Jan
23 2007 12:42:29) started
Feb 12 14:36:59 yildiz openais[2927]: [SYNC ] Not using a virtual
synchrony filter.
Feb 12 14:36:59 yildiz openais[2927]: [TOTEM] Creating commit token
because I am the rep.
Feb 12 14:36:59 yildiz openais[2927]: [TOTEM] Saving state aru 0 high
seq received 0
Feb 12 14:36:59 yildiz openais[2927]: [TOTEM] entering COMMIT state.
Feb 12 14:36:59 yildiz openais[2927]: [TOTEM] entering RECOVERY state.
Feb 12 14:36:59 yildiz openais[2927]: [TOTEM] position [0] member 172.16.40.11:
Feb 12 14:36:59 yildiz openais[2927]: [TOTEM] previous ring seq 0 rep
172.16.40.11
Feb 12 14:36:59 yildiz openais[2927]: [TOTEM] aru 0 high delivered 0
received flag 0
Feb 12 14:36:59 yildiz openais[2927]: [TOTEM] Did not need to
originate any messages in recovery.
Feb 12 14:36:59 yildiz openais[2927]: [TOTEM] Couldn't store new ring
id 4 to stable storage (Permission denied)
Feb 12 14:37:00 yildiz ccsd[2921]: Initial status:: Quorate
Feb 12 14:37:01 yildiz setroubleshoot:      SELinux is preventing the
/usr/sbin/aisexec from using potentially mislabeled files (tmp).
For complete SELinux messages. run sealert -l
a83caf42-8a8c-49d5-afec-81b67ee2aa68

# cat /etc/cluster/cluster.conf
<?xml version="1.0"?>
<cluster alias="RHEL5_CS" config_version="1" name="RHEL5_CS">
  <fence_daemon post_fail_delay="0" post_join_delay="3"/>
  <clusternodes>
    <clusternode name="node1.localdomain" votes="1" nodeid="1">
      <com_info>
        <syslog name="node1.localdomain"/>
          <sharedd name="/dev/VG_SHARE/LV_SHARE"/>
      </com_info>
      <fence>
        <method name="1">
          <device name="ManualFence" nodename="node1.localdomain"/>
        </method>
      </fence>
    </clusternode>
    <clusternode name="node2.localdomain" votes="1" nodeid="2">
      <com_info>
        <syslog name="node2.localdomain"/>
          <sharedd name="/dev/VG_SHARE/LV_SHARE"/>
      </com_info>
      <fence>
        <method name="1">
          <device name="ManualFence" nodename="node2.localdomain"/>
        </method>
      </fence>
    </clusternode>
  </clusternodes>
  <cman expected_votes="1" two_node="1"/>
  <fencedevices>
    <fencedevice agent="fence_manual" name="ManualFence"/>
  </fencedevices>
  <rm>
    <failoverdomains/>
    <resources/>
  </rm>
</cluster>


If i disable SElinux working. But...



From sdake at redhat.com  Wed Feb 13 16:58:09 2008
From: sdake at redhat.com (Steven Dake)
Date: Wed, 13 Feb 2008 09:58:09 -0700
Subject: [Linux-cluster] openais problem
In-Reply-To: <e1ce4452f7f349db9bcf48f1bd5b637e@Mail61.safesecureweb.com>
References: <e1ce4452f7f349db9bcf48f1bd5b637e@Mail61.safesecureweb.com>
Message-ID: <1202921890.3653.4.camel@balance>

Which openais package version are you using?

If it is the latest, this indicates a failure in multicast on your
switch hardware.  What kind of switch hardware are you using?  You might
try using a dumb device switch and see if that fixes the problem.  You
could also try overriding the MTU of totem via flags to the
configuration file.  It is possible your switch will not pass fragmented
multicast packets which occur rarely after a configuration change.  I
have seen switches that are defective which wont pass fragmented
multicast packets, especially some early generation ATCA switch hardware
or softswitches.

vserver = virtual server?  What type...

If you have Cisco hardware review:

http://www.openais.org/doku.php?id=faq:cisco_switches

On Wed, 2008-02-13 at 09:19 -0500, Marcos Ferreira da Silva wrote:
> I have two node cluster.
> 
> I start node 1.
> When I start node2 this join to cluster and appear this at log messages:
> 
> Feb 13 11:13:27 vserver1 openais[28108]: [TOTEM] FAILED TO RECEIVE 
> Feb 13 11:13:27 vserver1 openais[28108]: [TOTEM] entering GATHER state from 6. 
> 
> [root at vserver2 ~]# clustat  
> Member Status: Quorate
> 
>   Member Name                        ID   Status
>   ------ ----                        ---- ------
>   vserver1.teste.br                    1 Offline
>   vserver2.teste.br                    2 Online, Local, rgmanager
> 
> The firewall is stopped.
> 
> [root at vserver2 ~]# cat /etc/hosts
> # Do not remove the following line, or various programs
> # that require network functionality will fail.
> 127.0.0.1               localhost.localdomain localhost
> ::1                     localhost6.localdomain6 localhost6
> 192.168.200.200         vserver1.teste.br teste1
> 192.168.200.201         vserver2.teste.br teste2
> 
> My cluster.conf:
> 
> <?xml version="1.0"?>
> <cluster config_version="47" name="cluster1">
>         <fence_daemon clean_start="0" post_fail_delay="0" post_join_delay="30"/>
>         <fence_xvmd family="ipv4" key_file="/etc/cluster/fence_xvm.key" auth="none" hash="none"  />
>         <clusternodes>
>                 <clusternode name="vserver1.teset.br" nodeid="1" votes="1">
>                         <fence>
>                                 <method name="1">
>                                         <device domain="admin" name="xvm"/>
>                                 </method>
>                         </fence>
>                 </clusternode>
>                 <clusternode name="vserver2.teset.br" nodeid="2" votes="1">
>                         <fence>
>                                 <method name="1">
>                                         <device domain="intranetteste" name="xvm"/>
>                                 </method>
>                         </fence>
>                 </clusternode>
>         </clusternodes>
>         <cman expected_votes="1" two_node="1"/>
>         <fencedevices>
>                 <fencedevice agent="fence_xvm" key_file="/etc/cluster/fence_xvm.key" auth="none" hash="none" name="xvm"/>
>         </fencedevices>
>         <rm>
>                 <failoverdomains/>
>                 <resources/>
>     <vm autostart="0" name="admin" path="/etc/xen"/>
>     <vm autostart="0" name="intranetteste" path="/etc/xen"/>
>         </rm>
>         <totem token="21000"/>
> </cluster>
> 
> ------------------------------
> Marcos Ferreira da Silva
> Digital Tecnologia
> Uberlandia-MG
> (34) 9154-0150 / 3226-2534
> 
> 
> 
> --
> Linux-cluster mailing list
> Linux-cluster at redhat.com
> https://www.redhat.com/mailman/listinfo/linux-cluster



From lhh at redhat.com  Wed Feb 13 18:30:16 2008
From: lhh at redhat.com (Lon Hohberger)
Date: Wed, 13 Feb 2008 13:30:16 -0500
Subject: [Linux-cluster] Netmask bit set to 32 in service ip
In-Reply-To: <20080213123347.ad6mnbk1coo44kwo@easymail-app.hol.gr>
References: <20080213123347.ad6mnbk1coo44kwo@easymail-app.hol.gr>
Message-ID: <1202927416.6841.8.camel@localhost.localdomain>


On Wed, 2008-02-13 at 12:33 +0200, Pavlos Parissis wrote:
> Hi,
> 
> I have a question which may sounds stupid.
> why the netmask for the service ip is set to 32 while the IP belongs  
> to a network with different netmask?
> 
> Regards,
> Pavlos
> 
> 
> : bond0: <BROADCAST,MULTICAST,MASTER,UP> mtu 1500 qdisc noqueue
>      link/ether 00:19:bb:3b:6c:b1 brd ff:ff:ff:ff:ff:ff
>      inet 10.10.21.133/26 brd 10.10.21.191 scope global bond0
>      inet 10.10.21.138/32 scope global bond0 <<================= service ip
> 3: bond1: <BROADCAST,MULTICAST,MASTER,UP> mtu 1500 qdisc noqueue
>      link/ether 00:1a:4b:ff:9c:e8 brd ff:ff:ff:ff:ff:ff
>      inet 10.10.21.69/27 brd 10.10.21.95 scope global bond1
>      inet 10.10.21.71/32 scope global bond1 <<================= service ip
> 4: bond2: <BROADCAST,MULTICAST,MASTER,UP> mtu 1500 qdisc noqueue
>      link/ether 00:1a:4b:ff:9c:ea brd ff:ff:ff:ff:ff:ff
>      inet 10.10.21.228/27 brd 10.10.21.255 scope global bond2
> 5: eth0: <BROADCAST,MULTICAST,SLAVE,UP> mtu 1500 qdisc pfifo_fast  
> master bond0 qlen 1000
>      link/ether 00:19:bb:3b:6c:b1 brd ff:ff:ff:ff:ff:ff
> 6: eth1: <BROADCAST,MULTICAST,SLAVE,UP> mtu 1500 qdisc pfifo_fast  
> master bond0 qlen 1000
>      link/ether 00:19:bb:3b:6c:b1 brd ff:ff:ff:ff:ff:ff
> 7: eth2: <BROADCAST,MULTICAST,SLAVE,UP> mtu 1500 qdisc pfifo_fast  
> master bond1 qlen 1000
>      link/ether 00:1a:4b:ff:9c:e8 brd ff:ff:ff:ff:ff:ff
> 8: eth3: <BROADCAST,MULTICAST,SLAVE,UP> mtu 1500 qdisc pfifo_fast  
> master bond1 qlen 1000
>      link/ether 00:1a:4b:ff:9c:e8 brd ff:ff:ff:ff:ff:ff
> 9: eth4: <BROADCAST,MULTICAST,SLAVE,UP> mtu 1500 qdisc pfifo_fast  
> master bond2 qlen 1000
>      link/ether 00:1a:4b:ff:9c:ea brd ff:ff:ff:ff:ff:ff
> 10: eth5: <BROADCAST,MULTICAST,SLAVE,UP> mtu 1500 qdisc pfifo_fast  
> master bond2 qlen 1000
>      link/ether 00:1a:4b:ff:9c:ea brd ff:ff:ff:ff:ff:ff
> 11: eth6: <BROADCAST,MULTICAST> mtu 1500 qdisc noop qlen 1000
>      link/ether 00:19:bb:3b:18:38 brd ff:ff:ff:ff:ff:ff
> 12: eth7: <BROADCAST,MULTICAST> mtu 1500 qdisc noop qlen 1000
>      link/ether 00:19:bb:3b:18:3a brd ff:ff:ff:ff:ff:ff
> ocsi2# grep ' 10.10.21.138' /etc/cluster/cluster.conf
> ocsi2# grep '10.10.21.138' /etc/cluster/cluster.conf
>        <ip monitor_link="1" address="10.10.21.138"/>

Strange that the netmask is wrong.  You can force it to the correct one
by doing:

    <ip monitor_link="1" address="10.10.21.138/26"/>

Or, you could apply the attached patch:

    cd /usr/share/cluster; patch -p0 < /tmp/fs.sh-netmask.patch

... and see if it helps you.  If it doesn't, you can revert the patch:

    cd /usr/share/cluster; patch -Rp0 < /tmp/fs.sh-netmask.patch

-- Lon
-------------- next part --------------
A non-text attachment was scrubbed...
Name: ip.sh-netmask.patch
Type: text/x-patch
Size: 518 bytes
Desc: not available
URL: <http://listman.redhat.com/archives/linux-cluster/attachments/20080213/725ffebc/attachment.bin>

From lhh at redhat.com  Wed Feb 13 18:37:53 2008
From: lhh at redhat.com (Lon Hohberger)
Date: Wed, 13 Feb 2008 13:37:53 -0500
Subject: [Linux-cluster] From piranha + system-config-cluster to Conga
In-Reply-To: <47B308C6.7@lexum.umontreal.ca>
References: <47B308C6.7@lexum.umontreal.ca>
Message-ID: <1202927873.6841.9.camel@localhost.localdomain>


On Wed, 2008-02-13 at 10:12 -0500, FM wrote:
> Hello,
> We are using RH 4.6  + GFS + cluster suite for several years now.
> 
> The new way to manage it with conga seems to be more easy then the old way.
> 
> Can we move from piranha

Conga doesn't manage piranha. 

>  + system-config-cluster easily ?

...for the rest, Conga is pretty easy to move to. :)

-- Lon



From p_pavlos at freemail.gr  Thu Feb 14 00:59:17 2008
From: p_pavlos at freemail.gr (Pavlos Parissis)
Date: Thu, 14 Feb 2008 02:59:17 +0200
Subject: [Linux-cluster] Netmask bit set to 32 in service ip
In-Reply-To: <1202927416.6841.8.camel@localhost.localdomain>
References: <20080213123347.ad6mnbk1coo44kwo@easymail-app.hol.gr>
	<1202927416.6841.8.camel@localhost.localdomain>
Message-ID: <20080214025917.ojocuj0c4gco0ogw@easymail-app.hol.gr>

Quoting Lon Hohberger <lhh at redhat.com>:

>
> On Wed, 2008-02-13 at 12:33 +0200, Pavlos Parissis wrote:
>> Hi,
>>
>> I have a question which may sounds stupid.
>> why the netmask for the service ip is set to 32 while the IP belongs
>> to a network with different netmask?
>>
...snip...
> Strange that the netmask is wrong.  You can force it to the correct one
> by doing:
>
>     <ip monitor_link="1" address="10.10.21.138/26"/>
The above worked.

> Or, you could apply the attached patch:
>
>     cd /usr/share/cluster; patch -p0 < /tmp/fs.sh-netmask.patch
>
> ... and see if it helps you.  If it doesn't, you can revert the patch:
>
>     cd /usr/share/cluster; patch -Rp0 < /tmp/fs.sh-netmask.patch
>
> -- Lon
>

but not this one

ocsi2# pwd
/usr/share/cluster
ocsi2# cat /tmp/ip.sh-netmask.patch
Index: ip.sh
===================================================================
RCS file: /cvs/cluster/cluster/rgmanager/src/resources/ip.sh,v
retrieving revision 1.5.2.17
diff -u -r1.5.2.17 ip.sh
--- ip.sh       22 Mar 2007 23:15:59 -0000      1.5.2.17
+++ ip.sh       13 Feb 2008 18:28:12 -0000
@@ -692,6 +692,10 @@
                         if [ $? -ne 0 ]; then
                                 continue
                         fi
+
+                       if [ "${addr/\/*/}" = "${addr}" ]; then
+                               addr="$addr/$maskbits"
+                       fi
                         ocf_log info "Adding IPv4 address $addr to $dev"
                 fi
                 if [ "$1" = "del" ]; then
ocsi2# patch -p0 <  /tmp/ip.sh-netmask.patch
patching file ip.sh
ocsi2# clusvcadm -R ppr1
Member ocsi2-cluster trying to restart ppr1...success
ocsi2# ip add sh
1: lo: <LOOPBACK,UP> mtu 16436 qdisc noqueue
     link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
     inet 127.0.0.1/8 brd 127.255.255.255 scope host lo
2: bond0: <BROADCAST,MULTICAST,MASTER,UP> mtu 1500 qdisc noqueue
     link/ether 00:19:bb:3b:6c:b1 brd ff:ff:ff:ff:ff:ff
     inet 10.10.21.133/26 brd 10.10.21.191 scope global bond0
     inet 10.10.21.138/32 scope global bond0
3: bond1: <BROADCAST,MULTICAST,MASTER,UP> mtu 1500 qdisc noqueue
     link/ether 00:1a:4b:ff:9c:e8 brd ff:ff:ff:ff:ff:ff
     inet 10.10.21.69/27 brd 10.10.21.95 scope global bond1
     inet 10.10.21.71/32 scope global bond1
4: bond2: <BROADCAST,MULTICAST,MASTER,UP> mtu 1500 qdisc noqueue
     link/ether 00:1a:4b:ff:9c:ea brd ff:ff:ff:ff:ff:ff
     inet 10.10.21.228/27 brd 10.10.21.255 scope global bond2
5: eth0: <BROADCAST,MULTICAST,SLAVE,UP> mtu 1500 qdisc pfifo_fast  
master bond0 qlen 1000
     link/ether 00:19:bb:3b:6c:b1 brd ff:ff:ff:ff:ff:ff
6: eth1: <BROADCAST,MULTICAST,SLAVE,UP> mtu 1500 qdisc pfifo_fast  
master bond0 qlen 1000
     link/ether 00:19:bb:3b:6c:b1 brd ff:ff:ff:ff:ff:ff
7: eth2: <BROADCAST,MULTICAST,SLAVE,UP> mtu 1500 qdisc pfifo_fast  
master bond1 qlen 1000
     link/ether 00:1a:4b:ff:9c:e8 brd ff:ff:ff:ff:ff:ff
8: eth3: <BROADCAST,MULTICAST,SLAVE,UP> mtu 1500 qdisc pfifo_fast  
master bond1 qlen 1000
     link/ether 00:1a:4b:ff:9c:e8 brd ff:ff:ff:ff:ff:ff
9: eth4: <BROADCAST,MULTICAST,SLAVE,UP> mtu 1500 qdisc pfifo_fast  
master bond2 qlen 1000
     link/ether 00:1a:4b:ff:9c:ea brd ff:ff:ff:ff:ff:ff
10: eth5: <BROADCAST,MULTICAST,SLAVE,UP> mtu 1500 qdisc pfifo_fast  
master bond2 qlen 1000
     link/ether 00:1a:4b:ff:9c:ea brd ff:ff:ff:ff:ff:ff
11: eth6: <BROADCAST,MULTICAST> mtu 1500 qdisc noop qlen 1000
     link/ether 00:19:bb:3b:18:38 brd ff:ff:ff:ff:ff:ff
12: eth7: <BROADCAST,MULTICAST> mtu 1500 qdisc noop qlen 1000
     link/ether 00:19:bb:3b:18:3a brd ff:ff:ff:ff:ff:ff
ocsi2# uname -a
Linux ocsi2 2.6.9-42.ELsmp #1 SMP Wed Jul 12 23:32:02 EDT 2006 x86_64  
x86_64 x86_64 GNU/Linux
ocsi2# cat /etc/redhat-release
Red Hat Enterprise Linux AS release 4 (Nahant Update 4)


I really wonder how an application can use that IP as a source IP.

Regards,
Pavlos





From schlegel at riege.com  Thu Feb 14 08:15:16 2008
From: schlegel at riege.com (Gunther Schlegel)
Date: Thu, 14 Feb 2008 09:15:16 +0100
Subject: [Linux-cluster] Xen DomU as Cluster service?
Message-ID: <47B3F894.6030801@riege.com>

Hello,

In short: Is it a good idea to run Xen DomUs as a cluster service or is 
there an easier way to do it?

Background:

- I am setting up a "xen cluster", that is a couple of xen Dom0 machines 
that should run a couple of more DomU machines.
- FC shared storage et at is in place. However exporting a LUN per DomU 
is not a preferred option.
- The DomUs should be always up.
-* If a Dom0 goes is shut down the DomUs need to be live migrated to 
another Dom0 host during Dom0 shutdown.
-* If a Dom0 dies unexpectedly the DomUs need to be restarted on 
antother hot.

Conclusion:
- I need clustered LVM to avoid individual LUNs on SAN level -> OK, 
shoudl be feasible, but brings in all the RedHat Cluster stuff.

Problems / open Questions:
- xen supports life migration on system shutdown, but only to a specific 
  host. As I will have a couple of hosts it is more desireable to 
distribute the DomUs among the other Dom0 hosts instead of migrating 
them all to the same Dom0 host. Has anyone done that before? Is it a 
good option? Are there other options?

- I suppose I need the full cluster stuff anyways to deal with a crashed 
Dom0, this implies to define a cluster service for each DomU?

Besides: Why not establish a RHEL Xen mailinglist?

best regards, Gunther

-- 
Gunther Schlegel
Manager IT Infrastructure


.............................................................
Riege Software International GmbH  Fon: +49 (2159) 9148 0
Mollsfeld 10                       Fax: +49 (2159) 9148 11
40670 Meerbusch                    Web: www.riege.com
Germany                            E-Mail: schlegel at riege.com
---                                ---
Handelsregister:                   Managing Directors:
Amtsgericht Neuss HRB-NR 4207      Johannes Riege &
USt-ID-Nr.: DE120585842            Gabriele Riege
.............................................................
           YOU CARE FOR FREIGHT, WE CARE FOR YOU          



-------------- next part --------------
A non-text attachment was scrubbed...
Name: schlegel.vcf
Type: text/x-vcard
Size: 346 bytes
Desc: not available
URL: <http://listman.redhat.com/archives/linux-cluster/attachments/20080214/ebf56ab8/attachment.vcf>

From wferi at niif.hu  Thu Feb 14 10:54:03 2008
From: wferi at niif.hu (Ferenc Wagner)
Date: Thu, 14 Feb 2008 11:54:03 +0100
Subject: [Linux-cluster] no version for "gfs2_unmount_lockproto"
In-Reply-To: <47B31A32.8030701@netapp.com> (Wendy Cheng's message of "Wed, 13
	Feb 2008 11:26:26 -0500")
References: <878x1q59hl.fsf@szonett.ki.iif.hu>
	<1202841274.2701.15.camel@technetium.msp.redhat.com>
	<87skzxq2wm.fsf@szonett.ki.iif.hu>
	<1202856202.2701.43.camel@technetium.msp.redhat.com>
	<87bq6lp8nv.fsf@szonett.ki.iif.hu>
	<1202915922.2701.69.camel@technetium.msp.redhat.com>
	<47B31A32.8030701@netapp.com>
Message-ID: <874pcb95bo.fsf@tac.ki.iif.hu>

Wendy Cheng <wcheng at netapp.com> writes:

> Bob Peterson wrote:
>
>>> # gfs_tool jindex /dev/mapper/gfs-test gfs_tool:
>>> /dev/mapper/gfs-test is not a GFS file/filesystem
>>
>> It sounds like gfs_tool may be somewhat confused about the mount
>> point.  Try using the mount point that was used on the mount
>> command, not the /dev/mapper mount point and see if that helps.
>
> If I remember this right, gfs_tool only recognizes *filesystem* mount
> point, not device file (/dev/mapper/..something... is a device file,
> not a mount point). So you may mount the GFS filesystem as:
>
> shell> mount /dev/mapper/something      /gfs-data
> shell> gfs_tool <flag> /gfs-data <op>

Yes, I've already figured gfs_tool can handle mounted filesystems
only.  I've also figured it's clearly written in the manual, which I
didn't check even after reading the error message.  Maybe my
terminology is wrong, but I'd say /dev/mapper/gfs-test IS a GFS
filesystem, but not the mount point of one.  Well, of anything.
Perhaps a better error message would be
"/dev/mapper/gfs-test is not a mount point"
or maybe
"/dev/mapper/gfs-test in not on a GFS filesystem"
(for Bob, speaking of better error messages. :)

----

As a side note, there's still something strange here (at least for me,
not knowing the LVM on-disk format), which is probably unrelated to my
mount problem, as it's (obviously, living on SAN) the same on the
working node.

# pvs
  PV                                            VG   Fmt  Attr PSize   PFree  
  /dev/mapper/360060160861611005c574c2126c7db11 gfs  lvm2 a-   200.00G 155.00G

# lvs
  LV   VG   Attr   LSize    Origin Snap%  Move Log Copy% 
  test gfs  -wi-a-   40.00G                              

# dmsetup table gfs-test
0 83886080 linear 254:3 384

That is, the test LV starts at sector number 384.  However, dumping
the start of the PV gives the output below, which has a gfs signatures
at sector 9, 11, 13, 16 and 18, then lots of zeroes, and finally the
file system name in sector 512.  It other words, the first 128 sectors
of the LV are pure zeros.  I don't mind that the least, but what are
thos gfs strings at the start of the PV?  Maybe some stray data from
previous mkfs attempts?

# dd if=/dev/mapper/360060160861611005c574c2126c7db11 bs=512 count=513 2>/dev/null | od -Ad -c
0000000  \0  \0  \0  \0  \0  \0  \0  \0  \0  \0  \0  \0  \0  \0  \0  \0
*
0000512   L   A   B   E   L   O   N   E 001  \0  \0  \0  \0  \0  \0  \0
0000528 223   3 025 220      \0  \0  \0   L   V   M   2       0   0   1
0000544   l   O   d   B   3   C   u   T   w   M   H   s   3   f   x   N
0000560   9   J   U   o   L   y   R   n   C   J   v   E   Q   l   D   G
0000576  \0  \0 375 377   1  \0  \0  \0  \0  \0 003  \0  \0  \0  \0  \0
0000592  \0  \0  \0  \0  \0  \0  \0  \0  \0  \0  \0  \0  \0  \0  \0  \0
0000608  \0  \0  \0  \0  \0  \0  \0  \0  \0 020  \0  \0  \0  \0  \0  \0
0000624  \0 360 002  \0  \0  \0  \0  \0  \0  \0  \0  \0  \0  \0  \0  \0
0000640  \0  \0  \0  \0  \0  \0  \0  \0  \0  \0  \0  \0  \0  \0  \0  \0
*
0004096  \b 353 330 235       L   V   M   2       x   [   5   A   %   r
0004112   0   N   *   > 001  \0  \0  \0  \0 020  \0  \0  \0  \0  \0  \0
0004128  \0 360 002  \0  \0  \0  \0  \0  \0 024  \0  \0  \0  \0  \0  \0
0004144   ( 004  \0  \0  \0  \0  \0  \0 255 365   W 035  \0  \0  \0  \0
0004160  \0  \0  \0  \0  \0  \0  \0  \0  \0  \0  \0  \0  \0  \0  \0  \0
*
0004608   g   f   s       {  \n   i   d       =       "   F   3   7   z
0004624   e   3   -   g   q   r   1   -   G   3   6   H   -   s   f   P
0004640   A   -   W   c   A   W   -   m   U   i   B   -   0   4   O   G
0004656   k   V   "  \n   s   e   q   n   o       =       2  \n   s   t
0004672   a   t   u   s       =       [   "   R   E   S   I   Z   E   A
0004688   B   L   E   "   ,       "   R   E   A   D   "   ,       "   W
0004704   R   I   T   E   "   ,       "   C   L   U   S   T   E   R   E
0004720   D   "   ]  \n   e   x   t   e   n   t   _   s   i   z   e    
0004736   =       8   1   9   2  \n   m   a   x   _   l   v       =    
0004752   0  \n   m   a   x   _   p   v       =       0  \n  \n   p   h
0004768   y   s   i   c   a   l   _   v   o   l   u   m   e   s       {
0004784  \n  \n   p   v   0       {  \n   i   d       =       "   l   O
0004800   d   B   3   C   -   u   T   w   M   -   H   s   3   f   -   x
0004816   N   9   J   -   U   o   L   y   -   R   n   C   J   -   v   E
0004832   Q   l   D   G   "  \n   d   e   v   i   c   e       =       "
0004848   /   d   e   v   /   d   m   -   3   "  \n  \n   s   t   a   t
0004864   u   s       =       [   "   A   L   L   O   C   A   T   A   B
0004880   L   E   "   ]  \n   p   e   _   s   t   a   r   t       =    
0004896   3   8   4  \n   p   e   _   c   o   u   n   t       =       5
0004912   1   1   9   9  \n   }  \n   }  \n  \n   }  \n   #       G   e
0004928   n   e   r   a   t   e   d       b   y       L   V   M   2   :
0004944       F   r   i       M   a   r           2       0   3   :   2
0004960   3   :   4   6       2   0   0   7  \n  \n   c   o   n   t   e
0004976   n   t   s       =       "   T   e   x   t       F   o   r   m
0004992   a   t       V   o   l   u   m   e       G   r   o   u   p   "
0005008  \n   v   e   r   s   i   o   n       =       1  \n  \n   d   e
0005024   s   c   r   i   p   t   i   o   n       =       "   "  \n  \n
0005040   c   r   e   a   t   i   o   n   _   h   o   s   t       =    
0005056   "   r   s   2   1   .   l   v   s   .   i   i   f   .   h   u
0005072   "  \t   #       L   i   n   u   x       r   s   2   1   .   l
0005088   v   s   .   i   i   f   .   h   u       2   .   6   .   1   8
0005104   -   4   -   6   8   6       #   1       S   M   P       W   e
0005120   d       F   e   b       2   1       1   6   :   0   6   :   5
0005136   4       U   T   C       2   0   0   7       i   6   8   6  \n
0005152   c   r   e   a   t   i   o   n   _   t   i   m   e       =    
0005168   1   1   7   2   8   0   2   2   2   6  \t   #       F   r   i
0005184       M   a   r           2       0   3   :   2   3   :   4   6
0005200       2   0   0   7  \n  \n  \0  \0  \0  \0  \0  \0  \0  \0  \0
0005216  \0  \0  \0  \0  \0  \0  \0  \0  \0  \0  \0  \0  \0  \0  \0  \0
*
0005632   g   f   s       {  \n   i   d       =       "   F   3   7   z
0005648   e   3   -   g   q   r   1   -   G   3   6   H   -   s   f   P
0005664   A   -   W   c   A   W   -   m   U   i   B   -   0   4   O   G
0005680   k   V   "  \n   s   e   q   n   o       =       3  \n   s   t
0005696   a   t   u   s       =       [   "   R   E   S   I   Z   E   A
0005712   B   L   E   "   ,       "   R   E   A   D   "   ,       "   W
0005728   R   I   T   E   "   ,       "   C   L   U   S   T   E   R   E
0005744   D   "   ]  \n   e   x   t   e   n   t   _   s   i   z   e    
0005760   =       8   1   9   2  \n   m   a   x   _   l   v       =    
0005776   0  \n   m   a   x   _   p   v       =       0  \n  \n   p   h
0005792   y   s   i   c   a   l   _   v   o   l   u   m   e   s       {
0005808  \n  \n   p   v   0       {  \n   i   d       =       "   l   O
0005824   d   B   3   C   -   u   T   w   M   -   H   s   3   f   -   x
0005840   N   9   J   -   U   o   L   y   -   R   n   C   J   -   v   E
0005856   Q   l   D   G   "  \n   d   e   v   i   c   e       =       "
0005872   /   d   e   v   /   d   m   -   3   "  \n  \n   s   t   a   t
0005888   u   s       =       [   "   A   L   L   O   C   A   T   A   B
0005904   L   E   "   ]  \n   p   e   _   s   t   a   r   t       =    
0005920   3   8   4  \n   p   e   _   c   o   u   n   t       =       5
0005936   1   1   9   9  \n   }  \n   }  \n  \n   l   o   g   i   c   a
0005952   l   _   v   o   l   u   m   e   s       {  \n  \n   t   e   s
0005968   t       {  \n   i   d       =       "   p   Q   C   B   2   M
0005984   -   J   1   6   3   -   f   1   o   b   -   J   s   r   I   -
0006000   l   q   I   V   -   2   i   j   Q   -   4   j   b   m   R   o
0006016   "  \n   s   t   a   t   u   s       =       [   "   R   E   A
0006032   D   "   ,       "   W   R   I   T   E   "   ,       "   V   I
0006048   S   I   B   L   E   "   ]  \n   s   e   g   m   e   n   t   _
0006064   c   o   u   n   t       =       1  \n  \n   s   e   g   m   e
0006080   n   t   1       {  \n   s   t   a   r   t   _   e   x   t   e
0006096   n   t       =       0  \n   e   x   t   e   n   t   _   c   o
0006112   u   n   t       =       1   0   2   4   0  \n  \n   t   y   p
0006128   e       =       "   s   t   r   i   p   e   d   "  \n   s   t
0006144   r   i   p   e   _   c   o   u   n   t       =       1  \t   #
0006160       l   i   n   e   a   r  \n  \n   s   t   r   i   p   e   s
0006176       =       [  \n   "   p   v   0   "   ,       0  \n   ]  \n
0006192   }  \n   }  \n   }  \n   }  \n   #       G   e   n   e   r   a
0006208   t   e   d       b   y       L   V   M   2   :       F   r   i
0006224       M   a   r           2       0   3   :   2   6   :   0   4
0006240       2   0   0   7  \n  \n   c   o   n   t   e   n   t   s    
0006256   =       "   T   e   x   t       F   o   r   m   a   t       V
0006272   o   l   u   m   e       G   r   o   u   p   "  \n   v   e   r
0006288   s   i   o   n       =       1  \n  \n   d   e   s   c   r   i
0006304   p   t   i   o   n       =       "   "  \n  \n   c   r   e   a
0006320   t   i   o   n   _   h   o   s   t       =       "   r   s   2
0006336   1   .   l   v   s   .   i   i   f   .   h   u   "  \t   #    
0006352   L   i   n   u   x       r   s   2   1   .   l   v   s   .   i
0006368   i   f   .   h   u       2   .   6   .   1   8   -   4   -   6
0006384   8   6       #   1       S   M   P       W   e   d       F   e
0006400   b       2   1       1   6   :   0   6   :   5   4       U   T
0006416   C       2   0   0   7       i   6   8   6  \n   c   r   e   a
0006432   t   i   o   n   _   t   i   m   e       =       1   1   7   2
0006448   8   0   2   3   6   4  \t   #       F   r   i       M   a   r
0006464           2       0   3   :   2   6   :   0   4       2   0   0
0006480   7  \n  \n  \0  \0  \0  \0  \0  \0  \0  \0  \0  \0  \0  \0  \0
0006496  \0  \0  \0  \0  \0  \0  \0  \0  \0  \0  \0  \0  \0  \0  \0  \0
*
0006656   g   f   s       {  \n   i   d       =       "   F   3   7   z
0006672   e   3   -   g   q   r   1   -   G   3   6   H   -   s   f   P
0006688   A   -   W   c   A   W   -   m   U   i   B   -   0   4   O   G
0006704   k   V   "  \n   s   e   q   n   o       =       4  \n   s   t
0006720   a   t   u   s       =       [   "   R   E   S   I   Z   E   A
0006736   B   L   E   "   ,       "   R   E   A   D   "   ,       "   W
0006752   R   I   T   E   "   ,       "   C   L   U   S   T   E   R   E
0006768   D   "   ]  \n   e   x   t   e   n   t   _   s   i   z   e    
0006784   =       8   1   9   2  \n   m   a   x   _   l   v       =    
0006800   0  \n   m   a   x   _   p   v       =       0  \n  \n   p   h
0006816   y   s   i   c   a   l   _   v   o   l   u   m   e   s       {
0006832  \n  \n   p   v   0       {  \n   i   d       =       "   l   O
0006848   d   B   3   C   -   u   T   w   M   -   H   s   3   f   -   x
0006864   N   9   J   -   U   o   L   y   -   R   n   C   J   -   v   E
0006880   Q   l   D   G   "  \n   d   e   v   i   c   e       =       "
0006896   /   d   e   v   /   d   m   -   2   "  \n  \n   s   t   a   t
0006912   u   s       =       [   "   A   L   L   O   C   A   T   A   B
0006928   L   E   "   ]  \n   p   e   _   s   t   a   r   t       =    
0006944   3   8   4  \n   p   e   _   c   o   u   n   t       =       5
0006960   1   1   9   9  \n   }  \n   }  \n  \n   l   o   g   i   c   a
0006976   l   _   v   o   l   u   m   e   s       {  \n  \n   t   e   s
0006992   t       {  \n   i   d       =       "   p   Q   C   B   2   M
0007008   -   J   1   6   3   -   f   1   o   b   -   J   s   r   I   -
0007024   l   q   I   V   -   2   i   j   Q   -   4   j   b   m   R   o
0007040   "  \n   s   t   a   t   u   s       =       [   "   R   E   A
0007056   D   "   ,       "   W   R   I   T   E   "   ,       "   V   I
0007072   S   I   B   L   E   "   ]  \n   s   e   g   m   e   n   t   _
0007088   c   o   u   n   t       =       1  \n  \n   s   e   g   m   e
0007104   n   t   1       {  \n   s   t   a   r   t   _   e   x   t   e
0007120   n   t       =       0  \n   e   x   t   e   n   t   _   c   o
0007136   u   n   t       =       1   0   2   4   0  \n  \n   t   y   p
0007152   e       =       "   s   t   r   i   p   e   d   "  \n   s   t
0007168   r   i   p   e   _   c   o   u   n   t       =       1  \t   #
0007184       l   i   n   e   a   r  \n  \n   s   t   r   i   p   e   s
0007200       =       [  \n   "   p   v   0   "   ,       0  \n   ]  \n
0007216   }  \n   }  \n  \n   t   2       {  \n   i   d       =       "
0007232   r   j   r   4   9   d   -   t   E   T   G   -   j   f   O   I
0007248   -   Q   F   G   u   -   L   q   H   j   -   z   p   r   d   -
0007264   9   9   q   K   7   E   "  \n   s   t   a   t   u   s       =
0007280       [   "   R   E   A   D   "   ,       "   W   R   I   T   E
0007296   "   ,       "   V   I   S   I   B   L   E   "   ]  \n   s   e
0007312   g   m   e   n   t   _   c   o   u   n   t       =       1  \n
0007328  \n   s   e   g   m   e   n   t   1       {  \n   s   t   a   r
0007344   t   _   e   x   t   e   n   t       =       0  \n   e   x   t
0007360   e   n   t   _   c   o   u   n   t       =       2   5   6  \n
0007376  \n   t   y   p   e       =       "   s   t   r   i   p   e   d
0007392   "  \n   s   t   r   i   p   e   _   c   o   u   n   t       =
0007408       1  \t   #       l   i   n   e   a   r  \n  \n   s   t   r
0007424   i   p   e   s       =       [  \n   "   p   v   0   "   ,    
0007440   1   0   2   4   0  \n   ]  \n   }  \n   }  \n   }  \n   }  \n
0007456   #       G   e   n   e   r   a   t   e   d       b   y       L
0007472   V   M   2   :       T   u   e       M   a   r           6    
0007488   0   1   :   3   8   :   2   1       2   0   0   7  \n  \n   c
0007504   o   n   t   e   n   t   s       =       "   T   e   x   t    
0007520   F   o   r   m   a   t       V   o   l   u   m   e       G   r
0007536   o   u   p   "  \n   v   e   r   s   i   o   n       =       1
0007552  \n  \n   d   e   s   c   r   i   p   t   i   o   n       =    
0007568   "   "  \n  \n   c   r   e   a   t   i   o   n   _   h   o   s
0007584   t       =       "   r   s   2   2   "  \t   #       L   i   n
0007600   u   x       r   s   2   2       2   .   6   .   1   8   -   4
0007616   -   6   8   6       #   1       S   M   P       W   e   d    
0007632   F   e   b       2   1       1   6   :   0   6   :   5   4    
0007648   U   T   C       2   0   0   7       i   6   8   6  \n   c   r
0007664   e   a   t   i   o   n   _   t   i   m   e       =       1   1
0007680   7   3   1   4   1   5   0   1  \t   #       T   u   e       M
0007696   a   r           6       0   1   :   3   8   :   2   1       2
0007712   0   0   7  \n  \n  \0  \0  \0  \0  \0  \0  \0  \0  \0  \0  \0
0007728  \0  \0  \0  \0  \0  \0  \0  \0  \0  \0  \0  \0  \0  \0  \0  \0
*
0008192   g   f   s       {  \n   i   d       =       "   F   3   7   z
0008208   e   3   -   g   q   r   1   -   G   3   6   H   -   s   f   P
0008224   A   -   W   c   A   W   -   m   U   i   B   -   0   4   O   G
0008240   k   V   "  \n   s   e   q   n   o       =       5  \n   s   t
0008256   a   t   u   s       =       [   "   R   E   S   I   Z   E   A
0008272   B   L   E   "   ,       "   R   E   A   D   "   ,       "   W
0008288   R   I   T   E   "   ,       "   C   L   U   S   T   E   R   E
0008304   D   "   ]  \n   e   x   t   e   n   t   _   s   i   z   e    
0008320   =       8   1   9   2  \n   m   a   x   _   l   v       =    
0008336   0  \n   m   a   x   _   p   v       =       0  \n  \n   p   h
0008352   y   s   i   c   a   l   _   v   o   l   u   m   e   s       {
0008368  \n  \n   p   v   0       {  \n   i   d       =       "   l   O
0008384   d   B   3   C   -   u   T   w   M   -   H   s   3   f   -   x
0008400   N   9   J   -   U   o   L   y   -   R   n   C   J   -   v   E
0008416   Q   l   D   G   "  \n   d   e   v   i   c   e       =       "
0008432   /   d   e   v   /   d   m   -   2   "  \n  \n   s   t   a   t
0008448   u   s       =       [   "   A   L   L   O   C   A   T   A   B
0008464   L   E   "   ]  \n   p   e   _   s   t   a   r   t       =    
0008480   3   8   4  \n   p   e   _   c   o   u   n   t       =       5
0008496   1   1   9   9  \n   }  \n   }  \n  \n   l   o   g   i   c   a
0008512   l   _   v   o   l   u   m   e   s       {  \n  \n   t   e   s
0008528   t       {  \n   i   d       =       "   p   Q   C   B   2   M
0008544   -   J   1   6   3   -   f   1   o   b   -   J   s   r   I   -
0008560   l   q   I   V   -   2   i   j   Q   -   4   j   b   m   R   o
0008576   "  \n   s   t   a   t   u   s       =       [   "   R   E   A
0008592   D   "   ,       "   W   R   I   T   E   "   ,       "   V   I
0008608   S   I   B   L   E   "   ]  \n   s   e   g   m   e   n   t   _
0008624   c   o   u   n   t       =       1  \n  \n   s   e   g   m   e
0008640   n   t   1       {  \n   s   t   a   r   t   _   e   x   t   e
0008656   n   t       =       0  \n   e   x   t   e   n   t   _   c   o
0008672   u   n   t       =       1   0   2   4   0  \n  \n   t   y   p
0008688   e       =       "   s   t   r   i   p   e   d   "  \n   s   t
0008704   r   i   p   e   _   c   o   u   n   t       =       1  \t   #
0008720       l   i   n   e   a   r  \n  \n   s   t   r   i   p   e   s
0008736       =       [  \n   "   p   v   0   "   ,       0  \n   ]  \n
0008752   }  \n   }  \n   }  \n   }  \n   #       G   e   n   e   r   a
0008768   t   e   d       b   y       L   V   M   2   :       T   u   e
0008784       M   a   r           6       0   1   :   3   8   :   5   5
0008800       2   0   0   7  \n  \n   c   o   n   t   e   n   t   s    
0008816   =       "   T   e   x   t       F   o   r   m   a   t       V
0008832   o   l   u   m   e       G   r   o   u   p   "  \n   v   e   r
0008848   s   i   o   n       =       1  \n  \n   d   e   s   c   r   i
0008864   p   t   i   o   n       =       "   "  \n  \n   c   r   e   a
0008880   t   i   o   n   _   h   o   s   t       =       "   r   s   2
0008896   1   "  \t   #       L   i   n   u   x       r   s   2   1    
0008912   2   .   6   .   1   8   -   4   -   6   8   6       #   1    
0008928   S   M   P       W   e   d       F   e   b       2   1       1
0008944   6   :   0   6   :   5   4       U   T   C       2   0   0   7
0008960       i   6   8   6  \n   c   r   e   a   t   i   o   n   _   t
0008976   i   m   e       =       1   1   7   3   1   4   1   5   3   5
0008992  \t   #       T   u   e       M   a   r           6       0   1
0009008   :   3   8   :   5   5       2   0   0   7  \n  \n  \0  \0  \0
0009024  \0  \0  \0  \0  \0  \0  \0  \0  \0  \0  \0  \0  \0  \0  \0  \0
*
0009216   g   f   s       {  \n   i   d       =       "   F   3   7   z
0009232   e   3   -   g   q   r   1   -   G   3   6   H   -   s   f   P
0009248   A   -   W   c   A   W   -   m   U   i   B   -   0   4   O   G
0009264   k   V   "  \n   s   e   q   n   o       =       6  \n   s   t
0009280   a   t   u   s       =       [   "   R   E   S   I   Z   E   A
0009296   B   L   E   "   ,       "   R   E   A   D   "   ,       "   W
0009312   R   I   T   E   "   ,       "   C   L   U   S   T   E   R   E
0009328   D   "   ]  \n   e   x   t   e   n   t   _   s   i   z   e    
0009344   =       8   1   9   2  \n   m   a   x   _   l   v       =    
0009360   0  \n   m   a   x   _   p   v       =       0  \n  \n   p   h
0009376   y   s   i   c   a   l   _   v   o   l   u   m   e   s       {
0009392  \n  \n   p   v   0       {  \n   i   d       =       "   l   O
0009408   d   B   3   C   -   u   T   w   M   -   H   s   3   f   -   x
0009424   N   9   J   -   U   o   L   y   -   R   n   C   J   -   v   E
0009440   Q   l   D   G   "  \n   d   e   v   i   c   e       =       "
0009456   /   d   e   v   /   d   m   -   2   "  \n  \n   s   t   a   t
0009472   u   s       =       [   "   A   L   L   O   C   A   T   A   B
0009488   L   E   "   ]  \n   p   e   _   s   t   a   r   t       =    
0009504   3   8   4  \n   p   e   _   c   o   u   n   t       =       5
0009520   1   1   9   9  \n   }  \n   }  \n  \n   l   o   g   i   c   a
0009536   l   _   v   o   l   u   m   e   s       {  \n  \n   t   e   s
0009552   t       {  \n   i   d       =       "   p   Q   C   B   2   M
0009568   -   J   1   6   3   -   f   1   o   b   -   J   s   r   I   -
0009584   l   q   I   V   -   2   i   j   Q   -   4   j   b   m   R   o
0009600   "  \n   s   t   a   t   u   s       =       [   "   R   E   A
0009616   D   "   ,       "   W   R   I   T   E   "   ,       "   V   I
0009632   S   I   B   L   E   "   ]  \n   s   e   g   m   e   n   t   _
0009648   c   o   u   n   t       =       1  \n  \n   s   e   g   m   e
0009664   n   t   1       {  \n   s   t   a   r   t   _   e   x   t   e
0009680   n   t       =       0  \n   e   x   t   e   n   t   _   c   o
0009696   u   n   t       =       1   0   2   4   0  \n  \n   t   y   p
0009712   e       =       "   s   t   r   i   p   e   d   "  \n   s   t
0009728   r   i   p   e   _   c   o   u   n   t       =       1  \t   #
0009744       l   i   n   e   a   r  \n  \n   s   t   r   i   p   e   s
0009760       =       [  \n   "   p   v   0   "   ,       0  \n   ]  \n
0009776   }  \n   }  \n  \n   x   f   s       {  \n   i   d       =    
0009792   "   i   h   2   d   I   7   -   f   7   E   B   -   g   k   c
0009808   z   -   C   K   F   V   -   0   O   H   p   -   9   B   S   Z
0009824   -   1   A   M   6   f   u   "  \n   s   t   a   t   u   s    
0009840   =       [   "   R   E   A   D   "   ,       "   W   R   I   T
0009856   E   "   ,       "   V   I   S   I   B   L   E   "   ]  \n   s
0009872   e   g   m   e   n   t   _   c   o   u   n   t       =       1
0009888  \n  \n   s   e   g   m   e   n   t   1       {  \n   s   t   a
0009904   r   t   _   e   x   t   e   n   t       =       0  \n   e   x
0009920   t   e   n   t   _   c   o   u   n   t       =       1   2   8
0009936   0  \n  \n   t   y   p   e       =       "   s   t   r   i   p
0009952   e   d   "  \n   s   t   r   i   p   e   _   c   o   u   n   t
0009968       =       1  \t   #       l   i   n   e   a   r  \n  \n   s
0009984   t   r   i   p   e   s       =       [  \n   "   p   v   0   "
0010000   ,       1   0   2   4   0  \n   ]  \n   }  \n   }  \n   }  \n
0010016   }  \n   #       G   e   n   e   r   a   t   e   d       b   y
0010032       L   V   M   2   :       T   h   u       M   a   r       2
0010048   2       1   6   :   3   2   :   1   6       2   0   0   7  \n
0010064  \n   c   o   n   t   e   n   t   s       =       "   T   e   x
0010080   t       F   o   r   m   a   t       V   o   l   u   m   e    
0010096   G   r   o   u   p   "  \n   v   e   r   s   i   o   n       =
0010112       1  \n  \n   d   e   s   c   r   i   p   t   i   o   n    
0010128   =       "   "  \n  \n   c   r   e   a   t   i   o   n   _   h
0010144   o   s   t       =       "   r   s   2   1   "  \t   #       L
0010160   i   n   u   x       r   s   2   1       2   .   6   .   1   8
0010176   -   4   -   6   8   6       #   1       S   M   P       W   e
0010192   d       F   e   b       2   1       1   6   :   0   6   :   5
0010208   4       U   T   C       2   0   0   7       i   6   8   6  \n
0010224   c   r   e   a   t   i   o   n   _   t   i   m   e       =    
0010240   1   1   7   4   5   7   7   5   3   6  \t   #       T   h   u
0010256       M   a   r       2   2       1   6   :   3   2   :   1   6
0010272       2   0   0   7  \n  \n  \0  \0  \0  \0  \0  \0  \0  \0  \0
0010288  \0  \0  \0  \0  \0  \0  \0  \0  \0  \0  \0  \0  \0  \0  \0  \0
*
0262144 001 026 031   p  \0  \0  \0 001  \0  \0  \0  \0  \0  \0  \0  \0
0262160  \0  \0  \0   d  \0  \0  \0  \0  \0  \0 005 035  \0  \0 005   y
0262176  \0  \0  \0  \0  \0  \0 020  \0  \0  \0  \0  \f  \0  \0  \0 020
0262192  \0  \0  \0  \0  \0  \0  \0 026  \0  \0  \0  \0  \0  \0  \0 026
0262208  \0  \0  \0  \0  \0  \0  \0 027  \0  \0  \0  \0  \0  \0  \0 027
0262224  \0  \0  \0  \0  \0  \0  \0 032  \0  \0  \0  \0  \0  \0  \0 032
0262240   l   o   c   k   _   d   l   m  \0  \0  \0  \0  \0  \0  \0  \0
0262256  \0  \0  \0  \0  \0  \0  \0  \0  \0  \0  \0  \0  \0  \0  \0  \0
*
0262304   p   i   l   o   t   :   t   e   s   t  \0  \0  \0  \0  \0  \0
0262320  \0  \0  \0  \0  \0  \0  \0  \0  \0  \0  \0  \0  \0  \0  \0  \0
*
0262368  \0  \0  \0  \0  \0  \0  \0 030  \0  \0  \0  \0  \0  \0  \0 030
0262384  \0  \0  \0  \0  \0  \0  \0 031  \0  \0  \0  \0  \0  \0  \0 031
0262400  \0  \0  \0  \0  \0  \0  \0  \0  \0  \0  \0  \0  \0  \0  \0  \0
*
0262656



From Santosh.Panigrahi at in.unisys.com  Thu Feb 14 11:37:12 2008
From: Santosh.Panigrahi at in.unisys.com (Panigrahi, Santosh Kumar)
Date: Thu, 14 Feb 2008 17:07:12 +0530
Subject: [Linux-cluster] help reqd. - VMware ESX 3.5 fencing
Message-ID: <D566E8CF3538B54D95B925CB69CB4D2A0C1F09EB@inblr-exch1.eu.uis.unisys.com>

Hi,

 

Does anybody have configured fencing in VMware ESX 3.5 environment? I
appreciate any help.

 

I have got some info from
http://www.tournament.org.il/run/index.php?/archives/140-VMware-Fencing-
in-RedHat-Cluster-5-RHCS5.html .

This script given here is for VMware server. Any idea whether it will
work for ESX 3.5 server or not?

 

My system configurations are as follows.

 

Host machine    : Unisys ES7000-one with host OS as VMware ESX 3.5

Guest Machines: Guest OS as Rhel5.1 AP

 

I am connecting to host machine using VMware VI 3.0.

 

Thanks,

Santosh

 

 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://listman.redhat.com/archives/linux-cluster/attachments/20080214/9ff9806c/attachment.htm>

From p_pavlos at freemail.gr  Thu Feb 14 12:28:30 2008
From: p_pavlos at freemail.gr (Pavlos Parissis)
Date: Thu, 14 Feb 2008 14:28:30 +0200
Subject: [Linux-cluster] config issuse or bug in 4.u4 for nfs exports
Message-ID: <20080214142830.n1e86e52ckks88oc@easymail-app.hol.gr>

Hi,

I am building a NFS Active/Passive cluster using ext3 filesystem and I  
don't know if I have a configuration issue or I come across a bug.

My service, nfs1, is started without problems but there is no nfs  
export available.

I went through the list and I found this thread
http://marc.info/?l=redhat-linux-cluster&m=118764091712577&w=2

I tried to find any evidence of this by looking at bug reports and the  
release notes of 4.5,4.6 and 5.0 but I couldn't find any thing.

Could you please someone give me an idea?

Regards,
Pavlos




ocsi1#  rpm -q rgmanager
rgmanager-1.9.53-0
ocsi1# rpm -q ccs
ccs-1.0.7-0
ocsi1# rpm -q magma
magma-1.0.6-0
ocsi1# rpm -q magma-plugins
magma-plugins-1.0.9-0
ocsi1# rpm -q cman
cman-1.0.11-0
ocsi1# rpm -q cman-kernel
cman-kernel-2.6.9-45.2
ocsi1# rpm -q dlm
dlm-1.0.1-1
ocsi1# rpm -q dlm-kernel
dlm-kernel-2.6.9-42.10
ocsi1# rpm -q fence
fence-1.32.25-1
ocsi1# rpm -q gulm
gulm-1.0.7-0
ocsi1# rpm -q iddev
iddev-2.0.0-3
ocsi1# cat /etc/redhat-release
Red Hat Enterprise Linux AS release 4 (Nahant Update 4)
ocsi1# uname -a
Linux ocsi1 2.6.9-42.ELsmp #1 SMP Wed Jul 12 23:32:02 EDT 2006 x86_64  
x86_64 x86_64 GNU/Linux


ocsi1# rg_test test /etc/cluster/cluster.conf
Running in test mode.
Loaded 9 resource rules
=== Resources List ===
Resource type: nfsclient
Agent: nfsclient.sh
Attributes:
   name = oam-network [ primary unique ]
   target = 10.10.21.128/26 [ required ]
   path [ inherit("path") ]
   fsid [ inherit("fsid") ]
   nfslock [ inherit("nfsexport%nfslock") ]
   options = rw

Resource type: nfsexport
Agent: nfsexport.sh
Attributes:
   name = omg_data [ primary ]
   device [ inherit("device") ]
   path [ inherit("mountpoint") ]
   fsid [ inherit("fsid") ]
   nfslock [ inherit("nfslock") ]

Resource type: service [ROOT] [INLINE]
Instances: 1/1
Agent: service.sh
Attributes:
   name = ppr2 [ primary unique required ]
   domain = SecondDomain
   autostart = 1
   recovery = relocate

Resource type: fs [INLINE]
Instances: 1/1
Agent: fs.sh
Attributes:
   name = /usr/omg_ppr2 [ primary ]
   mountpoint = /usr/omg_ppr2 [ unique required ]
   device = /dev/sde1 [ unique required ]
   fstype = ext3
   force_unmount = 1
   nfslock [ inherit("service%nfslock") ]

Resource type: ip [INLINE]
Instances: 1/1
Agent: ip.sh
Attributes:
   address = 10.10.21.72 [ primary unique ]
   monitor_link = 1
   nfslock [ inherit("service%nfslock") ]

Resource type: ip [INLINE]
Instances: 1/1
Agent: ip.sh
Attributes:
   address = 10.10.21.141 [ primary unique ]
   monitor_link = 1
   nfslock [ inherit("service%nfslock") ]

Resource type: script [INLINE]
Agent: script.sh
Attributes:
   name = ppr2 [ primary unique ]
   file = /usr/local/wsb/scripts/rhc_ppr2 [ unique required ]
   service_name [ inherit("service%name") ]

Resource type: service [ROOT] [INLINE]
Instances: 1/1
Agent: service.sh
Attributes:
   name = ppr1 [ primary unique required ]
   domain = FirstDomain
   autostart = 1
   recovery = relocate

Resource type: fs [INLINE]
Instances: 1/1
Agent: fs.sh
Attributes:
   name = /usr/omg_ppr [ primary ]
   mountpoint = /usr/omg_ppr [ unique required ]
   device = /dev/sdd1 [ unique required ]
   fstype = ext3
   force_unmount = 1
   nfslock [ inherit("service%nfslock") ]

Resource type: ip [INLINE]
Instances: 1/1
Agent: ip.sh
Attributes:
   address = 10.10.21.71 [ primary unique ]
   monitor_link = 1
   nfslock [ inherit("service%nfslock") ]

Resource type: ip [INLINE]
Instances: 1/1
Agent: ip.sh
Attributes:
   address = 10.10.21.138 [ primary unique ]
   monitor_link = 1
   nfslock [ inherit("service%nfslock") ]

Resource type: script [INLINE]
Agent: script.sh
Attributes:
   name = ppr1 [ primary unique ]
   file = /usr/local/wsb/scripts/rhc_ppr1 [ unique required ]
   service_name [ inherit("service%name") ]

Resource type: service [ROOT] [INLINE]
Instances: 1/1
Agent: service.sh
Attributes:
   name = nfs1 [ primary unique required ]
   domain = ThirdDomain
   autostart = 1
   recovery = relocate

Resource type: fs [INLINE]
Instances: 1/1
Agent: fs.sh
Attributes:
   name = /nfs_omg_data [ primary ]
   mountpoint = /nfs_omg_data [ unique required ]
   device = /dev/sdb2 [ unique required ]
   fstype = ext3
   force_unmount = 1
   nfslock [ inherit("service%nfslock") ]

Resource type: ip [INLINE]
Instances: 1/1
Agent: ip.sh
Attributes:
   address = 10.10.21.73 [ primary unique ]
   monitor_link = 1
   nfslock [ inherit("service%nfslock") ]

Resource type: ip [INLINE]
Instances: 1/1
Agent: ip.sh
Attributes:
   address = 10.10.21.142 [ primary unique ]
   monitor_link = 1
   nfslock [ inherit("service%nfslock") ]

=== Resource Tree ===
service {
   name = "ppr2";
   domain = "SecondDomain";
   autostart = "1";
   recovery = "relocate";
   fs {
     name = "/usr/omg_ppr2";
     mountpoint = "/usr/omg_ppr2";
     device = "/dev/sde1";
     fstype = "ext3";
     force_unmount = "1";
     nfslock = "(null)";
   }
   ip {
     address = "10.10.21.72";
     monitor_link = "1";
     nfslock = "(null)";
   }
   ip {
     address = "10.10.21.141";
     monitor_link = "1";
     nfslock = "(null)";
   }
   script {
     name = "ppr2";
     file = "/usr/local/wsb/scripts/rhc_ppr2";
     service_name = "ppr2";
   }
}
service {
   name = "ppr1";
   domain = "FirstDomain";
   autostart = "1";
   recovery = "relocate";
   fs {
     name = "/usr/omg_ppr";
     mountpoint = "/usr/omg_ppr";
     device = "/dev/sdd1";
     fstype = "ext3";
     force_unmount = "1";
     nfslock = "(null)";
   }
   ip {
     address = "10.10.21.71";
     monitor_link = "1";
     nfslock = "(null)";
   }
   ip {
     address = "10.10.21.138";
     monitor_link = "1";
     nfslock = "(null)";
   }
   script {
     name = "ppr1";
     file = "/usr/local/wsb/scripts/rhc_ppr1";
     service_name = "ppr1";
   }
}
service {
   name = "nfs1";
   domain = "ThirdDomain";
   autostart = "1";
   recovery = "relocate";
   fs {
     name = "/nfs_omg_data";
     mountpoint = "/nfs_omg_data";
     device = "/dev/sdb2";
     fstype = "ext3";
     force_unmount = "1";
     nfslock = "(null)";
     nfsexport {
       name = "omg_data";
       device = "/dev/sdb2";
       path = "/nfs_omg_data";
       fsid = "(null)";
       nfslock = "(null)";
     }
   }
   ip {
     address = "10.10.21.73";
     monitor_link = "1";
     nfslock = "(null)";
   }
   ip {
     address = "10.10.21.142";
     monitor_link = "1";
     nfslock = "(null)";
   }
}
=== Failover Domains ===
Failover domain: FirstDomain
Flags: Ordered Restricted
   Node ocsi2-cluster (priority 0)
   Node ocsi1-cluster (priority 1)
Failover domain: SecondDomain
Flags: Ordered Restricted
   Node ocsi3-cluster (priority 0)
   Node ocsi1-cluster (priority 1)
Failover domain: ThirdDomain
Flags: Ordered Restricted
   Node ocsi1-cluster (priority 0)
   Node ocsi2-cluster (priority 1)
   Node ocsi3-cluster (priority 2)
ocsi1# cat /etc/cluster/cluster.conf
<?xml version="1.0" encoding="UTF-8"?>
<cluster config_version="105" name="NGP-Cluster">
   <clusternodes>
     <clusternode votes="1" name="ocsi1-cluster">
       <fence>
         <method name="hardware">
           <device hostname="ocsi1-ilo" name="ilo"/>
         </method>
         <method name="last_resort">
           <device ipaddr="ocsi1-cluster" name="last_resort"/>
         </method>
       </fence>
     </clusternode>
     <clusternode votes="1" name="ocsi2-cluster">
       <fence>
         <method name="hardware">
           <device hostname="ocsi2-ilo" name="ilo"/>
         </method>
         <method name="last_resort">
           <device ipaddr="ocsi2-cluster" name="last_resort"/>
         </method>
       </fence>
     </clusternode>
     <clusternode votes="1" name="ocsi3-cluster">
       <fence>
         <method name="hardware">
           <device hostname="ocsi3-ilo" name="ilo"/>
         </method>
         <method name="last_resort">
           <device ipaddr="ocsi3-cluster" name="last_resort"/>
         </method>
       </fence>
     </clusternode>
   </clusternodes>
   <fencedevices>
     <fencedevice passwd="admin123" action="off" login="admin"  
name="ilo" agent="fence_ilo"/>
     <fencedevice name="last_resort" agent="fence_manual"/>
   </fencedevices>
   <rm log_facility="local3" log_level="4">
     <failoverdomains>
       <failoverdomain restricted="1" ordered="1" name="FirstDomain">
         <failoverdomainnode priority="0" name="ocsi2-cluster"/>
         <failoverdomainnode priority="1" name="ocsi1-cluster"/>
       </failoverdomain>
       <failoverdomain restricted="1" ordered="1" name="SecondDomain">
         <failoverdomainnode priority="0" name="ocsi3-cluster"/>
         <failoverdomainnode priority="1" name="ocsi1-cluster"/>
       </failoverdomain>
       <failoverdomain restricted="1" ordered="1" name="ThirdDomain">
         <failoverdomainnode priority="0" name="ocsi1-cluster"/>
         <failoverdomainnode priority="1" name="ocsi2-cluster"/>
         <failoverdomainnode priority="2" name="ocsi3-cluster"/>
       </failoverdomain>
     </failoverdomains>
     <resources>
       <nfsclient target="10.10.21.128/26" options="rw" name="oam-network"/>
       <nfsexport name="omg_data"/>
     </resources>
     <service domain="SecondDomain" name="ppr2" autostart="1"  
recovery="relocate">
       <script name="ppr2" file="/usr/local/wsb/scripts/rhc_ppr2"/>
       <ip monitor_link="1" address="10.10.21.72"/>
       <fs device="/dev/sde1" mountpoint="/usr/omg_ppr2"  
force_unmount="1" name="/usr/omg_ppr2" fstype="ext3"/>
       <ip monitor_link="1" address="10.10.21.141"/>
     </service>
     <service domain="FirstDomain" name="ppr1" autostart="1"  
recovery="relocate">
       <script name="ppr1" file="/usr/local/wsb/scripts/rhc_ppr1"/>
       <ip monitor_link="1" address="10.10.21.71"/>
       <fs device="/dev/sdd1" mountpoint="/usr/omg_ppr"  
force_unmount="1" name="/usr/omg_ppr" fstype="ext3"/>
       <ip monitor_link="1" address="10.10.21.138"/>
     </service>
     <service domain="ThirdDomain" name="nfs1" autostart="1"  
recovery="relocate">
       <ip monitor_link="1" address="10.10.21.73"/>
       <fs device="/dev/sdb2" mountpoint="/nfs_omg_data"  
force_unmount="1" name="/nfs_omg_data" fstype="ext3">
         <nfsexport ref="omg_data">
           <nfslient ref="oam-network"/>
         </nfsexport>
       </fs>
       <ip monitor_link="1" address="10.10.21.142"/>
     </service>
   </rm>
   <quorumd votes="2" log_level="4" tko="10" interval="1"  
label="priquorum" log_facility="local3" device="/dev/sdc"/>
   <fence_daemon clean_start="1"/>
</cluster>




From Mathieu.MARY at neufcegetel.fr  Thu Feb 14 12:29:23 2008
From: Mathieu.MARY at neufcegetel.fr (MARY, Mathieu)
Date: Thu, 14 Feb 2008 13:29:23 +0100
Subject: [Linux-cluster] help reqd. - VMware ESX 3.5 fencing
In-Reply-To: <D566E8CF3538B54D95B925CB69CB4D2A0C1F09EB@inblr-exch1.eu.uis.unisys.com>
Message-ID: <20080214122823.C611420B0DE@smtp3.ldcom.fr>

hello,

 

i'm using this script for VI 3 and  ESX3.02 i guess it would work for you too, cannot remember where I found it though :-)

note that you have to send the restart request to your VC server and not to the ESX server

 

________________________________

De : linux-cluster-bounces at redhat.com [mailto:linux-cluster-bounces at redhat.com] De la part de Panigrahi, Santosh Kumar
Envoy? : jeudi 14 f?vrier 2008 12:37
? : linux-cluster at redhat.com
Objet : [Linux-cluster] help reqd. - VMware ESX 3.5 fencing

 

Hi,

 

Does anybody have configured fencing in VMware ESX 3.5 environment? I appreciate any help.

 

I have got some info from http://www.tournament.org.il/run/index.php?/archives/140-VMware-Fencing-in-RedHat-Cluster-5-RHCS5.html .

This script given here is for VMware server. Any idea whether it will work for ESX 3.5 server or not?

 

My system configurations are as follows.

 

Host machine    : Unisys ES7000-one with host OS as VMware ESX 3.5

Guest Machines: Guest OS as Rhel5.1 AP

 

I am connecting to host machine using VMware VI 3.0.

 

Thanks,

Santosh

 

 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://listman.redhat.com/archives/linux-cluster/attachments/20080214/de64232f/attachment.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: fence_vi3
Type: application/octet-stream
Size: 4273 bytes
Desc: fence_vi3
URL: <http://listman.redhat.com/archives/linux-cluster/attachments/20080214/de64232f/attachment.obj>

From Santosh.Panigrahi at in.unisys.com  Thu Feb 14 12:50:27 2008
From: Santosh.Panigrahi at in.unisys.com (Panigrahi, Santosh Kumar)
Date: Thu, 14 Feb 2008 18:20:27 +0530
Subject: [Linux-cluster] help reqd. - VMware ESX 3.5 fencing
In-Reply-To: <20080214122823.C611420B0DE@smtp3.ldcom.fr>
References: <D566E8CF3538B54D95B925CB69CB4D2A0C1F09EB@inblr-exch1.eu.uis.unisys.com>
	<20080214122823.C611420B0DE@smtp3.ldcom.fr>
Message-ID: <D566E8CF3538B54D95B925CB69CB4D2A0C1F0E80@inblr-exch1.eu.uis.unisys.com>

Thanks Marry for the script. I will test and let you know. By the way what's this VC server? Is it the system where I am running my VI client?

Can you please elaborate little more on this configuration like where I will keep this script, what will I mention in my cluster.conf file and etc.

 

Thanks,

Santosh  

________________________________

From: linux-cluster-bounces at redhat.com [mailto:linux-cluster-bounces at redhat.com] On Behalf Of MARY, Mathieu
Sent: Thursday, February 14, 2008 5:59 PM
To: linux clustering
Subject: RE: [Linux-cluster] help reqd. - VMware ESX 3.5 fencing

 

hello,

 

i'm using this script for VI 3 and  ESX3.02 i guess it would work for you too, cannot remember where I found it though :-)

note that you have to send the restart request to your VC server and not to the ESX server

 

________________________________

De : linux-cluster-bounces at redhat.com [mailto:linux-cluster-bounces at redhat.com] De la part de Panigrahi, Santosh Kumar
Envoy? : jeudi 14 f?vrier 2008 12:37
? : linux-cluster at redhat.com
Objet : [Linux-cluster] help reqd. - VMware ESX 3.5 fencing

 

Hi,

 

Does anybody have configured fencing in VMware ESX 3.5 environment? I appreciate any help.

 

I have got some info from http://www.tournament.org.il/run/index.php?/archives/140-VMware-Fencing-in-RedHat-Cluster-5-RHCS5.html .

This script given here is for VMware server. Any idea whether it will work for ESX 3.5 server or not?

 

My system configurations are as follows.

 

Host machine    : Unisys ES7000-one with host OS as VMware ESX 3.5

Guest Machines: Guest OS as Rhel5.1 AP

 

I am connecting to host machine using VMware VI 3.0.

 

Thanks,

Santosh

 

 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://listman.redhat.com/archives/linux-cluster/attachments/20080214/1d1dac6f/attachment.htm>

From Mathieu.MARY at neufcegetel.fr  Thu Feb 14 13:08:55 2008
From: Mathieu.MARY at neufcegetel.fr (MARY, Mathieu)
Date: Thu, 14 Feb 2008 14:08:55 +0100
Subject: [Linux-cluster] help reqd. - VMware ESX 3.5 fencing
In-Reply-To: <D566E8CF3538B54D95B925CB69CB4D2A0C1F0E80@inblr-exch1.eu.uis.unisys.com>
Message-ID: <20080214130755.C24DA20B300@smtp3.ldcom.fr>

VC is the virtual center server, i understood from your mail that you're using virtual infrastructure, but you question points out the fact that you maybe are using standalone ESX server ?

in our configuration we use an ESX farm of 4 servers managed by the VC server where we connect with the VI client

 

 

<fencedevice name="your_fence_method" agent="fence_vi3" ipaddr="yourserver_ip" port="your_vm_name" login="xxx" passwd="yyyyy"/>

 

though I don't know if it works on standalone server, maybe you would have ton install the VMI perlmodules described inside the script to you ESX 3.5 server

 

________________________________

De : linux-cluster-bounces at redhat.com [mailto:linux-cluster-bounces at redhat.com] De la part de Panigrahi, Santosh Kumar
Envoy? : jeudi 14 f?vrier 2008 13:50
? : linux clustering
Objet : RE: [Linux-cluster] help reqd. - VMware ESX 3.5 fencing

 

Thanks Marry for the script. I will test and let you know. By the way what's this VC server? Is it the system where I am running my VI client?

Can you please elaborate little more on this configuration like where I will keep this script, what will I mention in my cluster.conf file and etc.

 

Thanks,

Santosh  

________________________________

From: linux-cluster-bounces at redhat.com [mailto:linux-cluster-bounces at redhat.com] On Behalf Of MARY, Mathieu
Sent: Thursday, February 14, 2008 5:59 PM
To: linux clustering
Subject: RE: [Linux-cluster] help reqd. - VMware ESX 3.5 fencing

 

hello,

 

i'm using this script for VI 3 and  ESX3.02 i guess it would work for you too, cannot remember where I found it though :-)

note that you have to send the restart request to your VC server and not to the ESX server

 

________________________________

De : linux-cluster-bounces at redhat.com [mailto:linux-cluster-bounces at redhat.com] De la part de Panigrahi, Santosh Kumar
Envoy? : jeudi 14 f?vrier 2008 12:37
? : linux-cluster at redhat.com
Objet : [Linux-cluster] help reqd. - VMware ESX 3.5 fencing

 

Hi,

 

Does anybody have configured fencing in VMware ESX 3.5 environment? I appreciate any help.

 

I have got some info from http://www.tournament.org.il/run/index.php?/archives/140-VMware-Fencing-in-RedHat-Cluster-5-RHCS5.html .

This script given here is for VMware server. Any idea whether it will work for ESX 3.5 server or not?

 

My system configurations are as follows.

 

Host machine    : Unisys ES7000-one with host OS as VMware ESX 3.5

Guest Machines: Guest OS as Rhel5.1 AP

 

I am connecting to host machine using VMware VI 3.0.

 

Thanks,

Santosh

 

 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://listman.redhat.com/archives/linux-cluster/attachments/20080214/da3fc22a/attachment.htm>

From p_pavlos at freemail.gr  Thu Feb 14 19:09:54 2008
From: p_pavlos at freemail.gr (Pavlos Parissis)
Date: Thu, 14 Feb 2008 20:09:54 +0100
Subject: [Linux-cluster] nfsd looping with 100% CPU
In-Reply-To: <20080212140948.GE9620@mail.lowpingbastards.de>
References: <20080212140948.GE9620@mail.lowpingbastards.de>
Message-ID: <20080214200954.7e64784e.p_pavlos@freemail.gr>

what makes you believe that this issue is related to the cluster software?
Do you experience the same problem while the cluster software isn't running?




From lhh at redhat.com  Thu Feb 14 20:54:00 2008
From: lhh at redhat.com (Lon Hohberger)
Date: Thu, 14 Feb 2008 15:54:00 -0500
Subject: [Linux-cluster] Xen DomU as Cluster service?
In-Reply-To: <47B3F894.6030801@riege.com>
References: <47B3F894.6030801@riege.com>
Message-ID: <1203022440.2408.16.camel@ayanami.boston.devel.redhat.com>

On Thu, 2008-02-14 at 09:15 +0100, Gunther Schlegel wrote:
> Hello,
> 
> In short: Is it a good idea to run Xen DomUs as a cluster service or is 
> there an easier way to do it?

While it is not particularly hard, we're working on an easier way,
too ;)

https://bugzilla.redhat.com/show_bug.cgi?id=432640


> -* If a Dom0 goes is shut down the DomUs need to be live migrated to 
> another Dom0 host during Dom0 shutdown.

This isn't done automatically from the cluster software at this point.
You should migrate VMs before shutting the machine down, or they will be
offline for a few seconds.  There's an open bugzilla (feature request)
to make this happen automatically, but it will always be safe to do the
migrations manually.


> -* If a Dom0 dies unexpectedly the DomUs need to be restarted on 
> antother hot.

That can be done; just set recovery to 'relocate' instead of
'restart' (the default) as part of the service configuration.


> Problems / open Questions:
> - xen supports life migration on system shutdown, but only to a specific 
>   host. As I will have a couple of hosts it is more desireable to 
> distribute the DomUs among the other Dom0 hosts instead of migrating 
> them all to the same Dom0 host. Has anyone done that before? Is it a 
> good option? Are there other options?

Since you know you're shutting a particular host down and are doing the
migration as part of the shutdown process, you can decide where they go.


> - I suppose I need the full cluster stuff anyways to deal with a crashed 
> Dom0, this implies to define a cluster service for each DomU?

Not necessarily, unless you want to manage migrations/where things start
yourself.

Generally speaking, you *do* need a cluster running for the domUs to be
clustered (unless you running all domUs on one host...) - even if you
are not using rgmanager to manage the domUs.

This is because fence_xvmd (libvirt-based fencing host) stores domU
states in distributed AIS checkpoints, which are accessed when a fencing
request comes in.

-- Lon



From lhh at redhat.com  Thu Feb 14 21:04:47 2008
From: lhh at redhat.com (Lon Hohberger)
Date: Thu, 14 Feb 2008 16:04:47 -0500
Subject: [Linux-cluster] Netmask bit set to 32 in service ip
In-Reply-To: <20080214025917.ojocuj0c4gco0ogw@easymail-app.hol.gr>
References: <20080213123347.ad6mnbk1coo44kwo@easymail-app.hol.gr>
	<1202927416.6841.8.camel@localhost.localdomain>
	<20080214025917.ojocuj0c4gco0ogw@easymail-app.hol.gr>
Message-ID: <1203023087.2408.23.camel@ayanami.boston.devel.redhat.com>

On Thu, 2008-02-14 at 02:59 +0200, Pavlos Parissis wrote:

> ocsi2# patch -p0 <  /tmp/ip.sh-netmask.patch
> patching file ip.sh

That's strange - it worked great for me.  Could you run:

   rg_test rules &> /tmp/foo.out

Look at /tmp/foo.out for a line that says:

   "Error storing ip: Duplicate"

If you see that, try cleaning up /usr/share/cluster.  Look for files
like:

   /usr/share/cluster/ip.sh~
   /usr/share/cluster/ip.rpm*

If there are any of these, you need to chmod -x them or remove them.  In
later versions, we will ignore some obvious ones (.rpm*, for example).

-- Lon



From jstoner at opsource.net  Thu Feb 14 22:15:57 2008
From: jstoner at opsource.net (Jeff Stoner)
Date: Thu, 14 Feb 2008 22:15:57 -0000
Subject: [Linux-cluster] Conga question
In-Reply-To: <1203023087.2408.23.camel@ayanami.boston.devel.redhat.com>
Message-ID: <38A48FA2F0103444906AD22E14F1B5A306E2A50C@mailxchg01.corp.opsource.net>

Can Conga (luci), as shipped with Redhat 4 or 5, authenticate against an
external data store (LDAP, Active Directory, a csv file, whatever)?

Can Conga be clustered? Anyone have any pointers for doing so?

--Jeff
Sr. Systems Engineer

OpSource, Inc.
www.opsource.net
"Your Success is Our Success"
 



From rpeterso at redhat.com  Thu Feb 14 22:49:14 2008
From: rpeterso at redhat.com (Bob Peterson)
Date: Thu, 14 Feb 2008 16:49:14 -0600
Subject: [Linux-cluster] no version for "gfs2_unmount_lockproto"
In-Reply-To: <87y79oomh8.fsf@szonett.ki.iif.hu>
References: <878x1q59hl.fsf@szonett.ki.iif.hu>
	<1202841274.2701.15.camel@technetium.msp.redhat.com>
	<87skzxq2wm.fsf@szonett.ki.iif.hu>
	<1202856202.2701.43.camel@technetium.msp.redhat.com>
	<87bq6lp8nv.fsf@szonett.ki.iif.hu>
	<1202915922.2701.69.camel@technetium.msp.redhat.com>
	<87y79oomh8.fsf@szonett.ki.iif.hu>
Message-ID: <1203029354.2701.90.camel@technetium.msp.redhat.com>

On Wed, 2008-02-13 at 17:22 +0100, Ferenc Wagner wrote:
> *Here* comes something possibly interesting, after fence_tool join:
> 
> fenced[4543]: fencing deferred to prior member
> 
> Though it doesn't look like node3 (which has the filesystem mounted)
> would want to fence node1 (which has this message in its syslog).  Is
> there a command available to find out the current fencing status or
> history?

Not as far as I know.  You should probably look in the /var/log/messages
on all the nodes to see which node decided it needed to fence the other
and why.  Perhaps it's not letting you mount gfs because of a pending
fence operation.  You could do cman_tool services to see the status
of the cluster from all nodes.

> Well, it helps on the node which has the filesystem mounted.  Of
> course not on the other.  Is gfs_tool supposed to work on mounted
> filesystems only?  Probably so.

Some of the gfs_tool commands like "gfs_tool sb" need a device
and others like "gfs_tool lockdump" need a mount point.  The man
page says which requires which.

> Do you think I should apply them?  It doesn't sound like they would
> help with this problem.

Well, the patches won't help solve the root issue, which is why the
mount is failing in the first place.

Another thing you can try is mounting it with the mount helper
manually, with verbose mode, by doing something like this:

/sbin/mount.gfs -v -o users -t gfs /dev/your/device /your/mount/point

And see what information it gives you.  Using the straight mount
command won't put the mount helper into verbose mode, so you may
get more information that way.

Perhaps you should also try "group_tool dump gfs" to see if there are
error messages from the gfs control daemon pertaining to gfs and
why the mount failed.

> Thanks for the clarification.  And what does that deferred fencing
> mean?

That means some node decided it was necessary to fence another node
and it is waiting for that fence to complete.  If there's a pending
fence of a node that's not completing, check to make sure your
fence device is configured and working properly.

Regards,

Bob Peterson
Red Hat GFS




From wferi at niif.hu  Fri Feb 15 02:56:31 2008
From: wferi at niif.hu (Ferenc Wagner)
Date: Fri, 15 Feb 2008 03:56:31 +0100
Subject: [Linux-cluster] no version for "gfs2_unmount_lockproto"
In-Reply-To: <1203029354.2701.90.camel@technetium.msp.redhat.com> (Bob
	Peterson's message of "Thu, 14 Feb 2008 16:49:14 -0600")
References: <878x1q59hl.fsf@szonett.ki.iif.hu>
	<1202841274.2701.15.camel@technetium.msp.redhat.com>
	<87skzxq2wm.fsf@szonett.ki.iif.hu>
	<1202856202.2701.43.camel@technetium.msp.redhat.com>
	<87bq6lp8nv.fsf@szonett.ki.iif.hu>
	<1202915922.2701.69.camel@technetium.msp.redhat.com>
	<87y79oomh8.fsf@szonett.ki.iif.hu>
	<1203029354.2701.90.camel@technetium.msp.redhat.com>
Message-ID: <87myq3hqqo.fsf@szonett.ki.iif.hu>

Hi Bob,

You can skip to the middle; I leave my ramblings here since I've typed
them already...

Bob Peterson <rpeterso at redhat.com> writes:

> On Wed, 2008-02-13 at 17:22 +0100, Ferenc Wagner wrote:
>> *Here* comes something possibly interesting, after fence_tool join:
>> 
>> fenced[4543]: fencing deferred to prior member
>> 
>> Though it doesn't look like node3 (which has the filesystem mounted)
>> would want to fence node1 (which has this message in its syslog).  Is
>> there a command available to find out the current fencing status or
>> history?
>
> Not as far as I know.  You should probably look in the /var/log/messages
> on all the nodes to see which node decided it needed to fence the other
> and why.  Perhaps it's not letting you mount gfs because of a pending
> fence operation.  You could do cman_tool services to see the status
> of the cluster from all nodes.

On node3, which has the GFS mounted:

# cman_tool services
type             level name     id       state       
fence            0     default  00010001 none        
[1 3]
dlm              1     clvmd    00030001 none        
[1 3]
dlm              1     test     00050003 none        
[3]
gfs              2     test     00040003 none        
[3]

On node1, which can't mount the filesystem, the first half is the
same, and the second half (dlm and gfs) is missing.

There are failed fence attempts in the logs of node3 from a couple of
days ago.  Since then, node1 was rebooted a couple of times; I also
stopped the cluster infrastructure on node3 (back to killing ccsd).
Then brought up the two nodes simultaneously, starting fenced with the
-c option; activation of the clustered VG propagated to the other node
as expected.  After all this, node1 still can't mount the filesystem.
Node3 can, but it seemingly doesn't influence node1...

>> Well, it helps on the node which has the filesystem mounted.  Of
>> course not on the other.  Is gfs_tool supposed to work on mounted
>> filesystems only?  Probably so.
>
> Some of the gfs_tool commands like "gfs_tool sb" need a device
> and others like "gfs_tool lockdump" need a mount point.  The man
> page says which requires which.

Exactly.  Too bad I didn't care to check earlyer.  Sorry for that.

> Another thing you can try is mounting it with the mount helper
> manually, with verbose mode, by doing something like this:
>
> /sbin/mount.gfs -v -o users -t gfs /dev/your/device /your/mount/point
>
> And see what information it gives you.  Using the straight mount
> command won't put the mount helper into verbose mode, so you may
> get more information that way.

Not only more info, but... see:

# mount -t gfs /dev/gfs/test /mnt
mount: wrong fs type, bad option, bad superblock on /dev/gfs/test,
       missing codepage or other error
       In some cases useful info is found in syslog - try
       dmesg | tail  or so

# /sbin/mount.gfs -v -o users -t gfs /dev/gfs/test /mnt
bash: /sbin/mount.gfs: No such file or directory
# /usr/sbin/mount.gfs -v -o users -t gfs /dev/gfs/test /mnt
/usr/sbin/mount.gfs: mount /dev/mapper/gfs-test /mnt
/usr/sbin/mount.gfs: parse_opts: opts = "users"
/usr/sbin/mount.gfs:   set flag 0 for "users", flags = 0
/usr/sbin/mount.gfs: parse_opts: flags = 0
/usr/sbin/mount.gfs: parse_opts: extra = ""
/usr/sbin/mount.gfs: parse_opts: hostdata = ""
/usr/sbin/mount.gfs: parse_opts: lockproto = ""
/usr/sbin/mount.gfs: parse_opts: locktable = ""
/usr/sbin/mount.gfs: message to gfs_controld: asking to join mountgroup:
/usr/sbin/mount.gfs: write "join /mnt gfs lock_dlm pilot:test users /dev/mapper/gfs-test"
/usr/sbin/mount.gfs: message from gfs_controld: response to join request:
/usr/sbin/mount.gfs: lock_dlm_join: read "0"
/usr/sbin/mount.gfs: message from gfs_controld: mount options:
/usr/sbin/mount.gfs: lock_dlm_join: read "hostdata=jid=1:id=65539:first=0"
/usr/sbin/mount.gfs: lock_dlm_join: hostdata: "hostdata=jid=1:id=65539:first=0"
/usr/sbin/mount.gfs: lock_dlm_join: extra_plus: "hostdata=jid=1:id=65539:first=0"
/usr/sbin/mount.gfs: mount(2) ok
/usr/sbin/mount.gfs: lock_dlm_mount_result: write "mount_result /mnt gfs 0"
/usr/sbin/mount.gfs: read_proc_mounts: device = "/dev/mapper/gfs-test"
/usr/sbin/mount.gfs: read_proc_mounts: opts = "rw,hostdata=jid=1:id=65539:first=0"

Which for me means that the mount tool couldn't find the helper as I
put it into /usr/sbin instead of /sbin (probably some unfortunate
configure option or installation choice -- it's in /sbin on node3
which runs the cluster suite compiled agains the previous kernel).  I
will investigate this after having some good sleep.

Since the overly general error message is from mount, not from the
mount.gfs helper, you probably can't do much for improving it.  But
explicitly invoking the helper in verbose mode looks like a very
powerful troubleshooting trick!

> Perhaps you should also try "group_tool dump gfs" to see if there are
> error messages from the gfs control daemon pertaining to gfs and
> why the mount failed.

That's another interesting information source.  Still it wasn't enough
for me to get out of this trap: after the above successful mount, I
unmounted the GFS with the stock umount, which again coultn't find the
helper, but did the job nevertheless.  Except for leaving the mount
group, so that I can mount the filesystem again...  Now the helper
says:

message to gfs_controld: asking to join mountgroup:
write "join /mnt gfs lock_dlm pilot:test users /dev/mapper/gfs-test"
mount point already used or other mount in progress
error mounting lockproto lock_dlm

and umount.gfs can't help as it doesn't find the mount in
/proc/mounts...  Is it possible to fix this or do I have to reboot?

>> Thanks for the clarification.  And what does that deferred fencing
>> mean?
>
> That means some node decided it was necessary to fence another node
> and it is waiting for that fence to complete.  If there's a pending
> fence of a node that's not completing, check to make sure your
> fence device is configured and working properly.

How could I find out about a pending fence?  Only by periodic messages
in the syslog?
-- 
Thanks,
Feri.



From raziebe at gmail.com  Fri Feb 15 07:32:40 2008
From: raziebe at gmail.com (Raz)
Date: Fri, 15 Feb 2008 09:32:40 +0200
Subject: [Linux-cluster] centos5 cman-kernel packacge question
Message-ID: <5d96567b0802142332q3560f792v8629be27245fd154@mail.gmail.com>

is there a cman-kernel rpm for linux kernel 2.6.18-8 ?
thank you

-- 
Raz



From p_pavlos at freemail.gr  Fri Feb 15 08:13:47 2008
From: p_pavlos at freemail.gr (Pavlos Parissis)
Date: Fri, 15 Feb 2008 10:13:47 +0200
Subject: [Linux-cluster] SOLVED Netmask bit set to 32 in service ip
In-Reply-To: <1203023087.2408.23.camel@ayanami.boston.devel.redhat.com>
References: <20080213123347.ad6mnbk1coo44kwo@easymail-app.hol.gr>
	<1202927416.6841.8.camel@localhost.localdomain>
	<20080214025917.ojocuj0c4gco0ogw@easymail-app.hol.gr>
	<1203023087.2408.23.camel@ayanami.boston.devel.redhat.com>
Message-ID: <20080215101347.kerwubjpc0osc4gs@easymail-app.hol.gr>

Quoting Lon Hohberger <lhh at redhat.com>:

> On Thu, 2008-02-14 at 02:59 +0200, Pavlos Parissis wrote:
>
>> ocsi2# patch -p0 <  /tmp/ip.sh-netmask.patch
>> patching file ip.sh
>
> That's strange - it worked great for me.  Could you run:
>
>    rg_test rules &> /tmp/foo.out
>
> Look at /tmp/foo.out for a line that says:
>
>    "Error storing ip: Duplicate"
>
> If you see that, try cleaning up /usr/share/cluster.  Look for files
> like:
>
>    /usr/share/cluster/ip.sh~
>    /usr/share/cluster/ip.rpm*
ocsi1# cd /usr/share/cluster/
ocsi1# ls -sl ip.*
20 -rwxr-xr-x  1 root root 18248 Aug  2  2006 ip.sh
ocsi1# cp -p ip.sh /root/ip.sh-ORIGINAL
ocsi1# grep -A 1 -B 4 '10.10.21.138' /etc/cluster/cluster.conf
     <service domain="FirstDomain" name="ppr1" autostart="1"  
recovery="relocate">
       <script name="ppr1" file="/usr/local/wsb/scripts/rhc_ppr1"/>
       <ip monitor_link="1" address="10.10.21.71"/>
       <fs device="/dev/sdd1" mountpoint="/usr/omg_ppr"  
force_unmount="1" name="/usr/omg_ppr" fstype="ext3"/>
       <ip monitor_link="1" address="10.10.21.138"/>
     </service>
ocsi1#  ip add sh|grep  -B 3 '10.10.21.138'
     link/ether 00:19:bb:3b:ac:89 brd ff:ff:ff:ff:ff:ff
     inet 10.10.21.132/26 brd 10.10.21.191 scope global bond0
     inet 10.10.21.142/32 scope global bond0
     inet 10.10.21.138/32 scope global bond0

ocsi1# cat /tmp/ip.sh-netmask.patch
Index: ip.sh
===================================================================
RCS file: /cvs/cluster/cluster/rgmanager/src/resources/ip.sh,v
retrieving revision 1.5.2.17
diff -u -r1.5.2.17 ip.sh
--- ip.sh       22 Mar 2007 23:15:59 -0000      1.5.2.17
+++ ip.sh       13 Feb 2008 18:28:12 -0000
@@ -692,6 +692,10 @@
                         if [ $? -ne 0 ]; then
                                 continue
                         fi
+
+                       if [ "${addr/\/*/}" = "${addr}" ]; then
+                               addr="$addr/$maskbits"
+                       fi
                         ocf_log info "Adding IPv4 address $addr to $dev"
                 fi
                 if [ "$1" = "del" ]; then
ocsi1# patch -p0 <  /tmp/ip.sh-netmask.patch
patching file ip.sh
ocsi1# clusvcadm -R ppr1
Member ocsi1-cluster trying to restart ppr1...success
ocsi1#  ip add sh|grep  -B 3 '10.10.21.138'
     link/ether 00:19:bb:3b:ac:89 brd ff:ff:ff:ff:ff:ff
     inet 10.10.21.132/26 brd 10.10.21.191 scope global bond0
     inet 10.10.21.142/32 scope global bond0
     inet 10.10.21.138/26 scope global secondary bond0

It works now and I know why it didn't work before.
The last time I saved a copy of the ip.sh under /usr/share/cluster,  
reading you comment bellow I can guess that the backup file was used  
and not the patched file, even the backup file had a name ip.sh-bak.

I am sorry but I did expect from the cluster to pick up the backup file.
I should haven't saved the backup file under the same directory.

Thanks for your help.




>
> If there are any of these, you need to chmod -x them or remove them.  In
> later versions, we will ignore some obvious ones (.rpm*, for example).
>
> -- Lon
>
> --
> Linux-cluster mailing list
> Linux-cluster at redhat.com
> https://www.redhat.com/mailman/listinfo/linux-cluster
>






From mad at wol.de  Fri Feb 15 09:09:22 2008
From: mad at wol.de (Marc - A. Dahlhaus [ Administration | Westermann GmbH ])
Date: Fri, 15 Feb 2008 10:09:22 +0100
Subject: [Linux-cluster] no version for "gfs2_unmount_lockproto"
In-Reply-To: <87myq3hqqo.fsf@szonett.ki.iif.hu>
References: <878x1q59hl.fsf@szonett.ki.iif.hu>
	<1202841274.2701.15.camel@technetium.msp.redhat.com>
	<87skzxq2wm.fsf@szonett.ki.iif.hu>
	<1202856202.2701.43.camel@technetium.msp.redhat.com>
	<87bq6lp8nv.fsf@szonett.ki.iif.hu>
	<1202915922.2701.69.camel@technetium.msp.redhat.com>
	<87y79oomh8.fsf@szonett.ki.iif.hu>
	<1203029354.2701.90.camel@technetium.msp.redhat.com>
	<87myq3hqqo.fsf@szonett.ki.iif.hu>
Message-ID: <1203066562.11649.16.camel@marc>

Hello Ferenc,

Am Freitag, den 15.02.2008, 03:56 +0100 schrieb Ferenc Wagner:
> 
> How could I find out about a pending fence?  Only by periodic messages
> in the syslog?

"cman_tool nodes" is your friend here.
Look for a status value of "F".
The man page of cman_tool has more info on this.


Marc




From p_pavlos at freemail.gr  Fri Feb 15 09:44:24 2008
From: p_pavlos at freemail.gr (Pavlos Parissis)
Date: Fri, 15 Feb 2008 11:44:24 +0200
Subject: [Linux-cluster] config issuse or bug in 4.u4 for nfs exports
In-Reply-To: <20080214142830.n1e86e52ckks88oc@easymail-app.hol.gr>
References: <20080214142830.n1e86e52ckks88oc@easymail-app.hol.gr>
Message-ID: <20080215114424.2ga7t85o4kc0wgks@easymail-app.hol.gr>

Quoting Pavlos Parissis <p_pavlos at freemail.gr>:

> Hi,
>
> I am building a NFS Active/Passive cluster using ext3 filesystem and I
> don't know if I have a configuration issue or I come across a bug.
>
> My service, nfs1, is started without problems but there is no nfs
> export available.
>
> I went through the list and I found this thread
> http://marc.info/?l=redhat-linux-cluster&m=118764091712577&w=2
>
> I tried to find any evidence of this by looking at bug reports and the
> release notes of 4.5,4.6 and 5.0 but I couldn't find any thing.
>
> Could you please someone give me an idea?

Well I couldn't find why cluster couldn't handle NFS share.
As a result I made a small script for starting/stopping the NFS shares  
and modified my service accordingly.


  <service domain="ThirdDomain" name="nfs1" autostart="1" recovery="relocate">
       <ip monitor_link="1" address="10.10.21.73"/>
       <ip monitor_link="1" address="10.10.21.142"/>
       <fs device="/dev/sdb2" mountpoint="/nfs_omg_data"  
force_unmount="1" name="/nfs_omg_data" fstype="ext3"/>
       <fs device="/dev/sdb3" mountpoint="/nfs_apps" force_unmount="1"  
name="/nfs_apps" fstype="ext3"/>
       <fs device="/dev/sdb4" mountpoint="/nfs_cdr_central"  
force_unmount="1" name="/nfs_cdr_central" fstype="ext3"/>
       <script name="nfs1" file="/usr/local/wsb/scripts/rhc_nfs1"/>
     </service>


ocsi3# cat /usr/local/wsb/scripts/rhc_nfs1
#!/bin/sh
. /opt/ngp/tools/lib/ud_functions
check_daemons()
{
    NFS_DAEMONS="nfsd rpc.mountd rpc.statd"

    for daemon in $NFS_DAEMONS; do
        ps -ef | grep "$daemon" | grep -v grep >/dev/null 2>&1
        if [ $? -ne 0 ]; then
           log "NFS daemon $daemon is not running."
           return 1
        fi
    done

    return 0
}
check_shares()
{
    NFS_SHARES="/nfs_omg_data /nfs_apps /nfs_cdr_central"

    for share in $NFS_SHARES; do
        exportfs|grep "$share" >/dev/null 2>&1
        if [ $? -ne 0 ]; then
           log "$share is not shared."
           return 1
        fi
    done

    return 0
}
check_mounts()
{
   MOUNTS="/nfs_cdr_central /nfs_omg_data  /nfs_apps"

   for mount in $MOUNTS; do
      mount|grep $mount >/dev/null 2>&1
      if [ $? -ne 0 ]; then
         log "$mount file system isn't mounted"
         return 1
      fi
   done

   return 0
}

if [ "$1" = "start" ]; then
    log "Checking for NFS daemons"
    if ! check_daemons; then
       exit 1
    fi

    log "Checking for mounts"
    if ! check_mounts; then
       exit 1
    fi

    log "Starting NFS shares"
    exportfs -o rw 10.10.21.128/26:/nfs_omg_data
    exportfs -o rw 10.10.21.128/26:/nfs_apps
    exportfs -o rw 10.10.21.128/26:/nfs_cdr_central
    exit 0

elif [ "$1" = "stop" ]; then
    log "Stopping the NFS shares"
    exportfs -u 10.10.21.128/26:/nfs_omg_data
    exportfs -u 10.10.21.128/26:/nfs_apps
    exportfs -u 10.10.21.128/26:/nfs_cdr_central
    exit 0

elif [ "$1" = "status" ]; then
    if check_mounts; then
       # Disks mounted go and check daemons
       if ! check_daemons; then
          exit 1
       elif ! check_shares ; then
          exit 1
       fi
    else
       # Disks not mounted
       exit 1
    fi

   exit 0

else
    log "Unknown argument exit nicely"
    exit 0
fi






From mad at wol.de  Fri Feb 15 09:45:50 2008
From: mad at wol.de (Marc - A. Dahlhaus [ Administration | Westermann GmbH ])
Date: Fri, 15 Feb 2008 10:45:50 +0100
Subject: [Linux-cluster] no version for "gfs2_unmount_lockproto"
In-Reply-To: <1203066562.11649.16.camel@marc>
References: <878x1q59hl.fsf@szonett.ki.iif.hu>
	<1202841274.2701.15.camel@technetium.msp.redhat.com>
	<87skzxq2wm.fsf@szonett.ki.iif.hu>
	<1202856202.2701.43.camel@technetium.msp.redhat.com>
	<87bq6lp8nv.fsf@szonett.ki.iif.hu>
	<1202915922.2701.69.camel@technetium.msp.redhat.com>
	<87y79oomh8.fsf@szonett.ki.iif.hu>
	<1203029354.2701.90.camel@technetium.msp.redhat.com>
	<87myq3hqqo.fsf@szonett.ki.iif.hu>  <1203066562.11649.16.camel@marc>
Message-ID: <1203068750.11649.26.camel@marc>

Hello List,

Am Freitag, den 15.02.2008, 10:09 +0100 schrieb Marc - A. Dahlhaus
[ Administration | Westermann GmbH ]:
> Hello Ferenc,
> 
> Am Freitag, den 15.02.2008, 03:56 +0100 schrieb Ferenc Wagner:
> > 
> > How could I find out about a pending fence?  Only by periodic messages
> > in the syslog?
> 
> "cman_tool nodes" is your friend here.
> Look for a status value of "F".
> The man page of cman_tool has more info on this.

The openais based cluster suite (the one in RHEL5) doesn't have a status
"F" for a fenced node. I'm a little confused right now as the man pages
also have information on the status values.

> 
> Marc
> 
> 
> --
> Linux-cluster mailing list
> Linux-cluster at redhat.com
> https://www.redhat.com/mailman/listinfo/linux-cluster



From wferi at niif.hu  Fri Feb 15 09:59:40 2008
From: wferi at niif.hu (Ferenc Wagner)
Date: Fri, 15 Feb 2008 10:59:40 +0100
Subject: [Linux-cluster] no version for "gfs2_unmount_lockproto"
In-Reply-To: <1203066562.11649.16.camel@marc> (mad@wol.de's message of "Fri,
	15 Feb 2008 10:09:22 +0100")
References: <878x1q59hl.fsf@szonett.ki.iif.hu>
	<1202841274.2701.15.camel@technetium.msp.redhat.com>
	<87skzxq2wm.fsf@szonett.ki.iif.hu>
	<1202856202.2701.43.camel@technetium.msp.redhat.com>
	<87bq6lp8nv.fsf@szonett.ki.iif.hu>
	<1202915922.2701.69.camel@technetium.msp.redhat.com>
	<87y79oomh8.fsf@szonett.ki.iif.hu>
	<1203029354.2701.90.camel@technetium.msp.redhat.com>
	<87myq3hqqo.fsf@szonett.ki.iif.hu> <1203066562.11649.16.camel@marc>
Message-ID: <87ir0qilpv.fsf@szonett.ki.iif.hu>

"Marc - A. Dahlhaus [ Administration | Westermann GmbH ]" <mad at wol.de>
writes:

> Hello Ferenc,
>
> Am Freitag, den 15.02.2008, 03:56 +0100 schrieb Ferenc Wagner:
>
>> How could I find out about a pending fence?  Only by periodic messages
>> in the syslog?
>
> "cman_tool nodes" is your friend here.
> Look for a status value of "F".
> The man page of cman_tool has more info on this.

Thanks!  Both live nodes have status M (member?) now, so this doesn't
seem to be the problem.  My man page doesn't describe the meanings of
the flags, unfortunately...
-- 
Regards,
Feri.



From ccaulfie at redhat.com  Fri Feb 15 10:18:50 2008
From: ccaulfie at redhat.com (Christine Caulfield)
Date: Fri, 15 Feb 2008 10:18:50 +0000
Subject: [Linux-cluster] no version for "gfs2_unmount_lockproto"
In-Reply-To: <87ir0qilpv.fsf@szonett.ki.iif.hu>
References: <878x1q59hl.fsf@szonett.ki.iif.hu>	<1202841274.2701.15.camel@technetium.msp.redhat.com>	<87skzxq2wm.fsf@szonett.ki.iif.hu>	<1202856202.2701.43.camel@technetium.msp.redhat.com>	<87bq6lp8nv.fsf@szonett.ki.iif.hu>	<1202915922.2701.69.camel@technetium.msp.redhat.com>	<87y79oomh8.fsf@szonett.ki.iif.hu>	<1203029354.2701.90.camel@technetium.msp.redhat.com>	<87myq3hqqo.fsf@szonett.ki.iif.hu>
	<1203066562.11649.16.camel@marc> <87ir0qilpv.fsf@szonett.ki.iif.hu>
Message-ID: <47B5670A.7070004@redhat.com>

Ferenc Wagner wrote:
> "Marc - A. Dahlhaus [ Administration | Westermann GmbH ]" <mad at wol.de>
> writes:
> 
>> Hello Ferenc,
>>
>> Am Freitag, den 15.02.2008, 03:56 +0100 schrieb Ferenc Wagner:
>>
>>> How could I find out about a pending fence?  Only by periodic messages
>>> in the syslog?
>> "cman_tool nodes" is your friend here.
>> Look for a status value of "F".
>> The man page of cman_tool has more info on this.
> 
> Thanks!  Both live nodes have status M (member?) now, so this doesn't
> seem to be the problem.  My man page doesn't describe the meanings of
> the flags, unfortunately...

Later versions of cman_tool have the flags explained in the man page.

There is no 'F' flag, but you can get some fence details from the command

cman_tool nodes -f

-- 

Chrissie



From wferi at niif.hu  Fri Feb 15 11:18:36 2008
From: wferi at niif.hu (Ferenc Wagner)
Date: Fri, 15 Feb 2008 12:18:36 +0100
Subject: [Linux-cluster] no version for "gfs2_unmount_lockproto"
In-Reply-To: <47B5670A.7070004@redhat.com> (Christine Caulfield's message of
	"Fri, 15 Feb 2008 10:18:50 +0000")
References: <878x1q59hl.fsf@szonett.ki.iif.hu>
	<1202841274.2701.15.camel@technetium.msp.redhat.com>
	<87skzxq2wm.fsf@szonett.ki.iif.hu>
	<1202856202.2701.43.camel@technetium.msp.redhat.com>
	<87bq6lp8nv.fsf@szonett.ki.iif.hu>
	<1202915922.2701.69.camel@technetium.msp.redhat.com>
	<87y79oomh8.fsf@szonett.ki.iif.hu>
	<1203029354.2701.90.camel@technetium.msp.redhat.com>
	<87myq3hqqo.fsf@szonett.ki.iif.hu> <1203066562.11649.16.camel@marc>
	<87ir0qilpv.fsf@szonett.ki.iif.hu> <47B5670A.7070004@redhat.com>
Message-ID: <87ejbeii2b.fsf@szonett.ki.iif.hu>

Christine Caulfield <ccaulfie at redhat.com> writes:

> Ferenc Wagner wrote:
>> "Marc - A. Dahlhaus [ Administration | Westermann GmbH ]" <mad at wol.de>
>> writes:
>> 
>>> Hello Ferenc,
>>>
>>> Am Freitag, den 15.02.2008, 03:56 +0100 schrieb Ferenc Wagner:
>>>
>>>> How could I find out about a pending fence?  Only by periodic messages
>>>> in the syslog?
>>> "cman_tool nodes" is your friend here.
>>> Look for a status value of "F".
>>> The man page of cman_tool has more info on this.
>> 
>> Thanks!  Both live nodes have status M (member?) now, so this doesn't
>> seem to be the problem.  My man page doesn't describe the meanings of
>> the flags, unfortunately...
>
> Later versions of cman_tool have the flags explained in the man page.
> There is no 'F' flag, but you can get some fence details from the command
>
> cman_tool nodes -f

Ah.  For me, cman_tool nodes produces the exact same output as
cman_tool nodes -f.  This is with cluster-2.01.00.  But thanks for the
useful info.

Anyway, problem solved: it was binaries (mainly mount.gfs) ending up
in /usr/sbin instead of /sbin.  After correcting that, all three nodes
are up and happily sharing their GFS.  Thanks for the help, everybody!
I certainly learnt a lot during troubleshooting this.
-- 
Regards,
Feri.



From gordan at bobich.net  Fri Feb 15 12:54:44 2008
From: gordan at bobich.net (gordan at bobich.net)
Date: Fri, 15 Feb 2008 12:54:44 +0000 (GMT)
Subject: [Linux-cluster] fence_tool -c -w join failing
Message-ID: <alpine.LRH.1.00.0802151246100.19273@skynet.shatteredsilicon.net>

Hi,

I have a weird problem that I can't figure out. I have a two node cluster 
(<cman two_node="1" expected_votes="1">), which means that a node should 
be quorate on it's own, and there should be no problems for it to join 
it's own fence domain (presumably).

But when I do:
service cman start

All the components up to fenced start, but:
fence -c -w join
waits until it times out and never starts.

The logs don't seem to reveal anything other than that fenced failed to 
start. What are the likely causes of this kind of a problem? I don't have 
any real fencing devices defined (yet) in my cluster.conf, only the 
following stub entry:

<fence>
 	<method name="1">
 		<device name = "foo"/>
 	</method>
</fence>

Gordan



From ccaulfie at redhat.com  Fri Feb 15 13:19:13 2008
From: ccaulfie at redhat.com (Christine Caulfield)
Date: Fri, 15 Feb 2008 13:19:13 +0000
Subject: [Linux-cluster] fence_tool -c -w join failing
In-Reply-To: <alpine.LRH.1.00.0802151246100.19273@skynet.shatteredsilicon.net>
References: <alpine.LRH.1.00.0802151246100.19273@skynet.shatteredsilicon.net>
Message-ID: <47B59151.5040504@redhat.com>

gordan at bobich.net wrote:
> Hi,
> 
> I have a weird problem that I can't figure out. I have a two node
> cluster (<cman two_node="1" expected_votes="1">), which means that a
> node should be quorate on it's own, and there should be no problems for
> it to join it's own fence domain (presumably).
> 
> But when I do:
> service cman start
> 
> All the components up to fenced start, but:
> fence -c -w join
> waits until it times out and never starts.
> 
> The logs don't seem to reveal anything other than that fenced failed to
> start. What are the likely causes of this kind of a problem? I don't
> have any real fencing devices defined (yet) in my cluster.conf, only the
> following stub entry:
> 
> <fence>
>     <method name="1">
>         <device name = "foo"/>
>     </method>
> </fence>

That's probably why. It's trying to fence the non-member nodes and its
failing because you don't have any valid fence devices.

Try starting fenced with '-D', it'll show more debugging information.

Chrissie



From rpeterso at redhat.com  Fri Feb 15 14:16:30 2008
From: rpeterso at redhat.com (Bob Peterson)
Date: Fri, 15 Feb 2008 08:16:30 -0600
Subject: [Linux-cluster] no version for "gfs2_unmount_lockproto"
In-Reply-To: <87ejbeii2b.fsf@szonett.ki.iif.hu>
References: <878x1q59hl.fsf@szonett.ki.iif.hu>
	<1202841274.2701.15.camel@technetium.msp.redhat.com>
	<87skzxq2wm.fsf@szonett.ki.iif.hu>
	<1202856202.2701.43.camel@technetium.msp.redhat.com>
	<87bq6lp8nv.fsf@szonett.ki.iif.hu>
	<1202915922.2701.69.camel@technetium.msp.redhat.com>
	<87y79oomh8.fsf@szonett.ki.iif.hu>
	<1203029354.2701.90.camel@technetium.msp.redhat.com>
	<87myq3hqqo.fsf@szonett.ki.iif.hu> <1203066562.11649.16.camel@marc>
	<87ir0qilpv.fsf@szonett.ki.iif.hu> <47B5670A.7070004@redhat.com>
	<87ejbeii2b.fsf@szonett.ki.iif.hu>
Message-ID: <1203084990.2701.94.camel@technetium.msp.redhat.com>

On Fri, 2008-02-15 at 12:18 +0100, Ferenc Wagner wrote:
> Ah.  For me, cman_tool nodes produces the exact same output as
> cman_tool nodes -f.  This is with cluster-2.01.00.  But thanks for the
> useful info.
> 
> Anyway, problem solved: it was binaries (mainly mount.gfs) ending up
> in /usr/sbin instead of /sbin.  After correcting that, all three nodes
> are up and happily sharing their GFS.  Thanks for the help, everybody!
> I certainly learnt a lot during troubleshooting this.

Hi Feri,

Make sure you have the unmount-helper, umount.gfs, in /sbin too.
That's why it had problems unmounting and didn't know it was unmounted
when you tried to mount it a second time (from a previous email).

Regards,

Bob Peterson
Red Hat GFS




From wferi at niif.hu  Fri Feb 15 14:41:48 2008
From: wferi at niif.hu (Ferenc Wagner)
Date: Fri, 15 Feb 2008 15:41:48 +0100
Subject: [Linux-cluster] no version for "gfs2_unmount_lockproto"
In-Reply-To: <1203084990.2701.94.camel@technetium.msp.redhat.com> (Bob
	Peterson's message of "Fri, 15 Feb 2008 08:16:30 -0600")
References: <878x1q59hl.fsf@szonett.ki.iif.hu>
	<1202841274.2701.15.camel@technetium.msp.redhat.com>
	<87skzxq2wm.fsf@szonett.ki.iif.hu>
	<1202856202.2701.43.camel@technetium.msp.redhat.com>
	<87bq6lp8nv.fsf@szonett.ki.iif.hu>
	<1202915922.2701.69.camel@technetium.msp.redhat.com>
	<87y79oomh8.fsf@szonett.ki.iif.hu>
	<1203029354.2701.90.camel@technetium.msp.redhat.com>
	<87myq3hqqo.fsf@szonett.ki.iif.hu> <1203066562.11649.16.camel@marc>
	<87ir0qilpv.fsf@szonett.ki.iif.hu> <47B5670A.7070004@redhat.com>
	<87ejbeii2b.fsf@szonett.ki.iif.hu>
	<1203084990.2701.94.camel@technetium.msp.redhat.com>
Message-ID: <87abm2i8nn.fsf@szonett.ki.iif.hu>

Bob Peterson <rpeterso at redhat.com> writes:

> On Fri, 2008-02-15 at 12:18 +0100, Ferenc Wagner wrote:
>
>> Anyway, problem solved: it was binaries (mainly mount.gfs) ending up
>> in /usr/sbin instead of /sbin.  After correcting that, all three nodes
>> are up and happily sharing their GFS.  Thanks for the help, everybody!
>> I certainly learnt a lot during troubleshooting this.
>
> Make sure you have the unmount-helper, umount.gfs, in /sbin too.
> That's why it had problems unmounting and didn't know it was unmounted
> when you tried to mount it a second time (from a previous email).

Hi Bob,

Sure, I figured that, only wondered whether there was a way out without
rebooting the node.  I rebooted eventually, and hopefully everything
is in place now.
-- 
Thanks,
Feri.



From lhh at redhat.com  Fri Feb 15 15:29:32 2008
From: lhh at redhat.com (Lon Hohberger)
Date: Fri, 15 Feb 2008 10:29:32 -0500
Subject: [Linux-cluster] SOLVED Netmask bit set to 32 in service ip
In-Reply-To: <20080215101347.kerwubjpc0osc4gs@easymail-app.hol.gr>
References: <20080213123347.ad6mnbk1coo44kwo@easymail-app.hol.gr>
	<1202927416.6841.8.camel@localhost.localdomain>
	<20080214025917.ojocuj0c4gco0ogw@easymail-app.hol.gr>
	<1203023087.2408.23.camel@ayanami.boston.devel.redhat.com>
	<20080215101347.kerwubjpc0osc4gs@easymail-app.hol.gr>
Message-ID: <1203089372.2408.42.camel@ayanami.boston.devel.redhat.com>

On Fri, 2008-02-15 at 10:13 +0200, Pavlos Parissis wrote:

> It works now and I know why it didn't work before.

Actually, it's luck... see below. ;)

> The last time I saved a copy of the ip.sh under /usr/share/cluster,  
> reading you comment bellow I can guess that the backup file was used  
> and not the patched file, even the backup file had a name ip.sh-bak.

It's because readdir() doesn't necessarily read things in alphabetic
sort order.  So, if the directory entry for 'ip.sh-original' came before
'ip.sh', 'ip.sh-original' would get picked as the provider for the 'ip'
resource.

However, if you remove a file or two and create new ones, there's a
chance that the directory entry might come after 'ip.sh'... making
things work!

The rule to remember is that we won't use anything in /usr/share/cluster
that does not have the execute permissions bit set, so you can create
backups in /usr/share/cluster -- just 'chmod -x' them :)

The theory for this mode of operation is that we don't have to impose
file name extension requirements on users and developers (for example,
SAP* have no extensions - they were developed by the open source
community)...

> I am sorry but I did expect from the cluster to pick up the backup file.

...The downside is that it traps unsuspecting users - such as
yourself. :)

Maybe we should put a 'README' file in /usr/share/cluster?  (Or at least
a FAQ entry on the wiki?)

-- Lon



From p_pavlos at freemail.gr  Fri Feb 15 15:42:34 2008
From: p_pavlos at freemail.gr (Pavlos Parissis)
Date: Fri, 15 Feb 2008 16:42:34 +0100
Subject: [Linux-cluster] SOLVED Netmask bit set to 32 in service ip
In-Reply-To: <1203089372.2408.42.camel@ayanami.boston.devel.redhat.com>
References: <20080213123347.ad6mnbk1coo44kwo@easymail-app.hol.gr>
	<1202927416.6841.8.camel@localhost.localdomain>
	<20080214025917.ojocuj0c4gco0ogw@easymail-app.hol.gr>
	<1203023087.2408.23.camel@ayanami.boston.devel.redhat.com>
	<20080215101347.kerwubjpc0osc4gs@easymail-app.hol.gr>
	<1203089372.2408.42.camel@ayanami.boston.devel.redhat.com>
Message-ID: <20080215164234.360f048e.p_pavlos@freemail.gr>

On Fri, 15 Feb 2008 10:29:32 -0500
Lon Hohberger <lhh at redhat.com> wrote:

> On Fri, 2008-02-15 at 10:13 +0200, Pavlos Parissis wrote:
> 
> > It works now and I know why it didn't work before.
> 
> Actually, it's luck... see below. ;)
> 
> > The last time I saved a copy of the ip.sh under /usr/share/cluster,  
> > reading you comment bellow I can guess that the backup file was used  
> > and not the patched file, even the backup file had a name ip.sh-bak.
> 
> It's because readdir() doesn't necessarily read things in alphabetic
> sort order.  So, if the directory entry for 'ip.sh-original' came before
> 'ip.sh', 'ip.sh-original' would get picked as the provider for the 'ip'
> resource.
> 
> However, if you remove a file or two and create new ones, there's a
> chance that the directory entry might come after 'ip.sh'... making
> things work!
> 
> The rule to remember is that we won't use anything in /usr/share/cluster
> that does not have the execute permissions bit set, so you can create
> backups in /usr/share/cluster -- just 'chmod -x' them :)
> 
> The theory for this mode of operation is that we don't have to impose
> file name extension requirements on users and developers (for example,
> SAP* have no extensions - they were developed by the open source
> community)...

I prefer to have restrictions and requirements set, make life more predictable...

> > I am sorry but I did expect from the cluster to pick up the backup file.
> 
> ...The downside is that it traps unsuspecting users - such as
> yourself. :)
> 
> Maybe we should put a 'README' file in /usr/share/cluster?  (Or at least
> a FAQ entry on the wiki?)

Both will be better - README files are faster to be found and wiki pages are better readable

Thanks for the explanation

Pavlos



From marcos at digitaltecnologia.info  Fri Feb 15 16:09:41 2008
From: marcos at digitaltecnologia.info (Marcos Ferreira da Silva)
Date: Fri, 15 Feb 2008 14:09:41 -0200
Subject: [Linux-cluster] XEN VM Cluster
In-Reply-To: <384334.37325.qm@web32112.mail.mud.yahoo.com>
References: <384334.37325.qm@web32112.mail.mud.yahoo.com>
Message-ID: <1203091781.3332.4.camel@matriz.digitaltecnologia.info>

The problem was the switch blocking multicast.

-  
_____________________________
Marcos Ferreira da Silva
DiGital Tecnologia
Uberl?ndia - MG
(34) 9154-0150 / 3226-2534


Em Ter, 2008-02-05 ?s 19:55 -0800, Ray Charles escreveu:
> Hi Marcos,
> 
> Here are 2 links I found usefull when doing what
> you're trying. 
> 
> http://www.linux.com/articles/55773
> 
> http://sources.redhat.com/cluster/wiki/VMClusterCookbook
> 
> I would also say be sure to give some attenttion to
> the multicast messages between the hosts, make sure
> that multicast is passing throught the switch. Seemed
> to be a gotcha for me, and there's docs on that part
> floating around.
> 
> -Ray
> 
> 
> 
> --- Marcos Ferreira da Silva
> <marcos at digitaltecnologia.info> wrote:
> 
> > I'm trying to do a two node cluster.
> > I want start a virtual machine at vserver1 and
> > reallocate it to vserver2 if node 1 stop.
> > The VM is installed in a shared HP storage.
> > This access is made with two Emulex Corporation
> > Zephyr-X LightPulse Fibre Channel Host Adapter.
> > If I start it manually which xm create its ok in
> > both servers.
> > The partition is a LVM in /dev/VG2/LV01.
> > I install virtual machine directly in this
> > partition.
> > The names vserver1 e vserv2 are in the /etc/hosts.
> > The cluster start but vserver2 join and after appear
> > "Member Left".
> > 
> > I think that my problem is in fence device.
> > I don't have any equipament.
> > I have only the servers, storage, NICs and Emulex.
> > 
> > I didn't find any manual for this situation.
> > 
> >  
> >      +--- SWITCH ---+
> >      |              |
> >      |              |  
> > +----------+     +----------+
> > | XEN      |     | XEN      |
> > |   maq1   |     |          |
> > |          |     |          |
> > | vserver1 |     | vserver2 |
> > +----------+     +----------+
> >      |              |
> >      |              |
> >     +----------------+
> >     |  HP Storage    |
> >     +----------------+
> > 
> > 
> > 
> > My cluster.conf is: 
> > 
> > <?xml version="1.0"?>
> > <cluster alias="cluster1" config_version="13"
> > name="cluster1">
> >         <fence_daemon clean_start="0"
> > post_fail_delay="0" post_join_delay="3"/>
> >         <fence_xvmd family="ipv4"
> > key_file="/etc/cluster/fence_xvm.key"/>
> >         <clusternodes>
> >                 <clusternode
> > name="vserver1.teste.br" nodeid="1" votes="1">
> >                         <fence>
> >                                 <method name="1">
> >                                         <device
> > domain="teste.br" name="maq1"/>
> >                                 </method>
> >                         </fence>
> >                 </clusternode>
> >                 <clusternode
> > name="vserver2.teste.br" nodeid="2" votes="1">
> >                         <fence/>
> >                 </clusternode>
> >         </clusternodes>
> >         <cman expected_votes="1" two_node="1"/>
> >         <fencedevices>
> >                 <fencedevice agent="fence_xvm"
> > name="maq1" auth="none"/>
> >         </fencedevices>
> >         <rm>
> >                 <failoverdomains>
> >                         <failoverdomain
> > name="fodMaq1" ordered="1" restricted="1">
> >                                 <failoverdomainnode
> > name="vserver1.teste.br" priority="1"/>
> >                                 <failoverdomainnode
> > name="vserver2.teste.br" priority="2"/>
> >                         </failoverdomain>
> >                 </failoverdomains>
> >                 <resources/>
> >                 <vm autostart="1" domain="fodMaq1"
> > exclusive="0" name="maq1" path="/etc/xen"
> > recovery="relocate"/>
> >         </rm>
> > </cluster>
> > 
> > 
> > ------------------------------
> > Marcos Ferreira da Silva
> > Digital Tecnologia
> > Uberlandia-MG
> > (34) 9154-0150 / 3226-2534
> > 
> > 
> > 
> > --
> > Linux-cluster mailing list
> > Linux-cluster at redhat.com
> >
> https://www.redhat.com/mailman/listinfo/linux-cluster
> > 
> 
> 
> 
>       ____________________________________________________________________________________
> Looking for last minute shopping deals?  
> Find them fast with Yahoo! Search.  http://tools.search.yahoo.com/newsearch/category.php?category=shopping





From jruemker at redhat.com  Fri Feb 15 19:18:33 2008
From: jruemker at redhat.com (John Ruemker)
Date: Fri, 15 Feb 2008 14:18:33 -0500
Subject: [Linux-cluster] centos5 cman-kernel packacge question
In-Reply-To: <5d96567b0802142332q3560f792v8629be27245fd154@mail.gmail.com>
References: <5d96567b0802142332q3560f792v8629be27245fd154@mail.gmail.com>
Message-ID: <47B5E589.40702@redhat.com>

In RHEL 5 (CentOS 5) cman was moved out of the kernel, so there is no 
longer a cman-kernel rpm.  You just need cman.

John

Raz wrote:
> is there a cman-kernel rpm for linux kernel 2.6.18-8 ?
> thank you
>
>   



From gordan at bobich.net  Fri Feb 15 20:04:46 2008
From: gordan at bobich.net (Gordan Bobic)
Date: Fri, 15 Feb 2008 20:04:46 +0000
Subject: [Linux-cluster] fence_tool -c -w join failing
In-Reply-To: <47B59151.5040504@redhat.com>
References: <alpine.LRH.1.00.0802151246100.19273@skynet.shatteredsilicon.net>
	<47B59151.5040504@redhat.com>
Message-ID: <47B5F05E.6050300@bobich.net>

Christine Caulfield wrote:
> gordan at bobich.net wrote:
>> Hi,
>>
>> I have a weird problem that I can't figure out. I have a two node
>> cluster (<cman two_node="1" expected_votes="1">), which means that a
>> node should be quorate on it's own, and there should be no problems for
>> it to join it's own fence domain (presumably).
>>
>> But when I do:
>> service cman start
>>
>> All the components up to fenced start, but:
>> fence -c -w join
>> waits until it times out and never starts.
>>
>> The logs don't seem to reveal anything other than that fenced failed to
>> start. What are the likely causes of this kind of a problem? I don't
>> have any real fencing devices defined (yet) in my cluster.conf, only the
>> following stub entry:
>>
>> <fence>
>>     <method name="1">
>>         <device name = "foo"/>
>>     </method>
>> </fence>
> 
> That's probably why. It's trying to fence the non-member nodes and its
> failing because you don't have any valid fence devices.

I'm not sure that's right, because I've had dozens of clusters work 
without fencing devices in various prototyping environments. So how does 
one start up an incomplete cluster without any fence devices?

> Try starting fenced with '-D', it'll show more debugging information.

I am not starting fenced directly, I'm doing it via
fence_tool -c -w join

That is supposed to start up fenced, according to documentation, but it 
doesn't include the -D option.

Gordan



From isplist at logicore.net  Fri Feb 15 20:33:18 2008
From: isplist at logicore.net (isplist at logicore.net)
Date: Fri, 15 Feb 2008 14:33:18 -0600
Subject: [Linux-cluster] Redundant (multipath)/Replicating NFS
Message-ID: <2008215143318.587253@leena>

I recall that there is a multipath tool for RHEL which allows one to have 
redundant SCSI/FC paths in case one goes away. 

Are there any tools which would accomplish the same with NFS?

Is there any way of replicating NFS data in real time rather than as a regular 
backup, such as RAID1 for example, and be able to fail over to the second path 
or NFS IP should the first fail.

Mike






From isplist at logicore.net  Fri Feb 15 20:36:18 2008
From: isplist at logicore.net (isplist at logicore.net)
Date: Fri, 15 Feb 2008 14:36:18 -0600
Subject: [Linux-cluster] Redundant (multipath)/Replicating NFS
Message-ID: <2008215143618.598119@leena>

I should point out that my current NFS servers have NDMP services installed. 





From ebaydaan at gmail.com  Fri Feb 15 20:43:54 2008
From: ebaydaan at gmail.com (Daan Biere)
Date: Fri, 15 Feb 2008 21:43:54 +0100
Subject: [Linux-cluster] Redundant (multipath)/Replicating NFS
In-Reply-To: <2008215143318.587253@leena>
References: <2008215143318.587253@leena>
Message-ID: <97a2dbb00802151243s5f8d41d1p88fb9638a6d75435@mail.gmail.com>

Hi,
As far as i know the only solution which can archive this is ddraid, i don't
know if 0.6 is production ready yet.....
http://sourceware.org/cluster/ddraid/

Kind Regards,
Daan Biere

2008/2/15, isplist at logicore.net <isplist at logicore.net>:
>
> I recall that there is a multipath tool for RHEL which allows one to have
> redundant SCSI/FC paths in case one goes away.
>
> Are there any tools which would accomplish the same with NFS?
>
> Is there any way of replicating NFS data in real time rather than as a
> regular
> backup, such as RAID1 for example, and be able to fail over to the second
> path
> or NFS IP should the first fail.
>
> Mike
>
>
>
>
>
> --
> Linux-cluster mailing list
> Linux-cluster at redhat.com
> https://www.redhat.com/mailman/listinfo/linux-cluster
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://listman.redhat.com/archives/linux-cluster/attachments/20080215/978fb4fb/attachment.htm>

From gordan at bobich.net  Fri Feb 15 20:47:37 2008
From: gordan at bobich.net (Gordan Bobic)
Date: Fri, 15 Feb 2008 20:47:37 +0000
Subject: [Linux-cluster] Redundant (multipath)/Replicating NFS
In-Reply-To: <2008215143318.587253@leena>
References: <2008215143318.587253@leena>
Message-ID: <47B5FA69.3020601@bobich.net>

isplist at logicore.net wrote:
> I recall that there is a multipath tool for RHEL which allows one to have 
> redundant SCSI/FC paths in case one goes away. 
> 
> Are there any tools which would accomplish the same with NFS?

If you have 2 NFS server you need replicated and failed over, you can 
use DRBD to replicate a virtual block device. You can have this in 
primary/primary mode with GFS on top, and you can then export the FS 
from both machines via NFS. If you use UDP NFS, you can have a floating 
IP address for the server that you fail over in case of a node failing. 
There may be a way to load balance NFS, too, but I've yet to see that 
actually work. If you are just failing over, you could run DRBD in 
standard mode without GFS. DRBD has heartbeat plugs.

> Is there any way of replicating NFS data in real time rather than as a regular 
> backup, such as RAID1 for example, and be able to fail over to the second path 
> or NFS IP should the first fail.

DRBD is effectively RAID1 over TCP/IP.

Gordan



From gordan at bobich.net  Fri Feb 15 20:50:20 2008
From: gordan at bobich.net (Gordan Bobic)
Date: Fri, 15 Feb 2008 20:50:20 +0000
Subject: [Linux-cluster] Redundant (multipath)/Replicating NFS
In-Reply-To: <97a2dbb00802151243s5f8d41d1p88fb9638a6d75435@mail.gmail.com>
References: <2008215143318.587253@leena>
	<97a2dbb00802151243s5f8d41d1p88fb9638a6d75435@mail.gmail.com>
Message-ID: <47B5FB0C.9060902@bobich.net>

Yeah, that looked great right up to the point where somebody pointed out 
that it has been removed from the RHC CVS tree. It looks like the 
project may be unmaintained. :'(

Shame, since it seems to be the only openly available technology of that 
kind.

Gordan

Daan Biere wrote:
> Hi,
> As far as i know the only solution which can archive this is ddraid, i 
> don't know if 0.6 is production ready yet.....
> http://sourceware.org/cluster/ddraid/
> 
> Kind Regards,
> Daan Biere
> 
> 2008/2/15, isplist at logicore.net <mailto:isplist at logicore.net> 
> <isplist at logicore.net <mailto:isplist at logicore.net>>:
> 
>     I recall that there is a multipath tool for RHEL which allows one to
>     have
>     redundant SCSI/FC paths in case one goes away.
> 
>     Are there any tools which would accomplish the same with NFS?
> 
>     Is there any way of replicating NFS data in real time rather than as
>     a regular
>     backup, such as RAID1 for example, and be able to fail over to the
>     second path
>     or NFS IP should the first fail.
> 
>     Mike
> 
> 
> 
> 
> 
>     --
>     Linux-cluster mailing list
>     Linux-cluster at redhat.com <mailto:Linux-cluster at redhat.com>
>     https://www.redhat.com/mailman/listinfo/linux-cluster
> 
> 
> 
> ------------------------------------------------------------------------
> 
> --
> Linux-cluster mailing list
> Linux-cluster at redhat.com
> https://www.redhat.com/mailman/listinfo/linux-cluster



From gordan at bobich.net  Fri Feb 15 21:42:14 2008
From: gordan at bobich.net (Gordan Bobic)
Date: Fri, 15 Feb 2008 21:42:14 +0000
Subject: [Linux-cluster] fence_tool -c -w join failing
In-Reply-To: <47B5F05E.6050300@bobich.net>
References: <alpine.LRH.1.00.0802151246100.19273@skynet.shatteredsilicon.net>	<47B59151.5040504@redhat.com>
	<47B5F05E.6050300@bobich.net>
Message-ID: <47B60736.2090703@bobich.net>

Just for reference, I've found out what was the problem that has been 
driving me nuts for a good few hours. It turns out I made a really lame 
schoolboy mistake.

Cluster components seem to rely heavily on the /etc/hosts file. If 
cluster.conf seems to be OK and all other settings check out, it could 
just be that there are incorrect references in the hosts file. I had 
cman_tool status reporting the node IP to be wrong, and it didn't tally 
up with any of the interfaces which were correctly set in cluster.conf 
(I changed the IP address since I first set up the cluster). It all 
seems to fail rather silently and without warnings. Correcting the 
/etc/hosts file makes the problem go away.

Anyway, I hope this comes in useful to somebody googling the archives in 
the future.

Gordan

Gordan Bobic wrote:
> Christine Caulfield wrote:
>> gordan at bobich.net wrote:
>>> Hi,
>>>
>>> I have a weird problem that I can't figure out. I have a two node
>>> cluster (<cman two_node="1" expected_votes="1">), which means that a
>>> node should be quorate on it's own, and there should be no problems for
>>> it to join it's own fence domain (presumably).
>>>
>>> But when I do:
>>> service cman start
>>>
>>> All the components up to fenced start, but:
>>> fence -c -w join
>>> waits until it times out and never starts.
>>>
>>> The logs don't seem to reveal anything other than that fenced failed to
>>> start. What are the likely causes of this kind of a problem? I don't
>>> have any real fencing devices defined (yet) in my cluster.conf, only the
>>> following stub entry:
>>>
>>> <fence>
>>>     <method name="1">
>>>         <device name = "foo"/>
>>>     </method>
>>> </fence>
>>
>> That's probably why. It's trying to fence the non-member nodes and its
>> failing because you don't have any valid fence devices.
> 
> I'm not sure that's right, because I've had dozens of clusters work 
> without fencing devices in various prototyping environments. So how does 
> one start up an incomplete cluster without any fence devices?
> 
>> Try starting fenced with '-D', it'll show more debugging information.
> 
> I am not starting fenced directly, I'm doing it via
> fence_tool -c -w join
> 
> That is supposed to start up fenced, according to documentation, but it 
> doesn't include the -D option.
> 
> Gordan
> 
> -- 
> Linux-cluster mailing list
> Linux-cluster at redhat.com
> https://www.redhat.com/mailman/listinfo/linux-cluster



From isplist at logicore.net  Fri Feb 15 21:44:54 2008
From: isplist at logicore.net (isplist at logicore.net)
Date: Fri, 15 Feb 2008 15:44:54 -0600
Subject: [Linux-cluster] Redundant (multipath)/Replicating NFS
In-Reply-To: <97a2dbb00802151243s5f8d41d1p88fb9638a6d75435@mail.gmail.com>
Message-ID: <2008215154454.267424@leena>

I recall reading about this a few weeks ago. I'd like to use something which 
is definitely stable. This looks interesting though.

Mike


On Fri, 15 Feb 2008 21:43:54 +0100, Daan Biere wrote:
> Hi,
> 
> As far as i know the only solution which can archive this is ddraid, i
> don't know if 0.6 is production ready yet.....
> http://sourceware.org/cluster/ddraid/
> 
> Kind Regards,
> Daan Biere
> 
> 2008/2/15, isplist at logicore.net <isplist at logicore.net>:>  I recall that
> there is a multipath tool for RHEL which allows one to have
>> redundant SCSI/FC paths in case one goes away.
>> 
>> Are there any tools which would accomplish the same with NFS?
>> 
>> Is there any way of replicating NFS data in real time rather than as a
>> regular
>> backup, such as RAID1 for example, and be able to fail over to the second
>> path
>> or NFS IP should the first fail.
>> 
>> Mike
>> 
>> 
>> --
>> Linux-cluster mailing list
>> Linux-cluster at redhat.com
>> https://www.redhat.com/mailman/listinfo/linux-cluster






From isplist at logicore.net  Fri Feb 15 22:37:14 2008
From: isplist at logicore.net (isplist at logicore.net)
Date: Fri, 15 Feb 2008 16:37:14 -0600
Subject: [Linux-cluster] Redundant (multipath)/Replicating NFS
In-Reply-To: <47B5FA69.3020601@bobich.net>
Message-ID: <2008215163714.779964@leena>

> If you have 2 NFS server you need replicated and failed over, you can
> use DRBD to replicate a virtual block device. You can have this in

I'm looking on the net about this and it looks interesting. I see that it is 
available as RPM's but I don't see it as being part of RHEL? Is this something 
that will run on one or more servers? I can't actually run anything on the NFS 
servers since they are embedded OS's on hardware. I;m using NAS servers 
offering up NFS shares from pools of RAID FC storage.

I'd like to use something like this for the web data that the web servers need 
access to. Your aggregator suggestion is what I've decided upon for the larger 
ongoing needs of media storage. 

Static web stuff as above is relatively easy to deal with using the right 
tools but I'm trying to figure out how to deal with large amounts of media 
data. Obviously, I don't want users to lose their pictures, videos, files, 
work, etc. 

What are your thoughts on even bothering to replicate when using RAID storage 
devices to begin with? They are highly reliable as it is, using 12 drives, 
hard to imagine a loss off data.
I have huge amounts of tape storage using robot libraries with multiple drives 
but still, that doesn't seem like the way to deal with the media. Setting up 
fully redundant storage seems to be a doubling of costs no matter how I cut it 
so I am at a loss on how to deal with media. 

Mike


> primary/primary mode with GFS on top, and you can then export the FS
> from both machines via NFS. If you use UDP NFS, you can have a floating
> IP address for the server that you fail over in case of a node failing.
> There may be a way to load balance NFS, too, but I've yet to see that
> actually work. If you are just failing over, you could run DRBD in
> standard mode without GFS. DRBD has heartbeat plugs.
> 
>> Is there any way of replicating NFS data in real time rather than as a
>> regular
>> backup, such as RAID1 for example, and be able to fail over to the second
>> path
>> or NFS IP should the first fail.
>> 
> DRBD is effectively RAID1 over TCP/IP.
> 
> Gordan
> 
> --
> Linux-cluster mailing list
> Linux-cluster at redhat.com
> https://www.redhat.com/mailman/listinfo/linux-cluster






From isplist at logicore.net  Fri Feb 15 22:43:26 2008
From: isplist at logicore.net (isplist at logicore.net)
Date: Fri, 15 Feb 2008 16:43:26 -0600
Subject: [Linux-cluster] Redundant (multipath)/Replicating NFS
In-Reply-To: <47B5FA69.3020601@bobich.net>
Message-ID: <2008215164326.730459@leena>

> If you have 2 NFS server you need replicated and failed over, you can
> use DRBD to replicate a virtual block device. You can have this in
> primary/primary mode with GFS on top, and you can then export the FS
> from both machines via NFS. If you use UDP NFS, you can have a floating

Oh, and I've done away with GFS on the web server side. It's just so much 
easier to have the web servers load balanced and sharing NFS over clustering.

Mike





From gordan at bobich.net  Fri Feb 15 23:18:46 2008
From: gordan at bobich.net (Gordan Bobic)
Date: Fri, 15 Feb 2008 23:18:46 +0000
Subject: [Linux-cluster] Redundant (multipath)/Replicating NFS
In-Reply-To: <2008215163714.779964@leena>
References: <2008215163714.779964@leena>
Message-ID: <47B61DD6.4040208@bobich.net>

isplist at logicore.net wrote:
>> If you have 2 NFS server you need replicated and failed over, you can
>> use DRBD to replicate a virtual block device. You can have this in
> 
> I'm looking on the net about this and it looks interesting. I see that it is 
> available as RPM's but I don't see it as being part of RHEL?

It's not a part of RHEL, but if you add yum repositories for rpmforge 
and atrpms, the packages for RHEL5/CentOS5 are available.

> Is this something 
> that will run on one or more servers? I can't actually run anything on the NFS 
> servers since they are embedded OS's on hardware. I;m using NAS servers 
> offering up NFS shares from pools of RAID FC storage.

In that case you're out of luck. :-(

> I'd like to use something like this for the web data that the web servers need 
> access to. Your aggregator suggestion is what I've decided upon for the larger 
> ongoing needs of media storage. 
> 
> Static web stuff as above is relatively easy to deal with using the right 
> tools but I'm trying to figure out how to deal with large amounts of media 
> data. Obviously, I don't want users to lose their pictures, videos, files, 
> work, etc. 

If your NFS servers are proprietary hardware, I doubt you'll find 
anything to handle replication between the two of them, unless the 
appliance vendor has a module available for such a thing.

> What are your thoughts on even bothering to replicate when using RAID storage 
> devices to begin with? They are highly reliable as it is, using 12 drives, 
> hard to imagine a loss off data.

So you have 2 FC chasis with 12 drives each? I doubt mirroring them is 
vital provided they are running RAID5 or RAID6 on each. But if a chasis 
fails, you'll still have downtime until you can replace it, even if you 
can transplant all the drives into a new chasis. It depends on how much 
downtime you can live with, and on whether you need a system with 
absolutely no single points of failure.

> I have huge amounts of tape storage using robot libraries with multiple drives 
> but still, that doesn't seem like the way to deal with the media. Setting up 
> fully redundant storage seems to be a doubling of costs no matter how I cut it 
> so I am at a loss on how to deal with media. 

I don't think near-line storage is going to be workable for on-line 
media serving. I guess you have to decide how much redundancy and 
headroom you need. Based on this you might decide to run RAID 01 or RAID 
51 on the setup. But if you need mirroring for the NFS proxies, I 
suspect that's only going to be doable if the appliances support it.

Gordan



From isplist at logicore.net  Sat Feb 16 00:10:04 2008
From: isplist at logicore.net (isplist at logicore.net)
Date: Fri, 15 Feb 2008 18:10:04 -0600
Subject: [Linux-cluster] Redundant (multipath)/Replicating NFS
In-Reply-To: <47B61DD6.4040208@bobich.net>
Message-ID: <200821518104.113677@leena>

> If your NFS servers are proprietary hardware, I doubt you'll find
> anything to handle replication between the two of them, unless the
> appliance vendor has a module available for such a thing.

They can back up to each other's hardware, things like that but I was thinking 
more along the lines of something which could happen from the web servers 
themselves. Perhaps writing to two locations for every write or something.
 
> So you have 2 FC chasis with 12 drives each? I doubt mirroring them is
> vital provided they are running RAID5 or RAID6 on each.

Each controller chassis is the RAID chassis. At this point, I've been using 
RAID5 (5,3) since I don't need the extra speed of (0,0+1) for writes since 
it's for the mainly static web pages. So the RAID5 is spread across the 12 
drives on each chassis. Then on each controller, I have two additional chassis 
to extend the drive loop on each controller. So basically, the controller is 
taking care of 3 sets of RAID5 drives. Each chassis has dual loop controllers 
and the RAID chassis has dual loop and RAID controllers. Of course, each 
chassis has dual power supplies and it's all on UPS/Generator. 

I then connect the RAID controllers from each RAID chassis into an FC hub. The 
NAS servers see all of the storage and I just make it available as NFS through 
the NAS server. Ends up being a lot simpler than what I had going before. The 
cluster was overkill for the web pages.

> fails, you'll still have downtime until you can replace it, even if you
> can transplant all the drives into a new chasis. It depends on how much
> downtime you can live with, and on whether you need a system with
> absolutely no single points of failure.

Well, and this is where I'm not sure about industry standards. I know we all 
want zero down time but when cost is an issue initially, how do most folks go 
about it? Can LAMP services where users store media have an acceptable down 
time limit until they reach a certain point? The hardware I've chosen seems to 
offer a lot of security but as you point out, there could definitely be some 
down time if I have to move drives around.
 
> I don't think near-line storage is going to be workable for on-line
> media serving.

I was thinking more in terms of safekeeping the data, not serving it up from 
there. But then, if things get busy, that still would not be a great solution 
since tape is so slow and the constant backups would be a headache.

> headroom you need. Based on this you might decide to run RAID 01 or RAID
> 51 on the setup. But if you need mirroring for the NFS proxies, I
> suspect that's only going to be doable if the appliances support it.

More than anything, I am trying to find acceptable growth paths that will 
allow for budget conscious methods of getting to the point of being able to 
afford all the redundancy in the world. I can't imagine what youtube does?

Mike





From isplist at logicore.net  Sat Feb 16 01:00:25 2008
From: isplist at logicore.net (isplist at logicore.net)
Date: Fri, 15 Feb 2008 19:00:25 -0600
Subject: [Linux-cluster] Redundant (multipath)/Replicating NFS
In-Reply-To: <47B5FA69.3020601@bobich.net>
Message-ID: <200821519025.218571@leena>

> There may be a way to load balance NFS, too, but I've yet to see that
> actually work. If you are just failing over, you could run DRBD in
> standard mode without GFS. DRBD has heartbeat plugs.

Searching seems to imply that SUN's NFS services have failover capabilities?

If there is no RAID1 style NFS solution, is the only answer perhaps a 
synchronizer and then a failover NFS solution. 






From mailing-lists at hughesjr.com  Sat Feb 16 14:02:43 2008
From: mailing-lists at hughesjr.com (Johnny Hughes)
Date: Sat, 16 Feb 2008 08:02:43 -0600
Subject: [Linux-cluster] Cluster-1.03.00 tarball doesn't compile
In-Reply-To: <1166039772.21097.25.camel@rei.boston.devel.redhat.com>
References: <08A9A3213527A6428774900A80DBD8D80318D8AD@xmb-sjc-222.amer.cisco.com>
	<1166039772.21097.25.camel@rei.boston.devel.redhat.com>
Message-ID: <47B6ED03.7020207@hughesjr.com>

Lon Hohberger wrote:
> On Wed, 2006-12-13 at 11:12 -0800, Lin Shen (lshen) wrote:
>> I pulled a source tree out of the RHEL4 branch. This time the
>> compilation went a bit further but still failed. The outputs are
>> attached. Any ideas? 
> 
> up2date seamonkey-nss-devel seamonkey-nspr-devel
> 
> -- Lon

This is extremely old, however, the fence SRPM does not properly build 
as it needs some modification:

it needs this:

seamonkey-nss-devel as a buildrequire

pkgconfig as a buildrequire

added to CFLAGS/CXXFLAGS or appropriate Makefiles:
-I/usr/include/mozilla-seamonkey-1.0.9/nspr
-I/usr/include/mozilla-seamonkey-1.0.9/nss

I have produced such an SRPM for the latest CentOS build of fence:

http://mirror.centos.org/centos/4/csgfs/SRPMS/

Thanks,
Johnny Hughes

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 252 bytes
Desc: OpenPGP digital signature
URL: <http://listman.redhat.com/archives/linux-cluster/attachments/20080216/adeca378/attachment.sig>

From ohara at rd.scei.sony.co.jp  Mon Feb 18 05:32:07 2008
From: ohara at rd.scei.sony.co.jp (Kazuki Ohara)
Date: Mon, 18 Feb 2008 14:32:07 +0900
Subject: [Linux-cluster] GNBD packages for PPC
Message-ID: <47B91857.1090305@rd.scei.sony.co.jp>

Hi,

I noticed that the gnbd and kmod-gnbd packages for PPC platfroms
are no longer provided from RHEL and Fedora.
Is there someone knows the reason?

-- 
Kazuki Ohara



From p_pavlos at freemail.gr  Mon Feb 18 10:26:59 2008
From: p_pavlos at freemail.gr (Pavlos Parissis)
Date: Mon, 18 Feb 2008 12:26:59 +0200
Subject: [Linux-cluster] quotaoff -gu causes problems
Message-ID: <20080218122659.5znb55e4n400c0sc@easymail-app.hol.gr>

Hi,

I have a service which mounts 3 ext3 FS and then share it over a nfs -  
this is done manually by a script because nfs exports "are" broken in  
4.u4.
For more info about this read  
https://www.redhat.com/archives/linux-cluster/2008-February/msg00184.html.

When the exported file systems are mounted by the clients with options  
bg,rw,rsize=8192,wsize=8192,intr,hard and try to fail over the  
service, the stopping process hangs when it executes quotaoff -gu.
I see that in ps -ef and when I run manually quotaoff -gu hangs as well.

I thought to put noquota on the options for the fs but it didn't help  
because the /usr/share/cluster/fs.sh runs quotaoff -gu regardless if  
the fs are mounted with noquota.

Any idea how to solve this?

Regards,
Pavlos






From a_mdl at mail.ru  Mon Feb 18 10:31:07 2008
From: a_mdl at mail.ru (Denis Medvedev)
Date: Mon, 18 Feb 2008 13:31:07 +0300
Subject: [Linux-cluster] service clvmd restart
Message-ID: <E1JR3H9-000P5T-00.a_mdl-mail-ru@f65.mail.ru>

Dear developers,
is it safe to do /sbin/service clvmd restart in working cluster with some lv  GFS mounted?
What happens if I change locking in lvm.conf to 0 temorarily to change incorrectly marked as clustered logical volumes? 
       Denis Medvedev




From ccaulfie at redhat.com  Mon Feb 18 10:51:25 2008
From: ccaulfie at redhat.com (Christine Caulfield)
Date: Mon, 18 Feb 2008 10:51:25 +0000
Subject: [Linux-cluster] service clvmd restart
In-Reply-To: <E1JR3H9-000P5T-00.a_mdl-mail-ru@f65.mail.ru>
References: <E1JR3H9-000P5T-00.a_mdl-mail-ru@f65.mail.ru>
Message-ID: <47B9632D.6020607@redhat.com>

Denis Medvedev wrote:
> Dear developers,
> is it safe to do /sbin/service clvmd restart in working cluster with some lv  GFS mounted?
> What happens if I change locking in lvm.conf to 0 temorarily to change incorrectly marked as clustered logical volumes? 
>        Denis Medvedev


That should all be fine. clvmd is only needed to co-ordinate metadata
changes, and rebuilds its state when restarted.

Don't forget to change locking_type back when you've finished ;-)


Christine



From p_pavlos at freemail.gr  Mon Feb 18 11:54:22 2008
From: p_pavlos at freemail.gr (Pavlos Parissis)
Date: Mon, 18 Feb 2008 13:54:22 +0200
Subject: [Linux-cluster] quotaoff -gu causes problems
In-Reply-To: <20080218122659.5znb55e4n400c0sc@easymail-app.hol.gr>
References: <20080218122659.5znb55e4n400c0sc@easymail-app.hol.gr>
Message-ID: <20080218135422.phw92zeka8sow84g@easymail-app.hol.gr>

Quoting Pavlos Parissis <p_pavlos at freemail.gr>:

> Hi,
>
> I have a service which mounts 3 ext3 FS and then share it over a nfs -
> this is done manually by a script because nfs exports "are" broken in
> 4.u4.
> For more info about this read
> https://www.redhat.com/archives/linux-cluster/2008-February/msg00184.html.
>
> When the exported file systems are mounted by the clients with options
> bg,rw,rsize=8192,wsize=8192,intr,hard and try to fail over the
> service, the stopping process hangs when it executes quotaoff -gu.
> I see that in ps -ef and when I run manually quotaoff -gu hangs as well.
>
> I thought to put noquota on the options for the fs but it didn't help
> because the /usr/share/cluster/fs.sh runs quotaoff -gu regardless if
> the fs are mounted with noquota.
>
> Any idea how to solve this?
>
> Regards,
> Pavlos
>

here is my cluster conf for the service
question about the fsid - do I put any  number I want ?

</service>
     <service domain="ThirdDomain" name="nfs1" autostart="1"  
recovery="relocate">
       <fs device="/dev/sdb2" options="noquota" nfslock="1"  
fsid="1002" mountpoint="/nfs_omg_data" force_unmount="1"  
name="/nfs_omg_data" fstype="ext3"/>
       <fs device="/dev/sdb3" options="noquota" nfslock="1"  
fsid="1003" mountpoint="/nfs_apps" force_unmount="1" name="/nfs_apps"  
fstype="ext3"/>
       <fs device="/dev/sdb4" options="noquota" nfslock="1"  
fsid="1004" mountpoint="/nfs_cdr_central" force_unmount="1"  
name="/nfs_cdr_central" fstype="ext3"/>
       <ip monitor_link="1" address="10.10.21.73"/>
       <ip monitor_link="1" address="10.10.21.142"/>
       <script name="nfs1" file="/usr/local/wsb/scripts/rhc_nfs1"/>
     </service>




From gordan at bobich.net  Mon Feb 18 13:01:23 2008
From: gordan at bobich.net (gordan at bobich.net)
Date: Mon, 18 Feb 2008 13:01:23 +0000 (GMT)
Subject: [Linux-cluster] Redundant (multipath)/Replicating NFS
In-Reply-To: <97a2dbb00802151243s5f8d41d1p88fb9638a6d75435@mail.gmail.com>
References: <2008215143318.587253@leena>
	<97a2dbb00802151243s5f8d41d1p88fb9638a6d75435@mail.gmail.com>
Message-ID: <alpine.LRH.1.00.0802181300290.1826@skynet.shatteredsilicon.net>

It just occured to me that "dispersed storage" may be something that is 
relevant here:
http://www.cleversafe.org/dispersed-storage

Gordan

On Fri, 15 Feb 2008, Daan Biere wrote:

> Hi,
> As far as i know the only solution which can archive this is ddraid, i don't
> know if 0.6 is production ready yet.....
> http://sourceware.org/cluster/ddraid/
>
> Kind Regards,
> Daan Biere
>
> 2008/2/15, isplist at logicore.net <isplist at logicore.net>:
>>
>> I recall that there is a multipath tool for RHEL which allows one to have
>> redundant SCSI/FC paths in case one goes away.
>>
>> Are there any tools which would accomplish the same with NFS?
>>
>> Is there any way of replicating NFS data in real time rather than as a
>> regular
>> backup, such as RAID1 for example, and be able to fail over to the second
>> path
>> or NFS IP should the first fail.
>>
>> Mike
>>
>>
>>
>>
>>
>> --
>> Linux-cluster mailing list
>> Linux-cluster at redhat.com
>> https://www.redhat.com/mailman/listinfo/linux-cluster
>>
>



From jbrassow at redhat.com  Mon Feb 18 16:14:34 2008
From: jbrassow at redhat.com (Jonathan Brassow)
Date: Mon, 18 Feb 2008 10:14:34 -0600
Subject: [Linux-cluster] service clvmd restart
In-Reply-To: <47B9632D.6020607@redhat.com>
References: <E1JR3H9-000P5T-00.a_mdl-mail-ru@f65.mail.ru>
	<47B9632D.6020607@redhat.com>
Message-ID: <39B6A70A-061A-4AC5-A7EB-5806B21FE64A@redhat.com>

I believe you could also use a CLI override to the config file so you  
wouldn't actually have to change lvm.conf at all.

prompt> vgchange -cn <VG> --config 'global { locking_type = 3 }'

  brassow

On Feb 18, 2008, at 4:51 AM, Christine Caulfield wrote:

> Denis Medvedev wrote:
>> Dear developers,
>> is it safe to do /sbin/service clvmd restart in working cluster  
>> with some lv  GFS mounted?
>> What happens if I change locking in lvm.conf to 0 temorarily to  
>> change incorrectly marked as clustered logical volumes?
>>       Denis Medvedev
>
>
> That should all be fine. clvmd is only needed to co-ordinate metadata
> changes, and rebuilds its state when restarted.
>
> Don't forget to change locking_type back when you've finished ;-)
>
>
> Christine
>
> --
> Linux-cluster mailing list
> Linux-cluster at redhat.com
> https://www.redhat.com/mailman/listinfo/linux-cluster



From lhh at redhat.com  Mon Feb 18 17:54:43 2008
From: lhh at redhat.com (Lon Hohberger)
Date: Mon, 18 Feb 2008 12:54:43 -0500
Subject: [Linux-cluster] quotaoff -gu causes problems
In-Reply-To: <20080218122659.5znb55e4n400c0sc@easymail-app.hol.gr>
References: <20080218122659.5znb55e4n400c0sc@easymail-app.hol.gr>
Message-ID: <1203357283.20564.6.camel@ayanami.boston.devel.redhat.com>

On Mon, 2008-02-18 at 12:26 +0200, Pavlos Parissis wrote:

> I thought to put noquota on the options for the fs but it didn't help  
> because the /usr/share/cluster/fs.sh runs quotaoff -gu regardless if  
> the fs are mounted with noquota.
> 
> Any idea how to solve this?

Comment the offending line out of fs.sh and file a bug against
quotaoff? :)   (quotaoff shouldn't hang!)


-- Lon





From lhh at redhat.com  Mon Feb 18 18:01:51 2008
From: lhh at redhat.com (Lon Hohberger)
Date: Mon, 18 Feb 2008 13:01:51 -0500
Subject: [Linux-cluster] quotaoff -gu causes problems
In-Reply-To: <20080218135422.phw92zeka8sow84g@easymail-app.hol.gr>
References: <20080218122659.5znb55e4n400c0sc@easymail-app.hol.gr>
	<20080218135422.phw92zeka8sow84g@easymail-app.hol.gr>
Message-ID: <1203357711.20564.14.camel@ayanami.boston.devel.redhat.com>

On Mon, 2008-02-18 at 13:54 +0200, Pavlos Parissis wrote:
> Quoting Pavlos Parissis <p_pavlos at freemail.gr>:
> 
> > Hi,
> >
> > I have a service which mounts 3 ext3 FS and then share it over a nfs -
> > this is done manually by a script because nfs exports "are" broken in
> > 4.u4.
> > For more info about this read
> > https://www.redhat.com/archives/linux-cluster/2008-February/msg00184.html.
> >
> > When the exported file systems are mounted by the clients with options
> > bg,rw,rsize=8192,wsize=8192,intr,hard and try to fail over the
> > service, the stopping process hangs when it executes quotaoff -gu.
> > I see that in ps -ef and when I run manually quotaoff -gu hangs as well.
> >
> > I thought to put noquota on the options for the fs but it didn't help
> > because the /usr/share/cluster/fs.sh runs quotaoff -gu regardless if
> > the fs are mounted with noquota.
> >
> > Any idea how to solve this?
> >
> > Regards,
> > Pavlos
> >
> 
> here is my cluster conf for the service
> question about the fsid - do I put any  number I want ?

Since you're starting NFS yourself from a script (which is fine), you
should put the fsid in /etc/exports.  It won't do much from
cluster.conf.

-- Lon



From p_pavlos at freemail.gr  Mon Feb 18 18:16:12 2008
From: p_pavlos at freemail.gr (Pavlos Parissis)
Date: Mon, 18 Feb 2008 19:16:12 +0100
Subject: [Linux-cluster] quotaoff -gu causes problems
In-Reply-To: <1203357711.20564.14.camel@ayanami.boston.devel.redhat.com>
References: <20080218122659.5znb55e4n400c0sc@easymail-app.hol.gr>
	<20080218135422.phw92zeka8sow84g@easymail-app.hol.gr>
	<1203357711.20564.14.camel@ayanami.boston.devel.redhat.com>
Message-ID: <20080218191612.76cbe6d6.p_pavlos@freemail.gr>

On Mon, 18 Feb 2008 13:01:51 -0500
Lon Hohberger <lhh at redhat.com> wrote:

> On Mon, 2008-02-18 at 13:54 +0200, Pavlos Parissis wrote:
> > Quoting Pavlos Parissis <p_pavlos at freemail.gr>:
> > 
> > > Hi,
> > >
> > > I have a service which mounts 3 ext3 FS and then share it over a nfs -
> > > this is done manually by a script because nfs exports "are" broken in
> > > 4.u4.
> > > For more info about this read
> > > https://www.redhat.com/archives/linux-cluster/2008-February/msg00184.html.
> > >
> > > When the exported file systems are mounted by the clients with options
> > > bg,rw,rsize=8192,wsize=8192,intr,hard and try to fail over the
> > > service, the stopping process hangs when it executes quotaoff -gu.
> > > I see that in ps -ef and when I run manually quotaoff -gu hangs as well.
> > >
> > > I thought to put noquota on the options for the fs but it didn't help
> > > because the /usr/share/cluster/fs.sh runs quotaoff -gu regardless if
> > > the fs are mounted with noquota.
> > >
> > > Any idea how to solve this?
> > >
> > > Regards,
> > > Pavlos
> > >
> > 
> > here is my cluster conf for the service
> > question about the fsid - do I put any  number I want ?
> 
> Since you're starting NFS yourself from a script (which is fine), you
> should put the fsid in /etc/exports.  It won't do much from
> cluster.conf.

I did that later on, I modified the script.

Cheers,
Pavlos



From p_pavlos at freemail.gr  Mon Feb 18 18:21:46 2008
From: p_pavlos at freemail.gr (Pavlos Parissis)
Date: Mon, 18 Feb 2008 19:21:46 +0100
Subject: [Linux-cluster] quotaoff -gu causes problems
In-Reply-To: <1203357283.20564.6.camel@ayanami.boston.devel.redhat.com>
References: <20080218122659.5znb55e4n400c0sc@easymail-app.hol.gr>
	<1203357283.20564.6.camel@ayanami.boston.devel.redhat.com>
Message-ID: <20080218192146.52e6f1fc.p_pavlos@freemail.gr>

On Mon, 18 Feb 2008 12:54:43 -0500
Lon Hohberger <lhh at redhat.com> wrote:

> On Mon, 2008-02-18 at 12:26 +0200, Pavlos Parissis wrote:
> 
> > I thought to put noquota on the options for the fs but it didn't help  
> > because the /usr/share/cluster/fs.sh runs quotaoff -gu regardless if  
> > the fs are mounted with noquota.
> > 
> > Any idea how to solve this?
> 
> Comment the offending line out of fs.sh and file a bug against
> quotaoff? :)   (quotaoff shouldn't hang!)
> 
>

Well I did that as well few hours ago and since then I am failing over several times to see if it works.
But, tomorrow I will try to debug the issue by using ocf_log and see how it goes.
Actually today I asked my company for support contract number in order to file a bug report:-)



From lhh at redhat.com  Mon Feb 18 18:35:30 2008
From: lhh at redhat.com (Lon Hohberger)
Date: Mon, 18 Feb 2008 13:35:30 -0500
Subject: [Linux-cluster] quotaoff -gu causes problems
In-Reply-To: <20080218192146.52e6f1fc.p_pavlos@freemail.gr>
References: <20080218122659.5znb55e4n400c0sc@easymail-app.hol.gr>
	<1203357283.20564.6.camel@ayanami.boston.devel.redhat.com>
	<20080218192146.52e6f1fc.p_pavlos@freemail.gr>
Message-ID: <1203359730.20564.19.camel@ayanami.boston.devel.redhat.com>

On Mon, 2008-02-18 at 19:21 +0100, Pavlos Parissis wrote:
> On Mon, 18 Feb 2008 12:54:43 -0500
> Lon Hohberger <lhh at redhat.com> wrote:
> 
> > On Mon, 2008-02-18 at 12:26 +0200, Pavlos Parissis wrote:
> > 
> > > I thought to put noquota on the options for the fs but it didn't help  
> > > because the /usr/share/cluster/fs.sh runs quotaoff -gu regardless if  
> > > the fs are mounted with noquota.
> > > 
> > > Any idea how to solve this?
> > 
> > Comment the offending line out of fs.sh and file a bug against
> > quotaoff? :)   (quotaoff shouldn't hang!)
> > 
> >
> 
> Well I did that as well few hours ago and since then I am failing over several times to see if it works.
> But, tomorrow I will try to debug the issue by using ocf_log and see how it goes.
> Actually today I asked my company for support contract number in order to file a bug report:-)

Anyone can file a bugzilla.  However, a support request requires a
subscription.

-- Lon



From julianorodrigues at mac.com  Mon Feb 18 20:54:49 2008
From: julianorodrigues at mac.com (Juliano Rodrigues)
Date: Mon, 18 Feb 2008 17:54:49 -0300
Subject: [Linux-cluster] dont relocate service after node begin fenced
Message-ID: <4D7C10F0-CEB4-4A7F-9E08-E1CF7B1E9B71@mac.com>

While testing RHEL 5.1 to suit my needs (simple samba 2 nodes  
failover) Im running into this issue.

When poweroff node that service is running cluster dont relocate  
service to another node.

If killall smbd, cluster detects that samba dies and relocate properly  
to another node.

Conga display Unknown node state for that node poweroff, but still  
displaying that service is active/running in this node (powered off  
node)???

Cheers, Juliano.


Feb 18 15:17:05 node2 openais[1982]: [CLM  ] CLM CONFIGURATION CHANGE
Feb 18 15:17:05 node2 openais[1982]: [CLM  ] New Configuration:
Feb 18 15:17:05 node2 openais[1982]: [CLM  ]    r(0) ip(10.0.0.2)
Feb 18 15:17:05 node2 openais[1982]: [CLM  ] Members Left:
Feb 18 15:17:05 node2 openais[1982]: [CLM  ] Members Joined:
Feb 18 15:17:05 node2 openais[1982]: [SYNC ] This node is within the  
primary component and will provide service.
Feb 18 15:17:05 node2 fence_manual: Node node1.cluster needs to be  
reset before recovery can procede.  Waiting for node1.cluster to  
rejoin the cluster or for manual acknowledgement that it has been  
reset (i.e. fence_ack_manual -n node1.cluster)
Feb 18 15:17:05 node2 openais[1982]: [TOTEM] entering OPERATIONAL state.
Feb 18 15:17:05 node2 openais[1982]: [CLM  ] got nodejoin message  
10.0.0.2
Feb 18 15:17:05 node2 openais[1982]: [CPG  ] got joinlist message from  
node 2


<?xml version="1.0"?>
<cluster alias="CAMPIXCLU" config_version="22" name="CAMPIXCLU">
         <fence_daemon clean_start="0" post_fail_delay="0"  
post_join_delay="3"/>
         <clusternodes>
                 <clusternode name="node1.cluster" nodeid="1" votes="1">
                         <fence>
                                 <method name="1">
                                         <device name="node1"  
nodename="node1.cluster"/>
                                 </method>
                         </fence>
                 </clusternode>
                 <clusternode name="node2.cluster" nodeid="2" votes="1">
                         <fence>
                                 <method name="1">
                                         <device name="node2"  
nodename="node2.cluster"/>
                                 </method>
                         </fence>
                 </clusternode>
         </clusternodes>
         <cman expected_votes="1" two_node="1"/>
         <fencedevices>
                 <fencedevice agent="fence_manual" name="node1"/>
                 <fencedevice agent="fence_manual" name="node2"/>
         </fencedevices>
         <rm>
                 <failoverdomains>
                         <failoverdomain name="sambaha" ordered="1"  
restricted="1">
                                 <failoverdomainnode  
name="node1.cluster" priority="2"/>
                                 <failoverdomainnode  
name="node2.cluster" priority="1"/>
                         </failoverdomain>
                 </failoverdomains>
                 <resources/>
                 <service autostart="1" domain="sambaha" exclusive="0"  
name="samba00" recovery="relocate">
                         <smb name="vendas" workgroup="CAMPIX">
                                 <ip address="10.0.0.10/24"  
monitor_link="1"/>
                         </smb>
                 </service>
         </rm>
</cluster>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://listman.redhat.com/archives/linux-cluster/attachments/20080218/fc4f21b1/attachment.htm>

From d.skorupa at wasko.pl  Tue Feb 19 08:09:37 2008
From: d.skorupa at wasko.pl (Darek Skorupa)
Date: Tue, 19 Feb 2008 09:09:37 +0100
Subject: [Linux-cluster] dont relocate service after node begin fenced
In-Reply-To: <4D7C10F0-CEB4-4A7F-9E08-E1CF7B1E9B71@mac.com>
References: <4D7C10F0-CEB4-4A7F-9E08-E1CF7B1E9B71@mac.com>
Message-ID: <47BA8EC1.3070502@wasko.pl>


>
> Conga display Unknown node state for that node poweroff, but still 
> displaying that service is active/running in this node (powered off 
> node)???
How the node can know that the server is powered off if you .....
>
> Feb 18 15:17:05 node2 fence_manual: Node node1.cluster needs to be 
> reset before recovery can procede.  Waiting for node1.cluster to 
> rejoin the cluster or for manual acknowledgement that it has been 
> reset (i.e. fence_ack_manual -n node1.cluster)
.... don't use fence_ack_manual like is said in the log message ?

Darek



From celso at webbertek.com.br  Tue Feb 19 13:15:16 2008
From: celso at webbertek.com.br (Celso K. Webber)
Date: Tue, 19 Feb 2008 10:15:16 -0300
Subject: [Linux-cluster] RHCS 5.1 latest packages, 2-node cluster, doesn't
	come up with only 1 node
In-Reply-To: <1202509009.6443.140.camel@ayanami.boston.devel.redhat.com>
References: <20080208130449.M21432@webbertek.com.br>	<1202505336.6443.87.camel@ayanami.boston.devel.redhat.com>	<20080208211828.M67336@webbertek.com.br>
	<1202509009.6443.140.camel@ayanami.boston.devel.redhat.com>
Message-ID: <47BAD664.6090004@webbertek.com.br>

Hi Lon,

Sorry for a so long delay on answering this.

Just one more doubt:

Lon Hohberger escreveu:
...
>> Please tell me:
>> * is it really wrong set the node names in cluster.conf to a name different 
>> to that reported by "uname -n"?
>> * if it is "ugly" or considered wrong, what is the best way to instruct CMAN 
>> which interface to use for heartbeat?
> 
> I think it's mostly fixed in RHEL5.
> 
> We have updated the CMAN init script for RHEL5 to
> allow /etc/sysconfig/cluster to have "NODENAME=preferred_host_name".  It
> will go out with the next update, but here it is in CVS:
> 
So, after updating the CMAN init script, should I update cluster.conf to use 
the real servers' names, and then set NODENAME=xxx in etc/sysconfig/cluster?

...
> 
> We do what we can, but please keep in mind that a public mailing list
> isn't a very good support forum compared to (for example): 
> 
>   https://www.redhat.com/apps/support/

Yes, I understand this very clearly. I usually ask things at this mailing 
list only if the customer has the corresponding subscriptions, we want 
everybody to be officialy supported. I always instruct our customers to ask 
for support at Red Hat support personnel, and we only install solutions like 
this if the customer has contracted support from Red Hat.

But in this case, I was at the middle of an installation, where the 
behaviour was a little bit different from what I was used to, so I really 
appreciate all your help. And your not-yet-officially-released script solved 
my problem, thanks!!!

I think you're doing a great piece of work, some closed-source Cluster 
solutions are not always as flexible and as evolving as it is with Cluster 
Suite and GFS.

Best regards,

Celso.

-- 
Esta mensagem foi verificada pelo sistema de antiv?rus e
 acredita-se estar livre de perigo.



From julianorodrigues at mac.com  Tue Feb 19 15:11:44 2008
From: julianorodrigues at mac.com (Juliano Rodrigues)
Date: Tue, 19 Feb 2008 12:11:44 -0300
Subject: [Linux-cluster] dont relocate service after node begin fenced
In-Reply-To: <47BA8EC1.3070502@wasko.pl>
References: <4D7C10F0-CEB4-4A7F-9E08-E1CF7B1E9B71@mac.com>
	<47BA8EC1.3070502@wasko.pl>
Message-ID: <8317AE09-4443-451C-8F38-01DCF25BEA1E@mac.com>

Hi,

Thanks for your help, It solved the problem.

Do you know where can I download all cluster suite updates from RHEL  
5.1 since my virtual machines are not registered at rhn???
There are several bugzila issues that hit my configuration, are there  
any on-line repository for updates?

Juliano


On 19/02/2008, at 05:09, Darek Skorupa wrote:

>
>>
>> Conga display Unknown node state for that node poweroff, but still  
>> displaying that service is active/running in this node (powered off  
>> node)???
> How the node can know that the server is powered off if you .....
>>
>> Feb 18 15:17:05 node2 fence_manual: Node node1.cluster needs to be  
>> reset before recovery can procede.  Waiting for node1.cluster to  
>> rejoin the cluster or for manual acknowledgement that it has been  
>> reset (i.e. fence_ack_manual -n node1.cluster)
> .... don't use fence_ack_manual like is said in the log message ?
>
> Darek
>
> --
> Linux-cluster mailing list
> Linux-cluster at redhat.com
> https://www.redhat.com/mailman/listinfo/linux-cluster



From kpodesta at redbrick.dcu.ie  Tue Feb 19 17:17:08 2008
From: kpodesta at redbrick.dcu.ie (Karl Podesta)
Date: Tue, 19 Feb 2008 17:17:08 +0000
Subject: [Linux-cluster] Heartbeat tolerance on busy networks (RHCS3)
Message-ID: <20080219171708.GG29214@minerva.redbrick.dcu.ie>

Hi there, 

I'm looking to increase the tolerance level for heartbeats in a RHEL 4 U4
cluster. The network gets unavoidably busy at a single point each day. 
Short of seperating heartbeats onto a seperate network, is there any way 
I can increase the tolerance to prevent fencing due to missed hearbeats
during this busy period?

I've tried increasing deadnode_timeout, using the following in cluster.conf:
<cman deadnode_timeout="21">

(as per instructions in the FAQ for including it in the cman section, and 
for using cman_tool to update versions & transferring it between nodes)
... but unfortunately this has given me configuration errors when I try
to restart the cluster services so I'm forced to take the option out. 

Any ideas on what I'm doing wrong, or alternative recommendations?

Thanks!

Karl

--
Karl Podesta
Systems Engineer, Securelinx Ltd., Ireland 
http://www.securelinx.ie/
 



From p_pavlos at freemail.gr  Tue Feb 19 20:43:03 2008
From: p_pavlos at freemail.gr (Pavlos Parissis)
Date: Tue, 19 Feb 2008 21:43:03 +0100
Subject: [Linux-cluster] Heartbeat tolerance on busy networks (RHCS3)
In-Reply-To: <20080219171708.GG29214@minerva.redbrick.dcu.ie>
References: <20080219171708.GG29214@minerva.redbrick.dcu.ie>
Message-ID: <20080219214303.5724f3fb.p_pavlos@freemail.gr>

On Tue, 19 Feb 2008 17:17:08 +0000
Karl Podesta <kpodesta at redbrick.dcu.ie> wrote:

> Hi there, 
> 
> I'm looking to increase the tolerance level for heartbeats in a RHEL 4 U4
> cluster. The network gets unavoidably busy at a single point each day. 
> Short of seperating heartbeats onto a seperate network, is there any way 
> I can increase the tolerance to prevent fencing due to missed hearbeats
> during this busy period?
> 
> I've tried increasing deadnode_timeout, using the following in cluster.conf:
> <cman deadnode_timeout="21">
> 
> (as per instructions in the FAQ for including it in the cman section, and 
> for using cman_tool to update versions & transferring it between nodes)
> ... but unfortunately this has given me configuration errors when I try
> to restart the cluster services so I'm forced to take the option out. 
It would be much better and useful for everyone to post your clutser.conf and the error you get.

You can always test your configuration prior using it by using rg_test tool.

Cheers,
Pavlos



From raycharles_man at yahoo.com  Wed Feb 20 02:18:51 2008
From: raycharles_man at yahoo.com (Ray Charles)
Date: Tue, 19 Feb 2008 18:18:51 -0800 (PST)
Subject: [Linux-cluster] Defending GFS
Message-ID: <620467.38104.qm@web32111.mail.mud.yahoo.com>



Hi all,

GFS ver 6.1, not gfs2.

I am looking for an intelligent way to defend the use
of gfs on a prod cluster. Every time there's an issue
I hear a cacophony of voices that declare that "GFS
caused ... whatever."

Most recently there was an instance where doing an ls
of a certain sub dir that happened to be on a GFS
partition just hung. All other sub dir in that same
partition could be navigated. Does that sound like a
typical scenario? Aside from the system log is there
any other place to check??  

If gfs gets into a funny state how can i detect it or
test for it?

tia-

-Ray




      ____________________________________________________________________________________
Never miss a thing.  Make Yahoo your home page. 
http://www.yahoo.com/r/hs



From isplist at logicore.net  Wed Feb 20 04:57:47 2008
From: isplist at logicore.net (isplist at logicore.net)
Date: Tue, 19 Feb 2008 22:57:47 -0600
Subject: [Linux-cluster] Redundant (multipath)/Replicating NFS
In-Reply-To: <alpine.LRH.1.00.0802181300290.1826@skynet.shatteredsilicon.net>
Message-ID: <2008219225747.306698@leena>

Wow, centuries long storage :). 

What a cool project. I can see how it might be interesting for sensitive data.

 Are you thinking that it might have some value in pulling together storage 
such as sperate NFS servers for example? I suppose it could be used in a local 
manner while benefiting from it's features. I've got to read a bit more. 

What I've done so far is to dedicate a nice and quick server with a lot of 
memory to be the aggregator. This is going to sit in the background however as 
the NFS servers will do the trick for the up front web services. 

In the end, for media, I'd like to have one single point of storage so that 
things don't get overly complicated with endless multiple paths. 

Mike



On Mon, 18 Feb 2008 13:01:23 +0000 (GMT), gordan at bobich.net wrote:
> It just occured to me that "dispersed storage" may be something that is
> 
> relevant here:
> http://www.cleversafe.org/dispersed-storage
> 
> Gordan
> 
> On Fri, 15 Feb 2008, Daan Biere wrote:
> 
>> Hi,
>> As far as i know the only solution which can archive this is ddraid, i
>> don't
>> know if 0.6 is production ready yet.....
>> http://sourceware.org/cluster/ddraid/
>> 
>> Kind Regards,
>> Daan Biere
>> 
>> 2008/2/15, isplist at logicore.net <isplist at logicore.net>:
>> 
>>> I recall that there is a multipath tool for RHEL which allows one to
>>> have
>>> redundant SCSI/FC paths in case one goes away.
>>> 
>>> Are there any tools which would accomplish the same with NFS?
>>> 
>>> Is there any way of replicating NFS data in real time rather than as a
>>> regular
>>> backup, such as RAID1 for example, and be able to fail over to the
>>> second
>>> path
>>> or NFS IP should the first fail.
>>> 
>>> Mike
>>> 
>>> 
>>> --
>>> Linux-cluster mailing list
>>> Linux-cluster at redhat.com
>>> https://www.redhat.com/mailman/listinfo/linux-cluster
>> 
>> 
> --
> Linux-cluster mailing list
> Linux-cluster at redhat.com
> https://www.redhat.com/mailman/listinfo/linux-cluster






From gordan at bobich.net  Wed Feb 20 10:17:08 2008
From: gordan at bobich.net (gordan at bobich.net)
Date: Wed, 20 Feb 2008 10:17:08 +0000 (GMT)
Subject: [Linux-cluster] Redundant (multipath)/Replicating NFS
In-Reply-To: <2008219225747.306698@leena>
References: <2008219225747.306698@leena>
Message-ID: <alpine.LRH.1.00.0802201013180.24399@skynet.shatteredsilicon.net>



On Tue, 19 Feb 2008, isplist at logicore.net wrote:

> Wow, centuries long storage :).
>
> What a cool project. I can see how it might be interesting for sensitive data.
>
> Are you thinking that it might have some value in pulling together storage
> such as sperate NFS servers for example? I suppose it could be used in a local
> manner while benefiting from it's features. I've got to read a bit more.

The main point of it is that it provides functionality that DDRAID used 
to, unly in a much more extensive and scaleable manner. It is bassically 
full RAIDn (i.e. n+m RAID) where you can choose the redundancy level you 
want, so of n+m drives, you can lose m and still have everything working.

Gordan



From mathieu.avila at seanodes.com  Wed Feb 20 10:33:23 2008
From: mathieu.avila at seanodes.com (Mathieu Avila)
Date: Wed, 20 Feb 2008 11:33:23 +0100
Subject: [Linux-cluster] fast_statfs and growfs
Message-ID: <20080220113323.1192e8ff@mathieu.toulouse>

Hello GFS developers,

I'm using the new settune "fast_statfs" on a cluster, and when i use
gfs_grow to grow my FS, the new size doesn't appear when i run "df".
However, if i umount/mount it, the new size appears.

Should i run deactivate/reactivate fast_statfs after a grow ? (or
before ?), so that the new size is taken into account ?

Thanks a lot,

--
Mathieu Avila


--------------------------------------------------------------------------------
Les opinions et prises de position emises par le signataire du present
message lui sont propres et ne sauraient engager la responsabilite de la
societe SEANODES.

Ce message ainsi que les eventuelles pieces jointes constituent une
correspondance privee et confidentielle a l'attention exclusive du
destinataire designe ci-dessus. Si vous n'etes pas le destinataire du
present message ou une personne susceptible de pouvoir le lui delivrer, il
vous est signifie que toute divulgation, distribution ou copie de cette
transmission est strictement interdite. Si vous avez recu ce message par
erreur, nous vous remercions d'en informer l'expediteur par telephone ou de
lui retourner le present message, puis d'effacer immediatement ce message de
votre systeme.


The views and opinions expressed by the author of this message are personal.
SEANODES shall assume no liability, express or implied for such message.

This e-mail and any attachments is a confidential correspondence intended
only for use of the individual or entity named above. If you are not the
intended recipient or the agent responsible for delivering the message to
the intended recipient, you are hereby notified that any disclosure,
distribution or copying of this communication is strictly prohibited. If you
have received this communication in error, please notify the sender by phone
or by replying this message, and then delete this message from your system. 



From johannes.russek at io-consulting.net  Wed Feb 20 12:48:51 2008
From: johannes.russek at io-consulting.net (jr)
Date: Wed, 20 Feb 2008 13:48:51 +0100
Subject: [Linux-cluster] Faulty node detection
Message-ID: <1203511731.17907.59.camel@admc.win-rar.local>

Hi everybody,
is there a way that i can make the cluster detect faulty nodes such as
failed san paths?
in my case i had a node which lost the connection the san completely but
it wouldn't be fenced because it behaved completely normally in every
other sense, only the i/o got stalled because of the failed paths.
can i somehow make the cluster check that?
regards,
johannes



From Santosh.Panigrahi at in.unisys.com  Wed Feb 20 13:01:01 2008
From: Santosh.Panigrahi at in.unisys.com (Panigrahi, Santosh Kumar)
Date: Wed, 20 Feb 2008 18:31:01 +0530
Subject: [Linux-cluster] help reqd. - VMware ESX 3.5 fencing
In-Reply-To: <20080214130755.C24DA20B300@smtp3.ldcom.fr>
References: <D566E8CF3538B54D95B925CB69CB4D2A0C1F0E80@inblr-exch1.eu.uis.unisys.com>
	<20080214130755.C24DA20B300@smtp3.ldcom.fr>
Message-ID: <D566E8CF3538B54D95B925CB69CB4D2A0C6C4D7B@inblr-exch1.eu.uis.unisys.com>

Hi,

 

I am facing some issues on trying to fence a node using "fence_vmware" Perl script. This script is attached in this mail.

 

I have a single standalone physical machine installed with VMware ESX 3.5. On top of this I have created 2 VMs with guest OS as Rhel5.1 AP. In both the VMs I have installed VMware Perl APIs. I have kept "fence_vmware" script at /sbin directory on both the VMs. My cluster.conf file is also attached in this mail. I have not configured any service becoz I want only to test VMware fencing agent here.

 

Through conga on trying to fence a node, I am getting following errors in my /var/log/messages.

 

Feb 18 21:12:24 p2pv6 fence_node[5723]: agent "fence_vmware" reports: Global symbol "$RELEASE_VERSION" requires explicit package name at /sbin/fence_vmware line 102. Global symbol "$BUILD_DATE" requires explicit package name at /sbin/fence_vmware line 102. Global symbol "$REDHAT_COPYRIGHT" requires explicit package name at

Feb 18 21:12:24 p2pv6 fence_node[5723]: agent "fence_vmware" reports: /sbin/fence_vmware line 103. Global symbol "$REDHAT_COPYRIGHT" requires explicit package name at /sbin/fence_vmware line 103. Global symbol "$opt_ZZv" requires explicit package name at /sbin/fence_vmware line 267. Global symbol "$pwd_script_out" requires

Feb 18 21:12:24 p2pv6 fence_node[5723]: agent "fence_vmware" reports: explicit package name at /sbin/fence_vmware line 300. Global symbol "$pwd_script_out" requires explicit package name at /sbin/fence_vmware line 301. Global symbol "$pwd_script_out" requires explicit package name at /sbin/fence_vmware line 302. Global symb

Feb 18 21:12:24 p2pv6 fence_node[5723]: agent "fence_vmware" reports: ol "$pwd_script_out" requires explicit package name at /sbin/fence_vmware line 303. Global symbol "$pwd_script_out" requires explicit package name at /sbin/fence_vmware line 322. Global symbol "$pwd_script_out" requires explicit package name at /sbin/fenc

Feb 18 21:12:24 p2pv6 fence_node[5723]: agent "fence_vmware" reports: e_vmware line 323. Global symbol "$pwd_script_out" requires explicit package name at /sbin/fence_vmware line 324. Global symbol "$pwd_script_out" requires explicit package name at /sbin/fence_vmware line 325. Bareword "version" not allowed while "strict s

Feb 18 21:12:24 p2pv6 fence_node[5723]: agent "fence_vmware" reports: ubs" in use at /sbin/fence_vmware line 291. Execution of /sbin/fence_vmware aborted due to compilation errors.

Feb 18 21:12:24 p2pv6 fence_node[5723]: Fence of "p2pv5.tr.unisys.com" was unsuccessful

 

My initial guess is this fencing agent script can only be run with old VMware Perl APIs. Please correct me. Is there any way to run this script in my current environment?

 

If anyone is having a working script for VMware ESX 3.5 server, please pass it.

 

Thanks,

Santosh

 

________________________________

From: linux-cluster-bounces at redhat.com [mailto:linux-cluster-bounces at redhat.com] On Behalf Of MARY, Mathieu
Sent: Thursday, February 14, 2008 6:39 PM
To: linux clustering
Subject: RE: [Linux-cluster] help reqd. - VMware ESX 3.5 fencing

 

VC is the virtual center server, i understood from your mail that you're using virtual infrastructure, but you question points out the fact that you maybe are using standalone ESX server ?

in our configuration we use an ESX farm of 4 servers managed by the VC server where we connect with the VI client

 

 

<fencedevice name="your_fence_method" agent="fence_vi3" ipaddr="yourserver_ip" port="your_vm_name" login="xxx" passwd="yyyyy"/>

 

though I don't know if it works on standalone server, maybe you would have ton install the VMI perlmodules described inside the script to you ESX 3.5 server

 

________________________________

De : linux-cluster-bounces at redhat.com [mailto:linux-cluster-bounces at redhat.com] De la part de Panigrahi, Santosh Kumar
Envoy? : jeudi 14 f?vrier 2008 13:50
? : linux clustering
Objet : RE: [Linux-cluster] help reqd. - VMware ESX 3.5 fencing

 

Thanks Marry for the script. I will test and let you know. By the way what's this VC server? Is it the system where I am running my VI client?

Can you please elaborate little more on this configuration like where I will keep this script, what will I mention in my cluster.conf file and etc.

 

Thanks,

Santosh  

________________________________

From: linux-cluster-bounces at redhat.com [mailto:linux-cluster-bounces at redhat.com] On Behalf Of MARY, Mathieu
Sent: Thursday, February 14, 2008 5:59 PM
To: linux clustering
Subject: RE: [Linux-cluster] help reqd. - VMware ESX 3.5 fencing

 

hello,

 

i'm using this script for VI 3 and  ESX3.02 i guess it would work for you too, cannot remember where I found it though :-)

note that you have to send the restart request to your VC server and not to the ESX server

 

________________________________

De : linux-cluster-bounces at redhat.com [mailto:linux-cluster-bounces at redhat.com] De la part de Panigrahi, Santosh Kumar
Envoy? : jeudi 14 f?vrier 2008 12:37
? : linux-cluster at redhat.com
Objet : [Linux-cluster] help reqd. - VMware ESX 3.5 fencing

 

Hi,

 

Does anybody have configured fencing in VMware ESX 3.5 environment? I appreciate any help.

 

I have got some info from http://www.tournament.org.il/run/index.php?/archives/140-VMware-Fencing-in-RedHat-Cluster-5-RHCS5.html .

This script given here is for VMware server. Any idea whether it will work for ESX 3.5 server or not?

 

My system configurations are as follows.

 

Host machine    : Unisys ES7000-one with host OS as VMware ESX 3.5

Guest Machines: Guest OS as Rhel5.1 AP

 

I am connecting to host machine using VMware VI 3.0.

 

Thanks,

Santosh

 

 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://listman.redhat.com/archives/linux-cluster/attachments/20080220/19444090/attachment.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: cluster.conf.doc
Type: application/msword
Size: 27648 bytes
Desc: cluster.conf.doc
URL: <http://listman.redhat.com/archives/linux-cluster/attachments/20080220/19444090/attachment.doc>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: fence_vmware.doc
Type: application/msword
Size: 57856 bytes
Desc: fence_vmware.doc
URL: <http://listman.redhat.com/archives/linux-cluster/attachments/20080220/19444090/attachment-0001.doc>

From lpleiman at redhat.com  Wed Feb 20 13:14:45 2008
From: lpleiman at redhat.com (Leo Pleiman)
Date: Wed, 20 Feb 2008 08:14:45 -0500
Subject: [Linux-cluster] fast_statfs and growfs
In-Reply-To: <20080220113323.1192e8ff@mathieu.toulouse>
References: <20080220113323.1192e8ff@mathieu.toulouse>
Message-ID: <47BC27C5.7000105@redhat.com>

We have adopted to disable fast_statfs before starting gfs_grow, it 
works as advertised.



Mathieu Avila wrote:
> Hello GFS developers,
>
> I'm using the new settune "fast_statfs" on a cluster, and when i use
> gfs_grow to grow my FS, the new size doesn't appear when i run "df".
> However, if i umount/mount it, the new size appears.
>
> Should i run deactivate/reactivate fast_statfs after a grow ? (or
> before ?), so that the new size is taken into account ?
>
> Thanks a lot,
>
> --
> Mathieu Avila
>
>
> --------------------------------------------------------------------------------
> Les opinions et prises de position emises par le signataire du present
> message lui sont propres et ne sauraient engager la responsabilite de la
> societe SEANODES.
>
> Ce message ainsi que les eventuelles pieces jointes constituent une
> correspondance privee et confidentielle a l'attention exclusive du
> destinataire designe ci-dessus. Si vous n'etes pas le destinataire du
> present message ou une personne susceptible de pouvoir le lui delivrer, il
> vous est signifie que toute divulgation, distribution ou copie de cette
> transmission est strictement interdite. Si vous avez recu ce message par
> erreur, nous vous remercions d'en informer l'expediteur par telephone ou de
> lui retourner le present message, puis d'effacer immediatement ce message de
> votre systeme.
>
>
> The views and opinions expressed by the author of this message are personal.
> SEANODES shall assume no liability, express or implied for such message.
>
> This e-mail and any attachments is a confidential correspondence intended
> only for use of the individual or entity named above. If you are not the
> intended recipient or the agent responsible for delivering the message to
> the intended recipient, you are hereby notified that any disclosure,
> distribution or copying of this communication is strictly prohibited. If you
> have received this communication in error, please notify the sender by phone
> or by replying this message, and then delete this message from your system. 
>
> --
> Linux-cluster mailing list
> Linux-cluster at redhat.com
> https://www.redhat.com/mailman/listinfo/linux-cluster
>   
-------------- next part --------------
A non-text attachment was scrubbed...
Name: lpleiman.vcf
Type: text/x-vcard
Size: 206 bytes
Desc: not available
URL: <http://listman.redhat.com/archives/linux-cluster/attachments/20080220/c8c1782c/attachment.vcf>

From alaack at ustrap.com  Wed Feb 20 13:54:01 2008
From: alaack at ustrap.com (Andrea Laack)
Date: Wed, 20 Feb 2008 07:54:01 -0600
Subject: [Linux-cluster] FW: cluster crash problem
Message-ID: <200802201334.m1KDYBD2022182@gate.ustrap.com>

 

-----Original Message-----
From: Andrea Laack [mailto:alaack at ustrap.com] 
Sent: Tuesday, February 12, 2008 12:54 PM
To: 'linux-cluster at redhat.com'
Subject: cluster crash problem

We are running RHEL 3.0 with version 1.0.3 of RedHat cluster suite.  We are
utilizing a Promise Vtrak 15200 for shared storage and an Adaptec ASA-7211C
iSCSI initiator.
Having problems with any process that uses high I/O across the iSCSI link.

Last night dba attempted to create an Oracle instance on the shared storage
device.  The cluster crashed and failed over the the backup node.  Nothing
in the logs.  Log level set at 6.  Only indication I have that something
happened is from the graphs of the disk I/O (HotSanic).  This shows 69.42
Pentabytes (yes, it shows pentabytes).

We are using a watchdog timer.

This has happened before when copying *very* large amounts of data that
includes *very* large files.  Many small files does not cause the cluster to
crash.

Has anyone seen this type of problem?  Any help will be sincerely
appreciated.  Adaptec will only talk to me if I pay them $199/phone call.

Thanks
Andrea

Andrea Laack
Network Administrator
Universal Strap
W209N17500 Industrial Drive
Jackson, WI  53037
262-677-3641 Ext 5220


Thought I would answer my own questions in the hopes that it can be of use
to someone else.

Thanks to Lon Hohberger.  His information in an email I found in the mail
list archives sent me in the right direction.  

RedHat Knowledgebase gave the following suggestions.

A high network traffic or load can cause an cluster node to miss a
heartbeat.  This will cause the node to be fenced.  

The following performance tuning settings were suggested:

cludb -p clumembd%adaptive yes
cludb -p clumembd%interval 2000000
cludb -p clumembd%tko_count 15
cludb -p clumembd%rtp 10
cludb -p cluquorumd%rtp 10

(Be sure to stop cluster services before making these changes.)

I made the above changes and the problems were corrected.

Thanks
Andrea



From isplist at logicore.net  Wed Feb 20 15:08:49 2008
From: isplist at logicore.net (isplist at logicore.net)
Date: Wed, 20 Feb 2008 09:08:49 -0600
Subject: [Linux-cluster] Redundant (multipath)/Replicating NFS
In-Reply-To: <alpine.LRH.1.00.0802201013180.24399@skynet.shatteredsilicon.net>
Message-ID: <20082209849.839286@leena>

> The main point of it is that it provides functionality that DDRAID used
> to, unly in a much more extensive and scaleable manner. It is bassically
> full RAIDn (i.e. n+m RAID) where you can choose the redundancy level you
> want, so of n+m drives, you can lose m and still have everything working.

Really, an interesting project, thanks for the lead. I want to try and spend 
some time reading about it in the next day or two.

Mike





From kpodesta at redbrick.dcu.ie  Wed Feb 20 15:37:07 2008
From: kpodesta at redbrick.dcu.ie (Karl Podesta)
Date: Wed, 20 Feb 2008 15:37:07 +0000
Subject: [Linux-cluster] Heartbeat tolerance on busy networks (RHCS3)
In-Reply-To: <20080219214303.5724f3fb.p_pavlos@freemail.gr>
References: <20080219171708.GG29214@minerva.redbrick.dcu.ie>
	<20080219214303.5724f3fb.p_pavlos@freemail.gr>
Message-ID: <20080220153707.GA2279@minerva.redbrick.dcu.ie>

On Tue, Feb 19, 2008 at 09:43:03PM +0100, Pavlos Parissis wrote:
> It would be much better and useful for everyone to post your clutser.conf and the error you get.
> 
> You can always test your configuration prior using it by using rg_test tool.
> 
> Cheers,
> Pavlos

Ok - I make the change in cluster.conf (see below), then do:

  ccs_tool update /etc/cluster/cluster.conf
  cman_tool version -r 68

... this works fine, no errors. Clustat reports cluster working as normal, 
no messages in /var/log/messages etc. But then when I enter system-config-
cluster, I get a window with an error telling me it can't read the config
file (error is below). Any help you can give is appreciated! Or even if
you'd recommend something different to allow tolerance for heartbeats. 

Incidentally - it appears deadnode_timeout isn't a variable in the cman 
section in the RHEL 4 cluster.conf schema:
(http://sources.redhat.com/cluster/doc/cluster_schema_rhel4.html)
... so maybe deadnode_timeout isn't a valid variable anymore?


Errors (from system-config-cluster) :
=====================================

  "A problem was encountered while reading configuration file ..
   Details or the error appear below. Click the 'New' button to create
   a new configuration file. To continue anyway (Not Recommended!), 
   click the 'Ok' button

/etc/cluster/cluster.conf:20: element cman: Relax-NG validity error : Invalid
attribute deadnode_timeout for element cman
/etc/cluster/cluster.conf:20: element cman: Relax-NG validity error :
Expecting element gulm, got cman
/etc/cluster/cluster.conf:2: element cluster: Relax-NG validity error :
Invalid sequence in interleave
/etc/cluster/cluster.conf:2: element cluster: Relax-NG validity error :
Element cluster failed to validate content
/etc/cluster/cluster.conf:15: element device: validity error : IDREF attribute
name references an unknown ID "cluster2-drac"
/etc/cluster/cluster.conf:8: element device: validity error : IDREF attribute
name references an unknown ID "cluster1-drac"
/etc/cluster/cluster.conf fails to validate

cluster.conf:
============

<?xml version="1.0"?>
<cluster config_version="68" name="mycluster">
  <fence_daemon post_fail_delay="0" post_join_delay="3"/>
  <clusternodes>
    <clusternode name="cluster1" votes="1">
      <fence>
        <method name="1">
          <device name="cluster1-drac"/>
        </method>
      </fence>
    </clusternode>
    <clusternode name="cluster2" votes="1">
      <fence>
        <method name="1">
          <device name="cluster2-drac"/>
        </method>
      </fence>
    </clusternode>
  </clusternodes>
  <cman expected_votes="1" two_node="1" deadnode_timeout="60"/>
  <fencedevices>
    <fencedevice agent="fence_drac" ipaddr="X.73" login="root" name="cluster1-drac" passwd="X"/>
    <fencedevice agent="fence_drac" ipaddr="X.74" login="root" name="cluster2-drac" passwd="X"/>
  </fencedevices>
  <rm>
    <failoverdomains>
        <failoverdomain name="mysql" ordered="0" restricted="1">
          <failoverdomainnode name="cluster1" priority="1"/>
          <failoverdomainnode name="cluster2" priority="1"/>
        </failoverdomain>
    </failoverdomains>
    <resources>
      <fs device="/dev/emcpowera1" force_fsck="0"
force_unmount="1" fsid="6939" fstype="ext3" mountpoint="/disk1" name="/disk1"
options="" self_fence="1"/>
      <ip address="X.70" monitor_link="1"/>
      <script file="/etc/init.d/mysqld" name="mysqld"/>
      <script file="/etc/init.d/httpd" name="apache"/>
    </resources>
    <service autostart="1" name="all_cluster_services">
      <ip ref="X.70"/>
      <fs ref="/disk1"/>
      <script ref="mysqld"/>
      <script ref="apache"/>
    </service>
  </rm>
</cluster>

-- 
Karl Podesta
Systems Engineer, Securelinx Ltd., Ireland
http://www.securelinx.ie/



From Mathieu.MARY at neufcegetel.fr  Wed Feb 20 15:37:56 2008
From: Mathieu.MARY at neufcegetel.fr (MARY, Mathieu)
Date: Wed, 20 Feb 2008 16:37:56 +0100
Subject: [Linux-cluster] help reqd. - VMware ESX 3.5 fencing
In-Reply-To: <D566E8CF3538B54D95B925CB69CB4D2A0C6C4D7B@inblr-exch1.eu.uis.unisys.com>
Message-ID: <20080220153643.BC30020B3F3@smtp3.ldcom.fr>

the script i sent to you was, or it should have been this one, apologies if I miscopied, as I tried lots of scripts when I was searching for the good one at the time. 

it uses the VMware::VIM2Runtime wich is the ESX 3.xx perl library

 

 

#!/usr/bin/perl

 

###############################################################################

###############################################################################

##

##  Copyright (C) Sistina Software, Inc.  1997-2003  All rights reserved.

##  Copyright (C) 2004 Red Hat, Inc.  All rights reserved.

##

##  This copyrighted material is made available to anyone wishing to use,

##  modify, copy, or redistribute it subject to the terms and conditions

##  of the GNU General Public License v.2.

##

###############################################################################

###############################################################################

 

use Getopt::Std;

use VMware::VIM2Runtime;

 

# Get the program name from $0 and strip directory names

$_=$0;

s/.*\///;

my $pname = $_;

 

# WARNING!! Do not add code bewteen "#BEGIN_VERSION_GENERATION" and

# "#END_VERSION_GENERATION"  It is generated by the Makefile

 

#BEGIN_VERSION_GENERATION

$FENCE_RELEASE_NAME="2.0.64";

$REDHAT_COPYRIGHT=("Copyright (C) Red Hat, Inc.  2004  All rights reserved.");

$BUILD_DATE="(built Thu Jun 28 07:25:05 EDT 2007)";

#END_VERSION_GENERATION

 

sub usage

{

    print "Usage:\n\n";

    print "$pname [options]\n\n";

    print "Options:\n";

    print "  -a <ip>          IP address or hostname of VirtualCenter server\n";

    print "  -h               Usage\n";

    print "  -n <name>        Virtual machine name to reset\n";

                print "  -l <string>      Login name for VirtualCenter server\n";

    print "  -p <string>      Password for login\n";

    print "  -V               version\n\n";

 

    exit 0;

}

 

sub fail

{

  ($msg) = @_;

  print $msg."\n" unless defined $opt_q;

  $t->close if defined $t;

  exit 1;

}

 

sub fail_usage

{

  ($msg) = @_;

  print STDERR $msg."\n" if $msg;

  print STDERR "Please use '-h' for usage.\n";

  exit 1;

}

 

sub version

{

  print "$pname $FENCE_RELEASE_NAME $BUILD_DATE\n";

  print "$REDHAT_COPYRIGHT\n" if ( $REDHAT_COPYRIGHT );

 

  exit 0;

}

 

if (@ARGV > 0) {

    getopts("a:hn:l:p:V") || fail_usage ;

 

    usage if defined $opt_h;

    version if defined $opt_V;

 

    fail_usage "Unknown parameter." if (@ARGV > 0);

 

    fail_usage "No '-a' flag specified." unless defined $opt_a;

                fail_usage "No '-l' flag specified." unless defined $opt_l;

    fail_usage "No '-p' flag specified." unless defined $opt_p;

    fail_usage "No '-n' flag specified." unless defined $opt_n;

 

} else {

    get_options_stdin();

 

    fail "failed: no IP/host address for the VirtualCenter." unless defined $opt_a;

                fail "failed: no login name provided." unless defined $opt_l;

    fail "failed: no password provided." unless defined $opt_p;

    fail "failed: no VM name specified." unless defined $opt_n;

}

 

#

# Set up and log in

#

 

Vim::login(service_url=>"https://$opt_a/sdk/vimService", user_name=>"$opt_l", password=>"$opt_p");

 

#

# Do the command

#

 

my $vm_view = Vim::find_entity_view(view_type => 'VirtualMachine', filter => {name => $opt_n});

 

if (!$vm_view)

{

        fail "Virtual Machine name not found.";

}

 

$vm_view->ResetVM();

 

Vim::logout();

 

print "success: VM: $opt_n reset.\n";

exit 0;

 

sub get_options_stdin

{

    my $opt;

    my $line = 0;

 

    while( defined($in = <>) )

    {

        $_ = $in;

        chomp;

 

        # strip leading and trailing whitespace

        s/^\s*//;

        s/\s*$//;

 

        # skip comments

        next if /^#/;

 

        $line+=1;

        $opt=$_;

        next unless $opt;

 

        ($name,$val)=split /\s*=\s*/, $opt;

 

        if ( $name eq "" ) {

           print("parse error: illegal name in option $line\n");

           exit 2;

        }

 

        # DO NOTHING -- this field is used by fenced

        elsif ($name eq "agent" ) { }

 

        elsif ($name eq "login" ) {

            $opt_l = $val;

        }

 

        elsif ($name eq "ipaddr" )

        {

            $opt_a = $val;

        }

 

        elsif ($name eq "name" ) { }

 

        elsif ($name eq "passwd" )

        {

            $opt_p = $val;

        }

 

        elsif ($name eq "port" )

        {

            $opt_n = $val;

        }

    }

}

 

 

 

 

Regards,

 

 

Mathieu

________________________________

De : linux-cluster-bounces at redhat.com [mailto:linux-cluster-bounces at redhat.com] De la part de Panigrahi, Santosh Kumar
Envoy? : mercredi 20 f?vrier 2008 14:01
? : linux clustering
Objet : RE: [Linux-cluster] help reqd. - VMware ESX 3.5 fencing

 

Hi,

 

I am facing some issues on trying to fence a node using "fence_vmware" Perl script. This script is attached in this mail.

 

I have a single standalone physical machine installed with VMware ESX 3.5. On top of this I have created 2 VMs with guest OS as Rhel5.1 AP. In both the VMs I have installed VMware Perl APIs. I have kept "fence_vmware" script at /sbin directory on both the VMs. My cluster.conf file is also attached in this mail. I have not configured any service becoz I want only to test VMware fencing agent here.

 

Through conga on trying to fence a node, I am getting following errors in my /var/log/messages.

 

Feb 18 21:12:24 p2pv6 fence_node[5723]: agent "fence_vmware" reports: Global symbol "$RELEASE_VERSION" requires explicit package name at /sbin/fence_vmware line 102. Global symbol "$BUILD_DATE" requires explicit package name at /sbin/fence_vmware line 102. Global symbol "$REDHAT_COPYRIGHT" requires explicit package name at

Feb 18 21:12:24 p2pv6 fence_node[5723]: agent "fence_vmware" reports: /sbin/fence_vmware line 103. Global symbol "$REDHAT_COPYRIGHT" requires explicit package name at /sbin/fence_vmware line 103. Global symbol "$opt_ZZv" requires explicit package name at /sbin/fence_vmware line 267. Global symbol "$pwd_script_out" requires

Feb 18 21:12:24 p2pv6 fence_node[5723]: agent "fence_vmware" reports: explicit package name at /sbin/fence_vmware line 300. Global symbol "$pwd_script_out" requires explicit package name at /sbin/fence_vmware line 301. Global symbol "$pwd_script_out" requires explicit package name at /sbin/fence_vmware line 302. Global symb

Feb 18 21:12:24 p2pv6 fence_node[5723]: agent "fence_vmware" reports: ol "$pwd_script_out" requires explicit package name at /sbin/fence_vmware line 303. Global symbol "$pwd_script_out" requires explicit package name at /sbin/fence_vmware line 322. Global symbol "$pwd_script_out" requires explicit package name at /sbin/fenc

Feb 18 21:12:24 p2pv6 fence_node[5723]: agent "fence_vmware" reports: e_vmware line 323. Global symbol "$pwd_script_out" requires explicit package name at /sbin/fence_vmware line 324. Global symbol "$pwd_script_out" requires explicit package name at /sbin/fence_vmware line 325. Bareword "version" not allowed while "strict s

Feb 18 21:12:24 p2pv6 fence_node[5723]: agent "fence_vmware" reports: ubs" in use at /sbin/fence_vmware line 291. Execution of /sbin/fence_vmware aborted due to compilation errors.

Feb 18 21:12:24 p2pv6 fence_node[5723]: Fence of "p2pv5.tr.unisys.com" was unsuccessful

 

My initial guess is this fencing agent script can only be run with old VMware Perl APIs. Please correct me. Is there any way to run this script in my current environment?

 

If anyone is having a working script for VMware ESX 3.5 server, please pass it.

 

Thanks,

Santosh

 

________________________________

From: linux-cluster-bounces at redhat.com [mailto:linux-cluster-bounces at redhat.com] On Behalf Of MARY, Mathieu
Sent: Thursday, February 14, 2008 6:39 PM
To: linux clustering
Subject: RE: [Linux-cluster] help reqd. - VMware ESX 3.5 fencing

 

VC is the virtual center server, i understood from your mail that you're using virtual infrastructure, but you question points out the fact that you maybe are using standalone ESX server ?

in our configuration we use an ESX farm of 4 servers managed by the VC server where we connect with the VI client

 

 

<fencedevice name="your_fence_method" agent="fence_vi3" ipaddr="yourserver_ip" port="your_vm_name" login="xxx" passwd="yyyyy"/>

 

though I don't know if it works on standalone server, maybe you would have ton install the VMI perlmodules described inside the script to you ESX 3.5 server

 

________________________________

De : linux-cluster-bounces at redhat.com [mailto:linux-cluster-bounces at redhat.com] De la part de Panigrahi, Santosh Kumar
Envoy? : jeudi 14 f?vrier 2008 13:50
? : linux clustering
Objet : RE: [Linux-cluster] help reqd. - VMware ESX 3.5 fencing

 

Thanks Marry for the script. I will test and let you know. By the way what's this VC server? Is it the system where I am running my VI client?

Can you please elaborate little more on this configuration like where I will keep this script, what will I mention in my cluster.conf file and etc.

 

Thanks,

Santosh  

________________________________

From: linux-cluster-bounces at redhat.com [mailto:linux-cluster-bounces at redhat.com] On Behalf Of MARY, Mathieu
Sent: Thursday, February 14, 2008 5:59 PM
To: linux clustering
Subject: RE: [Linux-cluster] help reqd. - VMware ESX 3.5 fencing

 

hello,

 

i'm using this script for VI 3 and  ESX3.02 i guess it would work for you too, cannot remember where I found it though :-)

note that you have to send the restart request to your VC server and not to the ESX server

 

________________________________

De : linux-cluster-bounces at redhat.com [mailto:linux-cluster-bounces at redhat.com] De la part de Panigrahi, Santosh Kumar
Envoy? : jeudi 14 f?vrier 2008 12:37
? : linux-cluster at redhat.com
Objet : [Linux-cluster] help reqd. - VMware ESX 3.5 fencing

 

Hi,

 

Does anybody have configured fencing in VMware ESX 3.5 environment? I appreciate any help.

 

I have got some info from http://www.tournament.org.il/run/index.php?/archives/140-VMware-Fencing-in-RedHat-Cluster-5-RHCS5.html .

This script given here is for VMware server. Any idea whether it will work for ESX 3.5 server or not?

 

My system configurations are as follows.

 

Host machine    : Unisys ES7000-one with host OS as VMware ESX 3.5

Guest Machines: Guest OS as Rhel5.1 AP

 

I am connecting to host machine using VMware VI 3.0.

 

Thanks,

Santosh

 

 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://listman.redhat.com/archives/linux-cluster/attachments/20080220/31fee571/attachment.htm>

From ccaulfie at redhat.com  Wed Feb 20 16:09:29 2008
From: ccaulfie at redhat.com (Christine Caulfield)
Date: Wed, 20 Feb 2008 16:09:29 +0000
Subject: [Linux-cluster] Heartbeat tolerance on busy networks (RHCS3)
In-Reply-To: <20080220153707.GA2279@minerva.redbrick.dcu.ie>
References: <20080219171708.GG29214@minerva.redbrick.dcu.ie>	<20080219214303.5724f3fb.p_pavlos@freemail.gr>
	<20080220153707.GA2279@minerva.redbrick.dcu.ie>
Message-ID: <47BC50B9.9050208@redhat.com>

Karl Podesta wrote:
> On Tue, Feb 19, 2008 at 09:43:03PM +0100, Pavlos Parissis wrote:
>> It would be much better and useful for everyone to post your clutser.conf and the error you get.
>>
>> You can always test your configuration prior using it by using rg_test tool.
>>
>> Cheers,
>> Pavlos
> 
> Ok - I make the change in cluster.conf (see below), then do:
> 
>   ccs_tool update /etc/cluster/cluster.conf
>   cman_tool version -r 68
> 
> ... this works fine, no errors. Clustat reports cluster working as normal, 
> no messages in /var/log/messages etc. But then when I enter system-config-
> cluster, I get a window with an error telling me it can't read the config
> file (error is below). Any help you can give is appreciated! Or even if
> you'd recommend something different to allow tolerance for heartbeats. 
> 
> Incidentally - it appears deadnode_timeout isn't a variable in the cman 
> section in the RHEL 4 cluster.conf schema:
> (http://sources.redhat.com/cluster/doc/cluster_schema_rhel4.html)
> ... so maybe deadnode_timeout isn't a valid variable anymore?
> 

deadnode_timeout is a valid variable in RHEL4. It just seems that
system-config-cluster (at least your version of it) doesn't like it :(

The way to check it has been honoured is to cat
/proc/cluster/config/cman/deadnode_timeout and see if it has the right
value.

-- 

Chrissie



From raindoctor at gmail.com  Wed Feb 20 18:43:32 2008
From: raindoctor at gmail.com (Pedro Espinoza)
Date: Wed, 20 Feb 2008 13:43:32 -0500
Subject: [Linux-cluster] Defending GFS
In-Reply-To: <620467.38104.qm@web32111.mail.mud.yahoo.com>
References: <620467.38104.qm@web32111.mail.mud.yahoo.com>
Message-ID: <b86c876f0802201043v4a1886c5h9b24effc3baa20e@mail.gmail.com>

We ran into such problems few times: my collegue just reboots that node;)


On 2/19/08, Ray Charles <raycharles_man at yahoo.com> wrote:
>
>
> Hi all,
>
> GFS ver 6.1, not gfs2.
>
> I am looking for an intelligent way to defend the use
> of gfs on a prod cluster. Every time there's an issue
> I hear a cacophony of voices that declare that "GFS
> caused ... whatever."
>
> Most recently there was an instance where doing an ls
> of a certain sub dir that happened to be on a GFS
> partition just hung. All other sub dir in that same
> partition could be navigated. Does that sound like a
> typical scenario? Aside from the system log is there
> any other place to check??
>
> If gfs gets into a funny state how can i detect it or
> test for it?
>
> tia-
>
> -Ray
>
>
>
>
>      ____________________________________________________________________________________
> Never miss a thing.  Make Yahoo your home page.
> http://www.yahoo.com/r/hs
>
> --
> Linux-cluster mailing list
> Linux-cluster at redhat.com
> https://www.redhat.com/mailman/listinfo/linux-cluster
>



From shawnlhood at gmail.com  Wed Feb 20 19:45:14 2008
From: shawnlhood at gmail.com (Shawn Hood)
Date: Wed, 20 Feb 2008 14:45:14 -0500
Subject: [Linux-cluster] Initiating transition message
Message-ID: <cfe2fc960802201145j4680ac1fib446ffadf00a95@mail.gmail.com>

Though one instance of 'Initating transition' message seems to be
normal , what could the behavior shown in the following log indicate?
What exactly is happening during an 'Initating transition' message?

Shawn

Feb 14 15:25:55 odin kernel: CMAN: Initiating transition, generation 7
Feb 14 15:26:01 odin kernel: CMAN: removing node munin from the
cluster : No response to messages
Feb 14 15:26:01 odin kernel: CMAN: Initiating transition, generation 8
Feb 14 15:26:16 odin kernel: CMAN: Initiating transition, generation 9
Feb 14 15:26:31 odin kernel: CMAN: Initiating transition, generation 10
Feb 14 15:26:40 odin su(pam_unix)[20082]: session opened for user root
by shood(uid=0)
Feb 14 15:26:46 odin kernel: CMAN: Initiating transition, generation 11
Feb 14 15:27:01 odin kernel: CMAN: Initiating transition, generation 12
Feb 14 15:27:16 odin kernel: CMAN: Initiating transition, generation 13
Feb 14 15:27:31 odin kernel: CMAN: Initiating transition, generation 14
Feb 14 15:27:46 odin kernel: CMAN: Initiating transition, generation 15
Feb 14 15:28:01 odin kernel: CMAN: Initiating transition, generation 16
Feb 14 15:28:16 odin kernel: CMAN: Initiating transition, generation 17
Feb 14 15:28:31 odin kernel: CMAN: Initiating transition, generation 18
Feb 14 15:28:46 odin kernel: CMAN: too many transition restarts - will die
Feb 14 15:28:46 odin kernel: CMAN: we are leaving the cluster.
Inconsistent cluster view
Feb 14 15:28:46 odin kernel: WARNING: dlm_emergency_shutdown
Feb 14 15:28:46 odin kernel: WARNING: dlm_emergency_shutdown
Feb 14 15:28:46 odin kernel: SM: 00000002 sm_stop: SG still joined
Feb 14 15:28:46 odin kernel: SM: 01000004 sm_stop: SG still joined
Feb 14 15:28:46 odin kernel: SM: 02000014 sm_stop: SG still joined
Feb 14 15:28:46 odin ccsd[17392]: Cluster manager shutdown.  Attemping
to reconnect...



From ccaulfie at redhat.com  Thu Feb 21 08:30:48 2008
From: ccaulfie at redhat.com (Christine Caulfield)
Date: Thu, 21 Feb 2008 08:30:48 +0000
Subject: [Linux-cluster] Initiating transition message
In-Reply-To: <cfe2fc960802201145j4680ac1fib446ffadf00a95@mail.gmail.com>
References: <cfe2fc960802201145j4680ac1fib446ffadf00a95@mail.gmail.com>
Message-ID: <47BD36B8.6060408@redhat.com>

Shawn Hood wrote:
> Though one instance of 'Initating transition' message seems to be
> normal , what could the behavior shown in the following log indicate?
> What exactly is happening during an 'Initating transition' message?
> 
> Shawn
> 
> Feb 14 15:25:55 odin kernel: CMAN: Initiating transition, generation 7
> Feb 14 15:26:01 odin kernel: CMAN: removing node munin from the
> cluster : No response to messages
> Feb 14 15:26:01 odin kernel: CMAN: Initiating transition, generation 8
> Feb 14 15:26:16 odin kernel: CMAN: Initiating transition, generation 9
> Feb 14 15:26:31 odin kernel: CMAN: Initiating transition, generation 10
> Feb 14 15:26:40 odin su(pam_unix)[20082]: session opened for user root
> by shood(uid=0)
> Feb 14 15:26:46 odin kernel: CMAN: Initiating transition, generation 11
> Feb 14 15:27:01 odin kernel: CMAN: Initiating transition, generation 12
> Feb 14 15:27:16 odin kernel: CMAN: Initiating transition, generation 13
> Feb 14 15:27:31 odin kernel: CMAN: Initiating transition, generation 14
> Feb 14 15:27:46 odin kernel: CMAN: Initiating transition, generation 15
> Feb 14 15:28:01 odin kernel: CMAN: Initiating transition, generation 16
> Feb 14 15:28:16 odin kernel: CMAN: Initiating transition, generation 17
> Feb 14 15:28:31 odin kernel: CMAN: Initiating transition, generation 18
> Feb 14 15:28:46 odin kernel: CMAN: too many transition restarts - will die
> Feb 14 15:28:46 odin kernel: CMAN: we are leaving the cluster.
> Inconsistent cluster view
> Feb 14 15:28:46 odin kernel: WARNING: dlm_emergency_shutdown
> Feb 14 15:28:46 odin kernel: WARNING: dlm_emergency_shutdown
> Feb 14 15:28:46 odin kernel: SM: 00000002 sm_stop: SG still joined
> Feb 14 15:28:46 odin kernel: SM: 01000004 sm_stop: SG still joined
> Feb 14 15:28:46 odin kernel: SM: 02000014 sm_stop: SG still joined
> Feb 14 15:28:46 odin ccsd[17392]: Cluster manager shutdown.  Attemping


The usual cause of all those messages (not that it's usual!) is network
problems. Often a one-way connection can cause it, eg the node can send
messages but not receive them. There are pathological iptables rules
that can make that happen too.

It's hard to be specific without knowing more, but I would investigate
the network connections, routers/switches and routing/iptables rules

Chrissie



From Santosh.Panigrahi at in.unisys.com  Thu Feb 21 10:46:37 2008
From: Santosh.Panigrahi at in.unisys.com (Panigrahi, Santosh Kumar)
Date: Thu, 21 Feb 2008 16:16:37 +0530
Subject: [Linux-cluster] help reqd. - VMware ESX 3.5 fencing
In-Reply-To: <20080220153643.BC30020B3F3@smtp3.ldcom.fr>
References: <D566E8CF3538B54D95B925CB69CB4D2A0C6C4D7B@inblr-exch1.eu.uis.unisys.com>
	<20080220153643.BC30020B3F3@smtp3.ldcom.fr>
Message-ID: <D566E8CF3538B54D95B925CB69CB4D2A0C792136@inblr-exch1.eu.uis.unisys.com>

I have saved your script (as fence_vmware) in both the virtual machines at /sbin directory. Now on running this script I am getting following compilation errors.

 

[root at p2pv6 sbin]# ./fence_vmware

Can't locate VMware/VIM2Runtime.pm in @INC (@INC contains: /usr/lib/perl5/site_perl/5.8.8/i386-linux-thread-multi /usr/lib/perl5/site_perl/5.8.7/i386-linux-thread-multi /usr/lib/perl5/site_perl/5.8.6/i386-linux-thread-multi /usr/lib/perl5/site_perl/5.8.5/i386-linux-thread-multi /usr/lib/perl5/site_perl/5.8.8 /usr/lib/perl5/site_perl/5.8.7 /usr/lib/perl5/site_perl/5.8.6 /usr/lib/perl5/site_perl/5.8.5 /usr/lib/perl5/site_perl /usr/lib/perl5/vendor_perl/5.8.8/i386-linux-thread-multi /usr/lib/perl5/vendor_perl/5.8.7/i386-linux-thread-multi /usr/lib/perl5/vendor_perl/5.8.6/i386-linux-thread-multi /usr/lib/perl5/vendor_perl/5.8.5/i386-linux-thread-multi /usr/lib/perl5/vendor_perl/5.8.8 /usr/lib/perl5/vendor_perl/5.8.7 /usr/lib/perl5/vendor_perl/5.8.6 /usr/lib/perl5/vendor_perl/5.8.5 /usr/lib/perl5/vendor_perl /usr/lib/perl5/5.8.8/i386-linux-thread-multi /usr/lib/perl5/5.8.8 .) at ./fence_vmware line 17.

BEGIN failed--compilation aborted at ./fence_vmware line 17.

 

>From the above logs it seems it is not getting package "use VMware::VIM2Runtime".

I know I am not passing the proper arguments here, but before that this script should be complied properly in Perl environment. I have installed latest VMware Perl APIs on ESX server 3.5 as well as on both VMs.

Am I missing anything here? Please help me to proceed further.

 

Thanks,

Santosh

________________________________

From: linux-cluster-bounces at redhat.com [mailto:linux-cluster-bounces at redhat.com] On Behalf Of MARY, Mathieu
Sent: Wednesday, February 20, 2008 9:08 PM
To: linux clustering
Subject: RE: [Linux-cluster] help reqd. - VMware ESX 3.5 fencing

 

the script i sent to you was, or it should have been this one, apologies if I miscopied, as I tried lots of scripts when I was searching for the good one at the time. 

it uses the VMware::VIM2Runtime wich is the ESX 3.xx perl library

 

 

#!/usr/bin/perl

 

###############################################################################

###############################################################################

##

##  Copyright (C) Sistina Software, Inc.  1997-2003  All rights reserved.

##  Copyright (C) 2004 Red Hat, Inc.  All rights reserved.

##

##  This copyrighted material is made available to anyone wishing to use,

##  modify, copy, or redistribute it subject to the terms and conditions

##  of the GNU General Public License v.2.

##

###############################################################################

###############################################################################

 

use Getopt::Std;

use VMware::VIM2Runtime;

 

# Get the program name from $0 and strip directory names

$_=$0;

s/.*\///;

my $pname = $_;

 

# WARNING!! Do not add code bewteen "#BEGIN_VERSION_GENERATION" and

# "#END_VERSION_GENERATION"  It is generated by the Makefile

 

#BEGIN_VERSION_GENERATION

$FENCE_RELEASE_NAME="2.0.64";

$REDHAT_COPYRIGHT=("Copyright (C) Red Hat, Inc.  2004  All rights reserved.");

$BUILD_DATE="(built Thu Jun 28 07:25:05 EDT 2007)";

#END_VERSION_GENERATION

 

sub usage

{

    print "Usage:\n\n";

    print "$pname [options]\n\n";

    print "Options:\n";

    print "  -a <ip>          IP address or hostname of VirtualCenter server\n";

    print "  -h               Usage\n";

    print "  -n <name>        Virtual machine name to reset\n";

                print "  -l <string>      Login name for VirtualCenter server\n";

    print "  -p <string>      Password for login\n";

    print "  -V               version\n\n";

 

    exit 0;

}

 

sub fail

{

  ($msg) = @_;

  print $msg."\n" unless defined $opt_q;

  $t->close if defined $t;

  exit 1;

}

 

sub fail_usage

{

  ($msg) = @_;

  print STDERR $msg."\n" if $msg;

  print STDERR "Please use '-h' for usage.\n";

  exit 1;

}

 

sub version

{

  print "$pname $FENCE_RELEASE_NAME $BUILD_DATE\n";

  print "$REDHAT_COPYRIGHT\n" if ( $REDHAT_COPYRIGHT );

 

  exit 0;

}

 

if (@ARGV > 0) {

    getopts("a:hn:l:p:V") || fail_usage ;

 

    usage if defined $opt_h;

    version if defined $opt_V;

 

    fail_usage "Unknown parameter." if (@ARGV > 0);

 

    fail_usage "No '-a' flag specified." unless defined $opt_a;

                fail_usage "No '-l' flag specified." unless defined $opt_l;

    fail_usage "No '-p' flag specified." unless defined $opt_p;

    fail_usage "No '-n' flag specified." unless defined $opt_n;

 

} else {

    get_options_stdin();

 

    fail "failed: no IP/host address for the VirtualCenter." unless defined $opt_a;

                fail "failed: no login name provided." unless defined $opt_l;

    fail "failed: no password provided." unless defined $opt_p;

    fail "failed: no VM name specified." unless defined $opt_n;

}

 

#

# Set up and log in

#

 

Vim::login(service_url=>"https://$opt_a/sdk/vimService", user_name=>"$opt_l", password=>"$opt_p");

 

#

# Do the command

#

 

my $vm_view = Vim::find_entity_view(view_type => 'VirtualMachine', filter => {name => $opt_n});

 

if (!$vm_view)

{

        fail "Virtual Machine name not found.";

}

 

$vm_view->ResetVM();

 

Vim::logout();

 

print "success: VM: $opt_n reset.\n";

exit 0;

 

sub get_options_stdin

{

    my $opt;

    my $line = 0;

 

    while( defined($in = <>) )

    {

        $_ = $in;

        chomp;

 

        # strip leading and trailing whitespace

        s/^\s*//;

        s/\s*$//;

 

        # skip comments

        next if /^#/;

 

        $line+=1;

        $opt=$_;

        next unless $opt;

 

        ($name,$val)=split /\s*=\s*/, $opt;

 

        if ( $name eq "" ) {

           print("parse error: illegal name in option $line\n");

           exit 2;

        }

 

        # DO NOTHING -- this field is used by fenced

        elsif ($name eq "agent" ) { }

 

        elsif ($name eq "login" ) {

            $opt_l = $val;

        }

 

        elsif ($name eq "ipaddr" )

        {

            $opt_a = $val;

        }

 

        elsif ($name eq "name" ) { }

 

        elsif ($name eq "passwd" )

        {

            $opt_p = $val;

        }

 

        elsif ($name eq "port" )

        {

            $opt_n = $val;

        }

    }

}

 

 

 

 

Regards,

 

 

Mathieu

________________________________

De : linux-cluster-bounces at redhat.com [mailto:linux-cluster-bounces at redhat.com] De la part de Panigrahi, Santosh Kumar
Envoy? : mercredi 20 f?vrier 2008 14:01
? : linux clustering
Objet : RE: [Linux-cluster] help reqd. - VMware ESX 3.5 fencing

 

Hi,

 

I am facing some issues on trying to fence a node using "fence_vmware" Perl script. This script is attached in this mail.

 

I have a single standalone physical machine installed with VMware ESX 3.5. On top of this I have created 2 VMs with guest OS as Rhel5.1 AP. In both the VMs I have installed VMware Perl APIs. I have kept "fence_vmware" script at /sbin directory on both the VMs. My cluster.conf file is also attached in this mail. I have not configured any service becoz I want only to test VMware fencing agent here.

 

Through conga on trying to fence a node, I am getting following errors in my /var/log/messages.

 

Feb 18 21:12:24 p2pv6 fence_node[5723]: agent "fence_vmware" reports: Global symbol "$RELEASE_VERSION" requires explicit package name at /sbin/fence_vmware line 102. Global symbol "$BUILD_DATE" requires explicit package name at /sbin/fence_vmware line 102. Global symbol "$REDHAT_COPYRIGHT" requires explicit package name at

Feb 18 21:12:24 p2pv6 fence_node[5723]: agent "fence_vmware" reports: /sbin/fence_vmware line 103. Global symbol "$REDHAT_COPYRIGHT" requires explicit package name at /sbin/fence_vmware line 103. Global symbol "$opt_ZZv" requires explicit package name at /sbin/fence_vmware line 267. Global symbol "$pwd_script_out" requires

Feb 18 21:12:24 p2pv6 fence_node[5723]: agent "fence_vmware" reports: explicit package name at /sbin/fence_vmware line 300. Global symbol "$pwd_script_out" requires explicit package name at /sbin/fence_vmware line 301. Global symbol "$pwd_script_out" requires explicit package name at /sbin/fence_vmware line 302. Global symb

Feb 18 21:12:24 p2pv6 fence_node[5723]: agent "fence_vmware" reports: ol "$pwd_script_out" requires explicit package name at /sbin/fence_vmware line 303. Global symbol "$pwd_script_out" requires explicit package name at /sbin/fence_vmware line 322. Global symbol "$pwd_script_out" requires explicit package name at /sbin/fenc

Feb 18 21:12:24 p2pv6 fence_node[5723]: agent "fence_vmware" reports: e_vmware line 323. Global symbol "$pwd_script_out" requires explicit package name at /sbin/fence_vmware line 324. Global symbol "$pwd_script_out" requires explicit package name at /sbin/fence_vmware line 325. Bareword "version" not allowed while "strict s

Feb 18 21:12:24 p2pv6 fence_node[5723]: agent "fence_vmware" reports: ubs" in use at /sbin/fence_vmware line 291. Execution of /sbin/fence_vmware aborted due to compilation errors.

Feb 18 21:12:24 p2pv6 fence_node[5723]: Fence of "p2pv5.tr.unisys.com" was unsuccessful

 

My initial guess is this fencing agent script can only be run with old VMware Perl APIs. Please correct me. Is there any way to run this script in my current environment?

 

If anyone is having a working script for VMware ESX 3.5 server, please pass it.

 

Thanks,

Santosh

 

________________________________

From: linux-cluster-bounces at redhat.com [mailto:linux-cluster-bounces at redhat.com] On Behalf Of MARY, Mathieu
Sent: Thursday, February 14, 2008 6:39 PM
To: linux clustering
Subject: RE: [Linux-cluster] help reqd. - VMware ESX 3.5 fencing

 

VC is the virtual center server, i understood from your mail that you're using virtual infrastructure, but you question points out the fact that you maybe are using standalone ESX server ?

in our configuration we use an ESX farm of 4 servers managed by the VC server where we connect with the VI client

 

 

<fencedevice name="your_fence_method" agent="fence_vi3" ipaddr="yourserver_ip" port="your_vm_name" login="xxx" passwd="yyyyy"/>

 

though I don't know if it works on standalone server, maybe you would have ton install the VMI perlmodules described inside the script to you ESX 3.5 server

 

________________________________

De : linux-cluster-bounces at redhat.com [mailto:linux-cluster-bounces at redhat.com] De la part de Panigrahi, Santosh Kumar
Envoy? : jeudi 14 f?vrier 2008 13:50
? : linux clustering
Objet : RE: [Linux-cluster] help reqd. - VMware ESX 3.5 fencing

 

Thanks Marry for the script. I will test and let you know. By the way what's this VC server? Is it the system where I am running my VI client?

Can you please elaborate little more on this configuration like where I will keep this script, what will I mention in my cluster.conf file and etc.

 

Thanks,

Santosh  

________________________________

From: linux-cluster-bounces at redhat.com [mailto:linux-cluster-bounces at redhat.com] On Behalf Of MARY, Mathieu
Sent: Thursday, February 14, 2008 5:59 PM
To: linux clustering
Subject: RE: [Linux-cluster] help reqd. - VMware ESX 3.5 fencing

 

hello,

 

i'm using this script for VI 3 and  ESX3.02 i guess it would work for you too, cannot remember where I found it though :-)

note that you have to send the restart request to your VC server and not to the ESX server

 

________________________________

De : linux-cluster-bounces at redhat.com [mailto:linux-cluster-bounces at redhat.com] De la part de Panigrahi, Santosh Kumar
Envoy? : jeudi 14 f?vrier 2008 12:37
? : linux-cluster at redhat.com
Objet : [Linux-cluster] help reqd. - VMware ESX 3.5 fencing

 

Hi,

 

Does anybody have configured fencing in VMware ESX 3.5 environment? I appreciate any help.

 

I have got some info from http://www.tournament.org.il/run/index.php?/archives/140-VMware-Fencing-in-RedHat-Cluster-5-RHCS5.html .

This script given here is for VMware server. Any idea whether it will work for ESX 3.5 server or not?

 

My system configurations are as follows.

 

Host machine    : Unisys ES7000-one with host OS as VMware ESX 3.5

Guest Machines: Guest OS as Rhel5.1 AP

 

I am connecting to host machine using VMware VI 3.0.

 

Thanks,

Santosh

 

 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://listman.redhat.com/archives/linux-cluster/attachments/20080221/86ffc62b/attachment.htm>

From raycharles_man at yahoo.com  Thu Feb 21 16:02:37 2008
From: raycharles_man at yahoo.com (Ray Charles)
Date: Thu, 21 Feb 2008 08:02:37 -0800 (PST)
Subject: [Linux-cluster] Defending GFS
In-Reply-To: <b86c876f0802201043v4a1886c5h9b24effc3baa20e@mail.gmail.com>
Message-ID: <902973.46360.qm@web32104.mail.mud.yahoo.com>


Well that is a way to respond to an issue.  Anyone
know of a way to detect when GFS is having problems,
say by way of messages or logging or perhaps even
somewhere in /proc ?

-tia

--- Pedro Espinoza <raindoctor at gmail.com> wrote:

> We ran into such problems few times: my collegue
> just reboots that node;)
> 
> 
> On 2/19/08, Ray Charles <raycharles_man at yahoo.com>
> wrote:
> >
> >
> > Hi all,
> >
> > GFS ver 6.1, not gfs2.
> >
> > I am looking for an intelligent way to defend the
> use
> > of gfs on a prod cluster. Every time there's an
> issue
> > I hear a cacophony of voices that declare that
> "GFS
> > caused ... whatever."
> >
> > Most recently there was an instance where doing an
> ls
> > of a certain sub dir that happened to be on a GFS
> > partition just hung. All other sub dir in that
> same
> > partition could be navigated. Does that sound like
> a
> > typical scenario? Aside from the system log is
> there
> > any other place to check??
> >
> > If gfs gets into a funny state how can i detect it
> or
> > test for it?
> >
> > tia-
> >
> > -Ray
> >
> >
> >
> >
> >     
>
____________________________________________________________________________________
> > Never miss a thing.  Make Yahoo your home page.
> > http://www.yahoo.com/r/hs
> >
> > --
> > Linux-cluster mailing list
> > Linux-cluster at redhat.com
> >
>
https://www.redhat.com/mailman/listinfo/linux-cluster
> >
> 
> --
> Linux-cluster mailing list
> Linux-cluster at redhat.com
>
https://www.redhat.com/mailman/listinfo/linux-cluster
> 



      ____________________________________________________________________________________
Never miss a thing.  Make Yahoo your home page. 
http://www.yahoo.com/r/hs



From gordan at bobich.net  Thu Feb 21 16:09:11 2008
From: gordan at bobich.net (gordan at bobich.net)
Date: Thu, 21 Feb 2008 16:09:11 +0000 (GMT)
Subject: [Linux-cluster] Defending GFS
In-Reply-To: <902973.46360.qm@web32104.mail.mud.yahoo.com>
References: <902973.46360.qm@web32104.mail.mud.yahoo.com>
Message-ID: <alpine.LRH.1.00.0802211605400.17266@skynet.shatteredsilicon.net>

If it's having problems, it's usually detected pretty quickly, and when it 
gets detected it screams about it on the console and in the syslog, and 
disconnects the FS. The node most likely gets fenced at that point.

What distribution, kernel, gfs tools, etc. are you using? What is your 
shared storage?

Gordan

On Thu, 21 Feb 2008, Ray Charles wrote:

>
> Well that is a way to respond to an issue.  Anyone
> know of a way to detect when GFS is having problems,
> say by way of messages or logging or perhaps even
> somewhere in /proc ?
>
> -tia
>
> --- Pedro Espinoza <raindoctor at gmail.com> wrote:
>
>> We ran into such problems few times: my collegue
>> just reboots that node;)
>>
>>
>> On 2/19/08, Ray Charles <raycharles_man at yahoo.com>
>> wrote:
>>>
>>>
>>> Hi all,
>>>
>>> GFS ver 6.1, not gfs2.
>>>
>>> I am looking for an intelligent way to defend the
>> use
>>> of gfs on a prod cluster. Every time there's an
>> issue
>>> I hear a cacophony of voices that declare that
>> "GFS
>>> caused ... whatever."
>>>
>>> Most recently there was an instance where doing an
>> ls
>>> of a certain sub dir that happened to be on a GFS
>>> partition just hung. All other sub dir in that
>> same
>>> partition could be navigated. Does that sound like
>> a
>>> typical scenario? Aside from the system log is
>> there
>>> any other place to check??
>>>
>>> If gfs gets into a funny state how can i detect it
>> or
>>> test for it?
>>>
>>> tia-
>>>
>>> -Ray
>>>
>>>
>>>
>>>
>>>
>>
> ____________________________________________________________________________________
>>> Never miss a thing.  Make Yahoo your home page.
>>> http://www.yahoo.com/r/hs
>>>
>>> --
>>> Linux-cluster mailing list
>>> Linux-cluster at redhat.com
>>>
>>
> https://www.redhat.com/mailman/listinfo/linux-cluster
>>>
>>
>> --
>> Linux-cluster mailing list
>> Linux-cluster at redhat.com
>>
> https://www.redhat.com/mailman/listinfo/linux-cluster
>>
>
>
>
>      ____________________________________________________________________________________
> Never miss a thing.  Make Yahoo your home page.
> http://www.yahoo.com/r/hs
>
> --
> Linux-cluster mailing list
> Linux-cluster at redhat.com
> https://www.redhat.com/mailman/listinfo/linux-cluster
>



From l_x2828 at yahoo.com  Thu Feb 21 16:27:28 2008
From: l_x2828 at yahoo.com (BJ)
Date: Thu, 21 Feb 2008 08:27:28 -0800 (PST)
Subject: [Linux-cluster] Help - upgrading & rebooting one node makes another
	node fenced
Message-ID: <197900.59441.qm@web55510.mail.re4.yahoo.com>

Hi,

It would be appreciated if some on could help me on
this.

We have a cluster with three nodes:

NODE1: GFS-6.0.2-25
NODE2: GFS-6.0.2.36-1
NODE3: GFS-6.0.2-25

All three nodes connect to a FC switch which is used
as the fencing device.  Before we upgrade NODE3,
"gulm_tool nodelist localhost" shows all 3 nodes are
in the cluster and NODE1 is master.

After upgrade NODE3 from GFS-6.0.2-25 to
GFS-6.0.2.36-1 and reboot it, NODE2 missed three
heartbeats and then got fenced (see kernel log below)
and the FC port connected to NODE2 was disabled by
fencing (LED on that port was changed from green to
yellow).

Could some one please tell me why this could happen
and how to avoid it, or what do we need to check for
troubleshooting this issue?  I'm not very familiar
with GFS yet.

Regards,
BJ


Feb 19 18:45:16 NODE1 lock_gulmd_core[2617]: New
Client: idx:4 fd:9 from (192.168.20.111:NODE3) 
Feb 19 18:45:17 NODE1 lock_gulmd_LT000[2618]: Attached
slave NODE3:192.168.20.111 idx:5 fd:10 (soff:2
connected:0xc) 
Feb 19 18:45:18 NODE1 lock_gulmd_LT000[2618]: New
Client: idx 6 fd 11 from (192.168.20.111:NODE3) 
Feb 19 18:52:46 NODE1 kernel: scsi(0): RSCN database
changed -0x3,0x200.
Feb 19 18:52:46 NODE1 kernel: scsi(0): Waiting for LIP
to complete...
Feb 19 18:52:46 NODE1 kernel: scsi(0): Topology -
(F_Port), Host Loop address 0xffff
Feb 19 18:52:50 NODE1 lock_gulmd_core[2617]: NODE2
missed a heartbeat (time:1203468770103133 mb:1) 
Feb 19 18:53:05 NODE1 lock_gulmd_core[2617]: NODE2
missed a heartbeat (time:1203468785123133 mb:2) 
Feb 19 18:53:20 NODE1 lock_gulmd_core[2617]: NODE2
missed a heartbeat (time:1203468800143149 mb:3) 
Feb 19 18:53:20 NODE1 lock_gulmd_core[2617]: Client
(NODE2) expired 
Feb 19 18:53:20 NODE1 lock_gulmd_core[4968]: Gonna
exec fence_node NODE2 
Feb 19 18:53:20 NODE1 lock_gulmd_core[2617]: Forked
[4968] fence_node NODE2 with a 0 pause. 
Feb 19 18:53:20 NODE1 fence_node[4968]: Performing
fence method, Brocade, on NODE2. 
Feb 19 18:53:21 NODE1 fence_node[4968]: The agent
(fence_brocade) reports: success: portdisable 2  
Feb 19 18:53:21 NODE1 fence_node[4968]: Fence of
"NODE2" was successful. 
Feb 19 18:53:21 NODE1 lock_gulmd_core[2617]: found
match on pid 4968, marking node NODE2 as logged out. 
Feb 19 18:53:21 NODE1 kernel: lock_gulm: Checking for
journals for node "NODE2"
Feb 19 18:53:21 NODE1 kernel: GFS:
fsid=MY-CLUSTER:pool_gfs.0: jid=1: Trying to acquire
journal lock...
Feb 19 18:53:21 NODE1 kernel: GFS:
fsid=MY-CLUSTER:pool_gfs.0: jid=1: Looking at
journal...
Feb 19 18:53:21 NODE1 kernel: GFS:
fsid=MY-CLUSTER:pool_gfs.0: jid=1: Done






      ____________________________________________________________________________________
Looking for last minute shopping deals?  
Find them fast with Yahoo! Search.  http://tools.search.yahoo.com/newsearch/category.php?category=shopping



From shawnlhood at gmail.com  Thu Feb 21 19:13:05 2008
From: shawnlhood at gmail.com (Shawn Hood)
Date: Thu, 21 Feb 2008 14:13:05 -0500
Subject: [Linux-cluster] Initiating transition message
In-Reply-To: <47BD36B8.6060408@redhat.com>
References: <cfe2fc960802201145j4680ac1fib446ffadf00a95@mail.gmail.com>
	<47BD36B8.6060408@redhat.com>
Message-ID: <cfe2fc960802211113k8940c0eg99faa528032eb680@mail.gmail.com>

While this explains the situation somewhat, I was trying to bring a
bit more clarity to the problem (without examining th esource).  What
exactly is happening when a 'initiates transition'?

Shawn

On Thu, Feb 21, 2008 at 3:30 AM, Christine Caulfield
<ccaulfie at redhat.com> wrote:
>
> Shawn Hood wrote:
>  > Though one instance of 'Initating transition' message seems to be
>  > normal , what could the behavior shown in the following log indicate?
>  > What exactly is happening during an 'Initating transition' message?
>  >
>  > Shawn
>  >
>  > Feb 14 15:25:55 odin kernel: CMAN: Initiating transition, generation 7
>  > Feb 14 15:26:01 odin kernel: CMAN: removing node munin from the
>  > cluster : No response to messages
>  > Feb 14 15:26:01 odin kernel: CMAN: Initiating transition, generation 8
>  > Feb 14 15:26:16 odin kernel: CMAN: Initiating transition, generation 9
>  > Feb 14 15:26:31 odin kernel: CMAN: Initiating transition, generation 10
>  > Feb 14 15:26:40 odin su(pam_unix)[20082]: session opened for user root
>  > by shood(uid=0)
>  > Feb 14 15:26:46 odin kernel: CMAN: Initiating transition, generation 11
>  > Feb 14 15:27:01 odin kernel: CMAN: Initiating transition, generation 12
>  > Feb 14 15:27:16 odin kernel: CMAN: Initiating transition, generation 13
>  > Feb 14 15:27:31 odin kernel: CMAN: Initiating transition, generation 14
>  > Feb 14 15:27:46 odin kernel: CMAN: Initiating transition, generation 15
>  > Feb 14 15:28:01 odin kernel: CMAN: Initiating transition, generation 16
>  > Feb 14 15:28:16 odin kernel: CMAN: Initiating transition, generation 17
>  > Feb 14 15:28:31 odin kernel: CMAN: Initiating transition, generation 18
>  > Feb 14 15:28:46 odin kernel: CMAN: too many transition restarts - will die
>  > Feb 14 15:28:46 odin kernel: CMAN: we are leaving the cluster.
>  > Inconsistent cluster view
>  > Feb 14 15:28:46 odin kernel: WARNING: dlm_emergency_shutdown
>  > Feb 14 15:28:46 odin kernel: WARNING: dlm_emergency_shutdown
>  > Feb 14 15:28:46 odin kernel: SM: 00000002 sm_stop: SG still joined
>  > Feb 14 15:28:46 odin kernel: SM: 01000004 sm_stop: SG still joined
>  > Feb 14 15:28:46 odin kernel: SM: 02000014 sm_stop: SG still joined
>  > Feb 14 15:28:46 odin ccsd[17392]: Cluster manager shutdown.  Attemping
>
>
>  The usual cause of all those messages (not that it's usual!) is network
>  problems. Often a one-way connection can cause it, eg the node can send
>  messages but not receive them. There are pathological iptables rules
>  that can make that happen too.
>
>  It's hard to be specific without knowing more, but I would investigate
>  the network connections, routers/switches and routing/iptables rules
>
>  Chrissie
>
>  --
>  Linux-cluster mailing list
>  Linux-cluster at redhat.com
>  https://www.redhat.com/mailman/listinfo/linux-cluster
>



-- 
Shawn Hood
(910) 670-1819 Mobile



From jon at floorboard.com  Thu Feb 21 19:43:04 2008
From: jon at floorboard.com (Jonathan Biggar)
Date: Thu, 21 Feb 2008 11:43:04 -0800
Subject: [Linux-cluster] Using qdisk and a watchdog timer to eliminate power
 fencing single point of failure?
Message-ID: <fpkk96$h4s$1@ger.gmane.org>

I've got a deployment scenario for a two node cluster (where services 
are configured as active and standby) where the customer is concerned 
that the external power fencing device I am using (WTI) becomes a single 
point of failure.  If the WTI for the active node dies, taking down the 
active node, the standby cannot bring up services because it cannot 
successfully fence the failed node.  This leaves the cluster down.

In the setup, storage fencing is not feasible as a backup for power fencing.

I think I've worked out a scenario using qdiskd and the internal 
hardware watchdog timers in our nodes to use as a backup for power 
fencing that I hope will eliminate the single point of failure.

Here's how I see it working:

1.  Configure a quorum disk for the two nodes.

2.  Create a heuristic (besides the usual network reachability test) for 
qdisk that resets the node's hardware watchdog timer.  (I'll have to do 
some additional work to ensure that the watchdog gets turned off if I am 
gracefully shutting down the node's qdisk daemon.)

3.  Create a custom fencing script that is run if power fencing fails 
that examines qdisk's state to see if the node that needs to be fenced 
is no longer updating the quorum disk.   (I'm not sure how to do this--I 
hope that the information in stored in qdisk's status_file will be 
sufficient to determine this, if not, I might have to modify qdisk to 
supply what I need.)  This script will wait until it sees that the 
failed node has not updated the quorum disk for longer than the watchdog 
timer setting plus a safety margin, and then return success.  If it sees 
the other node is still updating the quorum disk, it will return failure.

The standby node then should be sure that the active node has rebooted 
itself either by qdiskd's action or via the watchdog timer, or else it 
is power dead.

Can anyone see a weakness in this approach I haven't thought of?

-- 
Jon Biggar
Floorboard Software
jon at floorboard.com
jon at biggar.org



From Christopher.Barry at qlogic.com  Thu Feb 21 23:13:55 2008
From: Christopher.Barry at qlogic.com (chris barry)
Date: Thu, 21 Feb 2008 18:13:55 -0500
Subject: [Linux-cluster] gfs 5.1 question
Message-ID: <1203635635.5257.111.camel@localhost>

Ok, a question for the old-timers:

gfs 5.1
GULM
RH 7.3, custom kernel
~350GB FC array.
Eg. ancient stuff - can't change it. migrating to new gfs cluster I just
built soon.

df shows 84% of volume used, but writes say out of space.

What tests can I do to determine why this is, and better how can I
eliminate this unwritable 16%? Do I need to 'reclaim' inodes or
something?


Thanks,
-C



From rpeterso at redhat.com  Thu Feb 21 23:29:15 2008
From: rpeterso at redhat.com (Bob Peterson)
Date: Thu, 21 Feb 2008 17:29:15 -0600
Subject: [Linux-cluster] gfs 5.1 question
In-Reply-To: <1203635635.5257.111.camel@localhost>
References: <1203635635.5257.111.camel@localhost>
Message-ID: <1203636555.3305.26.camel@technetium.msp.redhat.com>

On Thu, 2008-02-21 at 18:13 -0500, chris barry wrote:
> Ok, a question for the old-timers:
> 
> gfs 5.1
> GULM
> RH 7.3, custom kernel
> ~350GB FC array.
> Eg. ancient stuff - can't change it. migrating to new gfs cluster I just
> built soon.
> 
> df shows 84% of volume used, but writes say out of space.
> 
> What tests can I do to determine why this is, and better how can I
> eliminate this unwritable 16%? Do I need to 'reclaim' inodes or
> something?
> 
> 
> Thanks,
> -C

Hi Chris,

My guess is that the 16% is tied up in free metadata.
You may want to do a "gfs_tool reclaim" to turn the free metadata into
free data blocks.  (And as always, those will in turn be turned back
into metadata blocks as needed.)

Regards,

Bob Peterson
Red Hat GFS




From Christopher.Barry at qlogic.com  Thu Feb 21 23:34:34 2008
From: Christopher.Barry at qlogic.com (chris barry)
Date: Thu, 21 Feb 2008 18:34:34 -0500
Subject: [Linux-cluster] gfs 5.1 question
In-Reply-To: <1203636555.3305.26.camel@technetium.msp.redhat.com>
References: <1203635635.5257.111.camel@localhost>
	<1203636555.3305.26.camel@technetium.msp.redhat.com>
Message-ID: <1203636875.5257.119.camel@localhost>

On Thu, 2008-02-21 at 17:29 -0600, Bob Peterson wrote:
> On Thu, 2008-02-21 at 18:13 -0500, chris barry wrote:
> > Ok, a question for the old-timers:
> > 
> > gfs 5.1
> > GULM
> > RH 7.3, custom kernel
> > ~350GB FC array.
> > Eg. ancient stuff - can't change it. migrating to new gfs cluster I just
> > built soon.
> > 
> > df shows 84% of volume used, but writes say out of space.
> > 
> > What tests can I do to determine why this is, and better how can I
> > eliminate this unwritable 16%? Do I need to 'reclaim' inodes or
> > something?
> > 
> > 
> > Thanks,
> > -C
> 
> Hi Chris,
> 
> My guess is that the 16% is tied up in free metadata.
> You may want to do a "gfs_tool reclaim" to turn the free metadata into
> free data blocks.  (And as always, those will in turn be turned back
> into metadata blocks as needed.)
> 
> Regards,
> 
> Bob Peterson
> Red Hat GFS
> 

Hi Bob,

Thanks for getting back so soon.

Anything dangerous or scary about this? Will it take a long time?

Regards,
-C



From Christopher.Barry at qlogic.com  Fri Feb 22 00:38:33 2008
From: Christopher.Barry at qlogic.com (chris barry)
Date: Thu, 21 Feb 2008 19:38:33 -0500
Subject: [Linux-cluster] help reqd. - VMware ESX 3.5 fencing
In-Reply-To: <D566E8CF3538B54D95B925CB69CB4D2A0C792136@inblr-exch1.eu.uis.unisys.com>
References: <D566E8CF3538B54D95B925CB69CB4D2A0C6C4D7B@inblr-exch1.eu.uis.unisys.com>
	<20080220153643.BC30020B3F3@smtp3.ldcom.fr>
	<D566E8CF3538B54D95B925CB69CB4D2A0C792136@inblr-exch1.eu.uis.unisys.com>
Message-ID: <1203640714.5257.127.camel@localhost>

Use this script I hacked out of various parts. fence_vi3

Ideally you point it at the VC box, as it will down a node even if it
has migrated to another esx box, but it can be pointed directly at the
ESX box just as well.

You will need the viperltoolkit installed on all your nodes.
Part of the toolkit I had to manually install - read the attached
script.

Regards,
Christoper Barry


On Thu, 2008-02-21 at 16:16 +0530, Panigrahi, Santosh Kumar wrote:
> I have saved your script (as fence_vmware) in both the virtual
> machines at /sbin directory. Now on running this script I am getting
> following compilation errors.
> 
>  
> 
> [root at p2pv6 sbin]# ./fence_vmware
> 
> Can't locate VMware/VIM2Runtime.pm in @INC (@INC
> contains: /usr/lib/perl5/site_perl/5.8.8/i386-linux-thread-multi /usr/lib/perl5/site_perl/5.8.7/i386-linux-thread-multi /usr/lib/perl5/site_perl/5.8.6/i386-linux-thread-multi /usr/lib/perl5/site_perl/5.8.5/i386-linux-thread-multi /usr/lib/perl5/site_perl/5.8.8 /usr/lib/perl5/site_perl/5.8.7 /usr/lib/perl5/site_perl/5.8.6 /usr/lib/perl5/site_perl/5.8.5 /usr/lib/perl5/site_perl /usr/lib/perl5/vendor_perl/5.8.8/i386-linux-thread-multi /usr/lib/perl5/vendor_perl/5.8.7/i386-linux-thread-multi /usr/lib/perl5/vendor_perl/5.8.6/i386-linux-thread-multi /usr/lib/perl5/vendor_perl/5.8.5/i386-linux-thread-multi /usr/lib/perl5/vendor_perl/5.8.8 /usr/lib/perl5/vendor_perl/5.8.7 /usr/lib/perl5/vendor_perl/5.8.6 /usr/lib/perl5/vendor_perl/5.8.5 /usr/lib/perl5/vendor_perl /usr/lib/perl5/5.8.8/i386-linux-thread-multi /usr/lib/perl5/5.8.8 .) at ./fence_vmware line 17.
> 
> BEGIN failed--compilation aborted at ./fence_vmware line 17.
> 
>  
> 
> From the above logs it seems it is not getting package ?use
> VMware::VIM2Runtime?.
> 
> I know I am not passing the proper arguments here, but before that
> this script should be complied properly in Perl environment. I have
> installed latest VMware Perl APIs on ESX server 3.5 as well as on both
> VMs.
> 
> Am I missing anything here? Please help me to proceed further.
> 
>  
> 
> Thanks,
> 
> Santosh
> 
>                                    
> ______________________________________________________________________
> From:linux-cluster-bounces at redhat.com
> [mailto:linux-cluster-bounces at redhat.com] On Behalf Of MARY, Mathieu
> Sent: Wednesday, February 20, 2008 9:08 PM
> To: linux clustering
> Subject: RE: [Linux-cluster] help reqd. - VMware ESX 3.5 fencing
> 
> 
>  
> 
> the script i sent to you was, or it should have been this one,
> apologies if I miscopied, as I tried lots of scripts when I was
> searching for the good one at the time. 
> 
> it uses the VMware::VIM2Runtime wich is the ESX 3.xx perl library
> 
>  
> 
>  
> 
> #!/usr/bin/perl
> 
>  
> 
> ###############################################################################
> 
> ###############################################################################
> 
> ##
> 
> ##  Copyright (C) Sistina Software, Inc.  1997-2003  All rights
> reserved.
> 
> ##  Copyright (C) 2004 Red Hat, Inc.  All rights reserved.
> 
> ##
> 
> ##  This copyrighted material is made available to anyone wishing to
> use,
> 
> ##  modify, copy, or redistribute it subject to the terms and
> conditions
> 
> ##  of the GNU General Public License v.2.
> 
> ##
> 
> ###############################################################################
> 
> ###############################################################################
> 
>  
> 
> use Getopt::Std;
> 
> use VMware::VIM2Runtime;
> 
>  
> 
> # Get the program name from $0 and strip directory names
> 
> $_=$0;
> 
> s/.*\///;
> 
> my $pname = $_;
> 
>  
> 
> # WARNING!! Do not add code bewteen "#BEGIN_VERSION_GENERATION" and
> 
> # "#END_VERSION_GENERATION"  It is generated by the Makefile
> 
>  
> 
> #BEGIN_VERSION_GENERATION
> 
> $FENCE_RELEASE_NAME="2.0.64";
> 
> $REDHAT_COPYRIGHT=("Copyright (C) Red Hat, Inc.  2004  All rights
> reserved.");
> 
> $BUILD_DATE="(built Thu Jun 28 07:25:05 EDT 2007)";
> 
> #END_VERSION_GENERATION
> 
>  
> 
> sub usage
> 
> {
> 
>    print "Usage:\n\n";
> 
>     print "$pname [options]\n\n";
> 
>     print "Options:\n";
> 
>     print "  -a <ip>          IP address or hostname of VirtualCenter
> server\n";
> 
>     print "  -h               Usage\n";
> 
>     print "  -n <name>        Virtual machine name to reset\n";
> 
>                 print "  -l <string>      Login name for VirtualCenter
> server\n";
> 
>     print "  -p <string>      Password for login\n";
> 
>    print "  -V               version\n\n";
> 
>  
> 
>     exit 0;
> 
> }
> 
>  
> 
> sub fail
> 
> {
> 
>   ($msg) = @_;
> 
>   print $msg."\n" unless defined $opt_q;
> 
>   $t->close if defined $t;
> 
>   exit 1;
> 
> }
> 
>  
> 
> sub fail_usage
> 
> {
> 
>   ($msg) = @_;
> 
>   print STDERR $msg."\n" if $msg;
> 
>   print STDERR "Please use '-h' for usage.\n";
> 
>   exit 1;
> 
> }
> 
>  
> 
> sub version
> 
> {
> 
>   print "$pname $FENCE_RELEASE_NAME $BUILD_DATE\n";
> 
>   print "$REDHAT_COPYRIGHT\n" if ( $REDHAT_COPYRIGHT );
> 
>  
> 
>   exit 0;
> 
> }
> 
>  
> 
> if (@ARGV > 0) {
> 
>     getopts("a:hn:l:p:V") || fail_usage ;
> 
>  
> 
>     usage if defined $opt_h;
> 
>     version if defined $opt_V;
> 
>  
> 
>     fail_usage "Unknown parameter." if (@ARGV > 0);
> 
>  
> 
>     fail_usage "No '-a' flag specified." unless defined $opt_a;
> 
>                 fail_usage "No '-l' flag specified." unless defined
> $opt_l;
> 
>     fail_usage "No '-p' flag specified." unless defined $opt_p;
> 
>     fail_usage "No '-n' flag specified." unless defined $opt_n;
> 
>  
> 
> } else {
> 
>     get_options_stdin();
> 
>  
> 
>     fail "failed: no IP/host address for the VirtualCenter." unless
> defined $opt_a;
> 
>                 fail "failed: no login name provided." unless defined
> $opt_l;
> 
>     fail "failed: no password provided." unless defined $opt_p;
> 
>     fail "failed: no VM name specified." unless defined $opt_n;
> 
> }
> 
>  
> 
> #
> 
> # Set up and log in
> 
> #
> 
>  
> 
> Vim::login(service_url=>"https://$opt_a/sdk/vimService",
> user_name=>"$opt_l", password=>"$opt_p");
> 
>  
> 
> #
> 
> # Do the command
> 
> #
> 
>  
> 
> my $vm_view = Vim::find_entity_view(view_type => 'VirtualMachine',
> filter => {name => $opt_n});
> 
>  
> 
> if (!$vm_view)
> 
> {
> 
>         fail "Virtual Machine name not found.";
> 
> }
> 
>  
> 
> $vm_view->ResetVM();
> 
>  
> 
> Vim::logout();
> 
>  
> 
> print "success: VM: $opt_n reset.\n";
> 
> exit 0;
> 
>  
> 
> sub get_options_stdin
> 
> {
> 
>     my $opt;
> 
>     my $line = 0;
> 
>  
> 
>     while( defined($in = <>) )
> 
>     {
> 
>         $_ = $in;
> 
>         chomp;
> 
>  
> 
>         # strip leading and trailing whitespace
> 
>         s/^\s*//;
> 
>         s/\s*$//;
> 
>  
> 
>         # skip comments
> 
>         next if /^#/;
> 
>  
> 
>         $line+=1;
> 
>         $opt=$_;
> 
>         next unless $opt;
> 
>  
> 
>         ($name,$val)=split /\s*=\s*/, $opt;
> 
>  
> 
>        if ( $name eq "" ) {
> 
>            print("parse error: illegal name in option $line\n");
> 
>            exit 2;
> 
>         }
> 
>  
> 
>         # DO NOTHING -- this field is used by fenced
> 
>         elsif ($name eq "agent" ) { }
> 
>  
> 
>         elsif ($name eq "login" ) {
> 
>             $opt_l = $val;
> 
>         }
> 
>  
> 
>         elsif ($name eq "ipaddr" )
> 
>         {
> 
>             $opt_a = $val;
> 
>         }
> 
>  
> 
>         elsif ($name eq "name" ) { }
> 
>  
> 
>         elsif ($name eq "passwd" )
> 
>         {
> 
>             $opt_p = $val;
> 
>         }
> 
>  
> 
>         elsif ($name eq "port" )
> 
>         {
> 
>             $opt_n = $val;
> 
>         }
> 
>     }
> 
> }
> 
>  
> 
>  
> 
>  
> 
>  
> 
> Regards,
> 
>  
> 
>  
> 
> Mathieu
> 
>                                    
> ______________________________________________________________________
> De : linux-cluster-bounces at redhat.com
> [mailto:linux-cluster-bounces at redhat.com] De la part de Panigrahi,
> Santosh Kumar
> Envoy? : mercredi 20 f?vrier 2008 14:01
> ? : linux clustering
> Objet : RE: [Linux-cluster] help reqd. - VMware ESX 3.5 fencing
> 
> 
>  
> 
> Hi,
> 
>  
> 
> I am facing some issues on trying to fence a node using ?fence_vmware?
> Perl script. This script is attached in this mail.
> 
>  
> 
> I have a single standalone physical machine installed with VMware ESX
> 3.5. On top of this I have created 2 VMs with guest OS as Rhel5.1 AP.
> In both the VMs I have installed VMware Perl APIs. I have kept
> ?fence_vmware? script at /sbin directory on both the VMs. My
> cluster.conf file is also attached in this mail. I have not configured
> any service becoz I want only to test VMware fencing agent here.
> 
>  
> 
> Through conga on trying to fence a node, I am getting following errors
> in my /var/log/messages.
> 
>  
> 
> Feb 18 21:12:24 p2pv6 fence_node[5723]: agent "fence_vmware" reports:
> Global symbol "$RELEASE_VERSION" requires explicit package name
> at /sbin/fence_vmware line 102. Global symbol "$BUILD_DATE" requires
> explicit package name at /sbin/fence_vmware line 102. Global symbol
> "$REDHAT_COPYRIGHT" requires explicit package name at
> 
> Feb 18 21:12:24 p2pv6 fence_node[5723]: agent "fence_vmware"
> reports: /sbin/fence_vmware line 103. Global symbol
> "$REDHAT_COPYRIGHT" requires explicit package name
> at /sbin/fence_vmware line 103. Global symbol "$opt_ZZv" requires
> explicit package name at /sbin/fence_vmware line 267. Global symbol
> "$pwd_script_out" requires
> 
> Feb 18 21:12:24 p2pv6 fence_node[5723]: agent "fence_vmware" reports:
> explicit package name at /sbin/fence_vmware line 300. Global symbol
> "$pwd_script_out" requires explicit package name at /sbin/fence_vmware
> line 301. Global symbol "$pwd_script_out" requires explicit package
> name at /sbin/fence_vmware line 302. Global symb
> 
> Feb 18 21:12:24 p2pv6 fence_node[5723]: agent "fence_vmware" reports:
> ol "$pwd_script_out" requires explicit package name
> at /sbin/fence_vmware line 303. Global symbol "$pwd_script_out"
> requires explicit package name at /sbin/fence_vmware line 322. Global
> symbol "$pwd_script_out" requires explicit package name at /sbin/fenc
> 
> Feb 18 21:12:24 p2pv6 fence_node[5723]: agent "fence_vmware" reports:
> e_vmware line 323. Global symbol "$pwd_script_out" requires explicit
> package name at /sbin/fence_vmware line 324. Global symbol
> "$pwd_script_out" requires explicit package name at /sbin/fence_vmware
> line 325. Bareword "version" not allowed while "strict s
> 
> Feb 18 21:12:24 p2pv6 fence_node[5723]: agent "fence_vmware" reports:
> ubs" in use at /sbin/fence_vmware line 291. Execution
> of /sbin/fence_vmware aborted due to compilation errors.
> 
> Feb 18 21:12:24 p2pv6 fence_node[5723]: Fence of "p2pv5.tr.unisys.com"
> was unsuccessful
> 
>  
> 
> My initial guess is this fencing agent script can only be run with old
> VMware Perl APIs. Please correct me. Is there any way to run this
> script in my current environment?
> 
>  
> 
> If anyone is having a working script for VMware ESX 3.5 server, please
> pass it.
> 
>  
> 
> Thanks,
> 
> Santosh
> 
>  
> 
>                                    
> ______________________________________________________________________
> From: linux-cluster-bounces at redhat.com
> [mailto:linux-cluster-bounces at redhat.com] On Behalf Of MARY, Mathieu
> Sent: Thursday, February 14, 2008 6:39 PM
> To: linux clustering
> Subject: RE: [Linux-cluster] help reqd. - VMware ESX 3.5 fencing
> 
> 
>  
> 
> VC is the virtual center server, i understood from your mail that
> you?re using virtual infrastructure, but you question points out the
> fact that you maybe are using standalone ESX server ?
> 
> in our configuration we use an ESX farm of 4 servers managed by the VC
> server where we connect with the VI client
> 
>  
> 
>  
> 
> <fencedevice name="your_fence_method" agent="fence_vi3"
> ipaddr="yourserver_ip" port="your_vm_name" login="xxx"
> passwd="yyyyy"/>
> 
>  
> 
> though I don?t know if it works on standalone server, maybe you would
> have ton install the VMI perlmodules described inside the script to
> you ESX 3.5 server
> 
>  
> 
>                                    
> ______________________________________________________________________
> De :linux-cluster-bounces at redhat.com
> [mailto:linux-cluster-bounces at redhat.com] De la part de Panigrahi,
> Santosh Kumar
> Envoy? : jeudi 14 f?vrier 2008 13:50
> ? : linux clustering
> Objet : RE: [Linux-cluster] help reqd. - VMware ESX 3.5 fencing
> 
> 
>  
> 
> Thanks Marry for the script. I will test and let you know. By the way
> what?s this VC server? Is it the system where I am running my VI
> client?
> 
> Can you please elaborate little more on this configuration like where
> I will keep this script, what will I mention in my cluster.conf file
> and etc.
> 
>  
> 
> Thanks,
> 
> Santosh  
> 
>                                    
> ______________________________________________________________________
> From:linux-cluster-bounces at redhat.com
> [mailto:linux-cluster-bounces at redhat.com] On Behalf Of MARY, Mathieu
> Sent: Thursday, February 14, 2008 5:59 PM
> To: linux clustering
> Subject: RE: [Linux-cluster] help reqd. - VMware ESX 3.5 fencing
> 
> 
>  
> 
> hello,
> 
>  
> 
> i?m using this script for VI 3 and  ESX3.02 i guess it would work for
> you too, cannot remember where I found it though J
> 
> note that you have to send the restart request to your VC server and
> not to the ESX server
> 
>  
> 
>                                    
> ______________________________________________________________________
> De :linux-cluster-bounces at redhat.com
> [mailto:linux-cluster-bounces at redhat.com] De la part de Panigrahi,
> Santosh Kumar
> Envoy? : jeudi 14 f?vrier 2008 12:37
> ? : linux-cluster at redhat.com
> Objet : [Linux-cluster] help reqd. - VMware ESX 3.5 fencing
> 
> 
>  
> 
> Hi,
> 
>  
> 
> Does anybody have configured fencing in VMware ESX 3.5 environment? I
> appreciate any help.
> 
>  
> 
> I have got some info from
> http://www.tournament.org.il/run/index.php?/archives/140-VMware-Fencing-in-RedHat-Cluster-5-RHCS5.html .
> 
> This script given here is for VMware server. Any idea whether it will
> work for ESX 3.5 server or not?
> 
>  
> 
> My system configurations are as follows.
> 
>  
> 
> Host machine    : Unisys ES7000-one with host OS as VMware ESX 3.5
> 
> Guest Machines: Guest OS as Rhel5.1 AP
> 
>  
> 
> I am connecting to host machine using VMware VI 3.0.
> 
>  
> 
> Thanks,
> 
> Santosh
> 
>  
> 
>  
> 
> 
> --
> Linux-cluster mailing list
> Linux-cluster at redhat.com
> https://www.redhat.com/mailman/listinfo/linux-cluster
-------------- next part --------------
A non-text attachment was scrubbed...
Name: fence_vi3.gz
Type: application/x-gzip
Size: 2262 bytes
Desc: not available
URL: <http://listman.redhat.com/archives/linux-cluster/attachments/20080221/88249a82/attachment.bin>

From singh.rajeshwar at gmail.com  Fri Feb 22 05:04:58 2008
From: singh.rajeshwar at gmail.com (Rajesh singh)
Date: Fri, 22 Feb 2008 10:34:58 +0530
Subject: [Linux-cluster] help reqd. - VMware ESX 3.5 fencing
In-Reply-To: <D566E8CF3538B54D95B925CB69CB4D2A0C6C4D7B@inblr-exch1.eu.uis.unisys.com>
References: <D566E8CF3538B54D95B925CB69CB4D2A0C1F0E80@inblr-exch1.eu.uis.unisys.com>
	<20080214130755.C24DA20B300@smtp3.ldcom.fr>
	<D566E8CF3538B54D95B925CB69CB4D2A0C6C4D7B@inblr-exch1.eu.uis.unisys.com>
Message-ID: <e2a5a8050802212104hdd8a46dmb9d043e52a9b51d0@mail.gmail.com>

Hi,
As I can see from your mail that you are using RHEL 5 AP, you can use this
distro to create VM using xen. RHEL 5 AP comes with bundles cluster software
and xen fencing agent.

regards


2008/2/20 Panigrahi, Santosh Kumar <Santosh.Panigrahi at in.unisys.com>:

>  Hi,
>
>
>
> I am facing some issues on trying to fence a node using "fence_vmware"
> Perl script. This script is attached in this mail.
>
>
>
> I have a single standalone physical machine installed with VMware ESX 3.5.
> On top of this I have created 2 VMs with guest OS as Rhel5.1 AP. In both
> the VMs I have installed VMware Perl APIs. I have kept "fence_vmware" script
> at /sbin directory on both the VMs. My cluster.conf file is also attached
> in this mail. I have not configured any service becoz I want only to test
> VMware fencing agent here.
>
>
>
> Through conga on trying to fence a node, I am getting following errors in
> my /var/log/messages.
>
>
>
> Feb 18 21:12:24 p2pv6 fence_node[5723]: agent "fence_vmware" reports:
> Global symbol "$RELEASE_VERSION" requires explicit package name at
> /sbin/fence_vmware line 102. Global symbol "$BUILD_DATE" requires explicit
> package name at /sbin/fence_vmware line 102. Global symbol
> "$REDHAT_COPYRIGHT" requires explicit package name at
>
> Feb 18 21:12:24 p2pv6 fence_node[5723]: agent "fence_vmware" reports:
> /sbin/fence_vmware line 103. Global symbol "$REDHAT_COPYRIGHT" requires
> explicit package name at /sbin/fence_vmware line 103. Global symbol
> "$opt_ZZv" requires explicit package name at /sbin/fence_vmware line 267.
> Global symbol "$pwd_script_out" requires
>
> Feb 18 21:12:24 p2pv6 fence_node[5723]: agent "fence_vmware" reports:
> explicit package name at /sbin/fence_vmware line 300. Global symbol
> "$pwd_script_out" requires explicit package name at /sbin/fence_vmware line
> 301. Global symbol "$pwd_script_out" requires explicit package name at
> /sbin/fence_vmware line 302. Global symb
>
> Feb 18 21:12:24 p2pv6 fence_node[5723]: agent "fence_vmware" reports: ol
> "$pwd_script_out" requires explicit package name at /sbin/fence_vmware line
> 303. Global symbol "$pwd_script_out" requires explicit package name at
> /sbin/fence_vmware line 322. Global symbol "$pwd_script_out" requires
> explicit package name at /sbin/fenc
>
> Feb 18 21:12:24 p2pv6 fence_node[5723]: agent "fence_vmware" reports:
> e_vmware line 323. Global symbol "$pwd_script_out" requires explicit package
> name at /sbin/fence_vmware line 324. Global symbol "$pwd_script_out"
> requires explicit package name at /sbin/fence_vmware line 325. Bareword
> "version" not allowed while "strict s
>
> Feb 18 21:12:24 p2pv6 fence_node[5723]: agent "fence_vmware" reports: ubs"
> in use at /sbin/fence_vmware line 291. *Execution of /sbin/fence_vmware
> aborted due to compilation errors*.
>
> *Feb 18 21:12:24 p2pv6 fence_node[5723]: Fence of "p2pv5.tr.unisys.com"
> was unsuccessful*
>
>
>
> My initial guess is this fencing agent script can only be run with old
> VMware Perl APIs. Please correct me. Is there any way to run this script in
> my current environment?
>
>
>
> If anyone is having a working script for VMware ESX 3.5 server, please
> pass it.
>
>
>
> Thanks,
>
> Santosh
>
>
>  ------------------------------
>
> *From:* linux-cluster-bounces at redhat.com [mailto:
> linux-cluster-bounces at redhat.com] *On Behalf Of *MARY, Mathieu
> *Sent:* Thursday, February 14, 2008 6:39 PM
>
> *To:* linux clustering
> *Subject:* RE: [Linux-cluster] help reqd. - VMware ESX 3.5 fencing
>
>
>
> VC is the virtual center server, i understood from your mail that you're
> using virtual infrastructure, but you question points out the fact that you
> maybe are using standalone ESX server ?
>
> in our configuration we use an ESX farm of 4 servers managed by the VC
> server where we connect with the VI client
>
>
>
>
>
> <fencedevice name="your_fence_method" agent="fence_vi3"
> ipaddr="yourserver_ip" port="your_vm_name" login="xxx" passwd="yyyyy"/>
>
>
>
> though I don't know if it works on standalone server, maybe you would have
> ton install the VMI perlmodules described inside the script to you ESX 3.5server
>
>
>  ------------------------------
>
> *De :* linux-cluster-bounces at redhat.com [mailto:
> linux-cluster-bounces at redhat.com] *De la part de* Panigrahi, Santosh Kumar
> *Envoy? :* jeudi 14 f?vrier 2008 13:50
> *? :* linux clustering
> *Objet :* RE: [Linux-cluster] help reqd. - VMware ESX 3.5 fencing
>
>
>
> Thanks Marry for the script. I will test and let you know. By the way
> what's this VC server? Is it the system where I am running my VI client?
>
> Can you please elaborate little more on this configuration like where I
> will keep this script, what will I mention in my cluster.conf file and
> etc.
>
>
>
> Thanks,
>
> Santosh
>  ------------------------------
>
> *From:* linux-cluster-bounces at redhat.com [mailto:
> linux-cluster-bounces at redhat.com] *On Behalf Of *MARY, Mathieu
> *Sent:* Thursday, February 14, 2008 5:59 PM
> *To:* linux clustering
> *Subject:* RE: [Linux-cluster] help reqd. - VMware ESX 3.5 fencing
>
>
>
> hello,
>
>
>
> i'm using this script for VI 3 and  ESX3.02 i guess it would work for you
> too, cannot remember where I found it though J
>
> note that you have to send the restart request to your VC server and not
> to the ESX server
>
>
>  ------------------------------
>
> *De :* linux-cluster-bounces at redhat.com [mailto:
> linux-cluster-bounces at redhat.com] *De la part de* Panigrahi, Santosh Kumar
> *Envoy? :* jeudi 14 f?vrier 2008 12:37
> *? :* linux-cluster at redhat.com
> *Objet :* [Linux-cluster] help reqd. - VMware ESX 3.5 fencing
>
>
>
> Hi,
>
>
>
> Does anybody have configured fencing in VMware ESX 3.5 environment? I
> appreciate any help.
>
>
>
> I have got some info from
> http://www.tournament.org.il/run/index.php?/archives/140-VMware-Fencing-in-RedHat-Cluster-5-RHCS5.html.
>
> This script given here is for VMware server. Any idea whether it will work
> for ESX 3.5 server or not?
>
>
>
> My system configurations are as follows.
>
>
>
> Host machine    : Unisys ES7000-one with host OS as VMware ESX 3.5
>
> Guest Machines: Guest OS as Rhel5.1 AP
>
>
>
> I am connecting to host machine using VMware VI 3.0.
>
>
>
> Thanks,
>
> Santosh
>
>
>
>
>
> --
> Linux-cluster mailing list
> Linux-cluster at redhat.com
> https://www.redhat.com/mailman/listinfo/linux-cluster
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://listman.redhat.com/archives/linux-cluster/attachments/20080222/4747a3ee/attachment.htm>

From ccaulfie at redhat.com  Fri Feb 22 09:01:06 2008
From: ccaulfie at redhat.com (Christine Caulfield)
Date: Fri, 22 Feb 2008 09:01:06 +0000
Subject: [Linux-cluster] Initiating transition message
In-Reply-To: <cfe2fc960802211113k8940c0eg99faa528032eb680@mail.gmail.com>
References: <cfe2fc960802201145j4680ac1fib446ffadf00a95@mail.gmail.com>	<47BD36B8.6060408@redhat.com>
	<cfe2fc960802211113k8940c0eg99faa528032eb680@mail.gmail.com>
Message-ID: <47BE8F52.5030509@redhat.com>

Shawn Hood wrote:
> While this explains the situation somewhat, I was trying to bring a
> bit more clarity to the problem (without examining th esource).  What
> exactly is happening when a 'initiates transition'?

A cluster state transition is what happens when a node joins or leaves
the cluster. All the nodes that are known to be members collaborate in
the transition to work out the new cluster membership.

If the transition takes too long to complete (eg not all the nodes are
responding) then the transition is restarted - which is what you are
seeing here. It's a little more complicated than that, of course. But
that's the general idea.

One transition restart is unusual but reasonable in a very busy
environment. two is almost unheard of, and the repeating set you have is
either a very bad and strange network outage, or a very bad and strange
bug.

Christine



From cfeist at redhat.com  Fri Feb 22 14:20:38 2008
From: cfeist at redhat.com (Chris Feist)
Date: Fri, 22 Feb 2008 08:20:38 -0600
Subject: [Linux-cluster] CVS to git switch
Message-ID: <47BEDA36.3080206@redhat.com>

Hello,

We've completed our switch from CVS to git. I'm still working on putting 
together a quick HOWTO to make this change as seamless as possible.  For now, 
you can view the repository here: http://www.sourceware.org/git/ (we're the 
cluster.git project).  You can still checkout from CVS, however commits are now 
disabled.

Thanks!
Chris



From qqlka at nask.pl  Fri Feb 22 14:41:37 2008
From: qqlka at nask.pl (=?iso-8859-2?Q?Agnieszka_Kuka=B3owicz?=)
Date: Fri, 22 Feb 2008 15:41:37 +0100
Subject: [Linux-cluster] Quorum in xen guests cluster
Message-ID: <153a01c87561$07a43a60$0777b5c2@gda07ak>

Hi,

I have a question about quorum in xen guests cluster. 
I have two node cluster running virtual services - "cluster1".
"Cluster1" has two nodes - "d1" and "d2". On each node I've configured
three xen guests as virtual services ("vm1", "vm2", "vm3" on d1 and
"vm4","vm5", "vm6" on "d2" ). 
All of the guests are part of the other cluster - "cluster2". My problem
is when one of the physical machines is down (for example "d2") and the
"cluster2" says that it is not quorate because there are only 3 of 6 xen
guest running. But for me it is ok, because I have still "vm1", "vm2",
"vm3" virtual services running on "d1" node and I'd like the cluster2
has quorum even if only 3 of 6 guests are available.

Cheers,
Agnieszka Kuka?owicz

 






From bpkroth at wisc.edu  Fri Feb 22 15:52:03 2008
From: bpkroth at wisc.edu (Brian Kroth)
Date: Fri, 22 Feb 2008 09:52:03 -0600
Subject: [Linux-cluster] openais retransmit question
Message-ID: <20080222155203.GF25711@wisc.edu>

I've been seeing lots of messages like this recently on my GFS cluster
nodes:

[TOTEM] Retransmit List: 31d 31e 31f 321 322 324 327

Can anyone explain what might cause this and whether or not I should be
concerned?

Thanks,
Brian
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/x-pkcs7-signature
Size: 2192 bytes
Desc: not available
URL: <http://listman.redhat.com/archives/linux-cluster/attachments/20080222/9f668990/attachment.bin>

From tsucharz at poczta.onet.pl  Fri Feb 22 16:37:36 2008
From: tsucharz at poczta.onet.pl (Tomasz Sucharzewski)
Date: Fri, 22 Feb 2008 17:37:36 +0100
Subject: [Linux-cluster] Quorum in xen guests cluster
In-Reply-To: <153a01c87561$07a43a60$0777b5c2@gda07ak>
References: <153a01c87561$07a43a60$0777b5c2@gda07ak>
Message-ID: <47BEFA50.9050405@poczta.onet.pl>

Hi Agnieszka,

Please attach cluster.conf from domU. It should be a matter of properly 
defined voting (expected_votes)

Regards,
Tomek Sucharzewski

Agnieszka Kuka?owicz wrote:
> Hi,
>
> I have a question about quorum in xen guests cluster. 
> I have two node cluster running virtual services - "cluster1".
> "Cluster1" has two nodes - "d1" and "d2". On each node I've configured
> three xen guests as virtual services ("vm1", "vm2", "vm3" on d1 and
> "vm4","vm5", "vm6" on "d2" ). 
> All of the guests are part of the other cluster - "cluster2". My problem
> is when one of the physical machines is down (for example "d2") and the
> "cluster2" says that it is not quorate because there are only 3 of 6 xen
> guest running. But for me it is ok, because I have still "vm1", "vm2",
> "vm3" virtual services running on "d1" node and I'd like the cluster2
> has quorum even if only 3 of 6 guests are available.
>
> Cheers,
> Agnieszka Kuka?owicz
>
>  
>
>
>
>
> --
> Linux-cluster mailing list
> Linux-cluster at redhat.com
> https://www.redhat.com/mailman/listinfo/linux-cluster
>
>   




From kanderso at redhat.com  Fri Feb 22 16:44:28 2008
From: kanderso at redhat.com (Kevin Anderson)
Date: Fri, 22 Feb 2008 10:44:28 -0600
Subject: [Linux-cluster] Quorum in xen guests cluster
In-Reply-To: <153a01c87561$07a43a60$0777b5c2@gda07ak>
References: <153a01c87561$07a43a60$0777b5c2@gda07ak>
Message-ID: <1203698668.2763.6.camel@dhcp80-204.msp.redhat.com>

Do you need the virtual services to be clustered?  What application is
running that can deal with split brain mode, each side believing 3
guests make up a cluster?

Kevin

On Fri, 2008-02-22 at 15:41 +0100, Agnieszka Kuka?owicz wrote:
> Hi,
> 
> I have a question about quorum in xen guests cluster. 
> I have two node cluster running virtual services - "cluster1".
> "Cluster1" has two nodes - "d1" and "d2". On each node I've configured
> three xen guests as virtual services ("vm1", "vm2", "vm3" on d1 and
> "vm4","vm5", "vm6" on "d2" ). 
> All of the guests are part of the other cluster - "cluster2". My problem
> is when one of the physical machines is down (for example "d2") and the
> "cluster2" says that it is not quorate because there are only 3 of 6 xen
> guest running. But for me it is ok, because I have still "vm1", "vm2",
> "vm3" virtual services running on "d1" node and I'd like the cluster2
> has quorum even if only 3 of 6 guests are available.
> 
> Cheers,
> Agnieszka Kuka?owicz
> 
>  
> 
> 
> 
> 
> --
> Linux-cluster mailing list
> Linux-cluster at redhat.com
> https://www.redhat.com/mailman/listinfo/linux-cluster
> 
> 



From rpeterso at redhat.com  Fri Feb 22 17:21:34 2008
From: rpeterso at redhat.com (Bob Peterson)
Date: Fri, 22 Feb 2008 11:21:34 -0600
Subject: [Linux-cluster] gfs 5.1 question
In-Reply-To: <1203636875.5257.119.camel@localhost>
References: <1203635635.5257.111.camel@localhost>
	<1203636555.3305.26.camel@technetium.msp.redhat.com>
	<1203636875.5257.119.camel@localhost>
Message-ID: <1203700894.3305.29.camel@technetium.msp.redhat.com>

On Thu, 2008-02-21 at 18:34 -0500, chris barry wrote:
> Hi Bob,
> 
> Thanks for getting back so soon.
> 
> Anything dangerous or scary about this? Will it take a long time?
> 
> Regards,
> -C

AFAIK, it should not be dangerous or scary, it should be pretty routine.
I don't know how long it will take, but probably not long at all.

Regards,

Bob Peterson
Red Hat GFS




From shawnlhood at gmail.com  Fri Feb 22 18:48:39 2008
From: shawnlhood at gmail.com (Shawn Hood)
Date: Fri, 22 Feb 2008 13:48:39 -0500
Subject: [Linux-cluster] performance using low-latency network for
	cluster/GFS communication
Message-ID: <cfe2fc960802221048u277834a9h190c535d72b9fef1@mail.gmail.com>

I was just curious if anyone has used IP-over-Infiniband or other
low-latency network configurations with GFS?  Can any conclusion be
drawn about how well this improves overall GFS performance, especially
in scenarios where the filesystems contain large numbers of small
files?

Along the same vein, how unadisable is it to use a shared gigabit
network that is mildly to moderarely utilized for these
communications?  It seems out network performance may be hurting our
overall cluster performance, causing nodes to drop out of the cluster.

Shawn Hood



From lhh at redhat.com  Fri Feb 22 19:00:05 2008
From: lhh at redhat.com (Lon Hohberger)
Date: Fri, 22 Feb 2008 14:00:05 -0500
Subject: [Linux-cluster] Using qdisk and a watchdog timer to eliminate
	power fencing single point of failure?
In-Reply-To: <fpkk96$h4s$1@ger.gmane.org>
References: <fpkk96$h4s$1@ger.gmane.org>
Message-ID: <1203706805.20564.95.camel@ayanami.boston.devel.redhat.com>

On Thu, 2008-02-21 at 11:43 -0800, Jonathan Biggar wrote: 
> I've got a deployment scenario for a two node cluster (where services 
> are configured as active and standby) where the customer is concerned 
> that the external power fencing device I am using (WTI) becomes a single 
> point of failure.  If the WTI for the active node dies, taking down the 
> active node, the standby cannot bring up services because it cannot 
> successfully fence the failed node.  This leaves the cluster down.

Correct.  Although, if you plug in a serial terminal server, I have a
patch to talk to WTI switch through a terminal server in case the server
gets unjacked, though.


> In the setup, storage fencing is not feasible as a backup for power fencing.

Not even using fence_scsi? (SCSI3 reservations)?  That's unfortunate :(


> I think I've worked out a scenario using qdiskd and the internal 
> hardware watchdog timers in our nodes to use as a backup for power 
> fencing that I hope will eliminate the single point of failure.

Hardware watchdog timers = good stuff.


> Here's how I see it working:

> 2.  Create a heuristic (besides the usual network reachability test) for 
> qdisk that resets the node's hardware watchdog timer.  (I'll have to do 
> some additional work to ensure that the watchdog gets turned off if I am 
> gracefully shutting down the node's qdisk daemon.)

There's a watchdog daemon (userspace code) that lets you configure
heuristics for it.  Most are internal to it - and are therefore superior
to how qdiskd does heuristics from a HA / memory-neutrality perspective.
If some heuristic(s) are not met, the daemon can at your option stop
touching the watchdog device.


There's an open bugzilla to provide an integration path between qdiskd
and watchdogd - so that you can configure heuristics for watchdogd and
have qdiskd base its state on those.

For example, if watchdogd says "ok, we're not updating the watchdog
driver because of X", qdiskd can trigger a self-demotion off of that, or
maybe even write a 'If you don't hear from me in X seconds, consider me
dead' message to disk...?


> 3.  Create a custom fencing script that is run if power fencing fails 
> that examines qdisk's state to see if the node that needs to be fenced 
> is no longer updating the quorum disk.

I think the easiest thing to do is make a quick, small-footprint API or
utility to talk to qdiskd to get states...


> (I'm not sure how to do this--I 
> hope that the information in stored in qdisk's status_file will be 
> sufficient to determine this, if not, I might have to modify qdisk to 
> supply what I need.)

... because status_file is *sketchy* at best (really, it's a debugging
tool). ;)



> The standby node then should be sure that the active node has rebooted 
> itself either by qdiskd's action or via the watchdog timer, or else it 
> is power dead.


> Can anyone see a weakness in this approach I haven't thought of?

It's good from a best-effort standpoint.  We don't have anything that
does 'best effort' fencing - it's mostly all black/white.

A question that comes up is: if we use the watchdog + watchdog daemon,
do we need qdisk at all?  I mean, if there's an 'eventual timeout'
anyway based on the expectancy that the watchdog timer will fire and we
rely on it - why bother with the intermediate steps?

Hardware watchdog timers are going to be more reliable than just about
anything qdiskd could provide.

-- Lon



From sdake at redhat.com  Sat Feb 23 01:37:22 2008
From: sdake at redhat.com (Steven Dake)
Date: Fri, 22 Feb 2008 18:37:22 -0700
Subject: [Linux-cluster] openais retransmit question
In-Reply-To: <20080222155203.GF25711@wisc.edu>
References: <20080222155203.GF25711@wisc.edu>
Message-ID: <1203730642.3690.43.camel@balance>

On Fri, 2008-02-22 at 09:52 -0600, Brian Kroth wrote:
> I've been seeing lots of messages like this recently on my GFS cluster
> nodes:
> 
> [TOTEM] Retransmit List: 31d 31e 31f 321 322 324 327
> 
> Can anyone explain what might cause this and whether or not I should be
> concerned?
> 
> Thanks,
> Brian

This usually indicates a failure of your switch to multicast packets or
that your network is so overloaded that multicast packets are dropped by
the switch.  The totem protocol will automatically recover from this
issue which is what the retransmit list messages you see are.  I
wouldn't be too concerned, although retransmission does negatively
effect plock performance.

I have found this happens most often on ATCA switches.  Could you report
your switch brand and model number?

Thanks

> --
> Linux-cluster mailing list
> Linux-cluster at redhat.com
> https://www.redhat.com/mailman/listinfo/linux-cluster



From public at van-schelve.de  Sat Feb 23 10:40:17 2008
From: public at van-schelve.de (van Schelve)
Date: Sat, 23 Feb 2008 11:40:17 +0100
Subject: [Linux-cluster] unable to start virtual service
Message-ID: <df329a30c26283d28e6fc20e421d10c8@mail.van-schelve.de>

Hello.

I have just set up a test cluster environment based on RHEL5.1 advanced
platform + latest updates with two nodes + shared storage. What I want to
test is cluster services for virtual maschines because we need live
migration with xen.

The cluster itself is OK. I also have access to shared storage from both
nodes.

On each node I have a mountpoint /var/xen where the configurations for the
virtual maschines are located:

/dev/mapper/san01VG-xenconfiglv on /var/xen type gfs
(rw,hostdata=jid=0:id=196610:first=0)

As disk for the VM I have a lv based on clvm:

disk = [ "phy:/dev/san01VG/vux002-01-lv,xvda,w" ]

I have configured the virtual service with lucie and I am able to start the
virtual maschine manually using xm create vux002. I also can do a live
migration from node1 to node2 and back manually or with luci. But I cannot
start or enable the virtual maschine with luci. When I try to do this I get
every time a generic error:

Feb 23 11:31:11 ux071 clurgmgrd[28779]: <notice> Recovering failed service
vm:vux002 
Feb 23 11:31:11 ux071 clurgmgrd[28779]: <notice> start on vm "vux002"
returned 1 (generic error) 
Feb 23 11:31:11 ux071 clurgmgrd[28779]: <warning> #68: Failed to start
vm:vux002; return value: 1 
Feb 23 11:31:11 ux071 clurgmgrd[28779]: <notice> Stopping service vm:vux002

Feb 23 11:31:17 ux071 clurgmgrd[28779]: <notice> Service vm:vux002 is
recovering 
Feb 23 11:31:22 ux071 openais[28485]: [TOTEM] Retransmit List: 1be  

Is it possible that virtual service can only start a virtual maschine when
the disk is in a image file (by the way this would be the same behavior as
with the satellite)?

If it's so it would be very bad. Using image files for the virtual
maschines have extreme impact on performance and stability of the virtual
maschine. 

Is there a workaround of a fix available?

Thank you

-- Hans-Gerd van Schelve



From jon at floorboard.com  Sat Feb 23 17:06:58 2008
From: jon at floorboard.com (Jonathan Biggar)
Date: Sat, 23 Feb 2008 09:06:58 -0800
Subject: [Linux-cluster] Re: Using qdisk and a watchdog timer to eliminate
 power fencing single point of failure?
In-Reply-To: <1203706805.20564.95.camel@ayanami.boston.devel.redhat.com>
References: <fpkk96$h4s$1@ger.gmane.org>
	<1203706805.20564.95.camel@ayanami.boston.devel.redhat.com>
Message-ID: <fppjs4$vbj$1@ger.gmane.org>

Lon Hohberger wrote:
>> I've got a deployment scenario for a two node cluster (where services 
>> are configured as active and standby) where the customer is concerned 
>> that the external power fencing device I am using (WTI) becomes a single 
>> point of failure.  If the WTI for the active node dies, taking down the 
>> active node, the standby cannot bring up services because it cannot 
>> successfully fence the failed node.  This leaves the cluster down.
> 
> Correct.  Although, if you plug in a serial terminal server, I have a
> patch to talk to WTI switch through a terminal server in case the server
> gets unjacked, though.

Actually, I'm more worried about a WTI that blows up, taking the active 
node with it.  A terminal server won't help with that.

>> In the setup, storage fencing is not feasible as a backup for power fencing.
> 
> Not even using fence_scsi? (SCSI3 reservations)?  That's unfortunate :(

Well, it's possible, but this solution may be deployed with many 
different SAN implementations, so I was hoping to find a way to avoid 
having to certify that each SAN does SCSI reservations correctly.

>> I think I've worked out a scenario using qdiskd and the internal 
>> hardware watchdog timers in our nodes to use as a backup for power 
>> fencing that I hope will eliminate the single point of failure.
> 
> Hardware watchdog timers = good stuff.
> 
> 
>> Here's how I see it working:
> 
>> 2.  Create a heuristic (besides the usual network reachability test) for 
>> qdisk that resets the node's hardware watchdog timer.  (I'll have to do 
>> some additional work to ensure that the watchdog gets turned off if I am 
>> gracefully shutting down the node's qdisk daemon.)
> 
> There's a watchdog daemon (userspace code) that lets you configure
> heuristics for it.  Most are internal to it - and are therefore superior
> to how qdiskd does heuristics from a HA / memory-neutrality perspective.
> If some heuristic(s) are not met, the daemon can at your option stop
> touching the watchdog device.
> 
> There's an open bugzilla to provide an integration path between qdiskd
> and watchdogd - so that you can configure heuristics for watchdogd and
> have qdiskd base its state on those.
> 
> For example, if watchdogd says "ok, we're not updating the watchdog
> driver because of X", qdiskd can trigger a self-demotion off of that, or
> maybe even write a 'If you don't hear from me in X seconds, consider me
> dead' message to disk...?

That looks like good stuff, I'll look into it.  From looking at 
watchdogd, it can monitor if a file gets updated, so it's easy to 
integrate quorumd and watchdogd in a simple fashion by just having a 
quorumd heuristic that touches a file.

>> 3.  Create a custom fencing script that is run if power fencing fails 
>> that examines qdisk's state to see if the node that needs to be fenced 
>> is no longer updating the quorum disk.
> 
> I think the easiest thing to do is make a quick, small-footprint API or
> utility to talk to qdiskd to get states...

That's what I figured.

>> (I'm not sure how to do this--I 
>> hope that the information in stored in qdisk's status_file will be 
>> sufficient to determine this, if not, I might have to modify qdisk to 
>> supply what I need.)
> 
> ... because status_file is *sketchy* at best (really, it's a debugging
> tool). ;)

I was afraid of that...

>> The standby node then should be sure that the active node has rebooted 
>> itself either by qdiskd's action or via the watchdog timer, or else it 
>> is power dead.
> 
> 
>> Can anyone see a weakness in this approach I haven't thought of?
> 
> It's good from a best-effort standpoint.  We don't have anything that
> does 'best effort' fencing - it's mostly all black/white.
> 
> A question that comes up is: if we use the watchdog + watchdog daemon,
> do we need qdisk at all?  I mean, if there's an 'eventual timeout'
> anyway based on the expectancy that the watchdog timer will fire and we
> rely on it - why bother with the intermediate steps?
> 
> Hardware watchdog timers are going to be more reliable than just about
> anything qdiskd could provide.

Ok, I get it.  It's probably a couple of orders of magnitude more 
reliable, but since it relies only on timing, there's no real *positive* 
indication that the fencing succeeded, so it's really only best-effort. 
  Even though it would take three failures (network disruption of 
heartbeat, quorumd failing to reboot the node and the watchdog timer 
failing as well), there's still a slim, slim chance that the node is 
still trying to write to the SAN.  If I want to guarantee that there's 
never a split brain, then this isn't good enough.

Thanks for the advice.

-- 
Jon Biggar
Floorboard Software
jon at floorboard.com
jon at biggar.org



From public at van-schelve.de  Sat Feb 23 20:58:52 2008
From: public at van-schelve.de (van Schelve)
Date: Sat, 23 Feb 2008 21:58:52 +0100
Subject: [Linux-cluster] Obsolete: unable to start virtual service
Message-ID: <3148a787a1bad112d9a5f10a56011400@mail.van-schelve.de>

Hi list.

The problem has become obsolete. My mistake was that I have configured the
full path to the vm's config file and not only the path. After changing
this, it's ok.

-- Hans-Gerd van Schelve



From l_x2828 at yahoo.com  Sun Feb 24 20:29:29 2008
From: l_x2828 at yahoo.com (BJ)
Date: Sun, 24 Feb 2008 12:29:29 -0800 (PST)
Subject: [Linux-cluster] SOS: A node does not properly invoke "lock_gulmd:
	shutdown" during reboot
Message-ID: <782548.8403.qm@web55515.mail.re4.yahoo.com>

Hi,

I would appreciate it if some one could answer this
question.

We have three nodes in a GFS cluster:

NODE1: GFS-6.0.2-25
NODE2: GFS-6.0.2.36-1
NODE3: GFS-6.0.2.36-1

NODE2 does not always invoke "lock_gulmd: shutdown"
during every reboot.  When it does not, NODE1 (master)
will think NODE2 misses heartbeats and then fence
NODE2 because NODE1 does not know NODE2 is rebooting.

Please see the kernel log on NODE2 below.  The first
part of the log shows that NODE2 does not invoke
"lock_gulmd: shutdown" during the first reboot (then
it got fenced by NODE1).  The second part shows that
NODE2 invokes "lock_gulmd: shutdown" properly during
the second reboot (then NODE2 can re-join the cluster
automatically after bootup).

First part:

Feb 23 16:59:12 NODE2 crond: crond shutdown succeeded
Feb 23 16:59:12 NODE2 lock_gulmd_core[6633]: "GFS
Kernel Interface" is logged out. fd:9 
Feb 23 16:59:12 NODE2 gfs: Unmounting GFS filesystems:
 succeeded
Feb 23 16:59:14 NODE2 ccsd[6614]: Stopping ccsd,
SIGTERM received. 	
Feb 23 16:59:14 NODE2 ccsd: Stopping ccsd:
Feb 23 16:59:16 NODE2 ccsd: shutdown succeeded
Feb 23 16:59:16 NODE2 ccsd: _[60G
Feb 23 16:59:16 NODE2 ccsd: 
Feb 23 16:59:16 NODE2 rc: Stopping ccsd:  succeeded
Feb 23 16:59:16 NODE2 dd: 1+0 records in
Feb 23 16:59:16 NODE2 dd: 1+0 records out
Feb 23 16:59:16 NODE2 random: Saving random seed: 
succeeded
Feb 23 16:59:16 NODE2 mdmonitor: mdadm shutdown
succeeded
Feb 23 16:59:16 NODE2 pool: Stopping pool pool_ccs:
Feb 23 16:59:16 NODE2 pool: shutdown succeeded
Feb 23 16:59:16 NODE2 pool: shutdown succeeded
Feb 23 16:59:16 NODE2 pool: 
Feb 23 16:59:16 NODE2 pool: 
Feb 23 16:59:16 NODE2 rc: Stopping pool:  succeeded

Second part:

Feb 23 17:07:40 NODE2 crond: crond shutdown succeeded
Feb 23 17:07:41 NODE2 lock_gulmd_core[5189]: "GFS
Kernel Interface" is logged out. fd:9 
Feb 23 17:07:41 NODE2 gfs: Unmounting GFS filesystems:
 succeeded
Feb 23 17:07:43 NODE2 lock_gulmd: Checking for Gulm
Services...
Feb 23 17:07:43 NODE2 lock_gulmd: Stopping lock_gulmd:
Feb 23 17:07:44 NODE2 lock_gulmd: shutdown succeeded
Feb 23 17:07:44 NODE2 lock_gulmd: _[60G
Feb 23 17:07:44 NODE2 lock_gulmd: 
Feb 23 17:07:44 NODE2 rc: Stopping lock_gulmd: 
succeeded
Feb 23 17:07:44 NODE2 ccsd[5149]: Stopping ccsd,
SIGTERM received. 
Feb 23 17:07:44 NODE2 ccsd: Stopping ccsd:
Feb 23 17:07:46 NODE2 ccsd: shutdown succeeded
Feb 23 17:07:46 NODE2 ccsd: _[60G
Feb 23 17:07:46 NODE2 ccsd: 
Feb 23 17:07:46 NODE2 rc: Stopping ccsd:  succeeded
Feb 23 17:07:46 NODE2 dd: 1+0 records in
Feb 23 17:07:46 NODE2 dd: 1+0 records out
Feb 23 17:07:46 NODE2 random: Saving random seed: 
succeeded
Feb 23 17:07:46 NODE2 mdmonitor: mdadm shutdown
succeeded
Feb 23 17:07:46 NODE2 pool: Stopping pool pool_ccs:
Feb 23 17:07:46 NODE2 pool: shutdown succeeded
Feb 23 17:07:46 NODE2 pool: shutdown succeeded
Feb 23 17:07:46 NODE2 pool: 
Feb 23 17:07:46 NODE2 pool: 
Feb 23 17:07:46 NODE2 rc: Stopping pool:  succeeded

The question is what could be the reason for NODE2 not
to invoke "lock_gulmd: shutdown" during a reboot?

Best regards,
BJ
--





      ____________________________________________________________________________________
Be a better friend, newshound, and 
know-it-all with Yahoo! Mobile.  Try it now.  http://mobile.yahoo.com/;_ylt=Ahu06i62sR8HDtDypao8Wcj9tAcJ 



From pmshehzad at yahoo.com  Mon Feb 25 09:05:12 2008
From: pmshehzad at yahoo.com (Mshehzad Pankhawala)
Date: Mon, 25 Feb 2008 01:05:12 -0800 (PST)
Subject: [Linux-cluster] active/active configuration and nice-failback
	(heartbeat)
Message-ID: <580986.60482.qm@web45804.mail.sp1.yahoo.com>


Hallo 

I set up two cluster IP's, balanced 
between the nodes:
node1 192.168.3.103
node2 192.168.3.104

The heartbeat goes up and works:
on every node I have one cluster IP.
auto_failback is set to "on".

I do hb_standby and both IP's
go to the survivor node.

After I did restart heartbeat 
on inactive node, one of the cluster 
IP's does not come back.

Does nice_failback works if I
shutdown the one of cluster's nodes on
civilized manner ?
(i.e. for planned downtime)



Thanks in advance,

Shehzad

       
---------------------------------
Be a better friend, newshound, and know-it-all with Yahoo! Mobile.  Try it now.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://listman.redhat.com/archives/linux-cluster/attachments/20080225/ae911d57/attachment.htm>

From lhh at redhat.com  Mon Feb 25 18:00:46 2008
From: lhh at redhat.com (Lon Hohberger)
Date: Mon, 25 Feb 2008 13:00:46 -0500
Subject: [Linux-cluster] Re: Using qdisk and a watchdog timer to
	eliminate power fencing single point of failure?
In-Reply-To: <fppjs4$vbj$1@ger.gmane.org>
References: <fpkk96$h4s$1@ger.gmane.org>
	<1203706805.20564.95.camel@ayanami.boston.devel.redhat.com>
	<fppjs4$vbj$1@ger.gmane.org>
Message-ID: <1203962446.19473.24.camel@ayanami.boston.devel.redhat.com>

On Sat, 2008-02-23 at 09:06 -0800, Jonathan Biggar wrote:

> > Hardware watchdog timers are going to be more reliable than just about
> > anything qdiskd could provide.
> 
> Ok, I get it.  It's probably a couple of orders of magnitude more 
> reliable, but since it relies only on timing, there's no real *positive* 
> indication that the fencing succeeded, so it's really only best-effort. 
>   Even though it would take three failures (network disruption of 
> heartbeat, quorumd failing to reboot the node and the watchdog timer 
> failing as well), there's still a slim, slim chance that the node is 
> still trying to write to the SAN.  If I want to guarantee that there's 
> never a split brain, then this isn't good enough.

Correct.  Although, plenty of software relies on hardware watchdog
timers.

While it's not externally verifiable, I would estimate the chances of a
WDT failing when configured correctly are about as likely as a fence
device falsely claiming success (which could happen ... in theory).

The key is figuring out how to make it reliable on the software side.  I
think that the watchdog daemon is probably the answer (or pretty darn
close).

Practically speaking, when deciding to think about fencing or related
technologies, it helps to enumerate the failure cases you're worried
about and what component's job it is to handle each problem.  For
example:

 * Kernel panic -> Handled by WDT
 * System loses power -> Don't care (dead anyway)
 * Watchdog daemon hang -> Handled by WDT
 * ...
 * Network disconnect -> Watchdog daemon?
 * Cluster software hangs/crashes -> Watchdog daemon?
 * ...

The slim cases where stuff might break generally involve the (properly
configured) watchdog daemon misbehaving at the same time the node /
cluster software misbehaves:

 * Network disconnect + watchdog daemon doesn't notice ...
 * Cluster software hang/crash + watchdog daemon doesn't notice ...
 * ...

Historically (i.e. RHEL3's clumanager), we had watchdog daemon support
built in to the cluster membership layer.  There are advantages to this
design because it solves some of the problems in a fairly concrete way
(e.g. "cluster software hang" is a non-issue, since it would cause the
WDT to trigger).  Unfortunately, there are also some disadvantages, too,
which is why it's not in the current cluster software (e.g. not being
able to check routing because the membership layer is time-critical).

-- Lon



From lhh at redhat.com  Mon Feb 25 18:34:33 2008
From: lhh at redhat.com (Lon Hohberger)
Date: Mon, 25 Feb 2008 13:34:33 -0500
Subject: [Linux-cluster] Re: [Cluster-devel] Fix for bugzilla #362031
In-Reply-To: <Pine.LNX.4.64.0802200650060.14892@trider-g7>
References: <Pine.LNX.4.64.0802200650060.14892@trider-g7>
Message-ID: <1203964473.25796.7.camel@ayanami.boston.devel.redhat.com>

On Wed, 2008-02-20 at 06:53 +0100, Fabio M. Di Nitto wrote:
> Hi guys,
> 
> after a long time, here is the proposed fix for bug in subject.

The library looks pretty good, esp. for what it's doing.

Not only does it look generally useful, but it's leaps and bounds better
than how qdiskd locates devices by labels today.

It looks like this code more or less makes the ability to put device
name in cluster.conf for qdiskd obsolete.

-- Lon



From orkcu at yahoo.com  Mon Feb 25 21:06:02 2008
From: orkcu at yahoo.com (=?iso-8859-1?Q?Roger_Pe=F1a?=)
Date: Mon, 25 Feb 2008 16:06:02 -0500 (EST)
Subject: [Linux-cluster] is clvm a must all the time in a cluster ?
Message-ID: <960521.47103.qm@web50608.mail.re2.yahoo.com>

Hi

I am running RHEL4 with csgfs from centos, all
packages updates in both sets (RHEL and CS-GFS)
but since the last updates my cluster become more
unstable, sometimes after a failed shutdown of a
service (it failed because was unable to umount the
GFS) and the other two times just dont know exactly
why (I wasn't ther when it happen, just went to
fixed).
all of this in lest than two weeks
and every time, the cman infrastructure just hand or
collapse.
the first to times, I realice that one of the nodes
(and just one) was hanging the cman so the entire
cluster where in stand-by, until I fence (reboot) the
node.
from cman_tool services in that node, I guess clvm was
the guilty just because it were running (run state):-)
it shouldn't be in that state ;-) . it is just a
guess, ok? I am not an expert in CS.
also, a lot, and I mean a lot, of time my services
can't start is because the clustered LV are not
Activated even when clvm is running and cman_tool
services say it is running.
just a clvmd restar fix that.

so, my question is, can I run the cluster with GFS
without clvmd working?
I don't have plans to work with lvm (extending for
example) the sistem is working and should be in the
same state (from the filesystem point of view) for a
long time.
so, can I "declusterice" the LV where GFS live?

and if I can, what are the steps to do it?

1- vgchange -cn "VG Name"
2- cmand stop
3- lvmconf --disable-cluster

I guess I don't need to unmount the LV to do that, do
I?
nore the data in those FS should be lost because of
that operation (tha change), right?


thanks in advance for the help

cu
roger

__________________________________________
RedHat Certified ( RHCE )
Cisco Certified ( CCNA & CCDA )


      Be smarter than spam. See how smart SpamGuard is at giving junk email the boot with the All-new Yahoo! Mail.  Click on Options in Mail and switch to New Mail today or register for free at http://mail.yahoo.ca 



From sanjeev.saini at hitechos.com  Tue Feb 26 07:07:31 2008
From: sanjeev.saini at hitechos.com (sanjeev.saini at hitechos.com)
Date: Tue, 26 Feb 2008 12:37:31 +0530
Subject: [Linux-cluster] Unable to determine fence device
Message-ID: <007701c87846$43db79c0$a40110ac@GKTECNA1164>

Hi,

We have recently purchased a IBM Blade Center and we are in plan to configure an apache cluster on two blades. Now the problem is that I'm not able to find the details of fencing devices in IBM Blade Center for ex. IP Address, Username, Password.

Is there any device integrated in the IBM Bladecenter on which IP needs to be configured. 

Please Help,

Regards,

Sanjeev
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://listman.redhat.com/archives/linux-cluster/attachments/20080226/994b432a/attachment.htm>

From jakub.suchy at enlogit.cz  Tue Feb 26 12:48:34 2008
From: jakub.suchy at enlogit.cz (Jakub Suchy)
Date: Tue, 26 Feb 2008 13:48:34 +0100
Subject: [Linux-cluster] migrating to better node
Message-ID: <20080226124834.GA8542@localhost>

Hi,
I am currently testing following cluster of VM machines:
Two nodes, Shared storage, APC fencing device.
cluster.conf follows.

I am encountering this situation:
1) VM is running on clu2
2) clu2 gets fenced and VM is migrated to clu1
3) after clu2 is started again, VM is automatically migrated to clu1
according to logs and this fails.

Do anybody know, why this fails? 

Feb 26 13:25:27 clu1 fenced[2973]: fence "clu2.test-cluster.cz" success
Feb 26 13:25:32 clu1 kernel: GFS: fsid=adler:virtdata.1: jid=0: Trying
to acquire journal lock...
...
Feb 26 13:25:32 clu1 kernel: GFS: fsid=adler:virtdata.1: jid=0: Done
...
Feb 26 13:25:32 clu1 clurgmgrd[3885]: <notice> Taking over service
vm:win2003 from down member clu2.test-cluster.cz

...clu2 rejoins...
Feb 26 13:27:32 clu1 clurgmgrd[3885]: <notice> Migrating vm:win2003 to
better node clu2.test-cluster.cz
Feb 26 13:27:35 clu1 kernel: peth0: received packet with  own address as
source address
Feb 26 13:27:37 clu1 kernel: dlm: connecting to 1 
-----> Feb 26 13:27:47 clu1 clurgmgrd[3885]: <err> #75: Failed changing service
status 

Cluste.conf:
<?xml version="1.0"?>
<cluster alias="adler" config_version="13" name="adler">
        <fence_daemon clean_start="0" post_fail_delay="0" post_join_delay="3"/>
        <clusternodes>
                <clusternode name="clu2.test-cluster.cz" nodeid="1" votes="1">
                        <fence>
                                <method name="1">
                                        <device name="apc" port="3"/>
                                </method>
                        </fence>
                </clusternode>
                <clusternode name="clu1.test-cluster.cz" nodeid="2" votes="1">
                        <fence>
                                <method name="1">
                                        <device name="apc" port="1"/>
                                </method>
                        </fence>
                </clusternode>
        </clusternodes>
        <cman expected_votes="1" two_node="1"/>
        <fencedevices>
                <fencedevice agent="fence_apc" ipaddr="192.168.0.54" login="apc" name="apc" passwd="apc"/>
        </fencedevices>
        <rm>
                <failoverdomains>
                        <failoverdomain name="clu1" ordered="0" restricted="0">
                                <failoverdomainnode name="clu1.test-cluster.cz" priority="1"/>
                        </failoverdomain>
                        <failoverdomain name="clu2" ordered="0" restricted="0">
                                <failoverdomainnode name="clu2.test-cluster.cz" priority="1"/>
                        </failoverdomain>
                        <failoverdomain name="clu" ordered="0" restricted="1">
                                <failoverdomainnode name="clu2.test-cluster.cz" priority="1"/>
                                <failoverdomainnode name="clu1.test-cluster.cz" priority="1"/>
                        </failoverdomain>
                </failoverdomains>
                <resources>
                        <fs device="/dev/sdb8" force_fsck="0" force_unmount="1" fsid="62307" fstype="ext3" mountpoint="/mnt/data" name="data" self_fence="0"/>
                        <clusterfs device="/dev/mapper/gfs1-gfsdata" force_unmount="0" fsid="59408" fstype="gfs" mountpoint="/mnt/gfs" name="gfs"/>
                </resources>
                <vm autostart="1" domain="clu" exclusive="0" name="sybase" path="/mnt/gfs/" recovery="restart"/>
                <vm autostart="1" domain="clu2" exclusive="0" name="win2003" path="/mnt/gfs" recovery="relocate"/>
        </rm>
</cluster>


Thanks,
Jakub Suchy
-- 
Jakub Such? <jakub.suchy at enlogit.cz>
GSM: +420 - 777 817 949

Enlogit s.r.o, U Cukrovaru 509/4, 400 07 ?st? nad Labem
tel.: +420 - 474 745 159, fax: +420 - 474 745 160
e-mail: info at enlogit.cz, web: http://www.enlogit.cz



From Santosh.Panigrahi at in.unisys.com  Tue Feb 26 12:41:40 2008
From: Santosh.Panigrahi at in.unisys.com (Panigrahi, Santosh Kumar)
Date: Tue, 26 Feb 2008 18:11:40 +0530
Subject: [Linux-cluster] help reqd. - VMware ESX 3.5 fencing
In-Reply-To: <1203640714.5257.127.camel@localhost>
References: <D566E8CF3538B54D95B925CB69CB4D2A0C6C4D7B@inblr-exch1.eu.uis.unisys.com><20080220153643.BC30020B3F3@smtp3.ldcom.fr><D566E8CF3538B54D95B925CB69CB4D2A0C792136@inblr-exch1.eu.uis.unisys.com>
	<1203640714.5257.127.camel@localhost>
Message-ID: <D566E8CF3538B54D95B925CB69CB4D2A0CAF2309@inblr-exch1.eu.uis.unisys.com>

Hello Chrish,

As per your suggestion I installed Viper toolkit in all the cluster nodes. I have copied ur script to all the cluster nodes. Now on running this script, I'm getting following compilation error at line 49.
[root at p2pv6 sbin]# ./fence_vmware
Can't locate AppUtil/VMUtil.pm in @INC (@INC contains: /sbin/../ /usr/lib/perl5/site_perl/5.8.8/i386-linux-thread-multi /usr/lib/perl5/site_perl/5.8.7/i386-linux-thread-multi /usr/lib/perl5/site_perl/5.8.6/i386-linux-thread-multi /usr/lib/perl5/site_perl/5.8.5/i386-linux-thread-multi /usr/lib/perl5/site_perl/5.8.8 /usr/lib/perl5/site_perl/5.8.7 /usr/lib/perl5/site_perl/5.8.6 /usr/lib/perl5/site_perl/5.8.5 /usr/lib/perl5/site_perl /usr/lib/perl5/vendor_perl/5.8.8/i386-linux-thread-multi /usr/lib/perl5/vendor_perl/5.8.7/i386-linux-thread-multi /usr/lib/perl5/vendor_perl/5.8.6/i386-linux-thread-multi /usr/lib/perl5/vendor_perl/5.8.5/i386-linux-thread-multi /usr/lib/perl5/vendor_perl/5.8.8 /usr/lib/perl5/vendor_perl/5.8.7 /usr/lib/perl5/vendor_perl/5.8.6 /usr/lib/perl5/vendor_perl/5.8.5 /usr/lib/perl5/vendor_perl /usr/lib/perl5/5.8.8/i386-linux-thread-multi /usr/lib/perl5/5.8.8 .) at ./fence_vmware line 49.
BEGIN failed--compilation aborted at ./fence_vmware line 49.
[root at p2pv6 sbin]#

I know, I'm not giving all the correct inputs to this script but before this, script should compile properly. Please advice, what should be done to avoid this compilation error?

Thanks,
Santosh
=============== 
-----Original Message-----
From: linux-cluster-bounces at redhat.com [mailto:linux-cluster-bounces at redhat.com] On Behalf Of chris barry
Sent: Friday, February 22, 2008 6:09 AM
To: linux clustering
Subject: RE: [Linux-cluster] help reqd. - VMware ESX 3.5 fencing

Use this script I hacked out of various parts. fence_vi3

Ideally you point it at the VC box, as it will down a node even if it
has migrated to another esx box, but it can be pointed directly at the
ESX box just as well.

You will need the viperltoolkit installed on all your nodes.
Part of the toolkit I had to manually install - read the attached
script.

Regards,
Christoper Barry


On Thu, 2008-02-21 at 16:16 +0530, Panigrahi, Santosh Kumar wrote:
> I have saved your script (as fence_vmware) in both the virtual
> machines at /sbin directory. Now on running this script I am getting
> following compilation errors.
> 
>  
> 
> [root at p2pv6 sbin]# ./fence_vmware
> 
> Can't locate VMware/VIM2Runtime.pm in @INC (@INC
> contains: /usr/lib/perl5/site_perl/5.8.8/i386-linux-thread-multi /usr/lib/perl5/site_perl/5.8.7/i386-linux-thread-multi /usr/lib/perl5/site_perl/5.8.6/i386-linux-thread-multi /usr/lib/perl5/site_perl/5.8.5/i386-linux-thread-multi /usr/lib/perl5/site_perl/5.8.8 /usr/lib/perl5/site_perl/5.8.7 /usr/lib/perl5/site_perl/5.8.6 /usr/lib/perl5/site_perl/5.8.5 /usr/lib/perl5/site_perl /usr/lib/perl5/vendor_perl/5.8.8/i386-linux-thread-multi /usr/lib/perl5/vendor_perl/5.8.7/i386-linux-thread-multi /usr/lib/perl5/vendor_perl/5.8.6/i386-linux-thread-multi /usr/lib/perl5/vendor_perl/5.8.5/i386-linux-thread-multi /usr/lib/perl5/vendor_perl/5.8.8 /usr/lib/perl5/vendor_perl/5.8.7 /usr/lib/perl5/vendor_perl/5.8.6 /usr/lib/perl5/vendor_perl/5.8.5 /usr/lib/perl5/vendor_perl /usr/lib/perl5/5.8.8/i386-linux-thread-multi /usr/lib/perl5/5.8.8 .) at ./fence_vmware line 17.
> 
> BEGIN failed--compilation aborted at ./fence_vmware line 17.
> 
>  
> 
> From the above logs it seems it is not getting package "use
> VMware::VIM2Runtime".
> 
> I know I am not passing the proper arguments here, but before that
> this script should be complied properly in Perl environment. I have
> installed latest VMware Perl APIs on ESX server 3.5 as well as on both
> VMs.
> 
> Am I missing anything here? Please help me to proceed further.
> 
>  
> 
> Thanks,
> 
> Santosh
> 
>                                    
> ______________________________________________________________________
> From:linux-cluster-bounces at redhat.com
> [mailto:linux-cluster-bounces at redhat.com] On Behalf Of MARY, Mathieu
> Sent: Wednesday, February 20, 2008 9:08 PM
> To: linux clustering
> Subject: RE: [Linux-cluster] help reqd. - VMware ESX 3.5 fencing
> 
> 
>  
> 
> the script i sent to you was, or it should have been this one,
> apologies if I miscopied, as I tried lots of scripts when I was
> searching for the good one at the time. 
> 
> it uses the VMware::VIM2Runtime wich is the ESX 3.xx perl library
> 
>  
> 
>  
> 
> #!/usr/bin/perl
> 
>  
> 
> ###############################################################################
> 
> ###############################################################################
> 
> ##
> 
> ##  Copyright (C) Sistina Software, Inc.  1997-2003  All rights
> reserved.
> 
> ##  Copyright (C) 2004 Red Hat, Inc.  All rights reserved.
> 
> ##
> 
> ##  This copyrighted material is made available to anyone wishing to
> use,
> 
> ##  modify, copy, or redistribute it subject to the terms and
> conditions
> 
> ##  of the GNU General Public License v.2.
> 
> ##
> 
> ###############################################################################
> 
> ###############################################################################
> 
>  
> 
> use Getopt::Std;
> 
> use VMware::VIM2Runtime;
> 
>  
> 
> # Get the program name from $0 and strip directory names
> 
> $_=$0;
> 
> s/.*\///;
> 
> my $pname = $_;
> 
>  
> 
> # WARNING!! Do not add code bewteen "#BEGIN_VERSION_GENERATION" and
> 
> # "#END_VERSION_GENERATION"  It is generated by the Makefile
> 
>  
> 
> #BEGIN_VERSION_GENERATION
> 
> $FENCE_RELEASE_NAME="2.0.64";
> 
> $REDHAT_COPYRIGHT=("Copyright (C) Red Hat, Inc.  2004  All rights
> reserved.");
> 
> $BUILD_DATE="(built Thu Jun 28 07:25:05 EDT 2007)";
> 
> #END_VERSION_GENERATION
> 
>  
> 
> sub usage
> 
> {
> 
>    print "Usage:\n\n";
> 
>     print "$pname [options]\n\n";
> 
>     print "Options:\n";
> 
>     print "  -a <ip>          IP address or hostname of VirtualCenter
> server\n";
> 
>     print "  -h               Usage\n";
> 
>     print "  -n <name>        Virtual machine name to reset\n";
> 
>                 print "  -l <string>      Login name for VirtualCenter
> server\n";
> 
>     print "  -p <string>      Password for login\n";
> 
>    print "  -V               version\n\n";
> 
>  
> 
>     exit 0;
> 
> }
> 
>  
> 
> sub fail
> 
> {
> 
>   ($msg) = @_;
> 
>   print $msg."\n" unless defined $opt_q;
> 
>   $t->close if defined $t;
> 
>   exit 1;
> 
> }
> 
>  
> 
> sub fail_usage
> 
> {
> 
>   ($msg) = @_;
> 
>   print STDERR $msg."\n" if $msg;
> 
>   print STDERR "Please use '-h' for usage.\n";
> 
>   exit 1;
> 
> }
> 
>  
> 
> sub version
> 
> {
> 
>   print "$pname $FENCE_RELEASE_NAME $BUILD_DATE\n";
> 
>   print "$REDHAT_COPYRIGHT\n" if ( $REDHAT_COPYRIGHT );
> 
>  
> 
>   exit 0;
> 
> }
> 
>  
> 
> if (@ARGV > 0) {
> 
>     getopts("a:hn:l:p:V") || fail_usage ;
> 
>  
> 
>     usage if defined $opt_h;
> 
>     version if defined $opt_V;
> 
>  
> 
>     fail_usage "Unknown parameter." if (@ARGV > 0);
> 
>  
> 
>     fail_usage "No '-a' flag specified." unless defined $opt_a;
> 
>                 fail_usage "No '-l' flag specified." unless defined
> $opt_l;
> 
>     fail_usage "No '-p' flag specified." unless defined $opt_p;
> 
>     fail_usage "No '-n' flag specified." unless defined $opt_n;
> 
>  
> 
> } else {
> 
>     get_options_stdin();
> 
>  
> 
>     fail "failed: no IP/host address for the VirtualCenter." unless
> defined $opt_a;
> 
>                 fail "failed: no login name provided." unless defined
> $opt_l;
> 
>     fail "failed: no password provided." unless defined $opt_p;
> 
>     fail "failed: no VM name specified." unless defined $opt_n;
> 
> }
> 
>  
> 
> #
> 
> # Set up and log in
> 
> #
> 
>  
> 
> Vim::login(service_url=>"https://$opt_a/sdk/vimService",
> user_name=>"$opt_l", password=>"$opt_p");
> 
>  
> 
> #
> 
> # Do the command
> 
> #
> 
>  
> 
> my $vm_view = Vim::find_entity_view(view_type => 'VirtualMachine',
> filter => {name => $opt_n});
> 
>  
> 
> if (!$vm_view)
> 
> {
> 
>         fail "Virtual Machine name not found.";
> 
> }
> 
>  
> 
> $vm_view->ResetVM();
> 
>  
> 
> Vim::logout();
> 
>  
> 
> print "success: VM: $opt_n reset.\n";
> 
> exit 0;
> 
>  
> 
> sub get_options_stdin
> 
> {
> 
>     my $opt;
> 
>     my $line = 0;
> 
>  
> 
>     while( defined($in = <>) )
> 
>     {
> 
>         $_ = $in;
> 
>         chomp;
> 
>  
> 
>         # strip leading and trailing whitespace
> 
>         s/^\s*//;
> 
>         s/\s*$//;
> 
>  
> 
>         # skip comments
> 
>         next if /^#/;
> 
>  
> 
>         $line+=1;
> 
>         $opt=$_;
> 
>         next unless $opt;
> 
>  
> 
>         ($name,$val)=split /\s*=\s*/, $opt;
> 
>  
> 
>        if ( $name eq "" ) {
> 
>            print("parse error: illegal name in option $line\n");
> 
>            exit 2;
> 
>         }
> 
>  
> 
>         # DO NOTHING -- this field is used by fenced
> 
>         elsif ($name eq "agent" ) { }
> 
>  
> 
>         elsif ($name eq "login" ) {
> 
>             $opt_l = $val;
> 
>         }
> 
>  
> 
>         elsif ($name eq "ipaddr" )
> 
>         {
> 
>             $opt_a = $val;
> 
>         }
> 
>  
> 
>         elsif ($name eq "name" ) { }
> 
>  
> 
>         elsif ($name eq "passwd" )
> 
>         {
> 
>             $opt_p = $val;
> 
>         }
> 
>  
> 
>         elsif ($name eq "port" )
> 
>         {
> 
>             $opt_n = $val;
> 
>         }
> 
>     }
> 
> }
> 
>  
> 
>  
> 
>  
> 
>  
> 
> Regards,
> 
>  
> 
>  
> 
> Mathieu
> 
>                                    
> ______________________________________________________________________
> De : linux-cluster-bounces at redhat.com
> [mailto:linux-cluster-bounces at redhat.com] De la part de Panigrahi,
> Santosh Kumar
> Envoy? : mercredi 20 f?vrier 2008 14:01
> ? : linux clustering
> Objet : RE: [Linux-cluster] help reqd. - VMware ESX 3.5 fencing
> 
> 
>  
> 
> Hi,
> 
>  
> 
> I am facing some issues on trying to fence a node using "fence_vmware"
> Perl script. This script is attached in this mail.
> 
>  
> 
> I have a single standalone physical machine installed with VMware ESX
> 3.5. On top of this I have created 2 VMs with guest OS as Rhel5.1 AP.
> In both the VMs I have installed VMware Perl APIs. I have kept
> "fence_vmware" script at /sbin directory on both the VMs. My
> cluster.conf file is also attached in this mail. I have not configured
> any service becoz I want only to test VMware fencing agent here.
> 
>  
> 
> Through conga on trying to fence a node, I am getting following errors
> in my /var/log/messages.
> 
>  
> 
> Feb 18 21:12:24 p2pv6 fence_node[5723]: agent "fence_vmware" reports:
> Global symbol "$RELEASE_VERSION" requires explicit package name
> at /sbin/fence_vmware line 102. Global symbol "$BUILD_DATE" requires
> explicit package name at /sbin/fence_vmware line 102. Global symbol
> "$REDHAT_COPYRIGHT" requires explicit package name at
> 
> Feb 18 21:12:24 p2pv6 fence_node[5723]: agent "fence_vmware"
> reports: /sbin/fence_vmware line 103. Global symbol
> "$REDHAT_COPYRIGHT" requires explicit package name
> at /sbin/fence_vmware line 103. Global symbol "$opt_ZZv" requires
> explicit package name at /sbin/fence_vmware line 267. Global symbol
> "$pwd_script_out" requires
> 
> Feb 18 21:12:24 p2pv6 fence_node[5723]: agent "fence_vmware" reports:
> explicit package name at /sbin/fence_vmware line 300. Global symbol
> "$pwd_script_out" requires explicit package name at /sbin/fence_vmware
> line 301. Global symbol "$pwd_script_out" requires explicit package
> name at /sbin/fence_vmware line 302. Global symb
> 
> Feb 18 21:12:24 p2pv6 fence_node[5723]: agent "fence_vmware" reports:
> ol "$pwd_script_out" requires explicit package name
> at /sbin/fence_vmware line 303. Global symbol "$pwd_script_out"
> requires explicit package name at /sbin/fence_vmware line 322. Global
> symbol "$pwd_script_out" requires explicit package name at /sbin/fenc
> 
> Feb 18 21:12:24 p2pv6 fence_node[5723]: agent "fence_vmware" reports:
> e_vmware line 323. Global symbol "$pwd_script_out" requires explicit
> package name at /sbin/fence_vmware line 324. Global symbol
> "$pwd_script_out" requires explicit package name at /sbin/fence_vmware
> line 325. Bareword "version" not allowed while "strict s
> 
> Feb 18 21:12:24 p2pv6 fence_node[5723]: agent "fence_vmware" reports:
> ubs" in use at /sbin/fence_vmware line 291. Execution
> of /sbin/fence_vmware aborted due to compilation errors.
> 
> Feb 18 21:12:24 p2pv6 fence_node[5723]: Fence of "p2pv5.tr.unisys.com"
> was unsuccessful
> 
>  
> 
> My initial guess is this fencing agent script can only be run with old
> VMware Perl APIs. Please correct me. Is there any way to run this
> script in my current environment?
> 
>  
> 
> If anyone is having a working script for VMware ESX 3.5 server, please
> pass it.
> 
>  
> 
> Thanks,
> 
> Santosh
> 
>  
> 
>                                    
> ______________________________________________________________________
> From: linux-cluster-bounces at redhat.com
> [mailto:linux-cluster-bounces at redhat.com] On Behalf Of MARY, Mathieu
> Sent: Thursday, February 14, 2008 6:39 PM
> To: linux clustering
> Subject: RE: [Linux-cluster] help reqd. - VMware ESX 3.5 fencing
> 
> 
>  
> 
> VC is the virtual center server, i understood from your mail that
> you're using virtual infrastructure, but you question points out the
> fact that you maybe are using standalone ESX server ?
> 
> in our configuration we use an ESX farm of 4 servers managed by the VC
> server where we connect with the VI client
> 
>  
> 
>  
> 
> <fencedevice name="your_fence_method" agent="fence_vi3"
> ipaddr="yourserver_ip" port="your_vm_name" login="xxx"
> passwd="yyyyy"/>
> 
>  
> 
> though I don't know if it works on standalone server, maybe you would
> have ton install the VMI perlmodules described inside the script to
> you ESX 3.5 server
> 
>  
> 
>                                    
> ______________________________________________________________________
> De :linux-cluster-bounces at redhat.com
> [mailto:linux-cluster-bounces at redhat.com] De la part de Panigrahi,
> Santosh Kumar
> Envoy? : jeudi 14 f?vrier 2008 13:50
> ? : linux clustering
> Objet : RE: [Linux-cluster] help reqd. - VMware ESX 3.5 fencing
> 
> 
>  
> 
> Thanks Marry for the script. I will test and let you know. By the way
> what's this VC server? Is it the system where I am running my VI
> client?
> 
> Can you please elaborate little more on this configuration like where
> I will keep this script, what will I mention in my cluster.conf file
> and etc.
> 
>  
> 
> Thanks,
> 
> Santosh  
> 
>                                    
> ______________________________________________________________________
> From:linux-cluster-bounces at redhat.com
> [mailto:linux-cluster-bounces at redhat.com] On Behalf Of MARY, Mathieu
> Sent: Thursday, February 14, 2008 5:59 PM
> To: linux clustering
> Subject: RE: [Linux-cluster] help reqd. - VMware ESX 3.5 fencing
> 
> 
>  
> 
> hello,
> 
>  
> 
> i'm using this script for VI 3 and  ESX3.02 i guess it would work for
> you too, cannot remember where I found it though J
> 
> note that you have to send the restart request to your VC server and
> not to the ESX server
> 
>  
> 
>                                    
> ______________________________________________________________________
> De :linux-cluster-bounces at redhat.com
> [mailto:linux-cluster-bounces at redhat.com] De la part de Panigrahi,
> Santosh Kumar
> Envoy? : jeudi 14 f?vrier 2008 12:37
> ? : linux-cluster at redhat.com
> Objet : [Linux-cluster] help reqd. - VMware ESX 3.5 fencing
> 
> 
>  
> 
> Hi,
> 
>  
> 
> Does anybody have configured fencing in VMware ESX 3.5 environment? I
> appreciate any help.
> 
>  
> 
> I have got some info from
> http://www.tournament.org.il/run/index.php?/archives/140-VMware-Fencing-in-RedHat-Cluster-5-RHCS5.html .
> 
> This script given here is for VMware server. Any idea whether it will
> work for ESX 3.5 server or not?
> 
>  
> 
> My system configurations are as follows.
> 
>  
> 
> Host machine    : Unisys ES7000-one with host OS as VMware ESX 3.5
> 
> Guest Machines: Guest OS as Rhel5.1 AP
> 
>  
> 
> I am connecting to host machine using VMware VI 3.0.
> 
>  
> 
> Thanks,
> 
> Santosh
> 
>  
> 
>  
> 
> 
> --
> Linux-cluster mailing list
> Linux-cluster at redhat.com
> https://www.redhat.com/mailman/listinfo/linux-cluster
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://listman.redhat.com/archives/linux-cluster/attachments/20080226/82b0e595/attachment.htm>

From p_pavlos at freemail.gr  Tue Feb 26 13:21:07 2008
From: p_pavlos at freemail.gr (Pavlos Parissis)
Date: Tue, 26 Feb 2008 15:21:07 +0200
Subject: [Linux-cluster] migrating to better node
In-Reply-To: <20080226151803.lil69tlmw40ss8sw@easymail-app.hol.gr>
References: <20080226124834.GA8542@localhost>
	<20080226151803.lil69tlmw40ss8sw@easymail-app.hol.gr>
Message-ID: <20080226152107.zsm5i5642skk044c@easymail-app.hol.gr>

Quoting Jakub Suchy <jakub.suchy at enlogit.cz>:

> Hi,
> I am currently testing following cluster of VM machines:
> Two nodes, Shared storage, APC fencing device.
> cluster.conf follows.
>
> I am encountering this situation:
> 1) VM is running on clu2
> 2) clu2 gets fenced and VM is migrated to clu1
> 3) after clu2 is started again, VM is automatically migrated to clu1
> according to logs and this fails.

According to the logs the vm:win2003 was migrated to clu2 and not to
clu1 as you wrote.

> Do anybody know, why this fails?

What exactly do you want to achieve?
The vm:win2003 is assigned to a failover domain which isn't restricted
and has 1 cluster node.
The vm:win2003 moved to clu1 failover domain because it was the next
available and unrestricted domain.






From jakub.suchy at enlogit.cz  Tue Feb 26 13:36:05 2008
From: jakub.suchy at enlogit.cz (Jakub Suchy)
Date: Tue, 26 Feb 2008 14:36:05 +0100
Subject: [Linux-cluster] migrating to better node
Message-ID: <20080226132806.GD12927@localhost>

>> 3) after clu2 is started again, VM is automatically migrated to clu1
>> according to logs and this fails.
>
> According to the logs the vm:win2003 was migrated to clu2 and not to clu1 
> as you wrote.

Sure, this is my typo...

>> Do anybody know, why this fails?
>
> What exactly do you want to achieve?
> The vm:win2003 is assigned to a failover domain which isn't restricted and 
> has 1 cluster node.
> The vm:win2003 moved to clu1 failover domain because it was the next 
> unrestricted domain.

As far as I know, this is correct. But the migration fails...



From p.elmers at gmx.de  Tue Feb 26 13:40:38 2008
From: p.elmers at gmx.de (Peter)
Date: Tue, 26 Feb 2008 14:40:38 +0100
Subject: [Linux-cluster] General LDAP clustering question
Message-ID: <548CE8D3-43FA-4548-A550-8EC01117B7EC@gmx.de>

Hi!

Has anybody experiences in clustering LDAP Server? I am thinking about  
having a GFS location where one LDAP Database is located and two LDAP  
Server nodes are accessing.
Is it possible to have both of them up and running (active/activ) or  
is this configuration not recommended?

Maybe it is only possible to have one up and running and start the  
other service as soon as fencing occours?
This type of configuration would be difficult in my planned active/ 
active environment, because i have no dedicated Tier for LDAP and the  
applications on the same nodes has to decide where to find the LDAP.


Thanks,

Peter



From orkcu at yahoo.com  Tue Feb 26 13:54:55 2008
From: orkcu at yahoo.com (=?iso-8859-1?Q?Roger_Pe=F1a?=)
Date: Tue, 26 Feb 2008 08:54:55 -0500 (EST)
Subject: [Linux-cluster] General LDAP clustering question
In-Reply-To: <548CE8D3-43FA-4548-A550-8EC01117B7EC@gmx.de>
Message-ID: <295235.11748.qm@web50604.mail.re2.yahoo.com>


--- Peter <p.elmers at gmx.de> wrote:

> Hi!
> 
> Has anybody experiences in clustering LDAP Server? I
> am thinking about  
> having a GFS location where one LDAP Database is
> located and two LDAP  
> Server nodes are accessing.
> Is it possible to have both of them up and running
> (active/activ) or  
> is this configuration not recommended?
why you need shared storage for a cluster of ldap
servers if the ldap servers can be configurated to
syncronize by itsefts
I think that (master-master or master-slave relation
between servers) is a better algoritm than any shared
FS approach.
you only need to install a Load balance frontend to
the ldap servers :-) so the connections can be
distributed to all ldap servers and any downtime of
any server can be hidden from the clients
transparently
LVS from RHCS can help you with that in the case you
do not have  the specific hardware to do that.



cu
roger

__________________________________________
RedHat Certified ( RHCE )
Cisco Certified ( CCNA & CCDA )


      Connect with friends from any web browser - no download required. Try the new Yahoo! Canada Messenger for the Web BETA at http://ca.messenger.yahoo.com/webmessengerpromo.php



From Alain.Moulle at bull.net  Tue Feb 26 14:10:54 2008
From: Alain.Moulle at bull.net (Alain Moulle)
Date: Tue, 26 Feb 2008 15:10:54 +0100
Subject: [Linux-cluster] CS5 / About status requests
Message-ID: <47C41DEE.1030207@bull.net>

Hi

What is the politic of service status request :
it seems that there is systematically a status request
just after the start of the service and then a periodic
status (depending on monitor variable in script.sh) but the
1st periodic status can be requested between 1 and xx secunds
just after the service start (if xx if the monitor period)

Is that true ?

And is there any change on this status politic with regard to the CS4 ?

Thanks
Regards.
Alain Moull?



From johannes.russek at io-consulting.net  Tue Feb 26 14:13:00 2008
From: johannes.russek at io-consulting.net (jr)
Date: Tue, 26 Feb 2008 15:13:00 +0100
Subject: [Linux-cluster] General LDAP clustering question
In-Reply-To: <295235.11748.qm@web50604.mail.re2.yahoo.com>
References: <295235.11748.qm@web50604.mail.re2.yahoo.com>
Message-ID: <1204035180.4201.3.camel@localhost.localdomain>


> you only need to install a Load balance frontend to
> the ldap servers :-) so the connections can be
> distributed to all ldap servers and any downtime of
> any server can be hidden from the clients
> transparently
> LVS from RHCS can help you with that in the case you
> do not have  the specific hardware to do that.

i think there are some special cases where this wouldn't work though,
like a persistent search for instance. 
but the general idea of relying on the great replication features of
directory server is damn right ;)

johannes



From kadlec at sunserv.kfki.hu  Tue Feb 26 14:25:08 2008
From: kadlec at sunserv.kfki.hu (Kadlecsik Jozsef)
Date: Tue, 26 Feb 2008 15:25:08 +0100 (CET)
Subject: [Linux-cluster] gfs_glock_is_locked_by_me assertion failures
Message-ID: <Pine.LNX.4.64.0802261523570.9172@lxserv1.kfki.hu>

Hi,

In our five node cluster running the same software version on all 
machines, two of them have started to emit assertion failure messages:

Feb 26 13:54:47 web0 kernel: GFS: fsid=kfki:services.4: warning: assertion
"gfs_glock_is_locked_by_me(ip->i_gl)" failed
Feb 26 13:54:47 web0 kernel: GFS: fsid=kfki:services.4:   function = gfs_readpage
Feb 26 13:54:47 web0 kernel: GFS: fsid=kfki:services.4:   file =
/services/src/2.6.23.16/cluster-2.01.00/gfs-kernel/src/gfs/ops_address.c, 
line = 279
Feb 26 13:54:47 web0 kernel: GFS: fsid=kfki:services.4:   time = 1204030487

One of the machines in question has been rebooted today, the other one has 
been running for several days.

How could I debug what is the reason of the problem?

Best regards,
Jozsef
--
E-mail : kadlec at mail.kfki.hu, kadlec at blackhole.kfki.hu
PGP key: http://www.kfki.hu/~kadlec/pgp_public_key.txt
Address: KFKI Research Institute for Particle and Nuclear Physics
         H-1525 Budapest 114, POB. 49, Hungary



From jamesc at exa.com  Tue Feb 26 14:28:42 2008
From: jamesc at exa.com (James Chamberlain)
Date: Tue, 26 Feb 2008 09:28:42 -0500 (EST)
Subject: [Linux-cluster] General LDAP clustering question
In-Reply-To: <548CE8D3-43FA-4548-A550-8EC01117B7EC@gmx.de>
References: <548CE8D3-43FA-4548-A550-8EC01117B7EC@gmx.de>
Message-ID: <Pine.LNX.4.64.0802260918210.4462@hawking.exa.com>

Hi Peter,

> Has anybody experiences in clustering LDAP Server? I am thinking about having 
> a GFS location where one LDAP Database is located and two LDAP Server nodes 
> are accessing.

I'd recommend you look at replication rather than trying to do this through 
Red Hat Cluster Suite.

> Is it possible to have both of them up and running (active/activ) or is this 
> configuration not recommended?

I don't have any information about OpenLDAP, but I do know that Red Hat 
Directory Server and Fedora Directory Server both support up to four-way 
multi-master replication.  Red Hat has a very nice class on RHDS/FDS, and 
you can find FDS at:

http://directory.fedoraproject.org/

> Maybe it is only possible to have one up and running and start the other 
> service as soon as fencing occours?

You might be able to have RHCS restart the LDAP service on each node, but 
they should have replicated, rather than shared, databases.

Regards,

James



From p.elmers at gmx.de  Tue Feb 26 14:36:08 2008
From: p.elmers at gmx.de (Peter)
Date: Tue, 26 Feb 2008 15:36:08 +0100
Subject: [Linux-cluster] General LDAP clustering question
In-Reply-To: <1204035180.4201.3.camel@localhost.localdomain>
References: <295235.11748.qm@web50604.mail.re2.yahoo.com>
	<1204035180.4201.3.camel@localhost.localdomain>
Message-ID: <5FD6D46C-7E77-442D-82D6-E84E0383B912@gmx.de>

First of all thanks for the fast reply.

Is LVS possible without additional HW, so it can balance between the  
local service and the service on another node?

Thanks

Am 26.02.2008 um 15:13 schrieb jr:

>
>> you only need to install a Load balance frontend to
>> the ldap servers :-) so the connections can be
>> distributed to all ldap servers and any downtime of
>> any server can be hidden from the clients
>> transparently
>> LVS from RHCS can help you with that in the case you
>> do not have  the specific hardware to do that.
>
> i think there are some special cases where this wouldn't work though,
> like a persistent search for instance.
> but the general idea of relying on the great replication features of
> directory server is damn right ;)
>
> johannes
>
> --
> Linux-cluster mailing list
> Linux-cluster at redhat.com
> https://www.redhat.com/mailman/listinfo/linux-cluster



From orkcu at yahoo.com  Tue Feb 26 14:44:56 2008
From: orkcu at yahoo.com (=?iso-8859-1?Q?Roger_Pe=F1a?=)
Date: Tue, 26 Feb 2008 09:44:56 -0500 (EST)
Subject: [Linux-cluster] General LDAP clustering question
In-Reply-To: <5FD6D46C-7E77-442D-82D6-E84E0383B912@gmx.de>
Message-ID: <888019.57588.qm@web50611.mail.re2.yahoo.com>


--- Peter <p.elmers at gmx.de> wrote:

> First of all thanks for the fast reply.
> 
> Is LVS possible without additional HW, so it can
> balance between the  
> local service and the service on another node?
> 

using the LVS terminologie.
the LVS can be on the same server where real service
is running but, I would prefer to installed on a
diferent server just because to avoid any IP problem.
that "new" server can be a VM though :-)
if fact, it can be 2 VM, one for the active LVS and
the other one for the backup LVS, ofcourse those VM
should be on different hard :-) to avoid lose both VM
if tha hard fail :-)

cu
roger


__________________________________________
RedHat Certified ( RHCE )
Cisco Certified ( CCNA & CCDA )


      Connect with friends from any web browser - no download required. Try the new Yahoo! Canada Messenger for the Web BETA at http://ca.messenger.yahoo.com/webmessengerpromo.php



From bpkroth at wisc.edu  Tue Feb 26 14:59:15 2008
From: bpkroth at wisc.edu (Brian Kroth)
Date: Tue, 26 Feb 2008 08:59:15 -0600
Subject: [Linux-cluster] General LDAP clustering question
In-Reply-To: <888019.57588.qm@web50611.mail.re2.yahoo.com>
References: <5FD6D46C-7E77-442D-82D6-E84E0383B912@gmx.de>
	<888019.57588.qm@web50611.mail.re2.yahoo.com>
Message-ID: <20080226145915.GE23033@wisc.edu>

Roger Pe?a <orkcu at yahoo.com> 2008-02-26 09:44:
> 
> --- Peter <p.elmers at gmx.de> wrote:
> 
> > First of all thanks for the fast reply.
> > 
> > Is LVS possible without additional HW, so it can
> > balance between the  
> > local service and the service on another node?
> > 
> 
> using the LVS terminologie.
> the LVS can be on the same server where real service
> is running but, I would prefer to installed on a
> diferent server just because to avoid any IP problem.
> that "new" server can be a VM though :-)
> if fact, it can be 2 VM, one for the active LVS and
> the other one for the backup LVS, ofcourse those VM
> should be on different hard :-) to avoid lose both VM
> if tha hard fail :-)

You could also use something like heartbeat or rgmanager to pass service
IPs around and then rely upon DNS RR for the load balancing portion.
That won't require any extra hardware or a very complex setup.

Brian
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/x-pkcs7-signature
Size: 2192 bytes
Desc: not available
URL: <http://listman.redhat.com/archives/linux-cluster/attachments/20080226/434bf048/attachment.bin>

From david at eciad.ca  Tue Feb 26 15:57:13 2008
From: david at eciad.ca (David Ayre)
Date: Tue, 26 Feb 2008 07:57:13 -0800
Subject: [Linux-cluster] dlm_sendd 100% CPU
Message-ID: <2DA8E0E5-67D2-4829-B8AD-2C7F022C35D2@eciad.ca>

Any ideas why dlm_sendd is taking up 100% CPU ?

We have this intermittent problem which seems to happen when a group  
of users log into our servers at the same time, possibly opening/ 
writing files from the same mount point.

Should dlm_sendd ever take up 100% of the CPU ?

Any help would be greatly appreciated.... i mean greatly.... like sell  
my soul "greatly".  If there is any additional diagnostic info i can  
provide, please let me know.    /var/log/messages just shows failed  
SMB pipes/write failures due to the high load/lockups.

Version info:
----------------------------
Kernel:   2.6.9-55.0.6.ELsmp #1 SMP
GFS:  2.6.9-72.2.0.7
SMB: 3.0.10-1.4E.12.2

Top:
----------------------------
top - 15:48:44 up 53 days, 13:35,  3 users,  load average: 57.40,  
48.47, 37.00
Tasks: 257 total,  64 running, 193 sleeping,   0 stopped,   0 zombie
Cpu0  :  0.3% us, 99.7% sy,  0.0% ni,  0.0% id,  0.0% wa,  0.0% hi,   
0.0% si
Cpu1  :  0.0% us, 100.0% sy,  0.0% ni,  0.0% id,  0.0% wa,  0.0% hi,   
0.0% si
Cpu2  :  0.3% us, 99.7% sy,  0.0% ni,  0.0% id,  0.0% wa,  0.0% hi,   
0.0% si
Cpu3  :  0.0% us, 100.0% sy,  0.0% ni,  0.0% id,  0.0% wa,  0.0% hi,   
0.0% si
Mem:   4147164k total,  1089108k used,  3058056k free,     5200k buffers
Swap:  2031608k total,      224k used,  2031384k free,   795340k cached

  PID USER      PR  NI  VIRT  RES  SHR S %CPU %MEM    TIME+  COMMAND
4218 root       9 -10     0    0    0 R  100  0.0   1066:10 dlm_sendd
16846 root      22   0     0    0    0 R    9  0.0 173:36.82 nfsd
16848 root      25   0     0    0    0 R    9  0.0 171:54.71 nfsd
6169 jsalkeld  25   0  8400 3072 2384 R    9  0.1   0:12.12 imapd
8407 bjeon     25   0 14048 3112 2212 R    8  0.1   0:04.80 smbd
16847 root      25   0     0    0    0 R    8  0.0 174:12.58 nfsd
16850 root      25   0     0    0    0 R    8  0.0 172:22.35 nfsd
8116 bjeon     25   0 14048 3212 2312 R    8  0.1   0:14.97 smbd
8236 bschuetz  25   0 14048 3396 2492 R    8  0.1   0:18.72 smbd
8308 wuj       25   0 14048 3152 2252 R    8  0.1   0:08.19 smbd
8402 jacekim   25   0 14048 3340 2416 R    8  0.1   0:03.98 smbd
8443 wuj       25   0 14064 3172 2272 R    8  0.1   0:03.60 smbd
8355 wuj       25   0 14048 3260 2344 R    7  0.1   0:09.02 smbd
8386 ashatzko  25   0 14048 3300 2396 R    7  0.1   0:05.78 smbd
8417 wuj       25   0 14064 3204 2304 R    7  0.1   0:04.58 smbd
16845 root      25   0     0    0    0 R    7  0.0 172:15.61 nfsd
8432 rkhare    25   0 14064 3280 2360 R    7  0.1   0:03.95 smbd
8108 wuj       25   0 14048 3300 2380 R    7  0.1   0:30.34 smbd
8211 yjlee     25   0 14048 3380 2476 R    7  0.1   0:08.29 smbd
8297 bjeon     25   0 14048 3316 2380 R    7  0.1   0:13.02 smbd
8343 ssing     25   0 14048 3232 2320 R    7  0.1   0:08.49 smbd
16844 root      25   0     0    0    0 R    7  0.0 171:46.80 nfsd
8112 mtaghavi  25   0 14048 3408 2504 R    6  0.1   0:25.97 smbd
8182 wuj       25   0 14048 3200 2300 R    6  0.1   0:09.37 smbd
8438 atweedie  25   0 14064 3316 2412 R    6  0.1   0:03.69 smbd
8447 ssing     25   0 14072 3308 2384 R    6  0.1   0:01.38 smbd
8121 cmeire    25   0 14048 3396 2492 R    6  0.1   0:15.93 smbd
8223 akapur    25   0 14048 3372 2468 R    6  0.1   0:06.73 smbd
8241 jfromyr   25   0 14048 3376 2472 R    6  0.1   0:13.39 smbd
8345 jwallace  25   0 14140 3428 2476 R    6  0.1   0:05.99 smbd


~_~_~_~_~_~_~_~_~_~_~_~_~_~_~_~_~_~_~_~_~_~
David Ayre
Programmer/Analyst - Information Technlogy Services
Emily Carr Institute of Art and Design
Vancouver, B.C.   Canada
604-844-3875 /  david at eciad.ca
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://listman.redhat.com/archives/linux-cluster/attachments/20080226/6ce1f68b/attachment.htm>

From rpeterso at redhat.com  Tue Feb 26 17:25:27 2008
From: rpeterso at redhat.com (Bob Peterson)
Date: Tue, 26 Feb 2008 11:25:27 -0600
Subject: [Linux-cluster] gfs_glock_is_locked_by_me assertion failures
In-Reply-To: <Pine.LNX.4.64.0802261523570.9172@lxserv1.kfki.hu>
References: <Pine.LNX.4.64.0802261523570.9172@lxserv1.kfki.hu>
Message-ID: <1204046727.3272.3.camel@technetium.msp.redhat.com>

On Tue, 2008-02-26 at 15:25 +0100, Kadlecsik Jozsef wrote:
> Hi,
> 
> In our five node cluster running the same software version on all 
> machines, two of them have started to emit assertion failure messages:
> 
> Feb 26 13:54:47 web0 kernel: GFS: fsid=kfki:services.4: warning: assertion
> "gfs_glock_is_locked_by_me(ip->i_gl)" failed
> Feb 26 13:54:47 web0 kernel: GFS: fsid=kfki:services.4:   function = gfs_readpage
> Feb 26 13:54:47 web0 kernel: GFS: fsid=kfki:services.4:   file =
> /services/src/2.6.23.16/cluster-2.01.00/gfs-kernel/src/gfs/ops_address.c, 
> line = 279
> Feb 26 13:54:47 web0 kernel: GFS: fsid=kfki:services.4:   time = 1204030487
> 
> One of the machines in question has been rebooted today, the other one has 
> been running for several days.
> 
> How could I debug what is the reason of the problem?
> 
> Best regards,
> Jozsef

Hi Jozsef,

We already have a bugzilla 429343 open for this problem.  I believe it
was reported by a customer, so the bug record was automatically locked
to protect the customer's privacy.  We are working on a fix.
If you have a test or scenario that will recreate the failure, it may
help us with testing any fix we design.

Regards,

Bob Peterson
Red Hat GFS




From Christopher.Barry at qlogic.com  Tue Feb 26 22:30:30 2008
From: Christopher.Barry at qlogic.com (chris barry)
Date: Tue, 26 Feb 2008 17:30:30 -0500
Subject: [Linux-cluster] help reqd. - VMware ESX 3.5 fencing
In-Reply-To: <D566E8CF3538B54D95B925CB69CB4D2A0CAF2309@inblr-exch1.eu.uis.unisys.com>
References: <D566E8CF3538B54D95B925CB69CB4D2A0C6C4D7B@inblr-exch1.eu.uis.unisys.com>
	<20080220153643.BC30020B3F3@smtp3.ldcom.fr>
	<D566E8CF3538B54D95B925CB69CB4D2A0C792136@inblr-exch1.eu.uis.unisys.com>
	<1203640714.5257.127.camel@localhost>
	<D566E8CF3538B54D95B925CB69CB4D2A0CAF2309@inblr-exch1.eu.uis.unisys.com>
Message-ID: <1204065030.5195.56.camel@localhost>

Read the top section of the script itself. I explain that the install
script of viperltoolkit does not install the AppUtil directory with the
rest of itself in your particular site_perl dir.

do a 
$ locate site_perl
to see where on your system has your site_perl director(y|ies), and look
in each one to find the other vmware module dirs (includes) listed in
the top of the script. Then copy the AppUtil dir (from the viperltoolkit
source) into the same site_perl as the rest, and at the same level.

e.g.
...site_perl
       |-AppUtil
       |-VMware
       `-other stuff


Once the AppUtil dir is present in the right location, it should work
ok. I had to figure this out the hard way. ;)


Good Luck,
-C


On Tue, 2008-02-26 at 18:11 +0530, Panigrahi, Santosh Kumar wrote:
> Hello Chrish,
> 
> As per your suggestion I installed Viper toolkit in all the cluster
> nodes. I have copied ur script to all the cluster nodes. Now on
> running this script, I'm getting following compilation error at line
> 49.
> 
> [root at p2pv6 sbin]# ./fence_vmware
> 
> Can't locate AppUtil/VMUtil.pm in @INC (@INC
> contains: /sbin/../ /usr/lib/perl5/site_perl/5.8.8/i386-linux-thread-multi /usr/lib/perl5/site_perl/5.8.7/i386-linux-thread-multi /usr/lib/perl5/site_perl/5.8.6/i386-linux-thread-multi /usr/lib/perl5/site_perl/5.8.5/i386-linux-thread-multi /usr/lib/perl5/site_perl/5.8.8 /usr/lib/perl5/site_perl/5.8.7 /usr/lib/perl5/site_perl/5.8.6 /usr/lib/perl5/site_perl/5.8.5 /usr/lib/perl5/site_perl /usr/lib/perl5/vendor_perl/5.8.8/i386-linux-thread-multi /usr/lib/perl5/vendor_perl/5.8.7/i386-linux-thread-multi /usr/lib/perl5/vendor_perl/5.8.6/i386-linux-thread-multi /usr/lib/perl5/vendor_perl/5.8.5/i386-linux-thread-multi /usr/lib/perl5/vendor_perl/5.8.8 /usr/lib/perl5/vendor_perl/5.8.7 /usr/lib/perl5/vendor_perl/5.8.6 /usr/lib/perl5/vendor_perl/5.8.5 /usr/lib/perl5/vendor_perl /usr/lib/perl5/5.8.8/i386-linux-thread-multi /usr/lib/perl5/5.8.8 .) at ./fence_vmware line 49.
> 
> BEGIN failed--compilation aborted at ./fence_vmware line 49.
> 
> [root at p2pv6 sbin]#
> 
> I know, I'm not giving all the correct inputs to this script but
> before this, script should compile properly. Please advice, what
> should be done to avoid this compilation error?
> 
> Thanks,
> 
> Santosh
> 
> =============== 
> 
> -----Original Message-----
> From: linux-cluster-bounces at redhat.com
> [mailto:linux-cluster-bounces at redhat.com] On Behalf Of chris barry
> Sent: Friday, February 22, 2008 6:09 AM
> To: linux clustering
> Subject: RE: [Linux-cluster] help reqd. - VMware ESX 3.5 fencing
> 
> Use this script I hacked out of various parts. fence_vi3
> 
> Ideally you point it at the VC box, as it will down a node even if it
> 
> has migrated to another esx box, but it can be pointed directly at the
> 
> ESX box just as well.
> 
> You will need the viperltoolkit installed on all your nodes.
> 
> Part of the toolkit I had to manually install - read the attached
> 
> script.
> 
> Regards,
> 
> Christoper Barry
> 
> 
> On Thu, 2008-02-21 at 16:16 +0530, Panigrahi, Santosh Kumar wrote:
> 
> > I have saved your script (as fence_vmware) in both the virtual
> 
> > machines at /sbin directory. Now on running this script I am getting
> 
> > following compilation errors.
> 
> > 
> 
> >  
> 
> > 
> 
> > [root at p2pv6 sbin]# ./fence_vmware
> 
> > 
> 
> > Can't locate VMware/VIM2Runtime.pm in @INC (@INC
> 
> >
> contains: /usr/lib/perl5/site_perl/5.8.8/i386-linux-thread-multi /usr/lib/perl5/site_perl/5.8.7/i386-linux-thread-multi /usr/lib/perl5/site_perl/5.8.6/i386-linux-thread-multi /usr/lib/perl5/site_perl/5.8.5/i386-linux-thread-multi /usr/lib/perl5/site_perl/5.8.8 /usr/lib/perl5/site_perl/5.8.7 /usr/lib/perl5/site_perl/5.8.6 /usr/lib/perl5/site_perl/5.8.5 /usr/lib/perl5/site_perl /usr/lib/perl5/vendor_perl/5.8.8/i386-linux-thread-multi /usr/lib/perl5/vendor_perl/5.8.7/i386-linux-thread-multi /usr/lib/perl5/vendor_perl/5.8.6/i386-linux-thread-multi /usr/lib/perl5/vendor_perl/5.8.5/i386-linux-thread-multi /usr/lib/perl5/vendor_perl/5.8.8 /usr/lib/perl5/vendor_perl/5.8.7 /usr/lib/perl5/vendor_perl/5.8.6 /usr/lib/perl5/vendor_perl/5.8.5 /usr/lib/perl5/vendor_perl /usr/lib/perl5/5.8.8/i386-linux-thread-multi /usr/lib/perl5/5.8.8 .) at ./fence_vmware line 17.
> 
> > 
> 
> > BEGIN failed--compilation aborted at ./fence_vmware line 17.
> 
> > 
> 
> >  
> 
> > 
> 
> > From the above logs it seems it is not getting package ?use
> 
> > VMware::VIM2Runtime?.
> 
> > 
> 
> > I know I am not passing the proper arguments here, but before that
> 
> > this script should be complied properly in Perl environment. I have
> 
> > installed latest VMware Perl APIs on ESX server 3.5 as well as on
> both
> 
> > VMs.
> 
> > 
> 
> > Am I missing anything here? Please help me to proceed further.
> 
> > 
> 
> >  
> 
> > 
> 
> > Thanks,
> 
> > 
> 
> > Santosh
> 
> > 
> 
> >                                    
> 
> >
> ______________________________________________________________________
> 
> > From:linux-cluster-bounces at redhat.com
> 
> > [mailto:linux-cluster-bounces at redhat.com] On Behalf Of MARY, Mathieu
> 
> > Sent: Wednesday, February 20, 2008 9:08 PM
> 
> > To: linux clustering
> 
> > Subject: RE: [Linux-cluster] help reqd. - VMware ESX 3.5 fencing
> 
> > 
> 
> > 
> 
> >  
> 
> > 
> 
> > the script i sent to you was, or it should have been this one,
> 
> > apologies if I miscopied, as I tried lots of scripts when I was
> 
> > searching for the good one at the time. 
> 
> > 
> 
> > it uses the VMware::VIM2Runtime wich is the ESX 3.xx perl library
> 
> > 
> 
> >  
> 
> > 
> 
> >  
> 
> > 
> 
> > #!/usr/bin/perl
> 
> > 
> 
> >  
> 
> > 
> 
> >
> ###############################################################################
> 
> > 
> 
> >
> ###############################################################################
> 
> > 
> 
> > ##
> 
> > 
> 
> > ##  Copyright (C) Sistina Software, Inc.  1997-2003  All rights
> 
> > reserved.
> 
> > 
> 
> > ##  Copyright (C) 2004 Red Hat, Inc.  All rights reserved.
> 
> > 
> 
> > ##
> 
> > 
> 
> > ##  This copyrighted material is made available to anyone wishing to
> 
> > use,
> 
> > 
> 
> > ##  modify, copy, or redistribute it subject to the terms and
> 
> > conditions
> 
> > 
> 
> > ##  of the GNU General Public License v.2.
> 
> > 
> 
> > ##
> 
> > 
> 
> >
> ###############################################################################
> 
> > 
> 
> >
> ###############################################################################
> 
> > 
> 
> >  
> 
> > 
> 
> > use Getopt::Std;
> 
> > 
> 
> > use VMware::VIM2Runtime;
> 
> > 
> 
> >  
> 
> > 
> 
> > # Get the program name from $0 and strip directory names
> 
> > 
> 
> > $_=$0;
> 
> > 
> 
> > s/.*\///;
> 
> > 
> 
> > my $pname = $_;
> 
> > 
> 
> >  
> 
> > 
> 
> > # WARNING!! Do not add code bewteen "#BEGIN_VERSION_GENERATION" and
> 
> > 
> 
> > # "#END_VERSION_GENERATION"  It is generated by the Makefile
> 
> > 
> 
> >  
> 
> > 
> 
> > #BEGIN_VERSION_GENERATION
> 
> > 
> 
> > $FENCE_RELEASE_NAME="2.0.64";
> 
> > 
> 
> > $REDHAT_COPYRIGHT=("Copyright (C) Red Hat, Inc.  2004  All rights
> 
> > reserved.");
> 
> > 
> 
> > $BUILD_DATE="(built Thu Jun 28 07:25:05 EDT 2007)";
> 
> > 
> 
> > #END_VERSION_GENERATION
> 
> > 
> 
> >  
> 
> > 
> 
> > sub usage
> 
> > 
> 
> > {
> 
> > 
> 
> >    print "Usage:\n\n";
> 
> > 
> 
> >     print "$pname [options]\n\n";
> 
> > 
> 
> >     print "Options:\n";
> 
> > 
> 
> >     print "  -a <ip>          IP address or hostname of
> VirtualCenter
> 
> > server\n";
> 
> > 
> 
> >     print "  -h               Usage\n";
> 
> > 
> 
> >     print "  -n <name>        Virtual machine name to reset\n";
> 
> > 
> 
> >                 print "  -l <string>      Login name for
> VirtualCenter
> 
> > server\n";
> 
> > 
> 
> >     print "  -p <string>      Password for login\n";
> 
> > 
> 
> >    print "  -V               version\n\n";
> 
> > 
> 
> >  
> 
> > 
> 
> >     exit 0;
> 
> > 
> 
> > }
> 
> > 
> 
> >  
> 
> > 
> 
> > sub fail
> 
> > 
> 
> > {
> 
> > 
> 
> >   ($msg) = @_;
> 
> > 
> 
> >   print $msg."\n" unless defined $opt_q;
> 
> > 
> 
> >   $t->close if defined $t;
> 
> > 
> 
> >   exit 1;
> 
> > 
> 
> > }
> 
> > 
> 
> >  
> 
> > 
> 
> > sub fail_usage
> 
> > 
> 
> > {
> 
> > 
> 
> >   ($msg) = @_;
> 
> > 
> 
> >   print STDERR $msg."\n" if $msg;
> 
> > 
> 
> >   print STDERR "Please use '-h' for usage.\n";
> 
> > 
> 
> >   exit 1;
> 
> > 
> 
> > }
> 
> > 
> 
> >  
> 
> > 
> 
> > sub version
> 
> > 
> 
> > {
> 
> > 
> 
> >   print "$pname $FENCE_RELEASE_NAME $BUILD_DATE\n";
> 
> > 
> 
> >   print "$REDHAT_COPYRIGHT\n" if ( $REDHAT_COPYRIGHT );
> 
> > 
> 
> >  
> 
> > 
> 
> >   exit 0;
> 
> > 
> 
> > }
> 
> > 
> 
> >  
> 
> > 
> 
> > if (@ARGV > 0) {
> 
> > 
> 
> >     getopts("a:hn:l:p:V") || fail_usage ;
> 
> > 
> 
> >  
> 
> > 
> 
> >     usage if defined $opt_h;
> 
> > 
> 
> >     version if defined $opt_V;
> 
> > 
> 
> >  
> 
> > 
> 
> >     fail_usage "Unknown parameter." if (@ARGV > 0);
> 
> > 
> 
> >  
> 
> > 
> 
> >     fail_usage "No '-a' flag specified." unless defined $opt_a;
> 
> > 
> 
> >                 fail_usage "No '-l' flag specified." unless defined
> 
> > $opt_l;
> 
> > 
> 
> >     fail_usage "No '-p' flag specified." unless defined $opt_p;
> 
> > 
> 
> >     fail_usage "No '-n' flag specified." unless defined $opt_n;
> 
> > 
> 
> >  
> 
> > 
> 
> > } else {
> 
> > 
> 
> >     get_options_stdin();
> 
> > 
> 
> >  
> 
> > 
> 
> >     fail "failed: no IP/host address for the VirtualCenter." unless
> 
> > defined $opt_a;
> 
> > 
> 
> >                 fail "failed: no login name provided." unless
> defined
> 
> > $opt_l;
> 
> > 
> 
> >     fail "failed: no password provided." unless defined $opt_p;
> 
> > 
> 
> >     fail "failed: no VM name specified." unless defined $opt_n;
> 
> > 
> 
> > }
> 
> > 
> 
> >  
> 
> > 
> 
> > #
> 
> > 
> 
> > # Set up and log in
> 
> > 
> 
> > #
> 
> > 
> 
> >  
> 
> > 
> 
> > Vim::login(service_url=>"https://$opt_a/sdk/vimService",
> 
> > user_name=>"$opt_l", password=>"$opt_p");
> 
> > 
> 
> >  
> 
> > 
> 
> > #
> 
> > 
> 
> > # Do the command
> 
> > 
> 
> > #
> 
> > 
> 
> >  
> 
> > 
> 
> > my $vm_view = Vim::find_entity_view(view_type => 'VirtualMachine',
> 
> > filter => {name => $opt_n});
> 
> > 
> 
> >  
> 
> > 
> 
> > if (!$vm_view)
> 
> > 
> 
> > {
> 
> > 
> 
> >         fail "Virtual Machine name not found.";
> 
> > 
> 
> > }
> 
> > 
> 
> >  
> 
> > 
> 
> > $vm_view->ResetVM();
> 
> > 
> 
> >  
> 
> > 
> 
> > Vim::logout();
> 
> > 
> 
> >  
> 
> > 
> 
> > print "success: VM: $opt_n reset.\n";
> 
> > 
> 
> > exit 0;
> 
> > 
> 
> >  
> 
> > 
> 
> > sub get_options_stdin
> 
> > 
> 
> > {
> 
> > 
> 
> >     my $opt;
> 
> > 
> 
> >     my $line = 0;
> 
> > 
> 
> >  
> 
> > 
> 
> >     while( defined($in = <>) )
> 
> > 
> 
> >     {
> 
> > 
> 
> >         $_ = $in;
> 
> > 
> 
> >         chomp;
> 
> > 
> 
> >  
> 
> > 
> 
> >         # strip leading and trailing whitespace
> 
> > 
> 
> >         s/^\s*//;
> 
> > 
> 
> >         s/\s*$//;
> 
> > 
> 
> >  
> 
> > 
> 
> >         # skip comments
> 
> > 
> 
> >         next if /^#/;
> 
> > 
> 
> >  
> 
> > 
> 
> >         $line+=1;
> 
> > 
> 
> >         $opt=$_;
> 
> > 
> 
> >         next unless $opt;
> 
> > 
> 
> >  
> 
> > 
> 
> >         ($name,$val)=split /\s*=\s*/, $opt;
> 
> > 
> 
> >  
> 
> > 
> 
> >        if ( $name eq "" ) {
> 
> > 
> 
> >            print("parse error: illegal name in option $line\n");
> 
> > 
> 
> >            exit 2;
> 
> > 
> 
> >         }
> 
> > 
> 
> >  
> 
> > 
> 
> >         # DO NOTHING -- this field is used by fenced
> 
> > 
> 
> >         elsif ($name eq "agent" ) { }
> 
> > 
> 
> >  
> 
> > 
> 
> >         elsif ($name eq "login" ) {
> 
> > 
> 
> >             $opt_l = $val;
> 
> > 
> 
> >         }
> 
> > 
> 
> >  
> 
> > 
> 
> >         elsif ($name eq "ipaddr" )
> 
> > 
> 
> >         {
> 
> > 
> 
> >             $opt_a = $val;
> 
> > 
> 
> >         }
> 
> > 
> 
> >  
> 
> > 
> 
> >         elsif ($name eq "name" ) { }
> 
> > 
> 
> >  
> 
> > 
> 
> >         elsif ($name eq "passwd" )
> 
> > 
> 
> >         {
> 
> > 
> 
> >             $opt_p = $val;
> 
> > 
> 
> >         }
> 
> > 
> 
> >  
> 
> > 
> 
> >         elsif ($name eq "port" )
> 
> > 
> 
> >         {
> 
> > 
> 
> >             $opt_n = $val;
> 
> > 
> 
> >         }
> 
> > 
> 
> >     }
> 
> > 
> 
> > }
> 
> > 
> 
> >  
> 
> > 
> 
> >  
> 
> > 
> 
> >  
> 
> > 
> 
> >  
> 
> > 
> 
> > Regards,
> 
> > 
> 
> >  
> 
> > 
> 
> >  
> 
> > 
> 
> > Mathieu
> 
> > 
> 
> >                                    
> 
> >
> ______________________________________________________________________
> 
> > De : linux-cluster-bounces at redhat.com
> 
> > [mailto:linux-cluster-bounces at redhat.com] De la part de Panigrahi,
> 
> > Santosh Kumar
> 
> > Envoy? : mercredi 20 f?vrier 2008 14:01
> 
> > ? : linux clustering
> 
> > Objet : RE: [Linux-cluster] help reqd. - VMware ESX 3.5 fencing
> 
> > 
> 
> > 
> 
> >  
> 
> > 
> 
> > Hi,
> 
> > 
> 
> >  
> 
> > 
> 
> > I am facing some issues on trying to fence a node using
> ?fence_vmware?
> 
> > Perl script. This script is attached in this mail.
> 
> > 
> 
> >  
> 
> > 
> 
> > I have a single standalone physical machine installed with VMware
> ESX
> 
> > 3.5. On top of this I have created 2 VMs with guest OS as Rhel5.1
> AP.
> 
> > In both the VMs I have installed VMware Perl APIs. I have kept
> 
> > ?fence_vmware? script at /sbin directory on both the VMs. My
> 
> > cluster.conf file is also attached in this mail. I have not
> configured
> 
> > any service becoz I want only to test VMware fencing agent here.
> 
> > 
> 
> >  
> 
> > 
> 
> > Through conga on trying to fence a node, I am getting following
> errors
> 
> > in my /var/log/messages.
> 
> > 
> 
> >  
> 
> > 
> 
> > Feb 18 21:12:24 p2pv6 fence_node[5723]: agent "fence_vmware"
> reports:
> 
> > Global symbol "$RELEASE_VERSION" requires explicit package name
> 
> > at /sbin/fence_vmware line 102. Global symbol "$BUILD_DATE" requires
> 
> > explicit package name at /sbin/fence_vmware line 102. Global symbol
> 
> > "$REDHAT_COPYRIGHT" requires explicit package name at
> 
> > 
> 
> > Feb 18 21:12:24 p2pv6 fence_node[5723]: agent "fence_vmware"
> 
> > reports: /sbin/fence_vmware line 103. Global symbol
> 
> > "$REDHAT_COPYRIGHT" requires explicit package name
> 
> > at /sbin/fence_vmware line 103. Global symbol "$opt_ZZv" requires
> 
> > explicit package name at /sbin/fence_vmware line 267. Global symbol
> 
> > "$pwd_script_out" requires
> 
> > 
> 
> > Feb 18 21:12:24 p2pv6 fence_node[5723]: agent "fence_vmware"
> reports:
> 
> > explicit package name at /sbin/fence_vmware line 300. Global symbol
> 
> > "$pwd_script_out" requires explicit package name
> at /sbin/fence_vmware
> 
> > line 301. Global symbol "$pwd_script_out" requires explicit package
> 
> > name at /sbin/fence_vmware line 302. Global symb
> 
> > 
> 
> > Feb 18 21:12:24 p2pv6 fence_node[5723]: agent "fence_vmware"
> reports:
> 
> > ol "$pwd_script_out" requires explicit package name
> 
> > at /sbin/fence_vmware line 303. Global symbol "$pwd_script_out"
> 
> > requires explicit package name at /sbin/fence_vmware line 322.
> Global
> 
> > symbol "$pwd_script_out" requires explicit package name
> at /sbin/fenc
> 
> > 
> 
> > Feb 18 21:12:24 p2pv6 fence_node[5723]: agent "fence_vmware"
> reports:
> 
> > e_vmware line 323. Global symbol "$pwd_script_out" requires explicit
> 
> > package name at /sbin/fence_vmware line 324. Global symbol
> 
> > "$pwd_script_out" requires explicit package name
> at /sbin/fence_vmware
> 
> > line 325. Bareword "version" not allowed while "strict s
> 
> > 
> 
> > Feb 18 21:12:24 p2pv6 fence_node[5723]: agent "fence_vmware"
> reports:
> 
> > ubs" in use at /sbin/fence_vmware line 291. Execution
> 
> > of /sbin/fence_vmware aborted due to compilation errors.
> 
> > 
> 
> > Feb 18 21:12:24 p2pv6 fence_node[5723]: Fence of
> "p2pv5.tr.unisys.com"
> 
> > was unsuccessful
> 
> > 
> 
> >  
> 
> > 
> 
> > My initial guess is this fencing agent script can only be run with
> old
> 
> > VMware Perl APIs. Please correct me. Is there any way to run this
> 
> > script in my current environment?
> 
> > 
> 
> >  
> 
> > 
> 
> > If anyone is having a working script for VMware ESX 3.5 server,
> please
> 
> > pass it.
> 
> > 
> 
> >  
> 
> > 
> 
> > Thanks,
> 
> > 
> 
> > Santosh
> 
> > 
> 
> >  
> 
> > 
> 
> >                                    
> 
> >
> ______________________________________________________________________
> 
> > From: linux-cluster-bounces at redhat.com
> 
> > [mailto:linux-cluster-bounces at redhat.com] On Behalf Of MARY, Mathieu
> 
> > Sent: Thursday, February 14, 2008 6:39 PM
> 
> > To: linux clustering
> 
> > Subject: RE: [Linux-cluster] help reqd. - VMware ESX 3.5 fencing
> 
> > 
> 
> > 
> 
> >  
> 
> > 
> 
> > VC is the virtual center server, i understood from your mail that
> 
> > you?re using virtual infrastructure, but you question points out the
> 
> > fact that you maybe are using standalone ESX server ?
> 
> > 
> 
> > in our configuration we use an ESX farm of 4 servers managed by the
> VC
> 
> > server where we connect with the VI client
> 
> > 
> 
> >  
> 
> > 
> 
> >  
> 
> > 
> 
> > <fencedevice name="your_fence_method" agent="fence_vi3"
> 
> > ipaddr="yourserver_ip" port="your_vm_name" login="xxx"
> 
> > passwd="yyyyy"/>
> 
> > 
> 
> >  
> 
> > 
> 
> > though I don?t know if it works on standalone server, maybe you
> would
> 
> > have ton install the VMI perlmodules described inside the script to
> 
> > you ESX 3.5 server
> 
> > 
> 
> >  
> 
> > 
> 
> >                                    
> 
> >
> ______________________________________________________________________
> 
> > De :linux-cluster-bounces at redhat.com
> 
> > [mailto:linux-cluster-bounces at redhat.com] De la part de Panigrahi,
> 
> > Santosh Kumar
> 
> > Envoy? : jeudi 14 f?vrier 2008 13:50
> 
> > ? : linux clustering
> 
> > Objet : RE: [Linux-cluster] help reqd. - VMware ESX 3.5 fencing
> 
> > 
> 
> > 
> 
> >  
> 
> > 
> 
> > Thanks Marry for the script. I will test and let you know. By the
> way
> 
> > what?s this VC server? Is it the system where I am running my VI
> 
> > client?
> 
> > 
> 
> > Can you please elaborate little more on this configuration like
> where
> 
> > I will keep this script, what will I mention in my cluster.conf file
> 
> > and etc.
> 
> > 
> 
> >  
> 
> > 
> 
> > Thanks,
> 
> > 
> 
> > Santosh  
> 
> > 
> 
> >                                    
> 
> >
> ______________________________________________________________________
> 
> > From:linux-cluster-bounces at redhat.com
> 
> > [mailto:linux-cluster-bounces at redhat.com] On Behalf Of MARY, Mathieu
> 
> > Sent: Thursday, February 14, 2008 5:59 PM
> 
> > To: linux clustering
> 
> > Subject: RE: [Linux-cluster] help reqd. - VMware ESX 3.5 fencing
> 
> > 
> 
> > 
> 
> >  
> 
> > 
> 
> > hello,
> 
> > 
> 
> >  
> 
> > 
> 
> > i?m using this script for VI 3 and  ESX3.02 i guess it would work
> for
> 
> > you too, cannot remember where I found it though J
> 
> > 
> 
> > note that you have to send the restart request to your VC server and
> 
> > not to the ESX server
> 
> > 
> 
> >  
> 
> > 
> 
> >                                    
> 
> >
> ______________________________________________________________________
> 
> > De :linux-cluster-bounces at redhat.com
> 
> > [mailto:linux-cluster-bounces at redhat.com] De la part de Panigrahi,
> 
> > Santosh Kumar
> 
> > Envoy? : jeudi 14 f?vrier 2008 12:37
> 
> > ? : linux-cluster at redhat.com
> 
> > Objet : [Linux-cluster] help reqd. - VMware ESX 3.5 fencing
> 
> > 
> 
> > 
> 
> >  
> 
> > 
> 
> > Hi,
> 
> > 
> 
> >  
> 
> > 
> 
> > Does anybody have configured fencing in VMware ESX 3.5 environment?
> I
> 
> > appreciate any help.
> 
> > 
> 
> >  
> 
> > 
> 
> > I have got some info from
> 
> >
> http://www.tournament.org.il/run/index.php?/archives/140-VMware-Fencing-in-RedHat-Cluster-5-RHCS5.html .
> 
> > 
> 
> > This script given here is for VMware server. Any idea whether it
> will
> 
> > work for ESX 3.5 server or not?
> 
> > 
> 
> >  
> 
> > 
> 
> > My system configurations are as follows.
> 
> > 
> 
> >  
> 
> > 
> 
> > Host machine    : Unisys ES7000-one with host OS as VMware ESX 3.5
> 
> > 
> 
> > Guest Machines: Guest OS as Rhel5.1 AP
> 
> > 
> 
> >  
> 
> > 
> 
> > I am connecting to host machine using VMware VI 3.0.
> 
> > 
> 
> >  
> 
> > 
> 
> > Thanks,
> 
> > 
> 
> > Santosh
> 
> > 
> 
> >  
> 
> > 
> 
> >  
> 
> > 
> 
> > 
> 
> > --
> 
> > Linux-cluster mailing list
> 
> > Linux-cluster at redhat.com
> 
> > https://www.redhat.com/mailman/listinfo/linux-cluster
> 
> --
> Linux-cluster mailing list
> Linux-cluster at redhat.com
> https://www.redhat.com/mailman/listinfo/linux-cluster



From tb at tbits.net  Tue Feb 26 22:40:30 2008
From: tb at tbits.net (Thomas =?iso-8859-1?q?B=F6rnert?=)
Date: Tue, 26 Feb 2008 23:40:30 +0100
Subject: [Linux-cluster] GFS2 2 Node Cluster - lost Node - Mount not
	writeable
Message-ID: <200802262340.46493.tb@tbits.net>

Hi List,

2 Servers - connected with crossover

my rpms:
gfs2-utils-0.1.38-1.el5
gfs-utils-0.1.12-1.el5
kmod-gfs2-1.52-1.16.el5
cman-2.0.73-1.el5_1.1

my cluster.conf on both sites
---------------------------------------------------------------------------------
<?xml version="1.0"?>
<cluster name="cluster" config_version="2">
<cman two_node="1" expected_votes="1">
</cman>
<clusternodes>

<clusternode name="node1" votes="1" nodeid="1">
         <fence>
                <method name="human">
                        <device name="human" nodename="node1"/>
                </method>
        </fence>
</clusternode>

<clusternode name="node2" votes="1" nodeid="2">
         <fence>
                <method name="human">
                        <device name="human" nodename="node2"/>
                </method>
        </fence>
</clusternode>
</clusternodes>

<fencedevices>
        <fencedevice name="human" agent="fence_manual"/>
</fencedevices>
</cluster>
---------------------------------------------------------------------------------------
my hosts on both sites
192.168.0.1	node1
192.168.0.2	node2

my mountpoints
mkfs.gfs2 -p lock_dlm -t cluster:drbd -j 2 /dev/drbd0
mount -t gfs2 -o noatime,nodiratime /dev/drbd0 /test
(Btw: => drbd works fine as Primary/Primary)

ok, i can use /test on both sites and can write to files
and so on.

cman_tool nodes
--------------------------------------------------------------------------------------
Node  Sts   Inc   Joined               Name
   1   M    364   2008-02-26 23:20:16  node1
   2   M    360   2008-02-26 23:20:16  node2

cman_tool status
-------------------------------------------------------------------------------------
Version: 6.0.1
Config Version: 3
Cluster Name: cluster
Cluster Id: 34996
Cluster Member: Yes
Cluster Generation: 364
Membership state: Cluster-Member
Nodes: 2
Expected votes: 1
Total votes: 2
Quorum: 1  
Active subsystems: 6
Flags: 2node 
Ports Bound: 0  
Node name: node2
Node ID: 2
Multicast addresses: 239.192.136.61 
Node addresses: 192.168.0.2

NOW: i power node1 off !

my log on node2 shows:
-----------------------------------------------------------------------------------------
==> /var/log/messages <==
Feb 26 23:27:22 node2 last message repeated 13 times

==> /var/log/kernel <==
Feb 26 23:27:31 node2 kernel: tg3: eth1: Link is down.
Feb 26 23:27:32 node2 kernel: tg3: eth1: Link is up at 100 Mbps, full duplex.
Feb 26 23:27:32 node2 kernel: tg3: eth1: Flow control is off for TX and off 
for RX.
Feb 26 23:27:36 node2 kernel: drbd0: PingAck did not arrive in time.
Feb 26 23:27:36 node2 kernel: drbd0: peer( Primary -> Unknown ) conn( 
Connected -> NetworkFailure ) pdsk( UpToDate -> DUnknown )
Feb 26 23:27:36 node2 kernel: drbd0: Creating new current UUID
Feb 26 23:27:36 node2 kernel: drbd0: asender terminated
Feb 26 23:27:36 node2 kernel: drbd0: short read expecting header on sock: 
r=-512
Feb 26 23:27:36 node2 kernel: drbd0: tl_clear()
Feb 26 23:27:36 node2 kernel: drbd0: Connection closed
Feb 26 23:27:36 node2 kernel: drbd0: Writing meta data super block now.
Feb 26 23:27:36 node2 kernel: drbd0: conn( NetworkFailure -> Unconnected )
Feb 26 23:27:36 node2 kernel: drbd0: receiver terminated
Feb 26 23:27:36 node2 kernel: drbd0: receiver (re)started
Feb 26 23:27:36 node2 kernel: drbd0: conn( Unconnected -> WFConnection )

==> /var/log/messages <==
Feb 26 23:27:37 node2 last message repeated 3 times
Feb 26 23:27:40 node2 openais[3288]: [TOTEM] The token was lost in the 
OPERATIONAL state.
Feb 26 23:27:40 node2 openais[3288]: [TOTEM] Receive multicast socket recv 
buffer size (288000 bytes).
Feb 26 23:27:40 node2 openais[3288]: [TOTEM] Transmit multicast socket send 
buffer size (262142 bytes).
Feb 26 23:27:40 node2 openais[3288]: [TOTEM] entering GATHER state from 2.
Feb 26 23:27:42 node2 root: Process did not exit cleanly, returned 2 with 
signal 0
Feb 26 23:27:44 node2 openais[3288]: [TOTEM] entering GATHER state from 0.
Feb 26 23:27:44 node2 openais[3288]: [TOTEM] Creating commit token because I 
am the rep.
Feb 26 23:27:44 node2 openais[3288]: [TOTEM] Saving state aru 31 high seq 
received 31
Feb 26 23:27:44 node2 openais[3288]: [TOTEM] Storing new sequence id for ring 
170
Feb 26 23:27:44 node2 openais[3288]: [TOTEM] entering COMMIT state.
Feb 26 23:27:44 node2 openais[3288]: [TOTEM] entering RECOVERY state.
Feb 26 23:27:44 node2 openais[3288]: [TOTEM] position [0] member 192.168.0.2:
Feb 26 23:27:44 node2 openais[3288]: [TOTEM] previous ring seq 364 rep 
192.168.0.1
Feb 26 23:27:44 node2 openais[3288]: [TOTEM] aru 31 high delivered 31 received 
flag 1
Feb 26 23:27:44 node2 openais[3288]: [TOTEM] Did not need to originate any 
messages in recovery.
Feb 26 23:27:44 node2 openais[3288]: [TOTEM] Sending initial ORF token
Feb 26 23:27:44 node2 openais[3288]: [CLM  ] CLM CONFIGURATION CHANGE
Feb 26 23:27:44 node2 openais[3288]: [CLM  ] New Configuration:
Feb 26 23:27:44 node2 fenced[3307]: node1 not a cluster member after 0 sec 
post_fail_delay
Feb 26 23:27:44 node2 openais[3288]: [CLM  ]       r(0) ip(192.168.0.2)
Feb 26 23:27:44 node2 fenced[3307]: fencing node "node1"

==> /var/log/kernel <==
Feb 26 23:27:44 node2 kernel: dlm: closing connection to node 1

==> /var/log/messages <==
Feb 26 23:27:44 node2 openais[3288]: [CLM  ] Members Left:
Feb 26 23:27:45 node2 openais[3288]: [CLM  ]       r(0) ip(192.168.0.1)
Feb 26 23:27:45 node2 fence_manual: Node node1 needs to be reset before 
recovery can procede.  Waiting for node1 to rejoin the cluster or for manual 
acknowledgement that it has been reset (i.e. fence_ack_manual -n node1)
Feb 26 23:27:45 node2 openais[3288]: [CLM  ] Members Joined:
Feb 26 23:27:45 node2 openais[3288]: [CLM  ] CLM CONFIGURATION CHANGE
Feb 26 23:27:45 node2 openais[3288]: [CLM  ] New Configuration:
Feb 26 23:27:45 node2 openais[3288]: [CLM  ]       r(0) ip(192.168.0.2)
Feb 26 23:27:45 node2 openais[3288]: [CLM  ] Members Left:
Feb 26 23:27:45 node2 openais[3288]: [CLM  ] Members Joined:
Feb 26 23:27:45 node2 openais[3288]: [SYNC ] This node is within the primary 
component and will provide service.
Feb 26 23:27:45 node2 openais[3288]: [TOTEM] entering OPERATIONAL state.
Feb 26 23:27:45 node2 openais[3288]: [CLM  ] got nodejoin message 192.168.0.2
Feb 26 23:27:45 node2 openais[3288]: [CPG  ] got joinlist message from node 2
Feb 26 23:27:47 node2 root: Process did not exit cleanly, returned 2 with 
signal 0
-------------------------------------------------------------------------------------------------------------

ls /test works

BUT

touch /test/testfile hangs ....

cman_tool nodes shows
------------------------------------------------------------------------------------------------------------------
Node  Sts   Inc   Joined               Name
   1   X    364                        node1
   2   M    360   2008-02-26 23:20:16  node2
-----------------------------------------------------------------------------------------------------------------

cman_tool status shows
-----------------------------------------------------------------------------------------------------------------
Version: 6.0.1
Config Version: 3
Cluster Name: cluster
Cluster Id: 34996
Cluster Member: Yes
Cluster Generation: 368
Membership state: Cluster-Member
Nodes: 1
Expected votes: 1
Total votes: 1
Quorum: 1  
Active subsystems: 6
Flags: 2node 
Ports Bound: 0  
Node name: node2
Node ID: 2
Multicast addresses: 239.192.136.61 
Node addresses: 192.168.0.2
------------------------------------------------------------------------------------------------------------------

my drbd is no problem state is already primary (standalone)

Why can't i write to a gfs partition in the "lost Node" state ?

Now: i power node1 on !

drbd is no problem -> its recovered.
now i start cman
and my touch will be finished ....

Thanks for any ideas and help

-Thomas



From aletedavat at yahoo.com  Wed Feb 27 09:00:18 2008
From: aletedavat at yahoo.com (ar siv)
Date: Wed, 27 Feb 2008 01:00:18 -0800 (PST)
Subject: [Linux-cluster] "fence_mcdata" reports: failed: unexpected port
	state 
Message-ID: <143724.43494.qm@web55601.mail.re4.yahoo.com>

Hello;

I have 2 node Redhat Cluster (RHEL4 U4 and Cluster
Suite) I'm using mc_data fiber channel switch for
fencing

when I want to fence manually using 
fence_mcdata -a x.x.x. -l xxx -p xxxx -n 5 -o disable

following messages appears

fencing node "test1"
agent "fence_mcdata" reports: failed: unexpected port
state 

How can I resolve this issue ?

Thanks



      ____________________________________________________________________________________
Be a better friend, newshound, and 
know-it-all with Yahoo! Mobile.  Try it now.  http://mobile.yahoo.com/;_ylt=Ahu06i62sR8HDtDypao8Wcj9tAcJ 



From qqlka at nask.pl  Wed Feb 27 13:04:42 2008
From: qqlka at nask.pl (=?iso-8859-2?Q?Agnieszka_Kuka=B3owicz?=)
Date: Wed, 27 Feb 2008 14:04:42 +0100
Subject: [Linux-cluster] migrating to better node
In-Reply-To: <20080226124834.GA8542@localhost>
Message-ID: <00d801c87941$51d2e530$0777b5c2@gda07ak>

> ...clu2 rejoins...
> Feb 26 13:27:32 clu1 clurgmgrd[3885]: <notice> Migrating vm:win2003 to
> better node clu2.test-cluster.cz
> Feb 26 13:27:35 clu1 kernel: peth0: received packet with  own address
as
> source address
> Feb 26 13:27:37 clu1 kernel: dlm: connecting to 1
> -----> Feb 26 13:27:47 clu1 clurgmgrd[3885]: <err> #75: Failed
changing
> service
> status

Check the Bug #327721
https://bugzilla.redhat.com/show_bug.cgi?id=327721. 
I had the same problem with my cluster. The solution proposed there
helped me.

Cheers
Agnieszka Kukalowicz




From qqlka at nask.pl  Wed Feb 27 13:47:55 2008
From: qqlka at nask.pl (=?iso-8859-2?Q?Agnieszka_Kuka=B3owicz?=)
Date: Wed, 27 Feb 2008 14:47:55 +0100
Subject: [Linux-cluster] Clustat shows wrong service status
Message-ID: <00e301c87947$5afedc30$0777b5c2@gda07ak>

Hi,

Clustat shows something like that:

Member Name                        ID   Status
  ------ ----                        ---- ------
  w2.local					1 Offline
  w1.local					2 Online, Local,
rgmanager

  Service Name         Owner (Last)                   State
  ------- ----         ----- ------                   -----
  vm:VM_Work11_RHEL51  w1.local		            started
  vm:VM_Work12_RHEL51  w1.local		            started
  vm:VM_Work13_RHEL51  w1.local				started
  vm:VM_Work21_RHEL51  w2.local				started
  vm:VM_Work22_RHEL51  w2.local            		started
  vm:VM_Work23_RHEL51  w2.local             		started


The "w2.local" node is offline but clustat shows that all services
previously running on this node are "started". I think they should be
marked as "stopped"

I have installed:

cluster-cim-0.10.0-5.el5_1.1
modcluster-0.10.0-5.el5_1.1
cluster-snmp-0.10.0-5.el5_1.1
rgmanager-2.0.31-1.el5
cman-2.0.73-1.6.el5.test.bz327721
openais-0.80.3-7.el5

My kernel is: 2.6.18-53.1.4.el5xen

Services are configured as below:
     <rm>
                <failoverdomains>
                        <failoverdomain name="VM_w1_failover"
ordered="0" restricted="1">
                                <failoverdomainnode name="w1.local"
priority="1"/>
                        </failoverdomain>
                        <failoverdomain name="VM_w2_failover"
ordered="0" restricted="1">
                                <failoverdomainnode name="w2.local"
priority="1"/>
                        </failoverdomain>
                </failoverdomains>
                <resources/>
                <vm autostart="1" domain="VM_w1_failover" exclusive="0"
name="VM_Work11_RHEL51" path="/virts/w11" recovery="restart"/>
                <vm autostart="1" domain="VM_w1_failover" exclusive="0"
name="VM_Work12_RHEL51" path="/virts/w12" recovery="restart"/>
                <vm autostart="1" domain="VM_w1_failover" exclusive="0"
name="VM_Work13_RHEL51" path="/virts/w13" recovery="restart"/>
                <vm autostart="1" domain="VM_w2_failover" exclusive="0"
name="VM_Work21_RHEL51" path="/virts/w21" recovery="restart"/>
                <vm autostart="1" domain="VM_w2_failover" exclusive="0"
name="VM_Work22_RHEL51" path="/virts/w22" recovery="restart"/>
                <vm autostart="1" domain="VM_w2_failover" exclusive="0"
name="VM_Work23_RHEL51" path="/virts/w23" recovery="restart"/>
        </rm>

Cheers 
Agnieszka Kukalowicz
 




From jruemker at redhat.com  Wed Feb 27 14:34:58 2008
From: jruemker at redhat.com (John Ruemker)
Date: Wed, 27 Feb 2008 09:34:58 -0500
Subject: [Linux-cluster] GFS2 2 Node Cluster - lost Node - Mount
	not	writeable
In-Reply-To: <200802262340.46493.tb@tbits.net>
References: <200802262340.46493.tb@tbits.net>
Message-ID: <47C57512.3050700@redhat.com>

Thomas B?rnert wrote:
> Hi List,
>
> 2 Servers - connected with crossover
>
> my rpms:
> gfs2-utils-0.1.38-1.el5
> gfs-utils-0.1.12-1.el5
> kmod-gfs2-1.52-1.16.el5
> cman-2.0.73-1.el5_1.1
>
> my cluster.conf on both sites
> ---------------------------------------------------------------------------------
> <?xml version="1.0"?>
> <cluster name="cluster" config_version="2">
> <cman two_node="1" expected_votes="1">
> </cman>
> <clusternodes>
>
> <clusternode name="node1" votes="1" nodeid="1">
>          <fence>
>                 <method name="human">
>                         <device name="human" nodename="node1"/>
>                 </method>
>         </fence>
> </clusternode>
>
> <clusternode name="node2" votes="1" nodeid="2">
>          <fence>
>                 <method name="human">
>                         <device name="human" nodename="node2"/>
>                 </method>
>         </fence>
> </clusternode>
> </clusternodes>
>
> <fencedevices>
>         <fencedevice name="human" agent="fence_manual"/>
> </fencedevices>
> </cluster>
> ---------------------------------------------------------------------------------------
> my hosts on both sites
> 192.168.0.1	node1
> 192.168.0.2	node2
>
> my mountpoints
> mkfs.gfs2 -p lock_dlm -t cluster:drbd -j 2 /dev/drbd0
> mount -t gfs2 -o noatime,nodiratime /dev/drbd0 /test
> (Btw: => drbd works fine as Primary/Primary)
>
> ok, i can use /test on both sites and can write to files
> and so on.
>
> cman_tool nodes
> --------------------------------------------------------------------------------------
> Node  Sts   Inc   Joined               Name
>    1   M    364   2008-02-26 23:20:16  node1
>    2   M    360   2008-02-26 23:20:16  node2
>
> cman_tool status
> -------------------------------------------------------------------------------------
> Version: 6.0.1
> Config Version: 3
> Cluster Name: cluster
> Cluster Id: 34996
> Cluster Member: Yes
> Cluster Generation: 364
> Membership state: Cluster-Member
> Nodes: 2
> Expected votes: 1
> Total votes: 2
> Quorum: 1  
> Active subsystems: 6
> Flags: 2node 
> Ports Bound: 0  
> Node name: node2
> Node ID: 2
> Multicast addresses: 239.192.136.61 
> Node addresses: 192.168.0.2
>
> NOW: i power node1 off !
>
> my log on node2 shows:
> -----------------------------------------------------------------------------------------
> ==> /var/log/messages <==
> Feb 26 23:27:22 node2 last message repeated 13 times
>
> ==> /var/log/kernel <==
> Feb 26 23:27:31 node2 kernel: tg3: eth1: Link is down.
> Feb 26 23:27:32 node2 kernel: tg3: eth1: Link is up at 100 Mbps, full duplex.
> Feb 26 23:27:32 node2 kernel: tg3: eth1: Flow control is off for TX and off 
> for RX.
> Feb 26 23:27:36 node2 kernel: drbd0: PingAck did not arrive in time.
> Feb 26 23:27:36 node2 kernel: drbd0: peer( Primary -> Unknown ) conn( 
> Connected -> NetworkFailure ) pdsk( UpToDate -> DUnknown )
> Feb 26 23:27:36 node2 kernel: drbd0: Creating new current UUID
> Feb 26 23:27:36 node2 kernel: drbd0: asender terminated
> Feb 26 23:27:36 node2 kernel: drbd0: short read expecting header on sock: 
> r=-512
> Feb 26 23:27:36 node2 kernel: drbd0: tl_clear()
> Feb 26 23:27:36 node2 kernel: drbd0: Connection closed
> Feb 26 23:27:36 node2 kernel: drbd0: Writing meta data super block now.
> Feb 26 23:27:36 node2 kernel: drbd0: conn( NetworkFailure -> Unconnected )
> Feb 26 23:27:36 node2 kernel: drbd0: receiver terminated
> Feb 26 23:27:36 node2 kernel: drbd0: receiver (re)started
> Feb 26 23:27:36 node2 kernel: drbd0: conn( Unconnected -> WFConnection )
>
> ==> /var/log/messages <==
> Feb 26 23:27:37 node2 last message repeated 3 times
> Feb 26 23:27:40 node2 openais[3288]: [TOTEM] The token was lost in the 
> OPERATIONAL state.
> Feb 26 23:27:40 node2 openais[3288]: [TOTEM] Receive multicast socket recv 
> buffer size (288000 bytes).
> Feb 26 23:27:40 node2 openais[3288]: [TOTEM] Transmit multicast socket send 
> buffer size (262142 bytes).
> Feb 26 23:27:40 node2 openais[3288]: [TOTEM] entering GATHER state from 2.
> Feb 26 23:27:42 node2 root: Process did not exit cleanly, returned 2 with 
> signal 0
> Feb 26 23:27:44 node2 openais[3288]: [TOTEM] entering GATHER state from 0.
> Feb 26 23:27:44 node2 openais[3288]: [TOTEM] Creating commit token because I 
> am the rep.
> Feb 26 23:27:44 node2 openais[3288]: [TOTEM] Saving state aru 31 high seq 
> received 31
> Feb 26 23:27:44 node2 openais[3288]: [TOTEM] Storing new sequence id for ring 
> 170
> Feb 26 23:27:44 node2 openais[3288]: [TOTEM] entering COMMIT state.
> Feb 26 23:27:44 node2 openais[3288]: [TOTEM] entering RECOVERY state.
> Feb 26 23:27:44 node2 openais[3288]: [TOTEM] position [0] member 192.168.0.2:
> Feb 26 23:27:44 node2 openais[3288]: [TOTEM] previous ring seq 364 rep 
> 192.168.0.1
> Feb 26 23:27:44 node2 openais[3288]: [TOTEM] aru 31 high delivered 31 received 
> flag 1
> Feb 26 23:27:44 node2 openais[3288]: [TOTEM] Did not need to originate any 
> messages in recovery.
> Feb 26 23:27:44 node2 openais[3288]: [TOTEM] Sending initial ORF token
> Feb 26 23:27:44 node2 openais[3288]: [CLM  ] CLM CONFIGURATION CHANGE
> Feb 26 23:27:44 node2 openais[3288]: [CLM  ] New Configuration:
> Feb 26 23:27:44 node2 fenced[3307]: node1 not a cluster member after 0 sec 
> post_fail_delay
> Feb 26 23:27:44 node2 openais[3288]: [CLM  ]       r(0) ip(192.168.0.2)
> Feb 26 23:27:44 node2 fenced[3307]: fencing node "node1"
>
> ==> /var/log/kernel <==
> Feb 26 23:27:44 node2 kernel: dlm: closing connection to node 1
>
> ==> /var/log/messages <==
> Feb 26 23:27:44 node2 openais[3288]: [CLM  ] Members Left:
> Feb 26 23:27:45 node2 openais[3288]: [CLM  ]       r(0) ip(192.168.0.1)
> Feb 26 23:27:45 node2 fence_manual: Node node1 needs to be reset before 
> recovery can procede.  Waiting for node1 to rejoin the cluster or for manual 
> acknowledgement that it has been reset (i.e. fence_ack_manual -n node1)
>   
Note this message...

> Feb 26 23:27:45 node2 openais[3288]: [CLM  ] Members Joined:
> Feb 26 23:27:45 node2 openais[3288]: [CLM  ] CLM CONFIGURATION CHANGE
> Feb 26 23:27:45 node2 openais[3288]: [CLM  ] New Configuration:
> Feb 26 23:27:45 node2 openais[3288]: [CLM  ]       r(0) ip(192.168.0.2)
> Feb 26 23:27:45 node2 openais[3288]: [CLM  ] Members Left:
> Feb 26 23:27:45 node2 openais[3288]: [CLM  ] Members Joined:
> Feb 26 23:27:45 node2 openais[3288]: [SYNC ] This node is within the primary 
> component and will provide service.
> Feb 26 23:27:45 node2 openais[3288]: [TOTEM] entering OPERATIONAL state.
> Feb 26 23:27:45 node2 openais[3288]: [CLM  ] got nodejoin message 192.168.0.2
> Feb 26 23:27:45 node2 openais[3288]: [CPG  ] got joinlist message from node 2
> Feb 26 23:27:47 node2 root: Process did not exit cleanly, returned 2 with 
> signal 0
> -------------------------------------------------------------------------------------------------------------
>
> ls /test works
>
> BUT
>
> touch /test/testfile hangs ....
>
> cman_tool nodes shows
> ------------------------------------------------------------------------------------------------------------------
> Node  Sts   Inc   Joined               Name
>    1   X    364                        node1
>    2   M    360   2008-02-26 23:20:16  node2
> -----------------------------------------------------------------------------------------------------------------
>
> cman_tool status shows
> -----------------------------------------------------------------------------------------------------------------
> Version: 6.0.1
> Config Version: 3
> Cluster Name: cluster
> Cluster Id: 34996
> Cluster Member: Yes
> Cluster Generation: 368
> Membership state: Cluster-Member
> Nodes: 1
> Expected votes: 1
> Total votes: 1
> Quorum: 1  
> Active subsystems: 6
> Flags: 2node 
> Ports Bound: 0  
> Node name: node2
> Node ID: 2
> Multicast addresses: 239.192.136.61 
> Node addresses: 192.168.0.2
> ------------------------------------------------------------------------------------------------------------------
>
> my drbd is no problem state is already primary (standalone)
>
> Why can't i write to a gfs partition in the "lost Node" state ?
>
> Now: i power node1 on !
>
> drbd is no problem -> its recovered.
> now i start cman
> and my touch will be finished ....
>
> Thanks for any ideas and help
>
> -Thomas
>
> --
> Linux-cluster mailing list
> Linux-cluster at redhat.com
> https://www.redhat.com/mailman/listinfo/linux-cluster
>   

This is because you are using manual fencing.  Fencing is required to 
ensure that an errant node does not continue to write to the shared 
filesystem after it has lost communication with the cluster, thereby 
corrupting the data.  The only way to do this is to halt all cluster 
activity (including granting GFS locks) until the fencing succeeds.   
The "manual" means that an administrator must intervene and correct the 
problem before cluster operations can resume.  So when you power off 
node1, node2 detects missed heartbeats and fences node1.  Now you must 
manually fence node1 by powering it off (this is already done in your 
case) then do one of the following:

     1) Run the following command to acknowledge that you have manually 
fenced the node

               # /sbin/fence_ack_manual node1

         OR

     2) Start node1 back up and have it rejoin the cluster

The danger with manual fencing comes in when you quickly run 
fence_ack_manual without properly investigating the issue or fencing the 
node.  You may see that the fenced node is still up and quickly run that 
command without noticing that the network connection has been lost.  Now 
the nodes proceed with writing to GFS without being able to communicate 
and they quickly corrupt the data. 

So, when using manual fencing always take caution before running 
fence_ack_manual. 

John



From sanelson at gmail.com  Wed Feb 27 14:45:12 2008
From: sanelson at gmail.com (Stephen Nelson-Smith)
Date: Wed, 27 Feb 2008 14:45:12 +0000
Subject: [Linux-cluster] Clustering Oracle 10g
Message-ID: <b6131fdc0802270645o71ae76f7w63e3c9c018654cf3@mail.gmail.com>

Hi,

I've got a client with a single instance of 10g running on Windows Server 2003.

They've approached me with a view to migrating to Linux, and
increasing its availability.

What's the current ruling from Oracle about multple licences?  If I
just had an active-passive system, do I still have to fork out five
figure numbers for the second, idle Oracle instance?

S.



From petr.tuma at nenya.ms.mff.cuni.cz  Wed Feb 27 15:12:43 2008
From: petr.tuma at nenya.ms.mff.cuni.cz (Petr Tuma)
Date: Wed, 27 Feb 2008 16:12:43 +0100
Subject: [Linux-cluster] Probably some silly mistake setting up a cluster ?
Message-ID: <47C57DEB.5000506@dsrg.mff.cuni.cz>

Greetings,

I am trying to set up a cluster with (for now) two nodes, reason being
the semantic guarantees of GFS when accessing shared files (that is, I
am not interested in fault tolerance, performance or anything else).
Unfortunately, I keep running into all sorts of problems, for
example:

    - After a few hours of intensive workload, the cluster sometimes
simply stops. All file system calls block, but things like cman_tool
status or group_tool status insist everything is all right. Soft reboot
is not possible due to various services waiting infinitely, after power
cycling fsck finds inconsistencies on the file system.

    - Sometimes, when trying to execute a binary on the file system, I get
execvp returning permission denied when it should not, but when I try
again, everything is all right. I sometimes even observe this when
trying to start a script on the file system, as if the interpreter of
the script (which is on a different file system altogether) had wrong
permissions. Again, simply trying one more time makes everything work.

The config of the cluster seems relatively simple:

    - i686 single CPU node
       - file system device accessible over iSCSI
       - cluster subnet (unfortunately) connected over OpenVPN
    - x86_64 eight CPU virtual node
       - file system device provided by host which uses iSCSI
    - both nodes resolve into the same subnet using /etc/hosts
    - nothing except a single GFS2 file system is mounted
    - fencing uses fence_manual
    - both nodes run Fedora 8

Config attached, not like there is anything unusual in it.

As an absolute novice, I am probably making some glaringly obvious silly
mistake which results in the very weird behavior described above, but
try as I might, I do not see anything that can cause this ?

Thanks for any advice, Petr


-------------- next part --------------
A non-text attachment was scrubbed...
Name: cluster.conf
Type: text/xml
Size: 711 bytes
Desc: not available
URL: <http://listman.redhat.com/archives/linux-cluster/attachments/20080227/9ccfa91e/attachment.xml>

From raindoctor at gmail.com  Wed Feb 27 17:02:31 2008
From: raindoctor at gmail.com (Pedro Espinoza)
Date: Wed, 27 Feb 2008 12:02:31 -0500
Subject: [Linux-cluster] Clustering Oracle 10g
In-Reply-To: <b6131fdc0802270645o71ae76f7w63e3c9c018654cf3@mail.gmail.com>
References: <b6131fdc0802270645o71ae76f7w63e3c9c018654cf3@mail.gmail.com>
Message-ID: <b86c876f0802270902k7fd949f9gc125f0844f3565ba@mail.gmail.com>

Read this thread:

http://www.freelists.org/archives/oracle-l/02-2008/msg00370.html

On Wed, Feb 27, 2008 at 9:45 AM, Stephen Nelson-Smith
<sanelson at gmail.com> wrote:
> Hi,
>
>  I've got a client with a single instance of 10g running on Windows Server 2003.
>
>  They've approached me with a view to migrating to Linux, and
>  increasing its availability.
>
>  What's the current ruling from Oracle about multple licences?  If I
>  just had an active-passive system, do I still have to fork out five
>  figure numbers for the second, idle Oracle instance?
>
>  S.
>
>  --
>  Linux-cluster mailing list
>  Linux-cluster at redhat.com
>  https://www.redhat.com/mailman/listinfo/linux-cluster
>



From public at van-schelve.de  Wed Feb 27 19:23:18 2008
From: public at van-schelve.de (van Schelve)
Date: Wed, 27 Feb 2008 20:23:18 +0100
Subject: [Linux-cluster] High availability xen cluster
Message-ID: <4eccbcc3e1e1f2b73b7cd81b3bff73b6@mail.van-schelve.de>

Hello. I don't know if this here is the right list to discuss this but
maybe someone else with an equal scenario can describe how to best solve
this.

I plan to build a cluster environment with 6 or 8 nodes to provide xen
based virtual maschines. In our environment we have two data centre in
short rza and rzb. In addition we have a zoned SAN infra structure with a
Hitachi OPEN-V fabric in each data centre. My nodes are available to access
disks from both fabrics over multiple pathes. Please look at the following
multipath listing from one of my nodes: 

[root at ux072 ~]# multipath -l
mpath2_rzb (1HITACHI_R450F8D41022) dm-9 HITACHI,OPEN-V
[size=30G][features=1 queue_if_no_path][hwhandler=0]
\_ round-robin 0 [prio=0][active]
 \_ 1:0:0:2 sdd 8:48   [active][undef]
 \_ 1:0:1:2 sdg 8:96   [active][undef]
 \_ 2:0:0:2 sdp 8:240  [active][undef]
 \_ 2:0:1:2 sds 65:32  [active][undef]
mpath2_rza (1HITACHI_R450F94D1022) dm-12 HITACHI,OPEN-V
[size=30G][features=1 queue_if_no_path][hwhandler=0]
\_ round-robin 0 [prio=0][active]
 \_ 1:0:2:2 sdj 8:144  [active][undef]
 \_ 1:0:3:2 sdm 8:192  [active][undef]
 \_ 2:0:2:2 sdv 65:80  [active][undef]
 \_ 2:0:3:2 sdy 65:128 [active][undef]
mpath0_rzb (1HITACHI_R450F8D41020) dm-7 HITACHI,OPEN-V
[size=30G][features=1 queue_if_no_path][hwhandler=0]
\_ round-robin 0 [prio=0][active]
 \_ 1:0:0:0 sdb 8:16   [active][undef]
 \_ 1:0:1:0 sde 8:64   [active][undef]
 \_ 2:0:0:0 sdn 8:208  [active][undef]
 \_ 2:0:1:0 sdq 65:0   [active][undef]
mpath0_rza (1HITACHI_R450F94D1020) dm-10 HITACHI,OPEN-V
[size=30G][features=1 queue_if_no_path][hwhandler=0]
\_ round-robin 0 [prio=0][active]
 \_ 1:0:2:0 sdh 8:112  [active][undef]
 \_ 1:0:3:0 sdk 8:160  [active][undef]
 \_ 2:0:2:0 sdt 65:48  [active][undef]
 \_ 2:0:3:0 sdw 65:96  [active][undef]
mpath1_rzb (1HITACHI_R450F8D41021) dm-8 HITACHI,OPEN-V
[size=30G][features=1 queue_if_no_path][hwhandler=0]
\_ round-robin 0 [prio=0][active]
 \_ 1:0:0:1 sdc 8:32   [active][undef]
 \_ 1:0:1:1 sdf 8:80   [active][undef]
 \_ 2:0:0:1 sdo 8:224  [active][undef]
 \_ 2:0:1:1 sdr 65:16  [active][undef]
mpath1_rza (1HITACHI_R450F94D1021) dm-11 HITACHI,OPEN-V
[size=30G][features=1 queue_if_no_path][hwhandler=0]
\_ round-robin 0 [prio=0][active]
 \_ 1:0:2:1 sdi 8:128  [active][undef]
 \_ 1:0:3:1 sdl 8:176  [active][undef]
 \_ 2:0:2:1 sdu 65:64  [active][undef]
 \_ 2:0:3:1 sdx 65:112 [active][undef]

There are three disks in each data centre. Currently I only use the disks
in rza.

At the moment I'm testing with a two node cluster. The virtual machines are
on SAN disks and I can live migrate from one node to the other one. But
what I have to cover is the disaster. What happens when the fabric in rza
crashes? My virtual maschines are unavailable. What I'm thinking about is a
hardware based
mirroring between the both fabrics and break up the mirror when the
disaster happens or we need to power off the storage for maintenance. But
my problem is that I see duplicate pv id's in this situation. I cannot
mirror based on lvm because it is too slow.

Thank you for your ideas.

-- Hans-Gerd van Schelve



From cfeist at redhat.com  Wed Feb 27 20:35:07 2008
From: cfeist at redhat.com (Chris Feist)
Date: Wed, 27 Feb 2008 14:35:07 -0600
Subject: [Linux-cluster] Source Control switch from CVS to git
Message-ID: <47C5C97B.20609@redhat.com>

Hello,

Just an update to let everyone know that we've completed our switchover from CVS 
to git.  If you'd like instructions on how to access the new repository, you can 
get them here: http://sources.redhat.com/cluster/wiki/ClusterGit

The CVS cluster repository will still be available for read-only historical use.

Any questions, please let me know.

Thanks,
Chris



From jpalmae at gmail.com  Wed Feb 27 20:36:19 2008
From: jpalmae at gmail.com (Jorge Palma)
Date: Wed, 27 Feb 2008 17:36:19 -0300
Subject: [Linux-cluster] HA LVM
Message-ID: <5b65f1b10802271236u543555afybd7363fdf987ac3a@mail.gmail.com>

Hello:

I am trying to implement HA LVM in 2 nodes with RHEL 5.1, but I have
the following errors:

in vmdb01:

[root at vmdb01 ~]# rg_test test /etc/cluster/cluster.conf start service testSG
Running in test mode.
Starting testSG...
volume_list=["rootdg", "@vmdb01"]
<notice> Owner of lvmclusterdg/lvmclustervol is not in the cluster
<notice> Stealing lvmclusterdg/lvmclustervol
lvchange  Logical volume "lvmclustervol" changed
<err>    Failed to steal lvmclusterdg/lvmclustervol from lvs         .
Failed to start testSG

in vmfe01:

[root at vmfe01 ~]# rg_test test /etc/cluster/cluster.conf start service testSG
Running in test mode.
Starting testSG...
volume_list=["rootdg", "@vmfe01"]
<notice> Owner of lvmclusterdg/lvmclustervol is not in the cluster
<notice> Stealing lvmclusterdg/lvmclustervol
lvchange  Logical volume "lvmclustervol" changed
<err>    Failed to steal lvmclusterdg/lvmclustervol from lvs         .
Failed to start testSG

In vmdb01 lvm.conf have:

volume_list = [ "rootdg", "@vmdb01" ]

In vmfe01 lvm.cong have:

volume_list = [ "rootdg", "@vmfe01" ]

Will appreciate any ideas

PD: sorry by my english


-- 
Jorge Palma Escobar
Ingeniero de Sistemas
Red Hat Linux Certified Engineer
Certificate N? 804005089418233



From lhh at redhat.com  Wed Feb 27 22:22:37 2008
From: lhh at redhat.com (Lon Hohberger)
Date: Wed, 27 Feb 2008 17:22:37 -0500
Subject: [Linux-cluster] Clustat shows wrong service status
In-Reply-To: <00e301c87947$5afedc30$0777b5c2@gda07ak>
References: <00e301c87947$5afedc30$0777b5c2@gda07ak>
Message-ID: <1204150957.13733.3.camel@ayanami.boston.devel.redhat.com>

On Wed, 2008-02-27 at 14:47 +0100, Agnieszka Kuka?owicz wrote:
> Hi,
> 
> Clustat shows something like that:
> 
> Member Name                        ID   Status
>   ------ ----                        ---- ------
>   w2.local					1 Offline
>   w1.local					2 Online, Local,
> rgmanager

One of two things is likely:

(a) The node has not been fenced yet, or
(b) you did the manual override trick and hit this bug:
    https://bugzilla.redhat.com/show_bug.cgi?id=435189

I should add this to the FAQ.

-- Lon




From lhh at redhat.com  Wed Feb 27 22:23:54 2008
From: lhh at redhat.com (Lon Hohberger)
Date: Wed, 27 Feb 2008 17:23:54 -0500
Subject: [Linux-cluster] CS5 / About status requests
In-Reply-To: <47C41DEE.1030207@bull.net>
References: <47C41DEE.1030207@bull.net>
Message-ID: <1204151034.13733.5.camel@ayanami.boston.devel.redhat.com>

On Tue, 2008-02-26 at 15:10 +0100, Alain Moulle wrote:
> Hi
> 
> What is the politic of service status request :
> it seems that there is systematically a status request
> just after the start of the service and then a periodic
> status (depending on monitor variable in script.sh) but the
> 1st periodic status can be requested between 1 and xx secunds
> just after the service start (if xx if the monitor period)

It's actually xx=10, I think


> And is there any change on this status politic with regard to the CS4 ?

It would require a change to the code; I don't think it's hard, though.

-- Lon



From lhh at redhat.com  Wed Feb 27 22:25:52 2008
From: lhh at redhat.com (Lon Hohberger)
Date: Wed, 27 Feb 2008 17:25:52 -0500
Subject: [Linux-cluster] migrating to better node
In-Reply-To: <20080226124834.GA8542@localhost>
References: <20080226124834.GA8542@localhost>
Message-ID: <1204151152.13733.7.camel@ayanami.boston.devel.redhat.com>

On Tue, 2008-02-26 at 13:48 +0100, Jakub Suchy wrote:
> -----> Feb 26 13:27:47 clu1 clurgmgrd[3885]: <err> #75: Failed
> changing service

rpm -q rgmanager ?  It sounds familiar (like something we fixed).

-- Lon



From lhh at redhat.com  Wed Feb 27 22:26:34 2008
From: lhh at redhat.com (Lon Hohberger)
Date: Wed, 27 Feb 2008 17:26:34 -0500
Subject: [Linux-cluster] migrating to better node
In-Reply-To: <00d801c87941$51d2e530$0777b5c2@gda07ak>
References: <00d801c87941$51d2e530$0777b5c2@gda07ak>
Message-ID: <1204151194.13733.9.camel@ayanami.boston.devel.redhat.com>

On Wed, 2008-02-27 at 14:04 +0100, Agnieszka Kuka?owicz wrote:
> > ...clu2 rejoins...
> > Feb 26 13:27:32 clu1 clurgmgrd[3885]: <notice> Migrating vm:win2003 to
> > better node clu2.test-cluster.cz
> > Feb 26 13:27:35 clu1 kernel: peth0: received packet with  own address
> as
> > source address
> > Feb 26 13:27:37 clu1 kernel: dlm: connecting to 1
> > -----> Feb 26 13:27:47 clu1 clurgmgrd[3885]: <err> #75: Failed
> changing
> > service
> > status
> 
> Check the Bug #327721
> https://bugzilla.redhat.com/show_bug.cgi?id=327721. 
> I had the same problem with my cluster. The solution proposed there
> helped me.

Nice - that's the one!

-- Lon




From lhh at redhat.com  Wed Feb 27 22:30:56 2008
From: lhh at redhat.com (Lon Hohberger)
Date: Wed, 27 Feb 2008 17:30:56 -0500
Subject: [Linux-cluster] GFS2 2 Node Cluster - lost Node - Mount not
	writeable
In-Reply-To: <200802262340.46493.tb@tbits.net>
References: <200802262340.46493.tb@tbits.net>
Message-ID: <1204151456.13733.13.camel@ayanami.boston.devel.redhat.com>

On Tue, 2008-02-26 at 23:40 +0100, Thomas B?rnert wrote:
> ------------------------------------------------------------------------------------------------------------------
> 
> my drbd is no problem state is already primary (standalone)

It still needs to call the outdate_peer handler (which must succeed!),
or it will block writes until the other node comes back.

> Why can't i write to a gfs partition in the "lost Node" state ?
> 
> Now: i power node1 on !
> 
> drbd is no problem -> its recovered.
> now i start cman
> and my touch will be finished ....
> 
> Thanks for any ideas and help
> 
> -Thomas

What does drbd.conf look like?

I wrote this recently, maybe it will help -

http://sources.redhat.com/cluster/wiki/DRBD_Cookbook

(you will probably have to run fence_ack_manual *twice* in with a manual
fencing configuration!)

-- Lon



From kanderso at redhat.com  Wed Feb 27 22:39:38 2008
From: kanderso at redhat.com (Kevin Anderson)
Date: Wed, 27 Feb 2008 16:39:38 -0600
Subject: [Linux-cluster] Probably some silly mistake setting up a cluster ?
In-Reply-To: <47C57DEB.5000506@dsrg.mff.cuni.cz>
References: <47C57DEB.5000506@dsrg.mff.cuni.cz>
Message-ID: <1204151978.2731.20.camel@localhost.localdomain>


On Wed, 2008-02-27 at 16:12 +0100, Petr Tuma wrote:
> Greetings,
> 
> I am trying to set up a cluster with (for now) two nodes, reason being
> the semantic guarantees of GFS when accessing shared files (that is, I
> am not interested in fault tolerance, performance or anything else).
> Unfortunately, I keep running into all sorts of problems, for
> example:
> 
>     - After a few hours of intensive workload, the cluster sometimes
> simply stops. All file system calls block, but things like cman_tool
> status or group_tool status insist everything is all right. Soft reboot
> is not possible due to various services waiting infinitely, after power
> cycling fsck finds inconsistencies on the file system.

It would be helpful to generate a stack trace of all processes when this
happens to see what they are waiting on.
  
> 
>     - Sometimes, when trying to execute a binary on the file system, I get
> execvp returning permission denied when it should not, but when I try
> again, everything is all right. I sometimes even observe this when
> trying to start a script on the file system, as if the interpreter of
> the script (which is on a different file system altogether) had wrong
> permissions. Again, simply trying one more time makes everything work.

This is a defect that has been fixed in the upstream version of GFS2.
Which version are you using?  In general, although much better than it
used to be, GFS2 is not yet stable.  You should use gfs-kmod if you are
looking for a stable solution.

Thanks
Kevin




From bpkroth at wisc.edu  Wed Feb 27 22:44:59 2008
From: bpkroth at wisc.edu (Brian Kroth)
Date: Wed, 27 Feb 2008 16:44:59 -0600
Subject: [Linux-cluster] help reqd. - VMware ESX 3.5 fencing
In-Reply-To: <1204065030.5195.56.camel@localhost>
References: <D566E8CF3538B54D95B925CB69CB4D2A0C6C4D7B@inblr-exch1.eu.uis.unisys.com>
	<20080220153643.BC30020B3F3@smtp3.ldcom.fr>
	<D566E8CF3538B54D95B925CB69CB4D2A0C792136@inblr-exch1.eu.uis.unisys.com>
	<1203640714.5257.127.camel@localhost>
	<D566E8CF3538B54D95B925CB69CB4D2A0CAF2309@inblr-exch1.eu.uis.unisys.com>
	<1204065030.5195.56.camel@localhost>
Message-ID: <20080227224459.GG12021@wisc.edu>

More perl questions:

$ echo -e "server=vmware\nvmname=gfstest3\nusername=fencer\npassword=fencerpw\noperation=reset" | /sbin/fence_vi3

The component 'privilegeList' has already been installed in class -->AuthorizationManager<-- as a HASH(0x1f779834)
  (this time a scalar)
 at /usr/lib/perl5/vendor_perl/5.8.8/i686-linux/Class/MethodMaker.pm line 20
BEGIN failed--compilation aborted at /usr/lib/perl5/site_perl/5.8.8/VMware/VIM25Runtime.pm line 17, <> line 6.
Compilation failed in require at (eval 27) line 3, <> line 6.

Any thoughts?

Thanks,
Brian

chris barry <Christopher.Barry at qlogic.com> 2008-02-26 17:30:
> Read the top section of the script itself. I explain that the install
> script of viperltoolkit does not install the AppUtil directory with the
> rest of itself in your particular site_perl dir.
> 
> do a 
> $ locate site_perl
> to see where on your system has your site_perl director(y|ies), and look
> in each one to find the other vmware module dirs (includes) listed in
> the top of the script. Then copy the AppUtil dir (from the viperltoolkit
> source) into the same site_perl as the rest, and at the same level.
> 
> e.g.
> ...site_perl
>        |-AppUtil
>        |-VMware
>        `-other stuff
> 
> 
> Once the AppUtil dir is present in the right location, it should work
> ok. I had to figure this out the hard way. ;)
> 
> 
> Good Luck,
> -C

-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/x-pkcs7-signature
Size: 2192 bytes
Desc: not available
URL: <http://listman.redhat.com/archives/linux-cluster/attachments/20080227/4182d66e/attachment.bin>

From jpalmae at gmail.com  Wed Feb 27 22:47:55 2008
From: jpalmae at gmail.com (Jorge Palma)
Date: Wed, 27 Feb 2008 19:47:55 -0300
Subject: [Linux-cluster] HA LVM
Message-ID: <5b65f1b10802271447s69f736a2gec497abd1ec06317@mail.gmail.com>

Hello:

I am trying to implement HA LVM in 2 nodes with RHEL 5.1, but I have
the following errors:

in vmdb01:

[root at vmdb01 ~]# rg_test test /etc/cluster/cluster.conf start service testSG
Running in test mode.
Starting testSG...
volume_list=["rootdg", "@vmdb01"]
<notice> Owner of lvmclusterdg/lvmclustervol is not in the cluster
<notice> Stealing lvmclusterdg/lvmclustervol
lvchange  Logical volume "lvmclustervol" changed
<err>    Failed to steal lvmclusterdg/lvmclustervol from lvs         .
Failed to start testSG

in vmfe01:

[root at vmfe01 ~]# rg_test test /etc/cluster/cluster.conf start service testSG
Running in test mode.
Starting testSG...
volume_list=["rootdg", "@vmfe01"]
<notice> Owner of lvmclusterdg/lvmclustervol is not in the cluster
<notice> Stealing lvmclusterdg/lvmclustervol
lvchange  Logical volume "lvmclustervol" changed
<err>    Failed to steal lvmclusterdg/lvmclustervol from lvs         .
Failed to start testSG

In vmdb01 lvm.conf have:

volume_list = [ "rootdg", "@vmdb01" ]

In vmfe01 lvm.cong have:

volume_list = [ "rootdg", "@vmfe01" ]

Will appreciate any ideas

PD: sorry by my english

-- 
Jorge Palma Escobar
Ingeniero de Sistemas
Red Hat Linux Certified Engineer
Certificate N? 804005089418233



From barbos at gmail.com  Thu Feb 28 00:44:15 2008
From: barbos at gmail.com (Alex Kompel)
Date: Wed, 27 Feb 2008 16:44:15 -0800
Subject: [Linux-cluster] Clustering Oracle 10g
In-Reply-To: <b6131fdc0802270645o71ae76f7w63e3c9c018654cf3@mail.gmail.com>
References: <b6131fdc0802270645o71ae76f7w63e3c9c018654cf3@mail.gmail.com>
Message-ID: <3ae027040802271644u6c6e9a0fr26323fd98c6700e7@mail.gmail.com>

On Wed, Feb 27, 2008 at 6:45 AM, Stephen Nelson-Smith
<sanelson at gmail.com> wrote:
> Hi,
>
> I've got a client with a single instance of 10g running on Windows Server 2003.
>
> They've approached me with a view to migrating to Linux, and
> increasing its availability.
>
> What's the current ruling from Oracle about multple licences?  If I
> just had an active-passive system, do I still have to fork out five
> figure numbers for the second, idle Oracle instance?
>
>


http://www.oracle.com/corporate/pricing/sig.pdf

"
Failover ? In this type of recovery, nodes are configured in
"cluster;" the first
installed node acts as a primary node. If the primary node fails, one of the
nodes in the cluster acts as the primary node. In this type of environment,
Oracle permits licensed Oracle Database customers to run the Database on
an unlicensed spare computer for up to a total of ten separate days in any
given calendar year. Any other use requires the environment to be fully
licensed. Same rule applies for Internet Application Server. Additionally, the
same metric must be used when licensing the databases in a failover
environment. See illustration #4.
"



From Santosh.Panigrahi at in.unisys.com  Thu Feb 28 04:07:01 2008
From: Santosh.Panigrahi at in.unisys.com (Panigrahi, Santosh Kumar)
Date: Thu, 28 Feb 2008 09:37:01 +0530
Subject: [Linux-cluster] help reqd. - VMware ESX 3.5 fencing
In-Reply-To: <20080227224459.GG12021@wisc.edu>
References: <D566E8CF3538B54D95B925CB69CB4D2A0C6C4D7B@inblr-exch1.eu.uis.unisys.com><20080220153643.BC30020B3F3@smtp3.ldcom.fr><D566E8CF3538B54D95B925CB69CB4D2A0C792136@inblr-exch1.eu.uis.unisys.com><1203640714.5257.127.camel@localhost><D566E8CF3538B54D95B925CB69CB4D2A0CAF2309@inblr-exch1.eu.uis.unisys.com><1204065030.5195.56.camel@localhost>
	<20080227224459.GG12021@wisc.edu>
Message-ID: <D566E8CF3538B54D95B925CB69CB4D2A0CC3B64C@inblr-exch1.eu.uis.unisys.com>

Hello Brian,

I had also faced the same problem. Just change the line no 45 in your
script. The original line is <use VMware::VIM2Runtime>. Make it to
<use VMware::VIRuntime;> After changing this it worked fine for me and
hopes it will also solve your compilation aborted problem.

Chris,

Thanks for giving your precious time on debugging the problem, which I
had reported without coping the Apputil directory.

Thanks and Regards,
Santosh

-----Original Message-----
From: linux-cluster-bounces at redhat.com
[mailto:linux-cluster-bounces at redhat.com] On Behalf Of Brian Kroth
Sent: Thursday, February 28, 2008 4:15 AM
To: chris barry
Cc: linux clustering
Subject: Re: [Linux-cluster] help reqd. - VMware ESX 3.5 fencing

More perl questions:

$ echo -e
"server=vmware\nvmname=gfstest3\nusername=fencer\npassword=fencerpw\nope
ration=reset" | /sbin/fence_vi3

The component 'privilegeList' has already been installed in class
-->AuthorizationManager<-- as a HASH(0x1f779834)
  (this time a scalar)
 at /usr/lib/perl5/vendor_perl/5.8.8/i686-linux/Class/MethodMaker.pm
line 20
BEGIN failed--compilation aborted at
/usr/lib/perl5/site_perl/5.8.8/VMware/VIM25Runtime.pm line 17, <> line
6.
Compilation failed in require at (eval 27) line 3, <> line 6.

Any thoughts?

Thanks,
Brian

chris barry <Christopher.Barry at qlogic.com> 2008-02-26 17:30:
> Read the top section of the script itself. I explain that the install
> script of viperltoolkit does not install the AppUtil directory with
the
> rest of itself in your particular site_perl dir.
> 
> do a 
> $ locate site_perl
> to see where on your system has your site_perl director(y|ies), and
look
> in each one to find the other vmware module dirs (includes) listed in
> the top of the script. Then copy the AppUtil dir (from the
viperltoolkit
> source) into the same site_perl as the rest, and at the same level.
> 
> e.g.
> ...site_perl
>        |-AppUtil
>        |-VMware
>        `-other stuff
> 
> 
> Once the AppUtil dir is present in the right location, it should work
> ok. I had to figure this out the hard way. ;)
> 
> 
> Good Luck,
> -C

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://listman.redhat.com/archives/linux-cluster/attachments/20080228/d3954562/attachment.htm>

From tsucharz at poczta.onet.pl  Thu Feb 28 08:02:17 2008
From: tsucharz at poczta.onet.pl (Tomasz Sucharzewski)
Date: Thu, 28 Feb 2008 09:02:17 +0100
Subject: [Linux-cluster] High availability xen cluster
In-Reply-To: <4eccbcc3e1e1f2b73b7cd81b3bff73b6@mail.van-schelve.de>
References: <4eccbcc3e1e1f2b73b7cd81b3bff73b6@mail.van-schelve.de>
Message-ID: <20080228090217.14aee755.tsucharz@poczta.onet.pl>

Hi,
I guess this is not only the problem of data being available in both sites. You need true geographic cluster, which is usually different to typical HA cluster in one site. That is why you have that kind of problems. 

>> But my problem is that I see duplicate pv id's in this situatio
Why ?
In both sites you must use only disk from LOCAL storage array and define replication beetwen them. When the application runs in rza site data is beeing replicated  to rzb site. In rzb site disks are in read only mode. In case of disaster you only need to do a failover to rzb site, start to replicate data from rzb->rza and run application in rzb site. That is the theory - but I did not implemented such configuration already. Besides you need a script to do a failover/failback.

Second solution is a gnbd which is fully supported.

Best regards,
Tomek

On Wed, 27 Feb 2008 20:23:18 +0100
van Schelve <public at van-schelve.de> wrote:

> Hello. I don't know if this here is the right list to discuss this but
> maybe someone else with an equal scenario can describe how to best solve
> this.
> 
> I plan to build a cluster environment with 6 or 8 nodes to provide xen
> based virtual maschines. In our environment we have two data centre in
> short rza and rzb. In addition we have a zoned SAN infra structure with a
> Hitachi OPEN-V fabric in each data centre. My nodes are available to access
> disks from both fabrics over multiple pathes. Please look at the following
> multipath listing from one of my nodes: 
> 
> [root at ux072 ~]# multipath -l
> mpath2_rzb (1HITACHI_R450F8D41022) dm-9 HITACHI,OPEN-V
> [size=30G][features=1 queue_if_no_path][hwhandler=0]
> \_ round-robin 0 [prio=0][active]
>  \_ 1:0:0:2 sdd 8:48   [active][undef]
>  \_ 1:0:1:2 sdg 8:96   [active][undef]
>  \_ 2:0:0:2 sdp 8:240  [active][undef]
>  \_ 2:0:1:2 sds 65:32  [active][undef]
> mpath2_rza (1HITACHI_R450F94D1022) dm-12 HITACHI,OPEN-V
> [size=30G][features=1 queue_if_no_path][hwhandler=0]
> \_ round-robin 0 [prio=0][active]
>  \_ 1:0:2:2 sdj 8:144  [active][undef]
>  \_ 1:0:3:2 sdm 8:192  [active][undef]
>  \_ 2:0:2:2 sdv 65:80  [active][undef]
>  \_ 2:0:3:2 sdy 65:128 [active][undef]
> mpath0_rzb (1HITACHI_R450F8D41020) dm-7 HITACHI,OPEN-V
> [size=30G][features=1 queue_if_no_path][hwhandler=0]
> \_ round-robin 0 [prio=0][active]
>  \_ 1:0:0:0 sdb 8:16   [active][undef]
>  \_ 1:0:1:0 sde 8:64   [active][undef]
>  \_ 2:0:0:0 sdn 8:208  [active][undef]
>  \_ 2:0:1:0 sdq 65:0   [active][undef]
> mpath0_rza (1HITACHI_R450F94D1020) dm-10 HITACHI,OPEN-V
> [size=30G][features=1 queue_if_no_path][hwhandler=0]
> \_ round-robin 0 [prio=0][active]
>  \_ 1:0:2:0 sdh 8:112  [active][undef]
>  \_ 1:0:3:0 sdk 8:160  [active][undef]
>  \_ 2:0:2:0 sdt 65:48  [active][undef]
>  \_ 2:0:3:0 sdw 65:96  [active][undef]
> mpath1_rzb (1HITACHI_R450F8D41021) dm-8 HITACHI,OPEN-V
> [size=30G][features=1 queue_if_no_path][hwhandler=0]
> \_ round-robin 0 [prio=0][active]
>  \_ 1:0:0:1 sdc 8:32   [active][undef]
>  \_ 1:0:1:1 sdf 8:80   [active][undef]
>  \_ 2:0:0:1 sdo 8:224  [active][undef]
>  \_ 2:0:1:1 sdr 65:16  [active][undef]
> mpath1_rza (1HITACHI_R450F94D1021) dm-11 HITACHI,OPEN-V
> [size=30G][features=1 queue_if_no_path][hwhandler=0]
> \_ round-robin 0 [prio=0][active]
>  \_ 1:0:2:1 sdi 8:128  [active][undef]
>  \_ 1:0:3:1 sdl 8:176  [active][undef]
>  \_ 2:0:2:1 sdu 65:64  [active][undef]
>  \_ 2:0:3:1 sdx 65:112 [active][undef]
> 
> There are three disks in each data centre. Currently I only use the disks
> in rza.
> 
> At the moment I'm testing with a two node cluster. The virtual machines are
> on SAN disks and I can live migrate from one node to the other one. But
> what I have to cover is the disaster. What happens when the fabric in rza
> crashes? My virtual maschines are unavailable. What I'm thinking about is a
> hardware based
> mirroring between the both fabrics and break up the mirror when the
> disaster happens or we need to power off the storage for maintenance. But
> my problem is that I see duplicate pv id's in this situation. I cannot
> mirror based on lvm because it is too slow.
> 
> Thank you for your ideas.
> 
> -- Hans-Gerd van Schelve
> 
> --
> Linux-cluster mailing list
> Linux-cluster at redhat.com
> https://www.redhat.com/mailman/listinfo/linux-cluster


-- 
Tomasz Sucharzewski <tsucharz at poczta.onet.pl>



From qqlka at nask.pl  Thu Feb 28 08:39:03 2008
From: qqlka at nask.pl (=?iso-8859-2?Q?Agnieszka_Kuka=B3owicz?=)
Date: Thu, 28 Feb 2008 09:39:03 +0100
Subject: [Linux-cluster] Clustat shows wrong service status
In-Reply-To: <1204150957.13733.3.camel@ayanami.boston.devel.redhat.com>
Message-ID: <019b01c879e5$5f8a4cf0$0777b5c2@gda07ak>



> > Clustat shows something like that:
> >
> > Member Name                        ID   Status
> >   ------ ----                        ---- ------
> >   w2.local					1 Offline
> >   w1.local					2 Online, Local,
> > rgmanager
> 
> One of two things is likely:
> 
> (a) The node has not been fenced yet, or


I've checked fencing. I have 2 methods of fencing: Apc Power Switch, and
manual. This is from my log file (manual fencing):

Feb 28 07:50:21 w1 kernel: dlm: connecting to 1
Feb 28 07:50:23 w1 openais[11475]: [TOTEM] The token was lost in the
OPERATIONAL state.
Feb 28 07:50:28 w1 openais[11475]: [CLM  ] CLM CONFIGURATION CHANGE
Feb 28 07:50:28 w1 openais[11475]: [CLM  ] New Configuration:
Feb 28 07:50:28 w1 kernel: dlm: closing connection to node 1
Feb 28 07:50:28 w1 fenced[11494]: w2.local not a cluster member after 0
sec post_fail_delay
Feb 28 07:50:28 w1 openais[11475]: [CLM  ]      r(0) ip(10.0.200.1)
Feb 28 07:50:28 w1 fenced[11494]: fencing node "w2.local"
Feb 28 07:50:28 w1 openais[11475]: [CLM  ] Members Left:
Feb 28 07:50:28 w1 openais[11475]: [CLM  ]      r(0) ip(10.0.200.2)
Feb 28 07:50:28 w1 fence_manual: Node w2.local.polska.pl needs to be
reset before recovery can procede.  Waiting for w2.local to rejoin the
cluster ....
I've rebooted the node manually and done "fence_ack_manual". The log
shows:

Feb 28 07:52:01 w1 fenced[11494]: fence "w2.local.polska.pl" success

But clustat is still wrong.

[root at w1 ~]group_tool dump fence
1204181252 start default 151 members 1 2
1204181252 do_recovery stop 136 start 151 finish 136
1204181252 finish default 151
1204181428 stop default
1204181428 start default 166 members 2
1204181428 do_recovery stop 151 start 166 finish 151
1204181428 add node 1 to list 1
1204181428 node "w2.local" not a cman member, cn 1
1204181428 node "w2.local" has not been fenced
1204181428 fencing node w2.local.polska.pl
1204181526 finish default 166

[root at w1 ~]# cman_tool nodes -f
Node  Sts   Inc   Joined               Name
   1   X    464                        w2.local
       Last fenced:   2008-02-28 07:52:01 by manual_fence_w2
   2   M    420   2008-02-27 11:57:10  w1.local
       Last fenced:   2008-02-27 12:23:17 by apc_power_switch

I did the same with Apc Power Switch and still have the problem.


> (b) you did the manual override trick and hit this bug:
>     https://bugzilla.redhat.com/show_bug.cgi?id=435189

The steps to reproduce the bug were:
1. start cman, clvmd, gfs, rgmanager w1.local and w2.local
2. power off w2.local
3. on w1.local do "clustat"

And I don't have situation that cman_tool nodes says: 
" Last fenced   2008-02-27 15:24:16 by override"

Agnieszka Kukalowicz



From qqlka at nask.pl  Thu Feb 28 11:32:38 2008
From: qqlka at nask.pl (=?iso-8859-2?Q?Agnieszka_Kuka=B3owicz?=)
Date: Thu, 28 Feb 2008 12:32:38 +0100
Subject: [Linux-cluster] Clustat shows wrong service status
In-Reply-To: <019b01c879e5$5f8a4cf0$0777b5c2@gda07ak>
Message-ID: <01b101c879fd$9f71eef0$0777b5c2@gda07ak>

> 
> And I don't have situation that cman_tool nodes says:
> " Last fenced   2008-02-27 15:24:16 by override"
> 

I did more tests to find the cause of the problem.
I found that clustat has problem with "restricted" failover domain.
I tested 2 examples of my configuration: 

1. failover domain is "restricted"

<rm>
  <failoverdomains>
    <failoverdomain name="VM_w1_failover" ordered="0" restricted="1">
        <failoverdomainnode name="w1.local" priority="1"/>
    </failoverdomain>
    <failoverdomain name="VM_w2_failover" ordered="0" restricted="1">
        <failoverdomainnode name="w2.local" priority="1"/>

    </failoverdomain>
  </failoverdomains>
  <resources/>
  <vm autostart="1" domain="VM_w1_failover" exclusive="0"
name="VM_Work11_RHEL51" path="/virts/w11" recovery="restart"/>
  <vm autostart="1" domain="VM_w1_failover" exclusive="0"
name="VM_Work12_RHEL51" path="/virts/w12" recovery="restart"/>
  <vm autostart="0" domain="VM_w1_failover" exclusive="0"
name="VM_Work13_RHEL51" path="/virts/w13" recovery="disable"/>
  <vm autostart="1" domain="VM_w2_failover" exclusive="0"
name="VM_Work21_RHEL51" path="/virts/w21" recovery="restart"/>
  <vm autostart="0" domain="VM_w2_failover" exclusive="0"
name="VM_Work22_RHEL51" path="/virts/w22" recovery="disable"/>
  <vm autostart="0" domain="VM_w2_failover" exclusive="0"
name="VM_Work23_RHEL51" path="/virts/w23" recovery="disable"/>
        </rm>

Member Status: Quorate

  Member Name                        ID   Status
  ------ ----                        ---- ------
  w2.local		                    1 Online, Local, rgmanager
  w1.local		                    2 Online, rgmanager

  Service Name         Owner (Last)                   State
  ------- ----         ----- ------                   -----
  vm:VM_Work11_RHEL51  w1.local				started
  vm:VM_Work12_RHEL51  w1.local		            started
  vm:VM_Work13_RHEL51  (none)                         disabled
  vm:VM_Work21_RHEL51  w2.local		            started
  vm:VM_Work22_RHEL51  (none)                         disabled
  vm:VM_Work23_RHEL51  (none)                         disabled

After power off node w2.local and fencing "w2.local" by "w1.local"
clustat still shows the service vm:VM_Work21_RHEL51 is started on
w2.local

Member Status: Quorate

  Member Name                        ID   Status
  ------ ----                        ---- ------
  w2.local.polska.pl                    1 Offline
  w1.local.polska.pl                    2 Online, Local, rgmanager

  Service Name         Owner (Last)                   State
  ------- ----         ----- ------                   -----
  vm:VM_Work11_RHEL51  w1.local.polska.pl             started
  vm:VM_Work12_RHEL51  w1.local.polska.pl             started
  vm:VM_Work13_RHEL51  (none)                         disabled
  vm:VM_Work21_RHEL51  w2.local.polska.pl             started
  vm:VM_Work22_RHEL51  (none)                         disabled
  vm:VM_Work23_RHEL51  (none)                         disabled

2. failover domain is not restreicted
<failoverdomains>
   <failoverdomain name="VM_w1_failover" ordered="0" restricted="0">
	   <failoverdomainnode name="w1.local" priority="1"/>
</failoverdomain>
   <failoverdomain name="VM_w2_failover" ordered="0" restricted="0">
      <failoverdomainnode name="w2.local" priority="1"/>
   </failoverdomain>
</failoverdomains>

Clustat before shutting down w2.local:

[root at w1 ~]# clustat
Member Status: Quorate

  Member Name                        ID   Status
  ------ ----                        ---- ------
  w2.local.polska.pl                    1 Online
  w1.local.polska.pl                    2 Online, Local, rgmanager

  Service Name         Owner (Last)                   State
  ------- ----         ----- ------                   -----
  vm:VM_Work11_RHEL51  w1.local.polska.pl             started
  vm:VM_Work12_RHEL51  w1.local.polska.pl             started
  vm:VM_Work13_RHEL51  (none)                         disabled
  vm:VM_Work21_RHEL51  w2.local.polska.pl             started
  vm:VM_Work22_RHEL51  (none)                         disabled
  vm:VM_Work23_RHEL51  (none)                         disabled

After shutting down w2.local rgmanager migrate service
vm:VM_Work21_RHEL51  to w1.local and clustat shows correct states.

[root at w1 ~]# clustat
Member Status: Quorate

  Member Name                        ID   Status
  ------ ----                        ---- ------
  w2.local.polska.pl                    1 Offline
  w1.local.polska.pl                    2 Online, Local, rgmanager

  Service Name         Owner (Last)                   State
  ------- ----         ----- ------                   -----
  vm:VM_Work11_RHEL51  w1.local.polska.pl             started
  vm:VM_Work12_RHEL51  w1.local.polska.pl             started
  vm:VM_Work13_RHEL51  (none)                         disabled
  vm:VM_Work21_RHEL51  w1.local.polska.pl             started
  vm:VM_Work22_RHEL51  (none)                         disabled
  vm:VM_Work23_RHEL51  (none)                         disabled

I'm not sure but I think there is something wrong with rgmanager/clustat
wnen services are configured with restricted failover domain. 

Cheers 
Agnieszka Kukalowicz



From bpkroth at wisc.edu  Thu Feb 28 13:29:40 2008
From: bpkroth at wisc.edu (Brian Kroth)
Date: Thu, 28 Feb 2008 07:29:40 -0600
Subject: [Linux-cluster] help reqd. - VMware ESX 3.5 fencing
In-Reply-To: <D566E8CF3538B54D95B925CB69CB4D2A0CC3B64C@inblr-exch1.eu.uis.unisys.com>
References: <D566E8CF3538B54D95B925CB69CB4D2A0C6C4D7B@inblr-exch1.eu.uis.unisys.com>
	<20080220153643.BC30020B3F3@smtp3.ldcom.fr>
	<D566E8CF3538B54D95B925CB69CB4D2A0C792136@inblr-exch1.eu.uis.unisys.com>
	<1203640714.5257.127.camel@localhost>
	<D566E8CF3538B54D95B925CB69CB4D2A0CAF2309@inblr-exch1.eu.uis.unisys.com>
	<1204065030.5195.56.camel@localhost> <20080227224459.GG12021@wisc.edu>
	<D566E8CF3538B54D95B925CB69CB4D2A0CC3B64C@inblr-exch1.eu.uis.unisys.com>
Message-ID: <20080228132940.GA1087@wisc.edu>

That was it.  

Thanks,
Brian

Panigrahi, Santosh Kumar <Santosh.Panigrahi at in.unisys.com> 2008-02-28 09:37:
>    Hello Brian,
> 
>    I had also faced the same problem. Just change the line no 45 in your
>    script. The original line is <use VMware::VIM2Runtime>. Make it to
> 
>    <use VMware::VIRuntime;> After changing this it worked fine for me and
>    hopes it will also solve your compilation aborted problem.
> 
>    Chris,
> 
>    Thanks for giving your precious time on debugging the problem, which I
>    had reported without coping the Apputil directory.
> 
>    Thanks and Regards,
> 
>    Santosh
> 
>    -----Original Message-----
>    From: linux-cluster-bounces at redhat.com
>    [[1]mailto:linux-cluster-bounces at redhat.com] On Behalf Of Brian Kroth
>    Sent: Thursday, February 28, 2008 4:15 AM
>    To: chris barry
>    Cc: linux clustering
>    Subject: Re: [Linux-cluster] help reqd. - VMware ESX 3.5 fencing
> 
>    More perl questions:
> 
>    $ echo -e
>    "server=vmware\nvmname=gfstest3\nusername=fencer\npassword=fencerpw\nop
>    eration=reset" | /sbin/fence_vi3
> 
>    The component 'privilegeList' has already been installed in class
>    -->AuthorizationManager<-- as a HASH(0x1f779834)
> 
>      (this time a scalar)
> 
>     at /usr/lib/perl5/vendor_perl/5.8.8/i686-linux/Class/MethodMaker.pm
>    line 20
> 
>    BEGIN failed--compilation aborted at
>    /usr/lib/perl5/site_perl/5.8.8/VMware/VIM25Runtime.pm line 17, <> line
>    6.
> 
>    Compilation failed in require at (eval 27) line 3, <> line 6.
> 
>    Any thoughts?
> 
>    Thanks,
> 
>    Brian
> 
>    chris barry <Christopher.Barry at qlogic.com> 2008-02-26 17:30:
> 
>    > Read the top section of the script itself. I explain that the install
> 
>    > script of viperltoolkit does not install the AppUtil directory with
>    the
> 
>    > rest of itself in your particular site_perl dir.
> 
>    >
> 
>    > do a
> 
>    > $ locate site_perl
> 
>    > to see where on your system has your site_perl director(y|ies), and
>    look
> 
>    > in each one to find the other vmware module dirs (includes) listed in
> 
>    > the top of the script. Then copy the AppUtil dir (from the
>    viperltoolkit
> 
>    > source) into the same site_perl as the rest, and at the same level.
> 
>    >
> 
>    > e.g.
> 
>    > ...site_perl
> 
>    >        |-AppUtil
> 
>    >        |-VMware
> 
>    >        `-other stuff
> 
>    >
> 
>    >
> 
>    > Once the AppUtil dir is present in the right location, it should work
> 
>    > ok. I had to figure this out the hard way. ;)
> 
>    >
> 
>    >
> 
>    > Good Luck,
> 
>    > -C
> 
> References
> 
>    1. mailto:linux-cluster-bounces at redhat.com
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/x-pkcs7-signature
Size: 2192 bytes
Desc: not available
URL: <http://listman.redhat.com/archives/linux-cluster/attachments/20080228/115b3a76/attachment.bin>

From christopher.barry at qlogic.com  Thu Feb 28 13:50:17 2008
From: christopher.barry at qlogic.com (Christopher Barry)
Date: Thu, 28 Feb 2008 07:50:17 -0600
Subject: [Linux-cluster] help reqd. - VMware ESX 3.5 fencing
References: <D566E8CF3538B54D95B925CB69CB4D2A0C6C4D7B@inblr-exch1.eu.uis.unisys.com><20080220153643.BC30020B3F3@smtp3.ldcom.fr><D566E8CF3538B54D95B925CB69CB4D2A0C792136@inblr-exch1.eu.uis.unisys.com><1203640714.5257.127.camel@localhost><D566E8CF3538B54D95B925CB69CB4D2A0CAF2309@inblr-exch1.eu.uis.unisys.com><1204065030.5195.56.camel@localhost>
	<20080227224459.GG12021@wisc.edu><D566E8CF3538B54D95B925CB69CB4D2A0CC3B64C@inblr-exch1.eu.uis.unisys.com>
	<20080228132940.GA1087@wisc.edu>
Message-ID: <D158540CCC0AB54C8FD4818F823CCB2453AE49@EPEXCH1.qlogic.org>


What version of redhat are you using?

Are you saying that instead of copying the AppUtil directory post-install of the viperltoolkit, you simply changed the use line to use VMware::VIRuntime;?

Regards,
-C

-----Original Message-----
From: linux-cluster-bounces at redhat.com on behalf of Brian Kroth
Sent: Thu 2/28/2008 8:29 AM
To: Panigrahi, Santosh Kumar
Cc: linux clustering
Subject: Re: [Linux-cluster] help reqd. - VMware ESX 3.5 fencing
 
That was it.  

Thanks,
Brian

Panigrahi, Santosh Kumar <Santosh.Panigrahi at in.unisys.com> 2008-02-28 09:37:
>    Hello Brian,
> 
>    I had also faced the same problem. Just change the line no 45 in your
>    script. The original line is <use VMware::VIM2Runtime>. Make it to
> 
>    <use VMware::VIRuntime;> After changing this it worked fine for me and
>    hopes it will also solve your compilation aborted problem.
> 
>    Chris,
> 
>    Thanks for giving your precious time on debugging the problem, which I
>    had reported without coping the Apputil directory.
> 
>    Thanks and Regards,
> 
>    Santosh
> 
>    -----Original Message-----
>    From: linux-cluster-bounces at redhat.com
>    [[1]mailto:linux-cluster-bounces at redhat.com] On Behalf Of Brian Kroth
>    Sent: Thursday, February 28, 2008 4:15 AM
>    To: chris barry
>    Cc: linux clustering
>    Subject: Re: [Linux-cluster] help reqd. - VMware ESX 3.5 fencing
> 
>    More perl questions:
> 
>    $ echo -e
>    "server=vmware\nvmname=gfstest3\nusername=fencer\npassword=fencerpw\nop
>    eration=reset" | /sbin/fence_vi3
> 
>    The component 'privilegeList' has already been installed in class
>    -->AuthorizationManager<-- as a HASH(0x1f779834)
> 
>      (this time a scalar)
> 
>     at /usr/lib/perl5/vendor_perl/5.8.8/i686-linux/Class/MethodMaker.pm
>    line 20
> 
>    BEGIN failed--compilation aborted at
>    /usr/lib/perl5/site_perl/5.8.8/VMware/VIM25Runtime.pm line 17, <> line
>    6.
> 
>    Compilation failed in require at (eval 27) line 3, <> line 6.
> 
>    Any thoughts?
> 
>    Thanks,
> 
>    Brian
> 
>    chris barry <Christopher.Barry at qlogic.com> 2008-02-26 17:30:
> 
>    > Read the top section of the script itself. I explain that the install
> 
>    > script of viperltoolkit does not install the AppUtil directory with
>    the
> 
>    > rest of itself in your particular site_perl dir.
> 
>    >
> 
>    > do a
> 
>    > $ locate site_perl
> 
>    > to see where on your system has your site_perl director(y|ies), and
>    look
> 
>    > in each one to find the other vmware module dirs (includes) listed in
> 
>    > the top of the script. Then copy the AppUtil dir (from the
>    viperltoolkit
> 
>    > source) into the same site_perl as the rest, and at the same level.
> 
>    >
> 
>    > e.g.
> 
>    > ...site_perl
> 
>    >        |-AppUtil
> 
>    >        |-VMware
> 
>    >        `-other stuff
> 
>    >
> 
>    >
> 
>    > Once the AppUtil dir is present in the right location, it should work
> 
>    > ok. I had to figure this out the hard way. ;)
> 
>    >
> 
>    >
> 
>    > Good Luck,
> 
>    > -C
> 
> References
> 
>    1. mailto:linux-cluster-bounces at redhat.com




-------------- next part --------------
A non-text attachment was scrubbed...
Name: winmail.dat
Type: application/ms-tnef
Size: 4588 bytes
Desc: not available
URL: <http://listman.redhat.com/archives/linux-cluster/attachments/20080228/2bacd077/attachment.bin>

From Santosh.Panigrahi at in.unisys.com  Thu Feb 28 14:17:26 2008
From: Santosh.Panigrahi at in.unisys.com (Panigrahi, Santosh Kumar)
Date: Thu, 28 Feb 2008 19:47:26 +0530
Subject: [Linux-cluster] help reqd. - VMware ESX 3.5 fencing
In-Reply-To: <D158540CCC0AB54C8FD4818F823CCB2453AE49@EPEXCH1.qlogic.org>
References: <D566E8CF3538B54D95B925CB69CB4D2A0C6C4D7B@inblr-exch1.eu.uis.unisys.com><20080220153643.BC30020B3F3@smtp3.ldcom.fr><D566E8CF3538B54D95B925CB69CB4D2A0C792136@inblr-exch1.eu.uis.unisys.com><1203640714.5257.127.camel@localhost><D566E8CF3538B54D95B925CB69CB4D2A0CAF2309@inblr-exch1.eu.uis.unisys.com><1204065030.5195.56.camel@localhost>
	<20080227224459.GG12021@wisc.edu><D566E8CF3538B54D95B925CB69CB4D2A0CC3B64C@inblr-exch1.eu.uis.unisys.com>
	<20080228132940.GA1087@wisc.edu>
	<D158540CCC0AB54C8FD4818F823CCB2453AE49@EPEXCH1.qlogic.org>
Message-ID: <D566E8CF3538B54D95B925CB69CB4D2A0CD29E08@inblr-exch1.eu.uis.unisys.com>


No Chrish, I have copied Apputil directory from viperltoolkit directory
(/tmp/viperltoolkit/apps) to my site perl directory
(/usr/lib/perl5/site_perl/5.8.8) as per your suggestion. But after that
on running your fencing script, I got the same error, as reported by
Brian. Then I changed the package to VMware::VIruntime at line 45 and
the script worked fine without giving any compilation problem.

I don't know how u got the impression from the below mail chain that we
have executed the script successfully without coping the Apputil
directory to site_perl directory. 

Thanks and Regard,
Santosh

 
-----Original Message-----
From: linux-cluster-bounces at redhat.com
[mailto:linux-cluster-bounces at redhat.com] On Behalf Of Christopher Barry
Sent: Thursday, February 28, 2008 7:20 PM
To: linux clustering
Subject: RE: [Linux-cluster] help reqd. - VMware ESX 3.5 fencing


What version of redhat are you using?

Are you saying that instead of copying the AppUtil directory
post-install of the viperltoolkit, you simply changed the use line to
use VMware::VIRuntime;?

Regards,
-C

-----Original Message-----
From: linux-cluster-bounces at redhat.com on behalf of Brian Kroth
Sent: Thu 2/28/2008 8:29 AM
To: Panigrahi, Santosh Kumar
Cc: linux clustering
Subject: Re: [Linux-cluster] help reqd. - VMware ESX 3.5 fencing
 
That was it.  

Thanks,
Brian

Panigrahi, Santosh Kumar <Santosh.Panigrahi at in.unisys.com> 2008-02-28
09:37:
>    Hello Brian,
> 
>    I had also faced the same problem. Just change the line no 45 in
your
>    script. The original line is <use VMware::VIM2Runtime>. Make it to
> 
>    <use VMware::VIRuntime;> After changing this it worked fine for me
and
>    hopes it will also solve your compilation aborted problem.
> 
>    Chris,
> 
>    Thanks for giving your precious time on debugging the problem,
which I
>    had reported without coping the Apputil directory.
> 
>    Thanks and Regards,
> 
>    Santosh
> 
>    -----Original Message-----
>    From: linux-cluster-bounces at redhat.com
>    [[1]mailto:linux-cluster-bounces at redhat.com] On Behalf Of Brian
Kroth
>    Sent: Thursday, February 28, 2008 4:15 AM
>    To: chris barry
>    Cc: linux clustering
>    Subject: Re: [Linux-cluster] help reqd. - VMware ESX 3.5 fencing
> 
>    More perl questions:
> 
>    $ echo -e
>
"server=vmware\nvmname=gfstest3\nusername=fencer\npassword=fencerpw\nop
>    eration=reset" | /sbin/fence_vi3
> 
>    The component 'privilegeList' has already been installed in class
>    -->AuthorizationManager<-- as a HASH(0x1f779834)
> 
>      (this time a scalar)
> 
>     at
/usr/lib/perl5/vendor_perl/5.8.8/i686-linux/Class/MethodMaker.pm
>    line 20
> 
>    BEGIN failed--compilation aborted at
>    /usr/lib/perl5/site_perl/5.8.8/VMware/VIM25Runtime.pm line 17, <>
line
>    6.
> 
>    Compilation failed in require at (eval 27) line 3, <> line 6.
> 
>    Any thoughts?
> 
>    Thanks,
> 
>    Brian
> 
>    chris barry <Christopher.Barry at qlogic.com> 2008-02-26 17:30:
> 
>    > Read the top section of the script itself. I explain that the
install
> 
>    > script of viperltoolkit does not install the AppUtil directory
with
>    the
> 
>    > rest of itself in your particular site_perl dir.
> 
>    >
> 
>    > do a
> 
>    > $ locate site_perl
> 
>    > to see where on your system has your site_perl director(y|ies),
and
>    look
> 
>    > in each one to find the other vmware module dirs (includes)
listed in
> 
>    > the top of the script. Then copy the AppUtil dir (from the
>    viperltoolkit
> 
>    > source) into the same site_perl as the rest, and at the same
level.
> 
>    >
> 
>    > e.g.
> 
>    > ...site_perl
> 
>    >        |-AppUtil
> 
>    >        |-VMware
> 
>    >        `-other stuff
> 
>    >
> 
>    >
> 
>    > Once the AppUtil dir is present in the right location, it should
work
> 
>    > ok. I had to figure this out the hard way. ;)
> 
>    >
> 
>    >
> 
>    > Good Luck,
> 
>    > -C
> 
> References
> 
>    1. mailto:linux-cluster-bounces at redhat.com







From Christopher.Barry at qlogic.com  Thu Feb 28 14:51:27 2008
From: Christopher.Barry at qlogic.com (chris barry)
Date: Thu, 28 Feb 2008 09:51:27 -0500
Subject: [Linux-cluster] help reqd. - VMware ESX 3.5 fencing
In-Reply-To: <D566E8CF3538B54D95B925CB69CB4D2A0CD29E08@inblr-exch1.eu.uis.unisys.com>
References: <D566E8CF3538B54D95B925CB69CB4D2A0C6C4D7B@inblr-exch1.eu.uis.unisys.com>
	<20080220153643.BC30020B3F3@smtp3.ldcom.fr>
	<D566E8CF3538B54D95B925CB69CB4D2A0C792136@inblr-exch1.eu.uis.unisys.com>
	<1203640714.5257.127.camel@localhost>
	<D566E8CF3538B54D95B925CB69CB4D2A0CAF2309@inblr-exch1.eu.uis.unisys.com>
	<1204065030.5195.56.camel@localhost> <20080227224459.GG12021@wisc.edu>
	<D566E8CF3538B54D95B925CB69CB4D2A0CC3B64C@inblr-exch1.eu.uis.unisys.com>
	<20080228132940.GA1087@wisc.edu>
	<D158540CCC0AB54C8FD4818F823CCB2453AE49@EPEXCH1.qlogic.org>
	<D566E8CF3538B54D95B925CB69CB4D2A0CD29E08@inblr-exch1.eu.uis.unisys.com>
Message-ID: <1204210288.5562.42.camel@localhost>


I'm running RHEL4u5 VMs and VI3.02, and I did not encounter this error.
What versions are you using? VI3.5, and what VM distro?

Ok, what I am getting at is what made you have to change that line!

;)

On Thu, 2008-02-28 at 19:47 +0530, Panigrahi, Santosh Kumar wrote:
> No Chrish, I have copied Apputil directory from viperltoolkit directory
> (/tmp/viperltoolkit/apps) to my site perl directory
> (/usr/lib/perl5/site_perl/5.8.8) as per your suggestion. But after that
> on running your fencing script, I got the same error, as reported by
> Brian. Then I changed the package to VMware::VIruntime at line 45 and
> the script worked fine without giving any compilation problem.
> 
> I don't know how u got the impression from the below mail chain that we
> have executed the script successfully without coping the Apputil
> directory to site_perl directory. 
> 
> Thanks and Regard,
> Santosh
> 
>  
> -----Original Message-----
> From: linux-cluster-bounces at redhat.com
> [mailto:linux-cluster-bounces at redhat.com] On Behalf Of Christopher Barry
> Sent: Thursday, February 28, 2008 7:20 PM
> To: linux clustering
> Subject: RE: [Linux-cluster] help reqd. - VMware ESX 3.5 fencing
> 
> 
> What version of redhat are you using?
> 
> Are you saying that instead of copying the AppUtil directory
> post-install of the viperltoolkit, you simply changed the use line to
> use VMware::VIRuntime;?
> 
> Regards,
> -C
> 
> -----Original Message-----
> From: linux-cluster-bounces at redhat.com on behalf of Brian Kroth
> Sent: Thu 2/28/2008 8:29 AM
> To: Panigrahi, Santosh Kumar
> Cc: linux clustering
> Subject: Re: [Linux-cluster] help reqd. - VMware ESX 3.5 fencing
>  
> That was it.  
> 
> Thanks,
> Brian
> 
> Panigrahi, Santosh Kumar <Santosh.Panigrahi at in.unisys.com> 2008-02-28
> 09:37:
> >    Hello Brian,
> > 
> >    I had also faced the same problem. Just change the line no 45 in
> your
> >    script. The original line is <use VMware::VIM2Runtime>. Make it to
> > 
> >    <use VMware::VIRuntime;> After changing this it worked fine for me
> and
> >    hopes it will also solve your compilation aborted problem.
> > 
> >    Chris,
> > 
> >    Thanks for giving your precious time on debugging the problem,
> which I
> >    had reported without coping the Apputil directory.
> > 
> >    Thanks and Regards,
> > 
> >    Santosh
> > 
> >    -----Original Message-----
> >    From: linux-cluster-bounces at redhat.com
> >    [[1]mailto:linux-cluster-bounces at redhat.com] On Behalf Of Brian
> Kroth
> >    Sent: Thursday, February 28, 2008 4:15 AM
> >    To: chris barry
> >    Cc: linux clustering
> >    Subject: Re: [Linux-cluster] help reqd. - VMware ESX 3.5 fencing
> > 
> >    More perl questions:
> > 
> >    $ echo -e
> >
> "server=vmware\nvmname=gfstest3\nusername=fencer\npassword=fencerpw\nop
> >    eration=reset" | /sbin/fence_vi3
> > 
> >    The component 'privilegeList' has already been installed in class
> >    -->AuthorizationManager<-- as a HASH(0x1f779834)
> > 
> >      (this time a scalar)
> > 
> >     at
> /usr/lib/perl5/vendor_perl/5.8.8/i686-linux/Class/MethodMaker.pm
> >    line 20
> > 
> >    BEGIN failed--compilation aborted at
> >    /usr/lib/perl5/site_perl/5.8.8/VMware/VIM25Runtime.pm line 17, <>
> line
> >    6.
> > 
> >    Compilation failed in require at (eval 27) line 3, <> line 6.
> > 
> >    Any thoughts?
> > 
> >    Thanks,
> > 
> >    Brian
> > 
> >    chris barry <Christopher.Barry at qlogic.com> 2008-02-26 17:30:
> > 
> >    > Read the top section of the script itself. I explain that the
> install
> > 
> >    > script of viperltoolkit does not install the AppUtil directory
> with
> >    the
> > 
> >    > rest of itself in your particular site_perl dir.
> > 
> >    >
> > 
> >    > do a
> > 
> >    > $ locate site_perl
> > 
> >    > to see where on your system has your site_perl director(y|ies),
> and
> >    look
> > 
> >    > in each one to find the other vmware module dirs (includes)
> listed in
> > 
> >    > the top of the script. Then copy the AppUtil dir (from the
> >    viperltoolkit
> > 
> >    > source) into the same site_perl as the rest, and at the same
> level.
> > 
> >    >
> > 
> >    > e.g.
> > 
> >    > ...site_perl
> > 
> >    >        |-AppUtil
> > 
> >    >        |-VMware
> > 
> >    >        `-other stuff
> > 
> >    >
> > 
> >    >
> > 
> >    > Once the AppUtil dir is present in the right location, it should
> work
> > 
> >    > ok. I had to figure this out the hard way. ;)
> > 
> >    >
> > 
> >    >
> > 
> >    > Good Luck,
> > 
> >    > -C
> > 
> > References
> > 
> >    1. mailto:linux-cluster-bounces at redhat.com
> 
> 
> 
> 
> 
> --
> Linux-cluster mailing list
> Linux-cluster at redhat.com
> https://www.redhat.com/mailman/listinfo/linux-cluster



From bpkroth at wisc.edu  Thu Feb 28 15:06:16 2008
From: bpkroth at wisc.edu (Brian Kroth)
Date: Thu, 28 Feb 2008 09:06:16 -0600
Subject: [Linux-cluster] help reqd. - VMware ESX 3.5 fencing
In-Reply-To: <1204210288.5562.42.camel@localhost>
References: <D566E8CF3538B54D95B925CB69CB4D2A0C792136@inblr-exch1.eu.uis.unisys.com>
	<1203640714.5257.127.camel@localhost>
	<D566E8CF3538B54D95B925CB69CB4D2A0CAF2309@inblr-exch1.eu.uis.unisys.com>
	<1204065030.5195.56.camel@localhost> <20080227224459.GG12021@wisc.edu>
	<D566E8CF3538B54D95B925CB69CB4D2A0CC3B64C@inblr-exch1.eu.uis.unisys.com>
	<20080228132940.GA1087@wisc.edu>
	<D158540CCC0AB54C8FD4818F823CCB2453AE49@EPEXCH1.qlogic.org>
	<D566E8CF3538B54D95B925CB69CB4D2A0CD29E08@inblr-exch1.eu.uis.unisys.com>
	<1204210288.5562.42.camel@localhost>
Message-ID: <20080228150616.GB10586@wisc.edu>

I'm running Gentoo, but that shouldn't make a difference.  Here's what I
did:

- install various support perl packages as listed in the VMWare perl
  tooklit 1.5 source install instructions.  This is the one from ESX
  3.5.

- install VMware-VIPerl-Toolkit-1.5.0-source.tar.gz

- copy the AppUtil directory as listed in the source code

- run the test cmd I posted earlier "echo stuff | fence_vi3"

I think the disconnect is probably due to differing vipertoolkit
versions.

I had also tried switching VIM2Runtime.pm with VIM25Runtime.pm, but to
no avail.  Switching that line to VIRuntime is what did it.

Brian

chris barry <Christopher.Barry at qlogic.com> 2008-02-28 09:51:
> 
> I'm running RHEL4u5 VMs and VI3.02, and I did not encounter this error.
> What versions are you using? VI3.5, and what VM distro?
> 
> Ok, what I am getting at is what made you have to change that line!
> 
> ;)
> 
> On Thu, 2008-02-28 at 19:47 +0530, Panigrahi, Santosh Kumar wrote:
> > No Chrish, I have copied Apputil directory from viperltoolkit directory
> > (/tmp/viperltoolkit/apps) to my site perl directory
> > (/usr/lib/perl5/site_perl/5.8.8) as per your suggestion. But after that
> > on running your fencing script, I got the same error, as reported by
> > Brian. Then I changed the package to VMware::VIruntime at line 45 and
> > the script worked fine without giving any compilation problem.
> > 
> > I don't know how u got the impression from the below mail chain that we
> > have executed the script successfully without coping the Apputil
> > directory to site_perl directory. 
> > 
> > Thanks and Regard,
> > Santosh
> > 
> >  
> > -----Original Message-----
> > From: linux-cluster-bounces at redhat.com
> > [mailto:linux-cluster-bounces at redhat.com] On Behalf Of Christopher Barry
> > Sent: Thursday, February 28, 2008 7:20 PM
> > To: linux clustering
> > Subject: RE: [Linux-cluster] help reqd. - VMware ESX 3.5 fencing
> > 
> > 
> > What version of redhat are you using?
> > 
> > Are you saying that instead of copying the AppUtil directory
> > post-install of the viperltoolkit, you simply changed the use line to
> > use VMware::VIRuntime;?
> > 
> > Regards,
> > -C
> > 
> > -----Original Message-----
> > From: linux-cluster-bounces at redhat.com on behalf of Brian Kroth
> > Sent: Thu 2/28/2008 8:29 AM
> > To: Panigrahi, Santosh Kumar
> > Cc: linux clustering
> > Subject: Re: [Linux-cluster] help reqd. - VMware ESX 3.5 fencing
> >  
> > That was it.  
> > 
> > Thanks,
> > Brian
> > 
> > Panigrahi, Santosh Kumar <Santosh.Panigrahi at in.unisys.com> 2008-02-28
> > 09:37:
> > >    Hello Brian,
> > > 
> > >    I had also faced the same problem. Just change the line no 45 in
> > your
> > >    script. The original line is <use VMware::VIM2Runtime>. Make it to
> > > 
> > >    <use VMware::VIRuntime;> After changing this it worked fine for me
> > and
> > >    hopes it will also solve your compilation aborted problem.
> > > 
> > >    Chris,
> > > 
> > >    Thanks for giving your precious time on debugging the problem,
> > which I
> > >    had reported without coping the Apputil directory.
> > > 
> > >    Thanks and Regards,
> > > 
> > >    Santosh
> > > 
> > >    -----Original Message-----
> > >    From: linux-cluster-bounces at redhat.com
> > >    [[1]mailto:linux-cluster-bounces at redhat.com] On Behalf Of Brian
> > Kroth
> > >    Sent: Thursday, February 28, 2008 4:15 AM
> > >    To: chris barry
> > >    Cc: linux clustering
> > >    Subject: Re: [Linux-cluster] help reqd. - VMware ESX 3.5 fencing
> > > 
> > >    More perl questions:
> > > 
> > >    $ echo -e
> > >
> > "server=vmware\nvmname=gfstest3\nusername=fencer\npassword=fencerpw\nop
> > >    eration=reset" | /sbin/fence_vi3
> > > 
> > >    The component 'privilegeList' has already been installed in class
> > >    -->AuthorizationManager<-- as a HASH(0x1f779834)
> > > 
> > >      (this time a scalar)
> > > 
> > >     at
> > /usr/lib/perl5/vendor_perl/5.8.8/i686-linux/Class/MethodMaker.pm
> > >    line 20
> > > 
> > >    BEGIN failed--compilation aborted at
> > >    /usr/lib/perl5/site_perl/5.8.8/VMware/VIM25Runtime.pm line 17, <>
> > line
> > >    6.
> > > 
> > >    Compilation failed in require at (eval 27) line 3, <> line 6.
> > > 
> > >    Any thoughts?
> > > 
> > >    Thanks,
> > > 
> > >    Brian
> > > 
> > >    chris barry <Christopher.Barry at qlogic.com> 2008-02-26 17:30:
> > > 
> > >    > Read the top section of the script itself. I explain that the
> > install
> > > 
> > >    > script of viperltoolkit does not install the AppUtil directory
> > with
> > >    the
> > > 
> > >    > rest of itself in your particular site_perl dir.
> > > 
> > >    >
> > > 
> > >    > do a
> > > 
> > >    > $ locate site_perl
> > > 
> > >    > to see where on your system has your site_perl director(y|ies),
> > and
> > >    look
> > > 
> > >    > in each one to find the other vmware module dirs (includes)
> > listed in
> > > 
> > >    > the top of the script. Then copy the AppUtil dir (from the
> > >    viperltoolkit
> > > 
> > >    > source) into the same site_perl as the rest, and at the same
> > level.
> > > 
> > >    >
> > > 
> > >    > e.g.
> > > 
> > >    > ...site_perl
> > > 
> > >    >        |-AppUtil
> > > 
> > >    >        |-VMware
> > > 
> > >    >        `-other stuff
> > > 
> > >    >
> > > 
> > >    >
> > > 
> > >    > Once the AppUtil dir is present in the right location, it should
> > work
> > > 
> > >    > ok. I had to figure this out the hard way. ;)
> > > 
> > >    >
> > > 
> > >    >
> > > 
> > >    > Good Luck,
> > > 
> > >    > -C
> > > 
> > > References
> > > 
> > >    1. mailto:linux-cluster-bounces at redhat.com
> > 
> > 
> > 
> > 
> > 
> > --
> > Linux-cluster mailing list
> > Linux-cluster at redhat.com
> > https://www.redhat.com/mailman/listinfo/linux-cluster
> 
> --
> Linux-cluster mailing list
> Linux-cluster at redhat.com
> https://www.redhat.com/mailman/listinfo/linux-cluster
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/x-pkcs7-signature
Size: 2192 bytes
Desc: not available
URL: <http://listman.redhat.com/archives/linux-cluster/attachments/20080228/cbac3f8c/attachment.bin>

From Christopher.Barry at qlogic.com  Thu Feb 28 15:32:28 2008
From: Christopher.Barry at qlogic.com (chris barry)
Date: Thu, 28 Feb 2008 10:32:28 -0500
Subject: [Linux-cluster] help reqd. - VMware ESX 3.5 fencing
In-Reply-To: <20080228150616.GB10586@wisc.edu>
References: <D566E8CF3538B54D95B925CB69CB4D2A0C792136@inblr-exch1.eu.uis.unisys.com>
	<1203640714.5257.127.camel@localhost>
	<D566E8CF3538B54D95B925CB69CB4D2A0CAF2309@inblr-exch1.eu.uis.unisys.com>
	<1204065030.5195.56.camel@localhost> <20080227224459.GG12021@wisc.edu>
	<D566E8CF3538B54D95B925CB69CB4D2A0CC3B64C@inblr-exch1.eu.uis.unisys.com>
	<20080228132940.GA1087@wisc.edu>
	<D158540CCC0AB54C8FD4818F823CCB2453AE49@EPEXCH1.qlogic.org>
	<D566E8CF3538B54D95B925CB69CB4D2A0CD29E08@inblr-exch1.eu.uis.unisys.com>
	<1204210288.5562.42.camel@localhost> <20080228150616.GB10586@wisc.edu>
Message-ID: <1204212749.5562.49.camel@localhost>

We should note in the script the differences, and dependencies, and
which ESX server it runs on correctly, so others don't run down the same
path.

Regards,
-C

PS thanks, and good to know this - upgrading might have a whole lot
scarier.



On Thu, 2008-02-28 at 09:06 -0600, Brian Kroth wrote:
> I'm running Gentoo, but that shouldn't make a difference.  Here's what I
> did:
> 
> - install various support perl packages as listed in the VMWare perl
>   tooklit 1.5 source install instructions.  This is the one from ESX
>   3.5.
> 
> - install VMware-VIPerl-Toolkit-1.5.0-source.tar.gz
> 
> - copy the AppUtil directory as listed in the source code
> 
> - run the test cmd I posted earlier "echo stuff | fence_vi3"
> 
> I think the disconnect is probably due to differing vipertoolkit
> versions.
> 
> I had also tried switching VIM2Runtime.pm with VIM25Runtime.pm, but to
> no avail.  Switching that line to VIRuntime is what did it.
> 
> Brian
> 
> chris barry <Christopher.Barry at qlogic.com> 2008-02-28 09:51:
> > 
> > I'm running RHEL4u5 VMs and VI3.02, and I did not encounter this error.
> > What versions are you using? VI3.5, and what VM distro?
> > 
> > Ok, what I am getting at is what made you have to change that line!
> > 
> > ;)
> > 
> > On Thu, 2008-02-28 at 19:47 +0530, Panigrahi, Santosh Kumar wrote:
> > > No Chrish, I have copied Apputil directory from viperltoolkit directory
> > > (/tmp/viperltoolkit/apps) to my site perl directory
> > > (/usr/lib/perl5/site_perl/5.8.8) as per your suggestion. But after that
> > > on running your fencing script, I got the same error, as reported by
> > > Brian. Then I changed the package to VMware::VIruntime at line 45 and
> > > the script worked fine without giving any compilation problem.
> > > 
> > > I don't know how u got the impression from the below mail chain that we
> > > have executed the script successfully without coping the Apputil
> > > directory to site_perl directory. 
> > > 
> > > Thanks and Regard,
> > > Santosh
> > > 
> > >  
> > > -----Original Message-----
> > > From: linux-cluster-bounces at redhat.com
> > > [mailto:linux-cluster-bounces at redhat.com] On Behalf Of Christopher Barry
> > > Sent: Thursday, February 28, 2008 7:20 PM
> > > To: linux clustering
> > > Subject: RE: [Linux-cluster] help reqd. - VMware ESX 3.5 fencing
> > > 
> > > 
> > > What version of redhat are you using?
> > > 
> > > Are you saying that instead of copying the AppUtil directory
> > > post-install of the viperltoolkit, you simply changed the use line to
> > > use VMware::VIRuntime;?
> > > 
> > > Regards,
> > > -C
> > > 
> > > -----Original Message-----
> > > From: linux-cluster-bounces at redhat.com on behalf of Brian Kroth
> > > Sent: Thu 2/28/2008 8:29 AM
> > > To: Panigrahi, Santosh Kumar
> > > Cc: linux clustering
> > > Subject: Re: [Linux-cluster] help reqd. - VMware ESX 3.5 fencing
> > >  
> > > That was it.  
> > > 
> > > Thanks,
> > > Brian
> > > 
> > > Panigrahi, Santosh Kumar <Santosh.Panigrahi at in.unisys.com> 2008-02-28
> > > 09:37:
> > > >    Hello Brian,
> > > > 
> > > >    I had also faced the same problem. Just change the line no 45 in
> > > your
> > > >    script. The original line is <use VMware::VIM2Runtime>. Make it to
> > > > 
> > > >    <use VMware::VIRuntime;> After changing this it worked fine for me
> > > and
> > > >    hopes it will also solve your compilation aborted problem.
> > > > 
> > > >    Chris,
> > > > 
> > > >    Thanks for giving your precious time on debugging the problem,
> > > which I
> > > >    had reported without coping the Apputil directory.
> > > > 
> > > >    Thanks and Regards,
> > > > 
> > > >    Santosh
> > > > 
> > > >    -----Original Message-----
> > > >    From: linux-cluster-bounces at redhat.com
> > > >    [[1]mailto:linux-cluster-bounces at redhat.com] On Behalf Of Brian
> > > Kroth
> > > >    Sent: Thursday, February 28, 2008 4:15 AM
> > > >    To: chris barry
> > > >    Cc: linux clustering
> > > >    Subject: Re: [Linux-cluster] help reqd. - VMware ESX 3.5 fencing
> > > > 
> > > >    More perl questions:
> > > > 
> > > >    $ echo -e
> > > >
> > > "server=vmware\nvmname=gfstest3\nusername=fencer\npassword=fencerpw\nop
> > > >    eration=reset" | /sbin/fence_vi3
> > > > 
> > > >    The component 'privilegeList' has already been installed in class
> > > >    -->AuthorizationManager<-- as a HASH(0x1f779834)
> > > > 
> > > >      (this time a scalar)
> > > > 
> > > >     at
> > > /usr/lib/perl5/vendor_perl/5.8.8/i686-linux/Class/MethodMaker.pm
> > > >    line 20
> > > > 
> > > >    BEGIN failed--compilation aborted at
> > > >    /usr/lib/perl5/site_perl/5.8.8/VMware/VIM25Runtime.pm line 17, <>
> > > line
> > > >    6.
> > > > 
> > > >    Compilation failed in require at (eval 27) line 3, <> line 6.
> > > > 
> > > >    Any thoughts?
> > > > 
> > > >    Thanks,
> > > > 
> > > >    Brian
> > > > 
> > > >    chris barry <Christopher.Barry at qlogic.com> 2008-02-26 17:30:
> > > > 
> > > >    > Read the top section of the script itself. I explain that the
> > > install
> > > > 
> > > >    > script of viperltoolkit does not install the AppUtil directory
> > > with
> > > >    the
> > > > 
> > > >    > rest of itself in your particular site_perl dir.
> > > > 
> > > >    >
> > > > 
> > > >    > do a
> > > > 
> > > >    > $ locate site_perl
> > > > 
> > > >    > to see where on your system has your site_perl director(y|ies),
> > > and
> > > >    look
> > > > 
> > > >    > in each one to find the other vmware module dirs (includes)
> > > listed in
> > > > 
> > > >    > the top of the script. Then copy the AppUtil dir (from the
> > > >    viperltoolkit
> > > > 
> > > >    > source) into the same site_perl as the rest, and at the same
> > > level.
> > > > 
> > > >    >
> > > > 
> > > >    > e.g.
> > > > 
> > > >    > ...site_perl
> > > > 
> > > >    >        |-AppUtil
> > > > 
> > > >    >        |-VMware
> > > > 
> > > >    >        `-other stuff
> > > > 
> > > >    >
> > > > 
> > > >    >
> > > > 
> > > >    > Once the AppUtil dir is present in the right location, it should
> > > work
> > > > 
> > > >    > ok. I had to figure this out the hard way. ;)
> > > > 
> > > >    >
> > > > 
> > > >    >
> > > > 
> > > >    > Good Luck,
> > > > 
> > > >    > -C
> > > > 
> > > > References
> > > > 
> > > >    1. mailto:linux-cluster-bounces at redhat.com
> > > 
> > > 
> > > 
> > > 
> > > 
> > > --
> > > Linux-cluster mailing list
> > > Linux-cluster at redhat.com
> > > https://www.redhat.com/mailman/listinfo/linux-cluster
> > 
> > --
> > Linux-cluster mailing list
> > Linux-cluster at redhat.com
> > https://www.redhat.com/mailman/listinfo/linux-cluster



From rhurst at bidmc.harvard.edu  Thu Feb 28 15:28:29 2008
From: rhurst at bidmc.harvard.edu (rhurst at bidmc.harvard.edu)
Date: Thu, 28 Feb 2008 10:28:29 -0500
Subject: [Linux-cluster] gfs_tool: Cannot allocate memory
Message-ID: <C44AB05AAC2D694A907A91DA40CCF3730100406F@EVS6.its.caregroup.org>

An 11-node cluster, each with 12GB RAM, whereas every node can execute these commands, except for 2 of them:

gfs_tool df /home
gfs_tool gettune /home

>From strace, it is good when:

open("/home", O_RDONLY)                 = 3
ioctl(3, 0x4723, 0x7fbffdf73c)          = 0
ioctl(3, 0x472d, 0x7fbffff760)          = 719
close(3)                                = 0

And it fails when:

open("/home", O_RDONLY)                 = 3
ioctl(3, 0x4723, 0x7fbffcdf3c)          = 0
ioctl(3, 0x472d, 0x7fbfffe300)          = -1 ENOMEM (Cannot allocate memory)

The only difference on those 2 nodes is that they have 5GB shared mem allocated for its database instance, whereas the others only have 2GB, or no instance running.  There is plenty of memory (cached) available when reporting `free -mt` on them.


Robert Hurst, Sr. Cach? Administrator
Beth Israel Deaconess Medical Center
1135 Tremont Street, REN-7
Boston, Massachusetts   02120-2140
617-754-8754 ? Fax: 617-754-8730 ? Cell: 401-787-3154
Any technology distinguishable from magic is insufficiently advanced.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://listman.redhat.com/archives/linux-cluster/attachments/20080228/77d73a35/attachment.htm>

From marcos at digitaltecnologia.info  Thu Feb 28 17:35:59 2008
From: marcos at digitaltecnologia.info (Marcos Ferreira da Silva)
Date: Thu, 28 Feb 2008 14:35:59 -0300
Subject: [Linux-cluster] Cluster - process entered in D-state
Message-ID: <1204220159.4064.6.camel@matriz.digitaltecnologia.info>

I have two nodes in a cluster.
When I try to relocate the vm web2 to node2 then the second node freeze.

[root at vserv4 ~]# clustat
Member Status: Quorate

  Member Name                        ID   Status
  ------ ----                        ---- ------
  vserv3.uniube.br                      1 Online, rgmanager
  vserv4.uniube.br                      2 Online, Local, rgmanager

  Service Name         Owner (Last)                   State
  ------- ----         ----- ------                   -----
  vm:web1              vserv3.uniube.br               started
  vm:web2              vserv3.uniube.br               started

[root at vserv4 ~]# clusvcadm -r vm:web2 -m vserv4.uniube.br
Trying to relocate vm:web2 to vserv4.uniube.br...Success
vm:web2 is now running on vserv4.uniube.br

[root at vserv4 ~]# clustat
Member Status: Quorate

  Member Name                        ID   Status
  ------ ----                        ---- ------
  vserv3.teste.br                      1 Online, rgmanager
  vserv4.teste.br                      2 Online, Local, rgmanager

  Service Name         Owner (Last)                   State
  ------- ----         ----- ------                   -----
  vm:web1              vserv3.teste.br               started
  vm:web2              vserv4.teste.br               starting

when I use ps ax:

17349 ?        S<     0:00 /bin/bash /usr/share/cluster/vm.sh start
17356 ?        S<     0:00 python /usr/sbin/xm create web2 restart=never
--path=/etc/xen
17357 ?        D<     0:00 /usr/bin/python /usr/bin/pygrub -q
--output=/var/lib/xen/xenbl.12384 /storage/web-vms/web2.img


/var/log/messages

Feb 28 15:30:58 vserv4 clurgmgrd[10259]: <notice> Starting stopped
service vm:web2
Feb 28 15:31:00 vserv4 openais[5349]: [CKPT ] checkpoint_find returned 0
Calling error_exit.
Feb 28 15:31:40 vserv4 last message repeated 4 times

After this I have to reboot the vserv4.

The filesystem is gfs2 in RHEL5.

/dev/mapper/VGWEB-LVWebVMs on /storage/web-vms type gfs2
(rw,hostdata=jid=1:id=655361:first=0)
/dev/mapper/VGWEB-LVWeb on /storage/web type gfs2
(rw,hostdata=jid=1:id=786433:first=0)

[root at vserv4 ~]# uname -a
Linux vserv4.teste.br 2.6.18-53.1.13.el5xen #1 SMP Mon Feb 11 13:41:50
EST 2008 x86_64 x86_64 x86_64 GNU/Linux



-  
_____________________________
Marcos Ferreira da Silva
DiGital Tecnologia
Uberl?ndia - MG
(34) 9154-0150 / 3226-2534






From lhh at redhat.com  Thu Feb 28 18:25:50 2008
From: lhh at redhat.com (Lon Hohberger)
Date: Thu, 28 Feb 2008 13:25:50 -0500
Subject: [Linux-cluster] Clustat shows wrong service status
In-Reply-To: <01b101c879fd$9f71eef0$0777b5c2@gda07ak>
References: <01b101c879fd$9f71eef0$0777b5c2@gda07ak>
Message-ID: <1204223151.13733.29.camel@ayanami.boston.devel.redhat.com>

On Thu, 2008-02-28 at 12:32 +0100, Agnieszka Kuka?owicz wrote:
> > 
> > And I don't have situation that cman_tool nodes says:
> > " Last fenced   2008-02-27 15:24:16 by override"
> > 
> 
> I did more tests to find the cause of the problem.
> I found that clustat has problem with "restricted" failover domain.
> I tested 2 examples of my configuration: 
> 
> 1. failover domain is "restricted"
> 
> <rm>
>   <failoverdomains>
>     <failoverdomain name="VM_w1_failover" ordered="0" restricted="1">
>         <failoverdomainnode name="w1.local" priority="1"/>
>     </failoverdomain>
>     <failoverdomain name="VM_w2_failover" ordered="0" restricted="1">
>         <failoverdomainnode name="w2.local" priority="1"/>
> 
>     </failoverdomain>
>   </failoverdomains>
>   <resources/>
>   <vm autostart="1" domain="VM_w1_failover" exclusive="0"
> name="VM_Work11_RHEL51" path="/virts/w11" recovery="restart"/>
>   <vm autostart="1" domain="VM_w1_failover" exclusive="0"
> name="VM_Work12_RHEL51" path="/virts/w12" recovery="restart"/>
>   <vm autostart="0" domain="VM_w1_failover" exclusive="0"
> name="VM_Work13_RHEL51" path="/virts/w13" recovery="disable"/>
>   <vm autostart="1" domain="VM_w2_failover" exclusive="0"
> name="VM_Work21_RHEL51" path="/virts/w21" recovery="restart"/>
>   <vm autostart="0" domain="VM_w2_failover" exclusive="0"
> name="VM_Work22_RHEL51" path="/virts/w22" recovery="disable"/>
>   <vm autostart="0" domain="VM_w2_failover" exclusive="0"
> name="VM_Work23_RHEL51" path="/virts/w23" recovery="disable"/>
>         </rm>
> 
> Member Status: Quorate
> 
>   Member Name                        ID   Status
>   ------ ----                        ---- ------
>   w2.local		                    1 Online, Local, rgmanager
>   w1.local		                    2 Online, rgmanager
> 
>   Service Name         Owner (Last)                   State
>   ------- ----         ----- ------                   -----
>   vm:VM_Work11_RHEL51  w1.local				started
>   vm:VM_Work12_RHEL51  w1.local		            started
>   vm:VM_Work13_RHEL51  (none)                         disabled
>   vm:VM_Work21_RHEL51  w2.local		            started
>   vm:VM_Work22_RHEL51  (none)                         disabled
>   vm:VM_Work23_RHEL51  (none)                         disabled
> 
> After power off node w2.local and fencing "w2.local" by "w1.local"
> clustat still shows the service vm:VM_Work21_RHEL51 is started on
> w2.local
> 

Oh, so you had a restricted failover domain, and no nodes were online.
Looking at the code, it appears to be "correct weirdness" or perhaps
"known dysfunction":

http://sources.redhat.com/git/?p=cluster.git;a=blob;f=rgmanager/src/daemons/groups.c;h=a8325eec3425bbe124696bfe3dcd6f7ea1eebfea;hb=8e504af1adbadd2cb8fe7cab191d79a8d835540c#l742


                        /*
                         * TODO
                         * Mark a service as 'stopped' if no members in
its
                         * restricted fail-over domain are running.
                         */

Why it occurs:

The service states are typically only altered by a node which is taking
action on a service.  In this case, no nodes are online which are
allowed to act on the service - therefore, they do nothing.  What needs
to happen in this case is:

  * Check service failover domain config
  * Check nodes online
  * Mark service 'stopped' if no nodes are online capable of running
    the service

The reason this hasn't been fixed is because it doesn't actually cause
any service-availability problems - it just causes wrong reporting.

Could you file a bugzilla? :)

-- Lon



From lhh at redhat.com  Thu Feb 28 18:56:25 2008
From: lhh at redhat.com (Lon Hohberger)
Date: Thu, 28 Feb 2008 13:56:25 -0500
Subject: [Linux-cluster] Unable to determine fence device
In-Reply-To: <007701c87846$43db79c0$a40110ac@GKTECNA1164>
References: <007701c87846$43db79c0$a40110ac@GKTECNA1164>
Message-ID: <1204224985.13733.32.camel@ayanami.boston.devel.redhat.com>

On Tue, 2008-02-26 at 12:37 +0530, sanjeev.saini at hitechos.com wrote:
> Hi,
>  
> We have recently purchased a IBM Blade Center and we are in plan to
> configure an apache cluster on two blades. Now the problem is that I'm
> not able to find the details of fencing devices in IBM Blade Center
> for ex. IP Address, Username, Password.
>  
> Is there any device integrated in the IBM Bladecenter on which IP
> needs to be configured. 

It's actually the 'control' blade, I think, that you need information
about.

-- Lon




From david at eciad.ca  Thu Feb 28 19:04:39 2008
From: david at eciad.ca (David Ayre)
Date: Thu, 28 Feb 2008 11:04:39 -0800
Subject: [Linux-cluster] dlm_sendd 100% CPU
In-Reply-To: <2DA8E0E5-67D2-4829-B8AD-2C7F022C35D2@eciad.ca>
References: <2DA8E0E5-67D2-4829-B8AD-2C7F022C35D2@eciad.ca>
Message-ID: <667808AB-5958-497E-BF74-96573B694B89@eciad.ca>

Someone reported earlier a similar problem with dlm_sendd taking up  
100%:

http://www.mail-archive.com/linux-cluster at redhat.com/msg01002.html

Could our problem be with bugs in our kernel and GFS versions ? (2.6.9- 
X) ?



> Any ideas why dlm_sendd is taking up 100% CPU ?
>
> We have this intermittent problem which seems to happen when a group  
> of users log into our servers at the same time, possibly opening/ 
> writing files from the same mount point.
>
> Should dlm_sendd ever take up 100% of the CPU ?
>
> Any help would be greatly appreciated.... i mean greatly.... like  
> sell my soul "greatly".  If there is any additional diagnostic info  
> i can provide, please let me know.    /var/log/messages just shows  
> failed SMB pipes/write failures due to the high load/lockups.
>
> Version info:
> ----------------------------
> Kernel:   2.6.9-55.0.6.ELsmp #1 SMP
> GFS:  2.6.9-72.2.0.7
> SMB: 3.0.10-1.4E.12.2
>
> Top:
> ----------------------------
> top - 15:48:44 up 53 days, 13:35,  3 users,  load average: 57.40,  
> 48.47, 37.00
> Tasks: 257 total,  64 running, 193 sleeping,   0 stopped,   0 zombie
> Cpu0  :  0.3% us, 99.7% sy,  0.0% ni,  0.0% id,  0.0% wa,  0.0% hi,   
> 0.0% si
> Cpu1  :  0.0% us, 100.0% sy,  0.0% ni,  0.0% id,  0.0% wa,  0.0%  
> hi,  0.0% si
> Cpu2  :  0.3% us, 99.7% sy,  0.0% ni,  0.0% id,  0.0% wa,  0.0% hi,   
> 0.0% si
> Cpu3  :  0.0% us, 100.0% sy,  0.0% ni,  0.0% id,  0.0% wa,  0.0%  
> hi,  0.0% si
> Mem:   4147164k total,  1089108k used,  3058056k free,     5200k  
> buffers
> Swap:  2031608k total,      224k used,  2031384k free,   795340k  
> cached
>
>  PID USER      PR  NI  VIRT  RES  SHR S %CPU %MEM    TIME+  COMMAND
> 4218 root       9 -10     0    0    0 R  100  0.0   1066:10 dlm_sendd
> ...





From fog at t.is  Thu Feb 28 20:35:56 2008
From: fog at t.is (=?iso-8859-1?Q?Finnur_=D6rn_Gu=F0mundsson_-_TM_Software?=)
Date: Thu, 28 Feb 2008 20:35:56 -0000
Subject: [Linux-cluster] Unable to determine fence device
In-Reply-To: <1204224985.13733.32.camel@ayanami.boston.devel.redhat.com>
References: <007701c87846$43db79c0$a40110ac@GKTECNA1164>
	<1204224985.13733.32.camel@ayanami.boston.devel.redhat.com>
Message-ID: <3DDA6E3E456E144DA3BB0A62A7F7F77901D8570F@SKYHQAMX08.klasi.is>

Hi,

You just need to configure the management module IP adress for the blade chassis...then you can use it to fence :)

Thanks,
Finnur

-----Original Message-----
From: linux-cluster-bounces at redhat.com [mailto:linux-cluster-bounces at redhat.com] On Behalf Of Lon Hohberger
Sent: 28. febr?ar 2008 18:56
To: linux clustering
Subject: Re: [Linux-cluster] Unable to determine fence device

On Tue, 2008-02-26 at 12:37 +0530, sanjeev.saini at hitechos.com wrote:
> Hi,
>  
> We have recently purchased a IBM Blade Center and we are in plan to
> configure an apache cluster on two blades. Now the problem is that I'm
> not able to find the details of fencing devices in IBM Blade Center
> for ex. IP Address, Username, Password.
>  
> Is there any device integrated in the IBM Bladecenter on which IP
> needs to be configured. 

It's actually the 'control' blade, I think, that you need information
about.

-- Lon


--
Linux-cluster mailing list
Linux-cluster at redhat.com
https://www.redhat.com/mailman/listinfo/linux-cluster



From jbrassow at redhat.com  Thu Feb 28 20:45:18 2008
From: jbrassow at redhat.com (Jonathan Brassow)
Date: Thu, 28 Feb 2008 14:45:18 -0600
Subject: [Linux-cluster] HA LVM
In-Reply-To: <5b65f1b10802271447s69f736a2gec497abd1ec06317@mail.gmail.com>
References: <5b65f1b10802271447s69f736a2gec497abd1ec06317@mail.gmail.com>
Message-ID: <541A6F37-F850-42D8-B030-9C694453413E@redhat.com>

have you done 'service cman start' before running that test?  (It  
shouldn't really matter and this may be a bug, but try starting the  
cluster infrastructure anyway.)

  brassow


On Feb 27, 2008, at 4:47 PM, Jorge Palma wrote:

> Hello:
>
> I am trying to implement HA LVM in 2 nodes with RHEL 5.1, but I have
> the following errors:
>
> in vmdb01:
>
> [root at vmdb01 ~]# rg_test test /etc/cluster/cluster.conf start  
> service testSG
> Running in test mode.
> Starting testSG...
> volume_list=["rootdg", "@vmdb01"]
> <notice> Owner of lvmclusterdg/lvmclustervol is not in the cluster
> <notice> Stealing lvmclusterdg/lvmclustervol
> lvchange  Logical volume "lvmclustervol" changed
> <err>    Failed to steal lvmclusterdg/lvmclustervol from lvs         .
> Failed to start testSG
>
> in vmfe01:
>
> [root at vmfe01 ~]# rg_test test /etc/cluster/cluster.conf start  
> service testSG
> Running in test mode.
> Starting testSG...
> volume_list=["rootdg", "@vmfe01"]
> <notice> Owner of lvmclusterdg/lvmclustervol is not in the cluster
> <notice> Stealing lvmclusterdg/lvmclustervol
> lvchange  Logical volume "lvmclustervol" changed
> <err>    Failed to steal lvmclusterdg/lvmclustervol from lvs         .
> Failed to start testSG
>
> In vmdb01 lvm.conf have:
>
> volume_list = [ "rootdg", "@vmdb01" ]
>
> In vmfe01 lvm.cong have:
>
> volume_list = [ "rootdg", "@vmfe01" ]
>
> Will appreciate any ideas
>
> PD: sorry by my english
>
> -- 
> Jorge Palma Escobar
> Ingeniero de Sistemas
> Red Hat Linux Certified Engineer
> Certificate N? 804005089418233
>
> --
> Linux-cluster mailing list
> Linux-cluster at redhat.com
> https://www.redhat.com/mailman/listinfo/linux-cluster




From jbrassow at redhat.com  Thu Feb 28 20:49:49 2008
From: jbrassow at redhat.com (Jonathan Brassow)
Date: Thu, 28 Feb 2008 14:49:49 -0600
Subject: [Linux-cluster] is clvm a must all the time in a cluster ?
In-Reply-To: <960521.47103.qm@web50608.mail.re2.yahoo.com>
References: <960521.47103.qm@web50608.mail.re2.yahoo.com>
Message-ID: <E416F6CE-5D5E-4903-A740-9225CA5A5913@redhat.com>

 From the description, I am skeptical that clvm is your problem...   
(Also, are you using a proper fencing mechanism?)

We would probably need more information from the logs to determine  
what is going on.

  brassow

On Feb 25, 2008, at 3:06 PM, Roger Pe?a wrote:

> Hi
>
> I am running RHEL4 with csgfs from centos, all
> packages updates in both sets (RHEL and CS-GFS)
> but since the last updates my cluster become more
> unstable, sometimes after a failed shutdown of a
> service (it failed because was unable to umount the
> GFS) and the other two times just dont know exactly
> why (I wasn't ther when it happen, just went to
> fixed).
> all of this in lest than two weeks
> and every time, the cman infrastructure just hand or
> collapse.
> the first to times, I realice that one of the nodes
> (and just one) was hanging the cman so the entire
> cluster where in stand-by, until I fence (reboot) the
> node.
> from cman_tool services in that node, I guess clvm was
> the guilty just because it were running (run state):-)
> it shouldn't be in that state ;-) . it is just a
> guess, ok? I am not an expert in CS.
> also, a lot, and I mean a lot, of time my services
> can't start is because the clustered LV are not
> Activated even when clvm is running and cman_tool
> services say it is running.
> just a clvmd restar fix that.
>
> so, my question is, can I run the cluster with GFS
> without clvmd working?
> I don't have plans to work with lvm (extending for
> example) the sistem is working and should be in the
> same state (from the filesystem point of view) for a
> long time.
> so, can I "declusterice" the LV where GFS live?
>
> and if I can, what are the steps to do it?
>
> 1- vgchange -cn "VG Name"
> 2- cmand stop
> 3- lvmconf --disable-cluster
>
> I guess I don't need to unmount the LV to do that, do
> I?
> nore the data in those FS should be lost because of
> that operation (tha change), right?
>
>
> thanks in advance for the help
>
> cu
> roger
>
> __________________________________________
> RedHat Certified ( RHCE )
> Cisco Certified ( CCNA & CCDA )
>
>
>      Be smarter than spam. See how smart SpamGuard is at giving junk  
> email the boot with the All-new Yahoo! Mail.  Click on Options in  
> Mail and switch to New Mail today or register for free at http://mail.yahoo.ca
>
> --
> Linux-cluster mailing list
> Linux-cluster at redhat.com
> https://www.redhat.com/mailman/listinfo/linux-cluster




From orkcu at yahoo.com  Thu Feb 28 23:50:10 2008
From: orkcu at yahoo.com (=?iso-8859-1?Q?Roger_Pe=F1a?=)
Date: Thu, 28 Feb 2008 18:50:10 -0500 (EST)
Subject: [Linux-cluster] is clvm a must all the time in a cluster ?
In-Reply-To: <E416F6CE-5D5E-4903-A740-9225CA5A5913@redhat.com>
Message-ID: <992786.52488.qm@web50607.mail.re2.yahoo.com>


--- Jonathan Brassow <jbrassow at redhat.com> wrote:

>  From the description, I am skeptical that clvm is
> your problem...   
> (Also, are you using a proper fencing mechanism?)
yes, fencing is ok
everytime the cluster lose contact with a node, it is
fenced very quickly :-)
but, in the cases I am describing, the nodes remains
members of the cluster so no need to fence anyone .
just happen that cman get stuck because some cman
service in some node get stuck, and because cman is
stuck we can't do anything that interact with cman
except with the node who make the problem (we have to
guess what node is :-) )
what I had found is that usually, clvmd is the one
that it is not working as it should, but in other
cases we just don't know who is causing the problem.
usually the reboot of the offending node provoque some
transicions in the cluster and cman get out of the
stuck and cluster come back to live :-)

the cluster is in production so I am very limited to
do tests.
right now the admin team agree into let clvmd work
(started at boot time) but if in the future we get
more problems and if we find that that problem somehow
is related with clvmd then we will try to revert the
cluster lvm setting from our SAN lv 
any downside with this approach except not be able to
run lvm commands ?

thanks
roger

> 
> We would probably need more information from the
> logs to determine  
> what is going on.
> 
>   brassow
> 
> On Feb 25, 2008, at 3:06 PM, Roger Pe?a wrote:
> 
> > Hi
> >
> > I am running RHEL4 with csgfs from centos, all
> > packages updates in both sets (RHEL and CS-GFS)
> > but since the last updates my cluster become more
> > unstable, sometimes after a failed shutdown of a
> > service (it failed because was unable to umount
> the
> > GFS) and the other two times just dont know
> exactly
> > why (I wasn't ther when it happen, just went to
> > fixed).
> > all of this in lest than two weeks
> > and every time, the cman infrastructure just hand
> or
> > collapse.
> > the first to times, I realice that one of the
> nodes
> > (and just one) was hanging the cman so the entire
> > cluster where in stand-by, until I fence (reboot)
> the
> > node.
> > from cman_tool services in that node, I guess clvm
> was
> > the guilty just because it were running (run
> state):-)
> > it shouldn't be in that state ;-) . it is just a
> > guess, ok? I am not an expert in CS.
> > also, a lot, and I mean a lot, of time my services
> > can't start is because the clustered LV are not
> > Activated even when clvm is running and cman_tool
> > services say it is running.
> > just a clvmd restar fix that.
> >
> > so, my question is, can I run the cluster with GFS
> > without clvmd working?
> > I don't have plans to work with lvm (extending for
> > example) the sistem is working and should be in
> the
> > same state (from the filesystem point of view) for
> a
> > long time.
> > so, can I "declusterice" the LV where GFS live?
> >
> > and if I can, what are the steps to do it?
> >
> > 1- vgchange -cn "VG Name"
> > 2- cmand stop
> > 3- lvmconf --disable-cluster
> >
> > I guess I don't need to unmount the LV to do that,
> do
> > I?
> > nore the data in those FS should be lost because
> of
> > that operation (tha change), right?
> >
> >
> > thanks in advance for the help
> >
> > cu
> > roger
> >
> > __________________________________________
> > RedHat Certified ( RHCE )
> > Cisco Certified ( CCNA & CCDA )
> >
> >
> >      Be smarter than spam. See how smart SpamGuard
> is at giving junk  
> > email the boot with the All-new Yahoo! Mail. 
> Click on Options in  
> > Mail and switch to New Mail today or register for
> free at http://mail.yahoo.ca
> >
> > --
> > Linux-cluster mailing list
> > Linux-cluster at redhat.com
> >
>
https://www.redhat.com/mailman/listinfo/linux-cluster
> 
> 
> --
> Linux-cluster mailing list
> Linux-cluster at redhat.com
>
https://www.redhat.com/mailman/listinfo/linux-cluster
> 


__________________________________________
RedHat Certified ( RHCE )
Cisco Certified ( CCNA & CCDA )


      Connect with friends from any web browser - no download required. Try the new Yahoo! Canada Messenger for the Web BETA at http://ca.messenger.yahoo.com/webmessengerpromo.php



From tb at tbits.net  Fri Feb 29 01:23:10 2008
From: tb at tbits.net (Thomas =?iso-8859-1?q?B=F6rnert?=)
Date: Fri, 29 Feb 2008 02:23:10 +0100
Subject: [Linux-cluster] SOLVED: GFS2 2 Node Cluster - lost Node - Mount
	=?iso-8859-1?q?not=09writeable?=
In-Reply-To: <47C57512.3050700@redhat.com>
References: <200802262340.46493.tb@tbits.net> <47C57512.3050700@redhat.com>
Message-ID: <200802290223.26596.tb@tbits.net>

ok i understand. fence_ack_manual node1 works

i tried now fence_drac and it works automatically. fine.

Thx

Thomas

> This is because you are using manual fencing.  Fencing is required to
> ensure that an errant node does not continue to write to the shared
> filesystem after it has lost communication with the cluster, thereby
> corrupting the data.  The only way to do this is to halt all cluster
> activity (including granting GFS locks) until the fencing succeeds.
> The "manual" means that an administrator must intervene and correct the
> problem before cluster operations can resume.  So when you power off
> node1, node2 detects missed heartbeats and fences node1.  Now you must
> manually fence node1 by powering it off (this is already done in your
> case) then do one of the following:
>
>      1) Run the following command to acknowledge that you have manually
> fenced the node
>
>                # /sbin/fence_ack_manual node1
>
>          OR
>
>      2) Start node1 back up and have it rejoin the cluster
>
> The danger with manual fencing comes in when you quickly run
> fence_ack_manual without properly investigating the issue or fencing the
> node.  You may see that the fenced node is still up and quickly run that
> command without noticing that the network connection has been lost.  Now
> the nodes proceed with writing to GFS without being able to communicate
> and they quickly corrupt the data.
>
> So, when using manual fencing always take caution before running
> fence_ack_manual.
>
> John
>
> --
> Linux-cluster mailing list
> Linux-cluster at redhat.com
> https://www.redhat.com/mailman/listinfo/linux-cluster



From tb at tbits.net  Fri Feb 29 01:27:41 2008
From: tb at tbits.net (Thomas =?utf-8?q?B=C3=B6rnert?=)
Date: Fri, 29 Feb 2008 02:27:41 +0100
Subject: [Linux-cluster] GFS2 2 Node Cluster - lost Node - Mount not
	writeable
In-Reply-To: <1204151456.13733.13.camel@ayanami.boston.devel.redhat.com>
References: <200802262340.46493.tb@tbits.net>
	<1204151456.13733.13.camel@ayanami.boston.devel.redhat.com>
Message-ID: <200802290227.56566.tb@tbits.net>

my drbd.conf
----------------------------------------------------------------------------------------
global {
    usage-count no;
}
resource drbd0 {
  protocol C;
  handlers {
    pri-on-incon-degr "echo o > /proc/sysrq-trigger ; halt -f";
    pri-lost-after-sb "echo o > /proc/sysrq-trigger ; halt -f";
    local-io-error "echo o > /proc/sysrq-trigger ; halt -f";
#    outdate-peer "/usr/lib/heartbeat/drbd-peer-outdater -t 5";
  }
  startup {
    wfc-timeout  0;
    degr-wfc-timeout 120;
  }
  net {
    timeout       60;
    connect-int   10;
    ping-int      10;
    ping-timeout   5;
    max-buffers     2048;
    unplug-watermark   128;
    max-epoch-size  2048;
    ko-count 4;
    allow-two-primaries;
    after-sb-0pri disconnect;
    after-sb-1pri disconnect;
    after-sb-2pri disconnect;
    rr-conflict disconnect;
  }
  disk {
    on-io-error   detach;
    #size 16G;
  }
  syncer {
    rate 700000K;
    #after "drbd0";
    al-extents 257;
  }
  on node1 {
    device     /dev/drbd0;
    disk       /dev/volg1/lv_test;
    address    192.168.0.1:7788;
    flexible-meta-disk  internal;
  }
  on node2 {
    device     /dev/drbd0;
    disk       /dev/volg1/lv_test;
    address    192.168.0.2:7788;
    flexible-meta-disk  internal;
  }
}

On Wednesday 27 February 2008 11:30:56 pm Lon Hohberger wrote:
> On Tue, 2008-02-26 at 23:40 +0100, Thomas B?rnert wrote:
> > -------------------------------------------------------------------------
> >-----------------------------------------
> >
> > my drbd is no problem state is already primary (standalone)
>
> It still needs to call the outdate_peer handler (which must succeed!),
> or it will block writes until the other node comes back.

ok, i'd commented that, because i've not installed heartbeat.
do still need heartbeat for drbd ?

Thx

Thomas




From swplotner at amherst.edu  Fri Feb 29 01:39:48 2008
From: swplotner at amherst.edu (Steffen Plotner)
Date: Thu, 28 Feb 2008 20:39:48 -0500
Subject: [Linux-cluster] is clvm a must all the time in a cluster ?
In-Reply-To: <992786.52488.qm@web50607.mail.re2.yahoo.com>
Message-ID: <150F55E3591CD042B77ED3DB957854652B62C9@mail7.amherst.edu>

Hi,

You asked below: can I run the cluster with GFS without clvmd? The answer is yes. I believe in having the least number of components running, and found that clvmd had start up problems (and then refuses to stop) after doing an update of RHEL4 during December.  

It is clearly possible to use GFS directly on a SAN based LUN. The trick of course is how to deal with the /dev/sdb reference which will probably not be the same on all hosts. To fix that use udev rules that provide a symlink (using the serial number of the LUN, for example) by which the GFS file system can be referred to in /etc/fstab.

The conversion is simple and requires downtime. Create a new LUN sized as the old one, attach it to the cluster, create a GFS file system on the device /dev/sd-SN3030303 (for example), mount it, use whatever unix tool you would like to transfer the data from the existing GFS file system to the new one, modify the /etc/fstab files and you are done.

We have converted 2 clusters in the past few months because we have had real problems with clvmd misbehaving itself during startup. At this point it is a pleasure to let the cluster boot by itself and not to have to worry about GFS file systems not being mounted (ccsd, cman, fenced, iscsi, gfs).

Steffen

> -----Original Message-----
> From: linux-cluster-bounces at redhat.com 
> [mailto:linux-cluster-bounces at redhat.com] On Behalf Of Roger Pe?a
> Sent: Thursday, February 28, 2008 6:50 PM
> To: linux clustering
> Subject: Re: [Linux-cluster] is clvm a must all the time in a 
> cluster ?
> 
> 
> --- Jonathan Brassow <jbrassow at redhat.com> wrote:
> 
> >  From the description, I am skeptical that clvm is
> > your problem...   
> > (Also, are you using a proper fencing mechanism?)
> yes, fencing is ok
> everytime the cluster lose contact with a node, it is fenced 
> very quickly :-) but, in the cases I am describing, the nodes 
> remains members of the cluster so no need to fence anyone .
> just happen that cman get stuck because some cman service in 
> some node get stuck, and because cman is stuck we can't do 
> anything that interact with cman except with the node who 
> make the problem (we have to guess what node is :-) ) what I 
> had found is that usually, clvmd is the one that it is not 
> working as it should, but in other cases we just don't know 
> who is causing the problem.
> usually the reboot of the offending node provoque some 
> transicions in the cluster and cman get out of the stuck and 
> cluster come back to live :-)
> 
> the cluster is in production so I am very limited to do tests.
> right now the admin team agree into let clvmd work (started 
> at boot time) but if in the future we get more problems and 
> if we find that that problem somehow is related with clvmd 
> then we will try to revert the cluster lvm setting from our 
> SAN lv any downside with this approach except not be able to 
> run lvm commands ?
> 
> thanks
> roger
> 
> > 
> > We would probably need more information from the logs to determine 
> > what is going on.
> > 
> >   brassow
> > 
> > On Feb 25, 2008, at 3:06 PM, Roger Pe?a wrote:
> > 
> > > Hi
> > >
> > > I am running RHEL4 with csgfs from centos, all packages 
> updates in 
> > > both sets (RHEL and CS-GFS) but since the last updates my cluster 
> > > become more unstable, sometimes after a failed shutdown 
> of a service 
> > > (it failed because was unable to umount
> > the
> > > GFS) and the other two times just dont know
> > exactly
> > > why (I wasn't ther when it happen, just went to fixed).
> > > all of this in lest than two weeks
> > > and every time, the cman infrastructure just hand
> > or
> > > collapse.
> > > the first to times, I realice that one of the
> > nodes
> > > (and just one) was hanging the cman so the entire cluster 
> where in 
> > > stand-by, until I fence (reboot)
> > the
> > > node.
> > > from cman_tool services in that node, I guess clvm
> > was
> > > the guilty just because it were running (run
> > state):-)
> > > it shouldn't be in that state ;-) . it is just a guess, 
> ok? I am not 
> > > an expert in CS.
> > > also, a lot, and I mean a lot, of time my services can't start is 
> > > because the clustered LV are not Activated even when clvm 
> is running 
> > > and cman_tool services say it is running.
> > > just a clvmd restar fix that.
> > >
> > > so, my question is, can I run the cluster with GFS without clvmd 
> > > working?
> > > I don't have plans to work with lvm (extending for
> > > example) the sistem is working and should be in
> > the
> > > same state (from the filesystem point of view) for
> > a
> > > long time.
> > > so, can I "declusterice" the LV where GFS live?
> > >
> > > and if I can, what are the steps to do it?
> > >
> > > 1- vgchange -cn "VG Name"
> > > 2- cmand stop
> > > 3- lvmconf --disable-cluster
> > >
> > > I guess I don't need to unmount the LV to do that,
> > do
> > > I?
> > > nore the data in those FS should be lost because
> > of
> > > that operation (tha change), right?
> > >
> > >
> > > thanks in advance for the help
> > >
> > > cu
> > > roger
> > >
> > > __________________________________________
> > > RedHat Certified ( RHCE )
> > > Cisco Certified ( CCNA & CCDA )
> > >
> > >
> > >      Be smarter than spam. See how smart SpamGuard
> > is at giving junk
> > > email the boot with the All-new Yahoo! Mail. 
> > Click on Options in
> > > Mail and switch to New Mail today or register for
> > free at http://mail.yahoo.ca
> > >
> > > --
> > > Linux-cluster mailing list
> > > Linux-cluster at redhat.com
> > >
> >
> https://www.redhat.com/mailman/listinfo/linux-cluster
> > 
> > 
> > --
> > Linux-cluster mailing list
> > Linux-cluster at redhat.com
> >
> https://www.redhat.com/mailman/listinfo/linux-cluster
> > 
> 
> 
> __________________________________________
> RedHat Certified ( RHCE )
> Cisco Certified ( CCNA & CCDA )
> 
> 
>       Connect with friends from any web browser - no download 
> required. Try the new Yahoo! Canada Messenger for the Web 
> BETA at http://ca.messenger.yahoo.com/webmessengerpromo.php
> 
> --
> Linux-cluster mailing list
> Linux-cluster at redhat.com
> https://www.redhat.com/mailman/listinfo/linux-cluster
> 



From jpalmae at gmail.com  Fri Feb 29 01:45:52 2008
From: jpalmae at gmail.com (Jorge Palma)
Date: Thu, 28 Feb 2008 22:45:52 -0300
Subject: [Linux-cluster] HA LVM
In-Reply-To: <541A6F37-F850-42D8-B030-9C694453413E@redhat.com>
References: <5b65f1b10802271447s69f736a2gec497abd1ec06317@mail.gmail.com>
	<541A6F37-F850-42D8-B030-9C694453413E@redhat.com>
Message-ID: <5b65f1b10802281745n748afc21u99c93f9069f1239c@mail.gmail.com>

On Thu, Feb 28, 2008 at 5:45 PM, Jonathan Brassow <jbrassow at redhat.com> wrote:
> have you done 'service cman start' before running that test?  (It
>  shouldn't really matter and this may be a bug, but try starting the
>  cluster infrastructure anyway.)
>
>   brassow
>
>
>
>
>  On Feb 27, 2008, at 4:47 PM, Jorge Palma wrote:
>
>  > Hello:
>  >
>  > I am trying to implement HA LVM in 2 nodes with RHEL 5.1, but I have
>  > the following errors:
>  >
>  > in vmdb01:
>  >
>  > [root at vmdb01 ~]# rg_test test /etc/cluster/cluster.conf start
>  > service testSG
>  > Running in test mode.
>  > Starting testSG...
>  > volume_list=["rootdg", "@vmdb01"]
>  > <notice> Owner of lvmclusterdg/lvmclustervol is not in the cluster
>  > <notice> Stealing lvmclusterdg/lvmclustervol
>  > lvchange  Logical volume "lvmclustervol" changed
>  > <err>    Failed to steal lvmclusterdg/lvmclustervol from lvs         .
>  > Failed to start testSG
>  >
>  > in vmfe01:
>  >
>  > [root at vmfe01 ~]# rg_test test /etc/cluster/cluster.conf start
>  > service testSG
>  > Running in test mode.
>  > Starting testSG...
>  > volume_list=["rootdg", "@vmfe01"]
>  > <notice> Owner of lvmclusterdg/lvmclustervol is not in the cluster
>  > <notice> Stealing lvmclusterdg/lvmclustervol
>  > lvchange  Logical volume "lvmclustervol" changed
>  > <err>    Failed to steal lvmclusterdg/lvmclustervol from lvs         .
>  > Failed to start testSG
>  >
>  > In vmdb01 lvm.conf have:
>  >
>  > volume_list = [ "rootdg", "@vmdb01" ]
>  >
>  > In vmfe01 lvm.cong have:
>  >
>  > volume_list = [ "rootdg", "@vmfe01" ]
>  >
>  > Will appreciate any ideas
>  >
>  > PD: sorry by my english
>  >
>  > --
>  > Jorge Palma Escobar
>  > Ingeniero de Sistemas
>  > Red Hat Linux Certified Engineer
>  > Certificate N? 804005089418233
>  >
>  > --
>  > Linux-cluster mailing list
>  > Linux-cluster at redhat.com
>  > https://www.redhat.com/mailman/listinfo/linux-cluster
>
>
>  --
>  Linux-cluster mailing list
>  Linux-cluster at redhat.com
>  https://www.redhat.com/mailman/listinfo/linux-cluster
>

Of course, in fact we found other problems, such as the agent of lvm
read parameters name and the name of volume wrongly

In any event, the most common clustering services working properly

Greetings

-- 
Jorge Palma Escobar
Ingeniero de Sistemas
Red Hat Linux Certified Engineer
Certificate N? 804005089418233



From orkcu at yahoo.com  Fri Feb 29 02:55:36 2008
From: orkcu at yahoo.com (=?iso-8859-1?Q?Roger_Pe=F1a?=)
Date: Thu, 28 Feb 2008 21:55:36 -0500 (EST)
Subject: [Linux-cluster] is clvm a must all the time in a cluster ?
In-Reply-To: <150F55E3591CD042B77ED3DB957854652B62C9@mail7.amherst.edu>
Message-ID: <735712.34907.qm@web50606.mail.re2.yahoo.com>


--- Steffen Plotner <swplotner at amherst.edu> wrote:

> Hi,
> 
> You asked below: can I run the cluster with GFS
> without clvmd? The answer is yes. I believe in
> having the least number of components running, and
> found that clvmd had start up problems (and then
> refuses to stop) after doing an update of RHEL4
> during December.  
> 
I apply those updates this month so I guess I am
seeing the same as you 

> It is clearly possible to use GFS directly on a SAN
> based LUN. 
I know that but, as you already said, the problem is
"having a uniq name for the filesystem to all the
nodes"

>The trick of course is how to deal with
> the /dev/sdb reference which will probably not be
> the same on all hosts. To fix that use udev rules
> that provide a symlink (using the serial number of
> the LUN, for example) by which the GFS file system
> can be referred to in /etc/fstab.

I am sure udev rules works but definitly seting that
enviroment is more complex that use a LV :-)
so, what happen is I use the shared LV just as a local
LV?
each node will treated the same way as it treat the LV
from the local disks. I guess that will not be a
problem as far as I do not work with the VG metadata,
am I right?




> We have converted 2 clusters in the past few months
> because we have had real problems with clvmd
> misbehaving itself during startup. At this point it
> is a pleasure to let the cluster boot by itself and
> not to have to worry about GFS file systems not
> being mounted (ccsd, cman, fenced, iscsi, gfs).

not activating LV even when clvmd is running? it
happen to me several times in the last month
;-) 
that is why I want to get rid of lvm :-)

thanks

cu
roger

__________________________________________
RedHat Certified ( RHCE )
Cisco Certified ( CCNA & CCDA )


      Looking for the perfect gift? Give the gift of Flickr! 

http://www.flickr.com/gift/



From orkcu at yahoo.com  Fri Feb 29 03:00:04 2008
From: orkcu at yahoo.com (=?iso-8859-1?Q?Roger_Pe=F1a?=)
Date: Thu, 28 Feb 2008 22:00:04 -0500 (EST)
Subject: [Linux-cluster] is clvm a must all the time in a cluster ?
In-Reply-To: <735712.34907.qm@web50606.mail.re2.yahoo.com>
Message-ID: <233538.63310.qm@web50602.mail.re2.yahoo.com>


--- Roger Pe?a <orkcu at yahoo.com> wrote:

> 
> --- Steffen Plotner <swplotner at amherst.edu> wrote:
> 
> > Hi,
> > 
> > You asked below: can I run the cluster with GFS
> > without clvmd? The answer is yes. I believe in
> > having the least number of components running, and
> > found that clvmd had start up problems (and then
> > refuses to stop) after doing an update of RHEL4
> > during December.  
> > 
> I apply those updates this month so I guess I am
> seeing the same as you 
> 
> > It is clearly possible to use GFS directly on a
> SAN
> > based LUN. 
> I know that but, as you already said, the problem is
> "having a uniq name for the filesystem to all the
> nodes"
> 
> >The trick of course is how to deal with
> > the /dev/sdb reference which will probably not be
> > the same on all hosts. To fix that use udev rules
> > that provide a symlink (using the serial number of
> > the LUN, for example) by which the GFS file system
> > can be referred to in /etc/fstab.
> 
> I am sure udev rules works but definitly seting that
> enviroment is more complex that use a LV :-)
> so, what happen is I use the shared LV just as a
> local
> LV?
> each node will treated the same way as it treat the
> LV
> from the local disks. I guess that will not be a
> problem as far as I do not work with the VG
> metadata,
> am I right?
> 
> 
> 
> 
> > We have converted 2 clusters in the past few
> months
> > because we have had real problems with clvmd
> > misbehaving itself during startup. At this point
> it
> > is a pleasure to let the cluster boot by itself
> and
> > not to have to worry about GFS file systems not
> > being mounted (ccsd, cman, fenced, iscsi, gfs).
> 
> not activating LV even when clvmd is running? it
> happen to me several times in the last month
> ;-) 
> that is why I want to get rid of lvm :-)
                                   ^^^
I mean clvm

sorry, I want to use lvm, but I dont want to use clvm
all the time, just when, very rarely, need to create
or resize shared lv

cu
roger

__________________________________________
RedHat Certified ( RHCE )
Cisco Certified ( CCNA & CCDA )


      Get a sneak peak at messages with a handy reading pane with All new Yahoo! Mail: http://ca.promos.yahoo.com/newmail/overview2/



From rpeterso at redhat.com  Fri Feb 29 03:03:36 2008
From: rpeterso at redhat.com (Bob Peterson)
Date: Thu, 28 Feb 2008 21:03:36 -0600
Subject: [Linux-cluster] gfs_tool: Cannot allocate memory
In-Reply-To: <C44AB05AAC2D694A907A91DA40CCF3730100406F@EVS6.its.caregroup.org>
References: <C44AB05AAC2D694A907A91DA40CCF3730100406F@EVS6.its.caregroup.org>
Message-ID: <1204254216.3272.15.camel@technetium.msp.redhat.com>

On Thu, 2008-02-28 at 10:28 -0500, rhurst at bidmc.harvard.edu wrote:
> ioctl(3, 0x472d, 0x7fbfffe300)          = -1 ENOMEM (Cannot allocate 

Hi Robert,

The gfs_tool does most of its work using ioctl calls to the gfs kernel
module.  Often, it tries to allocate and pass in a huge buffer to make
sure it doesn't ask for more than the kernel needs to respond with.

In some cases, it doesn't need to allocate such a big buffer.
I fixed "gfs_tool counters" for a similar ENOMEM problem with
bugzilla record 229461 about a year ago.  (I don't know if that bug
record is public or locked so you may not be able to access it, which
is out of my control--sorry).

I should probably go through all the other gfs_tool functions, including
the two you mentioned, and figure out their minimum memory requirements
and change the code so it doesn't ask for so much memory.

Perhaps you can open up a bugzilla record so I can schedule this work?
Also, you didn't say whether you're on RHEL4/Centos4/similar, or
RHEL5/Centos5/similar.

Regards,

Bob Peterson
Red Hat GFS




From balajisundar at midascomm.com  Fri Feb 29 12:28:00 2008
From: balajisundar at midascomm.com (Balaji)
Date: Fri, 29 Feb 2008 17:58:00 +0530
Subject: [Linux-cluster] Ethernet Channel Bonding Configuration in RHEL
	Cluster Suite Setup
Message-ID: <47C7FA50.8080202@midascomm.com>

Dear All,

    I am new in RHEL Cluster Suite.

    I have Configure Cluster and Rebooted the system and then cluster 
become active in primary node and other node as passive and member 
status becomes Online for both the cluster nodes
 
    In Cluster Suite i am monitoring the resources as scripts files and 
ipaddress and During network failure one of the node or both the nodes 
are removed from the cluster member and All the resources are stopped 
and then rebooted the system only both the system are joining into the 
cluster member.

    I have followed the RHEL Cluster Suite Configuration document 
"rh-cs-en-4.pdf" and I have found out Ethernet Channel Bonding in Each 
Cluster Nodes will avoid the network single point failure in cluster 
system.
 
    I have configured the Ethernet Channel Bonding with mode as 
active-backup without fence device.

    Ethernet Channel Bonding Configuration Details are
    1. In " /etc/modprobe.conf" file added the following bonding driver 
support  
       alias bond0 bonding
       options bonding miimon=100 mode=1
    2. Edited the "/etc/sysconfig/network-scripts/ifcfg-eth0" file added 
the following configuration
       DEVICE=eth0
       USERCTL=no
       ONBOOT=yes
       MASTER=bond0
       SLAVE=yes
       BOOTPROTO=none
    3. Edited the "/etc/sysconfig/network-scripts/ifcfg-eth1" file added 
the following configuration
       DEVICE=eth1
       USERCTL=no
       ONBOOT=yes
       MASTER=bond0
       SLAVE=yes
       BOOTPROTO=none
    4. Created a  network  script for the bonding device 
"/etc/sysconfig/network-scripts/ifcfg-bond0"
        DEVICE=bond0
        USERCTL=no
        ONBOOT=yes
        IPADDR=192.168.13.109
        NETMASK=255.255.255.0
        GATEWAY=192.168.13.1
    5. Reboot the system for the changes to take effect.
    6. Configure Ethernet Channel Bonding
    7. Rebooted the system and then cluster services are active on both 
the nodes and member status of current node is Online and other node as 
Offline

    I need clarification about Ethernet Channel Bonding will work with 
Fence Device or not.

    I am not sure why this is happening. Can some one throw light on this.

Regards
-S.Balaji




       




















From l.dardini at comune.prato.it  Fri Feb 29 12:51:05 2008
From: l.dardini at comune.prato.it (Leandro Dardini)
Date: Fri, 29 Feb 2008 13:51:05 +0100
Subject: R: [Linux-cluster] Ethernet Channel Bonding Configuration in
	RHELCluster Suite Setup
In-Reply-To: <47C7FA50.8080202@midascomm.com>
References: <47C7FA50.8080202@midascomm.com>
Message-ID: <6F861500A5092B4C8CD653DE20A4AA0D511B91@exchange3.comune.prato.local>

 

> -----Messaggio originale-----
> Da: linux-cluster-bounces at redhat.com 
> [mailto:linux-cluster-bounces at redhat.com] Per conto di Balaji
> Inviato: venerd? 29 febbraio 2008 13.28
> A: ClusterGrp
> Oggetto: [Linux-cluster] Ethernet Channel Bonding 
> Configuration in RHELCluster Suite Setup
> 
> Dear All,
> 
>     I am new in RHEL Cluster Suite.
> 
>     I have Configure Cluster and Rebooted the system and then 
> cluster become active in primary node and other node as 
> passive and member status becomes Online for both the cluster nodes
>  
>     In Cluster Suite i am monitoring the resources as scripts 
> files and ipaddress and During network failure one of the 
> node or both the nodes are removed from the cluster member 
> and All the resources are stopped and then rebooted the 
> system only both the system are joining into the cluster member.
> 
>     I have followed the RHEL Cluster Suite Configuration 
> document "rh-cs-en-4.pdf" and I have found out Ethernet 
> Channel Bonding in Each Cluster Nodes will avoid the network 
> single point failure in cluster system.
>  
>     I have configured the Ethernet Channel Bonding with mode 
> as active-backup without fence device.
> 
>     Ethernet Channel Bonding Configuration Details are
>     1. In " /etc/modprobe.conf" file added the following 
> bonding driver support  
>        alias bond0 bonding
>        options bonding miimon=100 mode=1
>     2. Edited the "/etc/sysconfig/network-scripts/ifcfg-eth0" 
> file added the following configuration
>        DEVICE=eth0
>        USERCTL=no
>        ONBOOT=yes
>        MASTER=bond0
>        SLAVE=yes
>        BOOTPROTO=none
>     3. Edited the "/etc/sysconfig/network-scripts/ifcfg-eth1" 
> file added the following configuration
>        DEVICE=eth1
>        USERCTL=no
>        ONBOOT=yes
>        MASTER=bond0
>        SLAVE=yes
>        BOOTPROTO=none
>     4. Created a  network  script for the bonding device 
> "/etc/sysconfig/network-scripts/ifcfg-bond0"
>         DEVICE=bond0
>         USERCTL=no
>         ONBOOT=yes
>         IPADDR=192.168.13.109
>         NETMASK=255.255.255.0
>         GATEWAY=192.168.13.1
>     5. Reboot the system for the changes to take effect.
>     6. Configure Ethernet Channel Bonding
>     7. Rebooted the system and then cluster services are 
> active on both the nodes and member status of current node is 
> Online and other node as Offline
> 
>     I need clarification about Ethernet Channel Bonding will 
> work with Fence Device or not.
> 
>     I am not sure why this is happening. Can some one throw 
> light on this.
> 
> Regards
> -S.Balaji
> 

When there is a network failure, each member cannot reach the other one. Each member trigger the fence script to turn off the other one. Unfortunately the network is off, so the low level network interface take the fence script connection request in mind and wait for the network to come up. When the network is again available, each member can reach the fencing device and turn off the other. There is no simple way to avoid this. You can make network near 100% fault proof using bond device or you can use a STONITH fencing device, so the first member who regain network prevents the other to fence, or you can use three members. In a network failure no one have the quorum to fence the others.

Leandro



From p.elmers at gmx.de  Fri Feb 29 14:05:23 2008
From: p.elmers at gmx.de (Peter)
Date: Fri, 29 Feb 2008 15:05:23 +0100
Subject: [Linux-cluster] probe a special port and fence according to the
	result
Message-ID: <99FC135E-6367-41B5-B6B5-AA1FEC5D9833@gmx.de>

Hi!

I am planning to test a service for availability and if the service is  
not available anymore, fence the node and start the service on another  
node. Therefore, i need a clue how to probe a port with system tools.
Sure, with telnet there is a possibility to check. But i have no idea  
to avoid the interactivity. So it is too difficult for me to implement  
and usually not allowed in this environment.

On Solaris, there is the "ping -p" command to test the availability of  
a application waiting on a port. But for Redhat, i have no clue.

Could you please help?


Peter



From lhh at redhat.com  Fri Feb 29 14:20:23 2008
From: lhh at redhat.com (Lon Hohberger)
Date: Fri, 29 Feb 2008 09:20:23 -0500
Subject: [Linux-cluster] probe a special port and fence according to
	the result
In-Reply-To: <99FC135E-6367-41B5-B6B5-AA1FEC5D9833@gmx.de>
References: <99FC135E-6367-41B5-B6B5-AA1FEC5D9833@gmx.de>
Message-ID: <20080229142023.GD6571@redhat.com>

On Fri, Feb 29, 2008 at 03:05:23PM +0100, Peter wrote:
> Hi!
>
> I am planning to test a service for availability and if the service is not 
> available anymore, fence the node and start the service on another node. 
> Therefore, i need a clue how to probe a port with system tools.
> Sure, with telnet there is a possibility to check. But i have no idea to 
> avoid the interactivity. So it is too difficult for me to implement and 
> usually not allowed in this environment.
>
> On Solaris, there is the "ping -p" command to test the availability of a 
> application waiting on a port. But for Redhat, i have no clue.
>
> Could you please help?

Net Cat? (man nc ) ?

-- 
Lon Hohberger - Software Engineer - Red Hat, Inc.



From lhh at redhat.com  Fri Feb 29 14:28:45 2008
From: lhh at redhat.com (Lon Hohberger)
Date: Fri, 29 Feb 2008 09:28:45 -0500
Subject: [Linux-cluster] Ethernet Channel Bonding Configuration in RHEL
	Cluster Suite Setup
In-Reply-To: <47C7FA50.8080202@midascomm.com>
References: <47C7FA50.8080202@midascomm.com>
Message-ID: <20080229142845.GE6571@redhat.com>

On Fri, Feb 29, 2008 at 05:58:00PM +0530, Balaji wrote:
>    2. Edited the "/etc/sysconfig/network-scripts/ifcfg-eth0" file added the 
> following configuration
>    3. Edited the "/etc/sysconfig/network-scripts/ifcfg-eth1" file added the 
> following configuration
>    4. Created a  network  script for the bonding device 
> "/etc/sysconfig/network-scripts/ifcfg-bond0"

This looks correct.  What does your cable setup look like?

 +------------------------------------------------+
 |                   switch                       |
 +------------------------------------------------+
   |            |                |            |
  +--------------+              +--------------+
  |eth0      eth1|              |eth0      eth1|
  +--------------+              +--------------+

Also, what does cluster.conf look like? 


>    I am not sure why this is happening. Can some one throw light on this.

Does ping work?  If so, then it could be a cluster configuration issue.

-- 
Lon Hohberger - Software Engineer - Red Hat, Inc.



From bpkroth at wisc.edu  Fri Feb 29 15:01:29 2008
From: bpkroth at wisc.edu (Brian Kroth)
Date: Fri, 29 Feb 2008 09:01:29 -0600
Subject: [Linux-cluster] probe a special port and fence according to	the
	result
In-Reply-To: <99FC135E-6367-41B5-B6B5-AA1FEC5D9833@gmx.de>
References: <99FC135E-6367-41B5-B6B5-AA1FEC5D9833@gmx.de>
Message-ID: <20080229150129.GC29539@wisc.edu>

Peter <p.elmers at gmx.de> 2008-02-29 15:05:
> Hi!
>
> I am planning to test a service for availability and if the service is not 
> available anymore, fence the node and start the service on another node. 
> Therefore, i need a clue how to probe a port with system tools.
> Sure, with telnet there is a possibility to check. But i have no idea to 
> avoid the interactivity. So it is too difficult for me to implement and 
> usually not allowed in this environment.
>
> On Solaris, there is the "ping -p" command to test the availability of a 
> application waiting on a port. But for Redhat, i have no clue.
>
> Could you please help?

nmap -p will test that the port is responding, but not that the
application on the other end is actually doing what it's supposed to be.

Brian
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/x-pkcs7-signature
Size: 2192 bytes
Desc: not available
URL: <http://listman.redhat.com/archives/linux-cluster/attachments/20080229/627ab91f/attachment.bin>

From p.elmers at gmx.de  Fri Feb 29 15:14:28 2008
From: p.elmers at gmx.de (Peter)
Date: Fri, 29 Feb 2008 16:14:28 +0100
Subject: [Linux-cluster] probe a special port and fence according to the
	result
In-Reply-To: <20080229142023.GD6571@redhat.com>
References: <99FC135E-6367-41B5-B6B5-AA1FEC5D9833@gmx.de>
	<20080229142023.GD6571@redhat.com>
Message-ID: <40846CEC-F42D-496E-93DE-6F096DB4DF6B@gmx.de>

Hi Lon!

"nc -z -w3 <IP> <Port>" hit the spot!

Thanks!


Am 29.02.2008 um 15:20 schrieb Lon Hohberger:

> On Fri, Feb 29, 2008 at 03:05:23PM +0100, Peter wrote:
>> Hi!
>>
>> I am planning to test a service for availability and if the service  
>> is not
>> available anymore, fence the node and start the service on another  
>> node.
>> Therefore, i need a clue how to probe a port with system tools.
>> Sure, with telnet there is a possibility to check. But i have no  
>> idea to
>> avoid the interactivity. So it is too difficult for me to implement  
>> and
>> usually not allowed in this environment.
>>
>> On Solaris, there is the "ping -p" command to test the availability  
>> of a
>> application waiting on a port. But for Redhat, i have no clue.
>>
>> Could you please help?
>
> Net Cat? (man nc ) ?
>
> -- 
> Lon Hohberger - Software Engineer - Red Hat, Inc.
>
> --
> Linux-cluster mailing list
> Linux-cluster at redhat.com
> https://www.redhat.com/mailman/listinfo/linux-cluster



From isplist at logicore.net  Fri Feb 29 15:27:46 2008
From: isplist at logicore.net (isplist at logicore.net)
Date: Fri, 29 Feb 2008 09:27:46 -0600
Subject: [Linux-cluster] Redundant (multipath)/Replicating NFS
In-Reply-To: <alpine.LRH.1.00.0802201013180.24399@skynet.shatteredsilicon.net>
Message-ID: <200822992746.677421@leena>

Anyone know of any RAID SATA chassis that would hold (at least) four 1TB 
drives which could either hang on the network or behind the aggregator? 

I've found that there is also ATA-over-Ethernet out there but it's pretty 
pricey up front. I need something CHEAP initially for testing and evaluate.

Basically, the FC drives and chassis eat up an awful lot of power. I think I 
could cut my costs down drastically with the above.

Mike





From gordan at bobich.net  Fri Feb 29 15:33:47 2008
From: gordan at bobich.net (gordan at bobich.net)
Date: Fri, 29 Feb 2008 15:33:47 +0000 (GMT)
Subject: [Linux-cluster] Redundant (multipath)/Replicating NFS
In-Reply-To: <200822992746.677421@leena>
References: <200822992746.677421@leena>
Message-ID: <alpine.LRH.1.00.0802291532150.16751@skynet.shatteredsilicon.net>

On Fri, 29 Feb 2008, isplist at logicore.net wrote:

> Anyone know of any RAID SATA chassis that would hold (at least) four 1TB
> drives which could either hang on the network or behind the aggregator?
>
> I've found that there is also ATA-over-Ethernet out there but it's pretty
> pricey up front. I need something CHEAP initially for testing and evaluate.
>
> Basically, the FC drives and chassis eat up an awful lot of power. I think I
> could cut my costs down drastically with the above.

Getting a bit off topic here, but look into building your own. It would 
likely be the cheapest option. Make the box export directly what you need 
over IP, be it ATAoE, iSCSI or NFS.

Gordan



From isplist at logicore.net  Fri Feb 29 15:40:36 2008
From: isplist at logicore.net (isplist at logicore.net)
Date: Fri, 29 Feb 2008 09:40:36 -0600
Subject: [Linux-cluster] Redundant (multipath)/Replicating NFS
In-Reply-To: <alpine.LRH.1.00.0802291532150.16751@skynet.shatteredsilicon.net>
Message-ID: <200822994036.018242@leena>

> Getting a bit off topic here, but look into building your own. It would

You're right, end of thread :). Lot's of valuable information noted and 
appreciated. 

Mike





From rhurst at bidmc.harvard.edu  Fri Feb 29 15:44:41 2008
From: rhurst at bidmc.harvard.edu (rhurst at bidmc.harvard.edu)
Date: Fri, 29 Feb 2008 10:44:41 -0500
Subject: [Linux-cluster] gfs_tool: Cannot allocate memory
In-Reply-To: <1204254216.3272.15.camel@technetium.msp.redhat.com>
References: <C44AB05AAC2D694A907A91DA40CCF3730100406F@EVS6.its.caregroup.org>
	<1204254216.3272.15.camel@technetium.msp.redhat.com>
Message-ID: <1204299881.7409.20.camel@WSBID06223.bidmc.harvard.edu>

Excellent, thanks Bob!  It is a RHEL AS 4.5 cluster running on AMD64
Opteron.
I have opened up bugzilla #435469


On Thu, 2008-02-28 at 21:03 -0600, Bob Peterson wrote:

> On Thu, 2008-02-28 at 10:28 -0500, rhurst at bidmc.harvard.edu wrote:
> > ioctl(3, 0x472d, 0x7fbfffe300)          = -1 ENOMEM (Cannot allocate 
> 
> Hi Robert,
> 
> The gfs_tool does most of its work using ioctl calls to the gfs kernel
> module.  Often, it tries to allocate and pass in a huge buffer to make
> sure it doesn't ask for more than the kernel needs to respond with.
> 
> In some cases, it doesn't need to allocate such a big buffer.
> I fixed "gfs_tool counters" for a similar ENOMEM problem with
> bugzilla record 229461 about a year ago.  (I don't know if that bug
> record is public or locked so you may not be able to access it, which
> is out of my control--sorry).
> 
> I should probably go through all the other gfs_tool functions, including
> the two you mentioned, and figure out their minimum memory requirements
> and change the code so it doesn't ask for so much memory.
> 
> Perhaps you can open up a bugzilla record so I can schedule this work?
> Also, you didn't say whether you're on RHEL4/Centos4/similar, or
> RHEL5/Centos5/similar.
> 
> Regards,
> 
> Bob Peterson
> Red Hat GFS
> 
> 
> --
> Linux-cluster mailing list
> Linux-cluster at redhat.com
> https://www.redhat.com/mailman/listinfo/linux-cluster
> 


Robert Hurst, Sr. Cach? Administrator
Beth Israel Deaconess Medical Center
1135 Tremont Street, REN-7
Boston, Massachusetts   02120-2140
617-754-8754 ? Fax: 617-754-8730 ? Cell: 401-787-3154
Any technology distinguishable from magic is insufficiently advanced.


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://listman.redhat.com/archives/linux-cluster/attachments/20080229/a3633b36/attachment.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 3227 bytes
Desc: not available
URL: <http://listman.redhat.com/archives/linux-cluster/attachments/20080229/a3633b36/attachment.p7s>

From Alexandre.Racine at mhicc.org  Fri Feb 29 19:00:34 2008
From: Alexandre.Racine at mhicc.org (Alexandre Racine)
Date: Fri, 29 Feb 2008 14:00:34 -0500
Subject: [Linux-cluster] using fence_vmware - help
References: <200822992746.677421@leena>
	<alpine.LRH.1.00.0802291532150.16751@skynet.shatteredsilicon.net>
Message-ID: <C43CF0825BF59D4FBC1F6A2AF45EB88D6D13C4@cumulonimbus.RG.local>

Hi all,

I am trying to use fence_vmware and searchs with "fence_vmware vmperl" did not really got success.

I updated cpan and added some basic modules like LWP, but could not find any vmperl module. So after some search I found the binairies from vmware here http://www.vmware.com/support/developer/viperltoolkit/ and installed in the default folder [/usr/bin] but I still get the error message below. Is there something that I missed? Thanks.


SERVER2 vmware-viperl-distrib # /sbin/fence_vmware -h
Can't locate VMware/VmPerl.pm in @INC (@INC contains: /etc/perl /usr/lib/perl5/vendor_perl/5.8.8/i686-linux /usr/lib/perl5/vendor_perl/5.8.8 /usr/lib/perl5/vendor_perl /usr/lib/perl5/site_perl/5.8.8/i686-linux /usr/lib/perl5/site_perl/5.8.8 /usr/lib/perl5/site_perl /usr/lib/perl5/5.8.8/i686-linux /usr/lib/perl5/5.8.8 /usr/local/lib/site_perl .) at /sbin/fence_vmware line 20.
BEGIN failed--compilation aborted at /sbin/fence_vmware line 20.



Alexandre Racine
514-461-1300 poste 3304
alexandre.racine at mhicc.org

-------------- next part --------------
A non-text attachment was scrubbed...
Name: winmail.dat
Type: application/ms-tnef
Size: 2914 bytes
Desc: not available
URL: <http://listman.redhat.com/archives/linux-cluster/attachments/20080229/c2679822/attachment.bin>

From p.elmers at gmx.de  Fri Feb 29 19:47:02 2008
From: p.elmers at gmx.de (Peter)
Date: Fri, 29 Feb 2008 20:47:02 +0100
Subject: [Linux-cluster] Heuristics without quorum disk
Message-ID: <762AE60C-0850-4E41-B847-29848C38F3BB@gmx.de>

Hi!

I try to involve another failure detection method than heartbeat for  
failover. For example "nc -z -w3 <IP> <Port>" as a check wether the  
service behind the port is available.

The only thing i found is "heuristic program" from QDisk/quorumd. As i  
do not have a qourum disk, i am a little bit confused how to implement  
such a detection.

Can you please help me?

Thanks,

Peter



From jbrassow at redhat.com  Fri Feb 29 20:56:38 2008
From: jbrassow at redhat.com (Jonathan Brassow)
Date: Fri, 29 Feb 2008 14:56:38 -0600
Subject: [Linux-cluster] HA LVM
In-Reply-To: <5b65f1b10802281745n748afc21u99c93f9069f1239c@mail.gmail.com>
References: <5b65f1b10802271447s69f736a2gec497abd1ec06317@mail.gmail.com>
	<541A6F37-F850-42D8-B030-9C694453413E@redhat.com>
	<5b65f1b10802281745n748afc21u99c93f9069f1239c@mail.gmail.com>
Message-ID: <9CAA1922-44FD-4244-9B45-C6E0B51A1E67@redhat.com>


On Feb 28, 2008, at 7:45 PM, Jorge Palma wrote:
> Of course, in fact we found other problems, such as the agent of lvm
> read parameters name and the name of volume wrongly
>
> In any event, the most common clustering services working properly

What happens if you simply do 'clusvcadm -e <service>'?  Does it start- 
up then?  And if you use clusvcadm to relocate teh service to the  
other node?

  brassow