Ocfs2 users - Jun 2013 - o2cb strange behaviour; can't mount volume

Hi,

I wonder if I have discovered an openSUSE special or if someone shares
my problem...

I try to install an OCFS2 volume with an openSUSE 12.3 host. When I
create /etc/ocfs2/cluster.conf manually, o2cb refuses to read it. So I
removed it and startet configuration with o2cb (hostname is klops):

---snip---
klops:~ # o2cb add-cluster OCFS2WERNAS
klops:~ # o2cb heartbeat-mode OCFS2WERNAS global
klops:~ # o2cb add-heartbeat OCFS2WERNAS /dev/disk/by-label/wernasocfs2
klops:~ # o2cb start-heartbeat OCFS2WERNAS
Global heartbeat started
klops:~ # o2cb list-heartbeats OCFS2WERNAS
heartbeat:
        region = ACA40A8B09D242EA883765E68035E232
        cluster = OCFS2WERNAS
klops:~ # o2cb add-node --ip 192.168.2.55 --number 0 OCFS2WERNAS klops
klops:~ # o2cb add-node --ip 192.168.2.77 --number 1 OCFS2WERNAS sieben
klops:~ # o2cb add-node --ip 192.168.2.44 --number 2 OCFS2WERNAS thinkt51
klops:~ # o2cb list-cluster OCFS2WERNAS
heartbeat:
        region = 5F1672E500D94138BF3C4F517813A336
        cluster = OCFS2WERNAS

node:
        number = 0
        name = klops
        ip_address = 192.168.2.55
        ip_port = 7777
        cluster = OCFS2WERNAS

cluster:
        node_count = 3
        heartbeat_mode = global
        name = OCFS2WERNAS
---pins---

That's it. The cluster.conf contains only 1 node, but the node count is
set to 3.

Additional info:

---snip---
klops:~ # o2info --mkfs /dev/sdc1
-N 16 -J size=268435456 -b 4096 -C 4096 --fs-features
backup-super,strict-journal-super,sparse,extended-slotmap,inline-data,xattr,indexed-dirs,refcount,discontig-bg,clusterinfo,unwritten
-L wernasocfs2

klops:~ # o2info --volinfo /dev/sdc1
       Label: wernasocfs2
        UUID: 5F1672E500D94138BF3C4F517813A336
  Block Size: 4096
Cluster Size: 4096
  Node Slots: 16
    Features: backup-super strict-journal-super sparse extended-slotmap
    Features: inline-data xattr indexed-dirs refcount discontig-bg
clusterinfo
    Features: unwritten

klops:~ # mount /zdisk/ocfs2/
mount.ocfs2: Invalid argument while mounting /dev/sdc1 on /zdisk/ocfs2.
Check 'dmesg' for more information on this error.
---pins---

3 lines in the dmesg output for this time stamp:

[24882.420339] (mount.ocfs2,18895,0):ocfs2_verify_userspace_stack:876
ERROR: cluster stack passed to mount, but this filesystem does not
support it
[24882.420400] ocfs2: Unmounting device (8,33) on (node 0)
[24882.420417] (mount.ocfs2,18895,0):ocfs2_fill_super:1230 ERROR: status
= -22

Installed packages (with all dependencies):
ocfs2-tools-1.8.2-4.4.1.x86_64
ocfs2-tools-devel-1.8.2-4.4.1.x86_64
ocfs2-tools-o2cb-1.8.2-4.4.1.x86_64
ocfs2console-1.8.2-4.4.1.x86_64

Also, there are two bugzilla entries for openSUSE:
<https://bugzilla.novell.com/show_bug.cgi?id=822190> and
<https://bugzilla.novell.com/show_bug.cgi?id=827479>.

What's going wrong here?

Regards,
Werner

[29.06.2013 20:17] [Werner Flamme]:
> klops:~ # o2cb list-heartbeats OCFS2WERNAS
I gave the wrong output! The correct output is:

heartbeat:
        region = 5F1672E500D94138BF3C4F517813A336
        cluster = OCFS2WERNAS

And in the meantime, I tried another command to add a node to cluster.conf:

---snip---
klops:~ # o2cb_ctl -C -n sieben -t node -a number=1 -a
ip_address=192.168.2.77 -a ip_port=7777 -a cluster=OCFS2WERNAS
klops:~ # o2cb list-cluster OCFS2WERNAS
heartbeat:
        region = 5F1672E500D94138BF3C4F517813A336
        cluster = OCFS2WERNAS

node:
        number = 0
        name = klops
        ip_address = 192.168.2.55
        ip_port = 7777
        cluster = OCFS2WERNAS

cluster:
        node_count = 4
        heartbeat_mode = global
        name = OCFS2WERNAS
---pins---

So, again the "node count" is increased, but no additional node in the
config file.

I put in on my website,
<http://www.wernerflamme.net/doku.php?id=comp:en:comp:ocfs2os123>

Regards,
Werner

Am 29.06.2013 20:17, schrieb Werner Flamme:
> Hi,
>
> I wonder if I have discovered an openSUSE special or if someone shares
> my problem...
I still do not know this, but on my SUSE bugzilla entry, I now read that 
this will be fixed with the next maintenance release.

Regards,
Werner