CentOS 5.4 GFS2 ... Good God Please help!

[CommonCent]

I apoligize in advance for my lack of understanding of CentOS in general ... I am a noob at it and am learning along the way. I have looked for a remedy on other forums and google, but havent' been able to find the answer. I have a 3 node cluster that was functioning great until I decided to go offline for awhile. My config is as follows;

node 2: vh1
node 3: vh2
node 4: vh6
All nodes connect to a common shared area on an iscsi device (vguests_root)

Currently vh2 and vh6 connect great, however since putting the machines back online I can no longer connect with vh1. A dmesg command on vh1 reveals the following;
GFS2: fsid=: Trying to join cluster "lock_dlm", "Cluster1:vguest_roots"
GFS2: fsid=Cluster1:vguest_roots.2: Joined cluster. Now mounting FS...
GFS2: fsid=Cluster1:vguest_roots.2: can't mount journal #2
GFS2: fsid=Cluster1:vguest_roots.2: there are only 2 journals (0 - 1)

and a group_tool on vh1 returned:
type level name id state
fence 0 default 00000000 none
[2 3 4]
dlm 1 clvmd 00020004 none
[2 3 4]
dlm 1 rgmanager 00010004 none
[2 3 4]

a group_tool on vh2 and vh6 returned
type level name id state
fence 0 default 00000000 none
[2 3 4]
dlm 1 rgmanager 00010004 none
[2 3 4]
dlm 1 clvmd 00020004 none
[2 3 4]
dlm 1 vguest_roots 00020003 none
[3 4]
gfs 2 vguest_roots 00010003 none
[3 4]

All members of the cluster show up in Conga, but as you can see it's definitely not working the way it should.
Any help would be appreciated!

[Conway]

From looking at the message it's given;

GFS2: fsid=: Trying to join cluster "lock_dlm", "Cluster1:vguest_roots"
GFS2: fsid=Cluster1:vguest_roots.2: Joined cluster. Now mounting FS...
GFS2: fsid=Cluster1:vguest_roots.2: can't mount journal #2
GFS2: fsid=Cluster1:vguest_roots.2: there are only 2 journals (0 - 1)

It sounds like you may have issues with the journals. Unmount the filesystem on all the nodes and run an fsck.gfs2 with the verbose options and see what's going on. If that doesn't help then get the filesystem mounted on a single node, copy all your data and recreate the partition.

Cheers
Gavin