[Ocfs2-users] Problems with volumes coming from RHEL5 going to OEL6

[Ulf Zimmermann]

We have a production cluster of 6 nodes, which are currently running RHEL 5.8 with OCFS2 1.4.10. We snapclone these volumes to multiple destinations, one of them is a RHEL4 machine with OCFS2 1.2.9. Because of that the volumes are set so that we can read them there.

We are now trying to bring up a new server, this one has OEL 6.3 on it and it comes with OCFS2 1.8.0 and tools 1.8.0-10. I can use tunefs.ocfs2 -cloned-volume to reset the UUID, but when I try to change the label I get:

[root at co-db03 ulf]# tunefs.ocfs2 -L /export/backuprecovery.AUCP /dev/mapper/aucp_data_bk_2_x
tunefs.ocfs2: Invalid name for a cluster while opening device "/dev/mapper/aucp_data_bk_2_x"

fsck.ocfs2 core dumps with the following, I also filed a bug on Bugzilla for that:

[root at co-db03 ulf]# fsck.ocfs2 /dev/mapper/aucp_data_bk_2_x
fsck.ocfs2 1.8.0
*** glibc detected *** fsck.ocfs2: double free or corruption (fasttop): 0x000000000197f320 ***
======= Backtrace: =========
/lib64/libc.so.6[0x3656475366]
fsck.ocfs2[0x434c31]
fsck.ocfs2[0x403bc2]
/lib64/libc.so.6(__libc_start_main+0xfd)[0x365641ecdd]
fsck.ocfs2[0x402879]
======= Memory map: ========
00400000-00450000 r-xp 00000000 fc:00 12489                              /sbin/fsck.ocfs2
0064f000-00651000 rw-p 0004f000 fc:00 12489                              /sbin/fsck.ocfs2
00651000-00652000 rw-p 00000000 00:00 0
00850000-00851000 rw-p 00050000 fc:00 12489                              /sbin/fsck.ocfs2
0197e000-0199f000 rw-p 00000000 00:00 0                                  [heap]
3655c00000-3655c20000 r-xp 00000000 fc:00 8797                           /lib64/ld-2.12.so
3655e1f000-3655e20000 r--p 0001f000 fc:00 8797                           /lib64/ld-2.12.so
3655e20000-3655e21000 rw-p 00020000 fc:00 8797                           /lib64/ld-2.12.so
3655e21000-3655e22000 rw-p 00000000 00:00 0
3656400000-3656589000 r-xp 00000000 fc:00 8798                           /lib64/libc-2.12.so
3656589000-3656788000 ---p 00189000 fc:00 8798                           /lib64/libc-2.12.so
3656788000-365678c000 r--p 00188000 fc:00 8798                           /lib64/libc-2.12.so
365678c000-365678d000 rw-p 0018c000 fc:00 8798                           /lib64/libc-2.12.so
365678d000-3656792000 rw-p 00000000 00:00 0
3659c00000-3659c16000 r-xp 00000000 fc:00 8802                           /lib64/libgcc_s-4.4.6-20120305.so.1
3659c16000-3659e15000 ---p 00016000 fc:00 8802                           /lib64/libgcc_s-4.4.6-20120305.so.1
3659e15000-3659e16000 rw-p 00015000 fc:00 8802                           /lib64/libgcc_s-4.4.6-20120305.so.1
3d3e800000-3d3e817000 r-xp 00000000 fc:00 12028                          /lib64/libpthread-2.12.so
3d3e817000-3d3ea17000 ---p 00017000 fc:00 12028                          /lib64/libpthread-2.12.so
3d3ea17000-3d3ea18000 r--p 00017000 fc:00 12028                          /lib64/libpthread-2.12.so
3d3ea18000-3d3ea19000 rw-p 00018000 fc:00 12028                          /lib64/libpthread-2.12.so
3d3ea19000-3d3ea1d000 rw-p 00000000 00:00 0
3e26600000-3e26603000 r-xp 00000000 fc:00 426                            /lib64/libcom_err.so.2.1
3e26603000-3e26802000 ---p 00003000 fc:00 426                            /lib64/libcom_err.so.2.1
3e26802000-3e26803000 r--p 00002000 fc:00 426                            /lib64/libcom_err.so.2.1
3e26803000-3e26804000 rw-p 00003000 fc:00 426                            /lib64/libcom_err.so.2.1
7fb063711000-7fb063714000 rw-p 00000000 00:00 0
7fb06371d000-7fb063720000 rw-p 00000000 00:00 0
7fffd5b95000-7fffd5bb6000 rw-p 00000000 00:00 0                          [stack]
7fffd5bc5000-7fffd5bc6000 r-xp 00000000 00:00 0                          [vdso]
ffffffffff600000-ffffffffff601000 r-xp 00000000 00:00 0                  [vsyscall]
Abort (core dumped)

I think one of the main question is what is the "Invalid name for a cluster while trying to join the group" or "Invalid name for a cluster while opening device". I am pretty sure that /etc/sysconfig/o2cb and /etc/ocfs2/cluster.conf is correct.

Ulf.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://oss.oracle.com/pipermail/ocfs2-users/attachments/20130621/3e16acf2/attachment.html