Re: [Ocfs2-users] Multiple LUNs and ocfs2
Hi, I would recommend you to check Oracle VM 2.2 as it have the capabilities to use directly multipath block devices, and assign them to guest VMs. This way you could bypass ocfs2. Anyway if you MUST provide 6*100 G to you guest VM, you must either have 6*100 virtual disks as OCFS2 files, or have 6*100 logical volumes in the host environment (which is not recommended because the LVM is not cluster aware yet in OVM), or 6*100G partitions from a single SAN LUN, or 6*100G different SAN luns. After you provide 6*100G block devices to you guest VM, I would use ASM if I want a database on them... HTH, Mihail Daskalov, Technology Manager Software Development, TechnoLogica -Original Message- From: ocfs2-users-boun...@oss.oracle.com [mailto:ocfs2-users-boun...@oss.oracle.com] On Behalf Of Bill Ranck Sent: Tuesday, October 20, 2009 10:33 PM To: ocfs2-users@oss.oracle.com Subject: [Ocfs2-users] Multiple LUNs and ocfs2 Hello folks, I am a newbie with ocfs2 and Oracle VM in general, but I'm slowly figuring things out. I have installed ovm server on 2 blades in an IBM bladecenter, and I have gotten ocfs2 working such that both blades are mounting /OVS from a shared SAN LUN. So far, so good. I will be installing a guest VM on one of the blades with the idea that we can do live migration if/when needed. The database that will be set up there will need to use 6 X 100G LUNs from the SAN. What is the best way to aggregate these LUNs for that purpose? I've got them visible as /dev/dm-2 through /dev/dm-7 on both systems. Do I use LVM at the hypervisor level to combine them into one big disk group and volume, then use mkfs.ocfs2 on that? Or is there a better way? I see, with a quick look through of the archives from this list, that ocfs2 can not aggregate the LUNs itself. I'm just hoping for a pointer in the right direction so I don't shoot myself in the foot by choosing the wrong thing early in the project. -- Bill Ranck Blacksburg, Va. 540-231-3951 ___ Ocfs2-users mailing list Ocfs2-users@oss.oracle.com http://oss.oracle.com/mailman/listinfo/ocfs2-users smime.p7s Description: S/MIME cryptographic signature ___ Ocfs2-users mailing list Ocfs2-users@oss.oracle.com http://oss.oracle.com/mailman/listinfo/ocfs2-users
Re: [Ocfs2-users] Unable to mount cluster on CentOS and Ubunut at the same time
I think I found the core issue. The DLM on Centos is running 1.4.1, but on Ubuntu its 1.3.3, I can't seem to find any packages for debian or Ubuntu that upgrade the kernel modules to 1.4 series. Does anyone know how I can do this? David From: ocfs2-users-boun...@oss.oracle.com [mailto:ocfs2-users-boun...@oss.oracle.com] On Behalf Of David Murphy Sent: Wednesday, October 21, 2009 10:46 AM To: ocfs2-users@oss.oracle.com Subject: [Ocfs2-users] Unable to mount cluster on CentOS and Ubunut at the same time Web2 is out Ubuntu Node and Web1 is a new CentOS 5.3 Node I put 1.4.1-1 on CentOS to match the one on the Ubuntu nodes. Also I copied the o2cb configs from the Ubuntu node to the CentOS one. O2CB starts just fine , but I get these errors when I try to start the ocfs2 service or mount the partition: (6203,0):o2net_check_handshake:1205 node deploy (num 5) at 192.168.102.12: advertised net protocol version 8 but 11 is required, disconnecting (6203,0):o2net_check_handshake:1205 node deploy (num 5) at 192.168.102.12: advertised net protocol version 8 but 11 is required, disconnecting Does anyone have any ideas what's going on? Full Dmesg, rpm, dpkg output is below: OCFS2 Node Manager 1.4.1 Wed Jan 21 11:39:16 PST 2009 (build 304d9ff0c301f79f846e3cc423c30674) OCFS2 DLM 1.4.1 Wed Jan 21 11:39:16 PST 2009 (build 96988c7961cf38309cc33396bb27b400) OCFS2 DLMFS 1.4.1 Wed Jan 21 11:39:16 PST 2009 (build 96988c7961cf38309cc33396bb27b400) OCFS2 User DLM kernel interface loaded (6203,0):o2net_check_handshake:1205 node web2 (num 2) at 192.168.102.41: advertised net protocol version 8 but 11 is required, disconnecting (6203,0):o2net_check_handshake:1205 node web3 (num 3) at 192.168.102.42: advertised net protocol version 8 but 11 is required, disconnecting (6203,0):o2net_check_handshake:1205 node web3 (num 3) at 192.168.102.42: advertised net protocol version 8 but 11 is required, disconnecting (6203,0):o2net_check_handshake:1205 node app1 (num 6) at 192.168.102.10: advertised net protocol version 8 but 11 is required, disconnecting (6203,0):o2net_check_handshake:1205 node app1 (num 6) at 192.168.102.10: advertised net protocol version 8 but 11 is required, disconnecting (6203,0):o2net_check_handshake:1205 node rgapp1 (num 4) at 192.168.102.11: advertised net protocol version 8 but 11 is required, disconnecting (6203,0):o2net_check_handshake:1205 node rgapp1 (num 4) at 192.168.102.11: advertised net protocol version 8 but 11 is required, disconnecting (6203,0):o2net_check_handshake:1205 node deploy (num 5) at 192.168.102.12: advertised net protocol version 8 but 11 is required, disconnecting (6203,0):o2net_check_handshake:1205 node deploy (num 5) at 192.168.102.12: advertised net protocol version 8 but 11 is required, disconnecting OCFS2 1.4.1 Wed Jan 21 11:39:13 PST 2009 (build a1974724e90d3f07ae88531f6a9547a9) (6240,0):dlm_request_join:1033 ERROR: status = -107 (6240,0):dlm_try_to_join_domain:1207 ERROR: status = -107 (6240,0):dlm_join_domain:1485 ERROR: status = -107 (6240,0):dlm_register_domain:1732 ERROR: status = -107 (6240,0):ocfs2_dlm_init:2662 ERROR: status = -107 (6240,0):ocfs2_mount_volume:1251 ERROR: status = -107 ocfs2: Unmounting device (8,129) on (node 1) [r...@web1 /opt/build-scripts/CoreUtils/ocfs_rpms]# rpm -qa | grep ocfs ocfs2-tools-1.4.1-1.el5 ocfs2-2.6.18-128.el5-1.4.1-1.el5 [r...@web1 /opt/build-scripts/CoreUtils/ocfs_rpms]# ssh web2 dpkg -l | grep ocfs ii ocfs2-tools1.4.1-1 tools for managing OCFS2 cluster filesystems [r...@web1 /opt/build-scripts/CoreUtils/ocfs_rpms]# No virus found in this outgoing message. Checked by AVG - www.avg.com Version: 8.5.423 / Virus Database: 270.14.24/2449 - Release Date: 10/20/09 18:42:00 ___ Ocfs2-users mailing list Ocfs2-users@oss.oracle.com http://oss.oracle.com/mailman/listinfo/ocfs2-users
Re: [Ocfs2-users] Unable to mount cluster on CentOS and Ubunut at the same time
The production release of ocfs2 (1.2, 1.4, and the upcoming 1.6) is only available for (rh)el and sles. No other distributions. David Murphy wrote: I think I found the core issue… The DLM on Centos is running 1.4.1, but on Ubuntu its 1.3.3, I can’t seem to find any packages for debian or Ubuntu that upgrade the kernel modules to 1.4 series. Does anyone know how I can do this? David *From:* ocfs2-users-boun...@oss.oracle.com [mailto:ocfs2-users-boun...@oss.oracle.com] *On Behalf Of *David Murphy *Sent:* Wednesday, October 21, 2009 10:46 AM *To:* ocfs2-users@oss.oracle.com *Subject:* [Ocfs2-users] Unable to mount cluster on CentOS and Ubunut at the same time Web2 is out Ubuntu Node and Web1 is a new CentOS 5.3 Node I put 1.4.1-1 on CentOS to match the one on the Ubuntu nodes. Also I copied the o2cb configs from the Ubuntu node to the CentOS one. O2CB starts just fine , but I get these errors when I try to start the ocfs2 service or mount the partition: (6203,0):o2net_check_handshake:1205 node deploy (num 5) at 192.168.102.12: advertised net protocol version 8 but 11 is required, disconnecting (6203,0):o2net_check_handshake:1205 node deploy (num 5) at 192.168.102.12: advertised net protocol version 8 but 11 is required, disconnecting Does anyone have any ideas what’s going on? Full Dmesg, rpm, dpkg output is below: OCFS2 Node Manager 1.4.1 Wed Jan 21 11:39:16 PST 2009 (build 304d9ff0c301f79f846e3cc423c30674) OCFS2 DLM 1.4.1 Wed Jan 21 11:39:16 PST 2009 (build 96988c7961cf38309cc33396bb27b400) OCFS2 DLMFS 1.4.1 Wed Jan 21 11:39:16 PST 2009 (build 96988c7961cf38309cc33396bb27b400) OCFS2 User DLM kernel interface loaded (6203,0):o2net_check_handshake:1205 node web2 (num 2) at 192.168.102.41: advertised net protocol version 8 but 11 is required, disconnecting (6203,0):o2net_check_handshake:1205 node web3 (num 3) at 192.168.102.42: advertised net protocol version 8 but 11 is required, disconnecting (6203,0):o2net_check_handshake:1205 node web3 (num 3) at 192.168.102.42: advertised net protocol version 8 but 11 is required, disconnecting (6203,0):o2net_check_handshake:1205 node app1 (num 6) at 192.168.102.10: advertised net protocol version 8 but 11 is required, disconnecting (6203,0):o2net_check_handshake:1205 node app1 (num 6) at 192.168.102.10: advertised net protocol version 8 but 11 is required, disconnecting (6203,0):o2net_check_handshake:1205 node rgapp1 (num 4) at 192.168.102.11: advertised net protocol version 8 but 11 is required, disconnecting (6203,0):o2net_check_handshake:1205 node rgapp1 (num 4) at 192.168.102.11: advertised net protocol version 8 but 11 is required, disconnecting (6203,0):o2net_check_handshake:1205 node deploy (num 5) at 192.168.102.12: advertised net protocol version 8 but 11 is required, disconnecting (6203,0):o2net_check_handshake:1205 node deploy (num 5) at 192.168.102.12: advertised net protocol version 8 but 11 is required, disconnecting OCFS2 1.4.1 Wed Jan 21 11:39:13 PST 2009 (build a1974724e90d3f07ae88531f6a9547a9) (6240,0):dlm_request_join:1033 ERROR: status = -107 (6240,0):dlm_try_to_join_domain:1207 ERROR: status = -107 (6240,0):dlm_join_domain:1485 ERROR: status = -107 (6240,0):dlm_register_domain:1732 ERROR: status = -107 (6240,0):ocfs2_dlm_init:2662 ERROR: status = -107 (6240,0):ocfs2_mount_volume:1251 ERROR: status = -107 ocfs2: Unmounting device (8,129) on (node 1) [r...@web1 /opt/build-scripts/CoreUtils/ocfs_rpms]# rpm -qa | grep ocfs ocfs2-tools-1.4.1-1.el5 ocfs2-2.6.18-128.el5-1.4.1-1.el5 [r...@web1 /opt/build-scripts/CoreUtils/ocfs_rpms]# ssh web2 dpkg -l | grep ocfs ii ocfs2-tools 1.4.1-1 tools for managing OCFS2 cluster filesystems [r...@web1 /opt/build-scripts/CoreUtils/ocfs_rpms]# No virus found in this outgoing message. Checked by AVG - www.avg.com Version: 8.5.423 / Virus Database: 270.14.24/2449 - Release Date: 10/20/09 18:42:00 ___ Ocfs2-users mailing list Ocfs2-users@oss.oracle.com http://oss.oracle.com/mailman/listinfo/ocfs2-users ___ Ocfs2-users mailing list Ocfs2-users@oss.oracle.com http://oss.oracle.com/mailman/listinfo/ocfs2-users
Re: [Ocfs2-users] Unable to mount cluster on CentOS and Ubunut at the same time
We are trying to port our current Ubuntu based OCFS2 cluster to CentOS 5.2 (RHEL) but Ubuntu is using DLM v. 1.3.9 not 1.4.1 but its tools are on 1.4.1. So I am getting a Network version mismatch. Is there any way to upgrade the DLM , I have tried updating the kernels. IF I upgrade from Ubuntu 8.04 to 9.04. It says the DLM version is 1.50 not 1.41. Which further confuses me. Basically I need to have a temporary mixed environment to transition nodes over to CentOS. Is the DLM a kernel module like I assume it is or something the ocfs2-tools should be upgrading when those are on 1.41 + ? David -Original Message- From: ocfs2-users-boun...@oss.oracle.com [mailto:ocfs2-users-boun...@oss.oracle.com] On Behalf Of Sunil Mushran Sent: Wednesday, October 21, 2009 12:23 PM To: David Murphy Cc: ocfs2-users@oss.oracle.com Subject: Re: [Ocfs2-users] Unable to mount cluster on CentOS and Ubunut at the same time The production release of ocfs2 (1.2, 1.4, and the upcoming 1.6) is only available for (rh)el and sles. No other distributions. David Murphy wrote: I think I found the core issue. The DLM on Centos is running 1.4.1, but on Ubuntu its 1.3.3, I can't seem to find any packages for debian or Ubuntu that upgrade the kernel modules to 1.4 series. Does anyone know how I can do this? David *From:* ocfs2-users-boun...@oss.oracle.com [mailto:ocfs2-users-boun...@oss.oracle.com] *On Behalf Of *David Murphy *Sent:* Wednesday, October 21, 2009 10:46 AM *To:* ocfs2-users@oss.oracle.com *Subject:* [Ocfs2-users] Unable to mount cluster on CentOS and Ubunut at the same time Web2 is out Ubuntu Node and Web1 is a new CentOS 5.3 Node I put 1.4.1-1 on CentOS to match the one on the Ubuntu nodes. Also I copied the o2cb configs from the Ubuntu node to the CentOS one. O2CB starts just fine , but I get these errors when I try to start the ocfs2 service or mount the partition: (6203,0):o2net_check_handshake:1205 node deploy (num 5) at 192.168.102.12: advertised net protocol version 8 but 11 is required, disconnecting (6203,0):o2net_check_handshake:1205 node deploy (num 5) at 192.168.102.12: advertised net protocol version 8 but 11 is required, disconnecting Does anyone have any ideas what's going on? Full Dmesg, rpm, dpkg output is below: OCFS2 Node Manager 1.4.1 Wed Jan 21 11:39:16 PST 2009 (build 304d9ff0c301f79f846e3cc423c30674) OCFS2 DLM 1.4.1 Wed Jan 21 11:39:16 PST 2009 (build 96988c7961cf38309cc33396bb27b400) OCFS2 DLMFS 1.4.1 Wed Jan 21 11:39:16 PST 2009 (build 96988c7961cf38309cc33396bb27b400) OCFS2 User DLM kernel interface loaded (6203,0):o2net_check_handshake:1205 node web2 (num 2) at 192.168.102.41: advertised net protocol version 8 but 11 is required, disconnecting (6203,0):o2net_check_handshake:1205 node web3 (num 3) at 192.168.102.42: advertised net protocol version 8 but 11 is required, disconnecting (6203,0):o2net_check_handshake:1205 node web3 (num 3) at 192.168.102.42: advertised net protocol version 8 but 11 is required, disconnecting (6203,0):o2net_check_handshake:1205 node app1 (num 6) at 192.168.102.10: advertised net protocol version 8 but 11 is required, disconnecting (6203,0):o2net_check_handshake:1205 node app1 (num 6) at 192.168.102.10: advertised net protocol version 8 but 11 is required, disconnecting (6203,0):o2net_check_handshake:1205 node rgapp1 (num 4) at 192.168.102.11: advertised net protocol version 8 but 11 is required, disconnecting (6203,0):o2net_check_handshake:1205 node rgapp1 (num 4) at 192.168.102.11: advertised net protocol version 8 but 11 is required, disconnecting (6203,0):o2net_check_handshake:1205 node deploy (num 5) at 192.168.102.12: advertised net protocol version 8 but 11 is required, disconnecting (6203,0):o2net_check_handshake:1205 node deploy (num 5) at 192.168.102.12: advertised net protocol version 8 but 11 is required, disconnecting OCFS2 1.4.1 Wed Jan 21 11:39:13 PST 2009 (build a1974724e90d3f07ae88531f6a9547a9) (6240,0):dlm_request_join:1033 ERROR: status = -107 (6240,0):dlm_try_to_join_domain:1207 ERROR: status = -107 (6240,0):dlm_join_domain:1485 ERROR: status = -107 (6240,0):dlm_register_domain:1732 ERROR: status = -107 (6240,0):ocfs2_dlm_init:2662 ERROR: status = -107 (6240,0):ocfs2_mount_volume:1251 ERROR: status = -107 ocfs2: Unmounting device (8,129) on (node 1) [r...@web1 /opt/build-scripts/CoreUtils/ocfs_rpms]# rpm -qa | grep ocfs ocfs2-tools-1.4.1-1.el5 ocfs2-2.6.18-128.el5-1.4.1-1.el5 [r...@web1 /opt/build-scripts/CoreUtils/ocfs_rpms]# ssh web2 dpkg -l | grep ocfs ii ocfs2-tools 1.4.1-1 tools for managing OCFS2 cluster filesystems [r...@web1 /opt/build-scripts/CoreUtils/ocfs_rpms]# -- -- No virus found in this outgoing message. Checked by AVG - www.avg.com Version: 8.5.423 / Virus Database:
Re: [Ocfs2-users] Unable to mount cluster on CentOS and Ubunut at the same time
I don't think what you want to do is possible. Oracle provide specific builds for comercial distributions only. Centos works with those builds because it mirrors Redhat. Ubuntu is not on Oracle's supported list, but has OCFS2 functionality included because OCFS2 is now part of the upstream kernel. Redhat (and therefore Centos) don't use vanilla upstream kernels they roll their own. So you're never - or at least very unlikely - going to get a version match between Redhat and Ubuntu. Your only option I think is going to be a backup and restore. John On Wednesday, October 21, 2009, David Murphy da...@icewatermedia.com wrote: We are trying to port our current Ubuntu based OCFS2 cluster to CentOS 5.2 (RHEL) but Ubuntu is using DLM v. 1.3.9 not 1.4.1 but its tools are on 1.4.1. So I am getting a Network version mismatch. Is there any way to upgrade the DLM , I have tried updating the kernels. IF I upgrade from Ubuntu 8.04 to 9.04. It says the DLM version is 1.50 not 1.41. Which further confuses me. Basically I need to have a temporary mixed environment to transition nodes over to CentOS. Is the DLM a kernel module like I assume it is or something the ocfs2-tools should be upgrading when those are on 1.41 + ? David -Original Message- From: ocfs2-users-boun...@oss.oracle.com [mailto:ocfs2-users-boun...@oss.oracle.com] On Behalf Of Sunil Mushran Sent: Wednesday, October 21, 2009 12:23 PM To: David Murphy Cc: ocfs2-users@oss.oracle.com Subject: Re: [Ocfs2-users] Unable to mount cluster on CentOS and Ubunut at the same time The production release of ocfs2 (1.2, 1.4, and the upcoming 1.6) is only available for (rh)el and sles. No other distributions. David Murphy wrote: I think I found the core issue. The DLM on Centos is running 1.4.1, but on Ubuntu its 1.3.3, I can't seem to find any packages for debian or Ubuntu that upgrade the kernel modules to 1.4 series. Does anyone know how I can do this? David *From:* ocfs2-users-boun...@oss.oracle.com [mailto:ocfs2-users-boun...@oss.oracle.com] *On Behalf Of *David Murphy *Sent:* Wednesday, October 21, 2009 10:46 AM *To:* ocfs2-users@oss.oracle.com *Subject:* [Ocfs2-users] Unable to mount cluster on CentOS and Ubunut at the same time Web2 is out Ubuntu Node and Web1 is a new CentOS 5.3 Node I put 1.4.1-1 on CentOS to match the one on the Ubuntu nodes. Also I copied the o2cb configs from the Ubuntu node to the CentOS one. O2CB starts just fine , but I get these errors when I try to start the ocfs2 service or mount the partition: (6203,0):o2net_check_handshake:1205 node deploy (num 5) at 192.168.102.12: advertised net protocol version 8 but 11 is required, disconnecting (6203,0):o2net_check_handshake:1205 node deploy (num 5) at 192.168.102.12: advertised net protocol version 8 but 11 is required, disconnecting Does anyone have any ideas what's going on? Full Dmesg, rpm, dpkg output is below: OCFS2 Node Manager 1.4.1 Wed Jan 21 11:39:16 PST 2009 (build 304d9ff0c301f79f846e3cc423c30674) OCFS2 DLM 1.4.1 Wed Jan 21 11:39:16 PST 2009 (build 96988c7961cf38309cc33396bb27b400) OCFS2 DLMFS 1.4.1 Wed Jan 21 11:39:16 PST 2009 (build 96988c7961cf38309cc33396bb27b400) OCFS2 User DLM kernel interface loaded (6203,0):o2net_check_handshake:1205 node web2 (num 2) at 192.168.102.41: advertised net protocol version 8 but 11 is required, disconnecting (6203,0):o2net_check_handshake:1205 node web3 (num 3) at 192.168.102.42: advertised net protocol version 8 but 11 is required, disconnecting (6203,0):o2net_check_handshake:1205 node web3 (num 3) at 192.168.102.42: advertised net protocol version 8 but 11 is required, disconnecting (6203,0):o2net_check_handshake:1205 node app1 (num 6) at 192.168.102.10: advertised net protocol version 8 but 11 is required, disconnecting (6203,0):o2net_check_handshake:1205 node app1 (num 6) at 192.168.102.10: advertised net protocol version 8 but 11 is required, disconnecting (6203,0):o2net_check_handshake:1205 node rgapp1 (num 4) at 192.168.102.11: advertised net protocol version 8 but 11 is required, disconnecting (6203,0):o2net_check_handshake:1205 node rgapp1 (num 4) at 192.168.102.11: advertised net protocol version 8 but 11 is required, disconnecting (6203,0):o2net_check_handshake:1205 node deploy (num 5) at 192.168.102.12: advertised net protocol version 8 but 11 is required, disconnecting (6203,0):o2net_check_ ___ Ocfs2-users mailing list Ocfs2-users@oss.oracle.com http://oss.oracle.com/mailman/listinfo/ocfs2-users
Re: [Ocfs2-users] Unable to mount cluster on CentOS and Ubunut at the same time
ubuntu 9.04 is shipping 2.6.28. The O2NET_PROTOCOL_VERSION in that release is the same as in ocfs2 1.4. So one should be able to concurrently mount a volume from nodes running ubuntu 9.04 and ocfs2 1.4/centos. Have you tried it? David Murphy wrote: We are trying to port our current Ubuntu based OCFS2 cluster to CentOS 5.2 (RHEL) but Ubuntu is using DLM v. 1.3.9 not 1.4.1 but its tools are on 1.4.1. So I am getting a Network version mismatch. Is there any way to upgrade the DLM , I have tried updating the kernels. IF I upgrade from Ubuntu 8.04 to 9.04. It says the DLM version is 1.50 not 1.41. Which further confuses me. Basically I need to have a temporary mixed environment to transition nodes over to CentOS. Is the DLM a kernel module like I assume it is or something the ocfs2-tools should be upgrading when those are on 1.41 + ? David -Original Message- From: ocfs2-users-boun...@oss.oracle.com [mailto:ocfs2-users-boun...@oss.oracle.com] On Behalf Of Sunil Mushran Sent: Wednesday, October 21, 2009 12:23 PM To: David Murphy Cc: ocfs2-users@oss.oracle.com Subject: Re: [Ocfs2-users] Unable to mount cluster on CentOS and Ubunut at the same time The production release of ocfs2 (1.2, 1.4, and the upcoming 1.6) is only available for (rh)el and sles. No other distributions. David Murphy wrote: I think I found the core issue. The DLM on Centos is running 1.4.1, but on Ubuntu its 1.3.3, I can't seem to find any packages for debian or Ubuntu that upgrade the kernel modules to 1.4 series. Does anyone know how I can do this? David *From:* ocfs2-users-boun...@oss.oracle.com [mailto:ocfs2-users-boun...@oss.oracle.com] *On Behalf Of *David Murphy *Sent:* Wednesday, October 21, 2009 10:46 AM *To:* ocfs2-users@oss.oracle.com *Subject:* [Ocfs2-users] Unable to mount cluster on CentOS and Ubunut at the same time Web2 is out Ubuntu Node and Web1 is a new CentOS 5.3 Node I put 1.4.1-1 on CentOS to match the one on the Ubuntu nodes. Also I copied the o2cb configs from the Ubuntu node to the CentOS one. O2CB starts just fine , but I get these errors when I try to start the ocfs2 service or mount the partition: (6203,0):o2net_check_handshake:1205 node deploy (num 5) at 192.168.102.12: advertised net protocol version 8 but 11 is required, disconnecting (6203,0):o2net_check_handshake:1205 node deploy (num 5) at 192.168.102.12: advertised net protocol version 8 but 11 is required, disconnecting Does anyone have any ideas what's going on? Full Dmesg, rpm, dpkg output is below: OCFS2 Node Manager 1.4.1 Wed Jan 21 11:39:16 PST 2009 (build 304d9ff0c301f79f846e3cc423c30674) OCFS2 DLM 1.4.1 Wed Jan 21 11:39:16 PST 2009 (build 96988c7961cf38309cc33396bb27b400) OCFS2 DLMFS 1.4.1 Wed Jan 21 11:39:16 PST 2009 (build 96988c7961cf38309cc33396bb27b400) OCFS2 User DLM kernel interface loaded (6203,0):o2net_check_handshake:1205 node web2 (num 2) at 192.168.102.41: advertised net protocol version 8 but 11 is required, disconnecting (6203,0):o2net_check_handshake:1205 node web3 (num 3) at 192.168.102.42: advertised net protocol version 8 but 11 is required, disconnecting (6203,0):o2net_check_handshake:1205 node web3 (num 3) at 192.168.102.42: advertised net protocol version 8 but 11 is required, disconnecting (6203,0):o2net_check_handshake:1205 node app1 (num 6) at 192.168.102.10: advertised net protocol version 8 but 11 is required, disconnecting (6203,0):o2net_check_handshake:1205 node app1 (num 6) at 192.168.102.10: advertised net protocol version 8 but 11 is required, disconnecting (6203,0):o2net_check_handshake:1205 node rgapp1 (num 4) at 192.168.102.11: advertised net protocol version 8 but 11 is required, disconnecting (6203,0):o2net_check_handshake:1205 node rgapp1 (num 4) at 192.168.102.11: advertised net protocol version 8 but 11 is required, disconnecting (6203,0):o2net_check_handshake:1205 node deploy (num 5) at 192.168.102.12: advertised net protocol version 8 but 11 is required, disconnecting (6203,0):o2net_check_handshake:1205 node deploy (num 5) at 192.168.102.12: advertised net protocol version 8 but 11 is required, disconnecting OCFS2 1.4.1 Wed Jan 21 11:39:13 PST 2009 (build a1974724e90d3f07ae88531f6a9547a9) (6240,0):dlm_request_join:1033 ERROR: status = -107 (6240,0):dlm_try_to_join_domain:1207 ERROR: status = -107 (6240,0):dlm_join_domain:1485 ERROR: status = -107 (6240,0):dlm_register_domain:1732 ERROR: status = -107 (6240,0):ocfs2_dlm_init:2662 ERROR: status = -107 (6240,0):ocfs2_mount_volume:1251 ERROR: status = -107 ocfs2: Unmounting device (8,129) on (node 1) [r...@web1 /opt/build-scripts/CoreUtils/ocfs_rpms]# rpm -qa | grep ocfs ocfs2-tools-1.4.1-1.el5 ocfs2-2.6.18-128.el5-1.4.1-1.el5 [r...@web1 /opt/build-scripts/CoreUtils/ocfs_rpms]# ssh web2 dpkg -l | grep ocfs ii ocfs2-tools 1.4.1-1 tools for
Re: [Ocfs2-users] Persistent lun problem
Look at device-mapper-multipath Regards, Ulf. - OPENLANE Inc., T: 650-532-6382, F: 650-532-6441 4600 Bohannon Drive, Suite 100, Menlo Park, CA 94025 - -Original Message- From: ocfs2-users-boun...@oss.oracle.com [mailto:ocfs2-users- boun...@oss.oracle.com] On Behalf Of Pedro Figueira Sent: 10/01/2008 11:40 To: ocfs2-users@oss.oracle.com Subject: [Ocfs2-users] Persistent lun problem Dear all I'm investigating the possible solutions for persistent device names to mount OCFS2 disks, without using LVM2 that is not supported. In RH4 if you reboot the server, add or remove LUNS the device files (traditionally /dev/sdX) can change, so you can mount the filesystem on the wrong directory. From what I can see there are some solution like the multipath or udev to create persistent device files. However the solution can be more simple if in the /etc/fstab file one indicate the label of the OCFS2 volume and not the device file. I've tried this with OCFS1.2 with good results but my question is if it's supported (i.e if mounting an OCFS2 volume by label is supported) and if there is any problem with this approach. Will it work on future OCFS2 releases? Best regards and thanks Pedro Figueira CONFIDENCIAL NOTICE: This message, as well as any existing attached files, is confidential and intended exclusively for the individual(s) named as addressees. If you are not the intended recipient, you are kindly requested not to make any use whatsoever of its contents and to proceed to the destruction of the message, thereby notifying the sender. DISCLAIMER: The sender of this message can NOT ensure the security of its electronic transmission and consequently does not accept liability for any fact, which may interfere with the integrity of its content. ___ Ocfs2-users mailing list Ocfs2-users@oss.oracle.com http://oss.oracle.com/mailman/listinfo/ocfs2-users ___ Ocfs2-users mailing list Ocfs2-users@oss.oracle.com http://oss.oracle.com/mailman/listinfo/ocfs2-users
Re: [Ocfs2-users] OCFS2 and VMware ESX
What I did a few days ago was to create a vmware disk for each OCFS2 filesystem, and store it with one of the VM nodes. Then, add that disk to each additional VM. When you add it, use a separate SCSI host number. In other words, if the OS is on SCSI 0:0, make the disk SCSI 1:0, or some arbitrary other HBA number. Then you can go to each hosts second VM SCSI device and modify it to be shared, and of type Physical (if I remember correctly). At that point, it works fine. -- Kent Rankin -Original Message- From: ocfs2-users-boun...@oss.oracle.com on behalf of Haydn Cahir Sent: Mon 7/28/2008 9:48 PM To: ocfs2-users@oss.oracle.com Subject: [Ocfs2-users] OCFS2 and VMware ESX Hi, We are haing some serious issues trying to configure an OCFS2 cluster on 3 SLES 10 SP2 boxes running in VMware ESX 3.0.1. Before I go into any of the detailed errors we are experiencing I first wanted to ask everyone if they have successfully configured this solution? We would be interested to find out what needs to be set at the VMware level (RDM, VMFS, NICS etc) and what needs to be configured at the O/S level. We have a LUN on our SAN that we have presented to our VMware hosts that we are using for this. Any help would be greatly appreciated! ___ Ocfs2-users mailing list Ocfs2-users@oss.oracle.com http://oss.oracle.com/mailman/listinfo/ocfs2-users ___ Ocfs2-users mailing list Ocfs2-users@oss.oracle.com http://oss.oracle.com/mailman/listinfo/ocfs2-users
Re: [Ocfs2-users] Default Values of heartbeat dead threshold
Hi Devender, this is a very complex question. Timeouts must be set in conjunction with your infrastructure. What type of storage? What OCFS2 Version? Etc. The major problem is, to synchronies the timeouts with CRS timeouts to prevent different decisions. In fact, I am pretty sure, you won’t get a default value ore suggestion. In general you have to do a lot of tests! Good praxis for me: Heartbeat dead threshold = around 61 network idle timeout = around 7 network keepalive delay in ms 5000 network reconnect delay in ms 5000 in a multipath environment with a virtual san. As I already mentioned timeouts have to be set in conjunction with your infrastructure and san system. This can be totally different for your needs. Do not take OCFS2 with CRS easy. This is very difficult and make sure you are using the latest releases. Everything without warranty! Good Luck Regards Martin Von: ocfs2-users-boun...@oss.oracle.com [ocfs2-users-boun...@oss.oracle.com] im Auftrag von Devender Narula [devendernar...@yahoo.com] Gesendet: Freitag, 5. Juni 2009 12:59 An: ocfs2-users@oss.oracle.com Betreff: [Ocfs2-users] Default Values of heartbeat dead threshold Hi Guys i got two node RAC cluster Running on RHEL 5.0 .. i just want to what is oracle recomendid Defaults values for below mention parameters Thanks for your help Heartbeat dead threshold network idle timeout network keepalive delay in ms network reconnect delay in ms kernel.panic_on_oops kernel.panic Regards, Devender ___ Ocfs2-users mailing list Ocfs2-users@oss.oracle.com http://oss.oracle.com/mailman/listinfo/ocfs2-users ___ Ocfs2-users mailing list Ocfs2-users@oss.oracle.com http://oss.oracle.com/mailman/listinfo/ocfs2-users
Re: [Ocfs2-users] [Ocfs2-devel] FW: Oracle 9204 installation on linux x86-64 on ocfs
Thanks Srinivas. That was the problem. Things worked after I mounted it using
following options. how should I make this changes into /etc/fstab. Should it
look like as below ? Can you please confirm it ?
/dev/sde/u04ocfs2 _netdev,defaults,datavolume, nointr0
0
Thanks
` Keyur
-Original Message-
From: Srinivas Eeda [mailto:srinivas.e...@oracle.com]
Sent: Monday, May 04, 2009 1:03 PM
To: keyur.pa...@oracle.com
Cc: ocfs2-de...@oss.oracle.com; ocfs2-users@oss.oracle.com
Subject: Re: [Ocfs2-devel] FW: Oracle 9204 installation on linux x86-64
on ocfs
did you use -o datavolume, nointr options for mounting?
keyur patel wrote:
Hello All,
I have installed Oracle Cluster Manager on linux x86-64 nit. I am
using ocfs file system for quorum file. But I am getting following
error. Please see ocfs configureation below. I would appreciate, if
someone could help me to understand if I am doing something wrong.
Thanks in advance.
--cm.log file
oracm, version[ AMD64.9.2.0.4.0.00 ] started {Mon May 4 05:34:38 2009 }
TRACE:Can't read registry value for HeartBeat, tid =
main:182895169120 file = unixinc.c, line = 1077 {Mon May 4 05:34:38
2009 }
TRACE:Can't read registry value for PollInterval, tid =
main:182895169120 file = unixinc.c, line = 1077 {Mon May 4 05:34:38
2009 }
TRACE:Can't read registry value for WatchdogTimerMargin, tid =
main:182895169120 file = unixinc.c, line = 1077 {Mon May 4 05:34:38
2009 }
TRACE:Can't read registry value for WatchdogSafetyMargin, tid =
main:182895169120 file = unixinc.c, line = 1077 {Mon May 4 05:34:38
2009 }
KernelModuleName is hangcheck-timer {Mon May 4 05:34:38 2009 }
TRACE:Can't read registry value for ClientTimeout, tid =
main:182895169120 file = unixinc.c, line = 1077 {Mon May 4 05:34:38
2009 }
TRACE:InitNMInfo: setting clientTimeout to 143s based on
MissCount 215 and PollInterval 1000ms, tid = main:182895169120 file =
nmconfig.c, line = 138 {Mon May 4 05:34:38 2009 }
TRACE:InitClusterDb(): getservbyname on CMSrvr failed - 0 :
assigning 9998, tid = main:182895169120 file = nmconfig.c, line = 208
{Mon May 4 05:34:38 2009 }
OemNodeConfig(): Network Address of node0: 1.1.1.1 (port 9998)
{Mon May 4 05:34:38 2009 }
OemNodeConfig(): Network Address of node1: 1.1.1.2 (port 9998)
{Mon May 4 05:34:38 2009 }
TRACE:OemCreateListenPort: bound at 9998, tid =
main:182895169120 file = oem.c, line = 858 {Mon May 4 05:34:38 2009 }
TRACE:InitClusterDb(): found my node info at 1 name
s602749nj3el19, priv s602749nj3el19priv, port 3623, tid =
main:182895169120 file = nmconfig.c, line = 261 {Mon May 4 05:34:38
2009 }
OemNodeConfig(): Network Address of node2: 1.1.1.3 (port 9998)
{Mon May 4 05:34:38 2009 }
OemNodeConfig(): Network Address of node3: 1.1.1.4 (port 9998)
{Mon May 4 05:34:38 2009 }
TRACE:InitClusterDb(): Local Node(1)
NodeName[s602749nj3el19priv], tid = main:182895169120 file =
nmconfig.c, line = 279 {Mon May 4 05:34:38 2009 }
TRACE:InitClusterDb(): Cluster(Oracle) with (4) Defined Nodes,
tid = main:182895169120 file = nmconfig.c, line = 282 {Mon May 4
05:34:38 2009 }
TRACE:OEMInits(): CM Disk File (/u04/quorum/quorum.dbf), tid =
main:182895169120 file = oem.c, line = 243 {Mon May 4 05:34:38 2009 }
ERROR:OemInit2: Attempting to open the CMDiskFile for a
multi-node RAC on a non-NFS, non-OCFS, or non-raw device cluster, tid
= main:182895169120 file = oem.c, line = 482 {Mon May 4 05:34:38 2009 }
ERROR:OemInit2: If the CMDiskFile is supposed to be an NFS or
OCFS file, please make sure that the relevant shared file system is
mounted properly, tid = main:182895169120 file = oem.c, line = 483
{Mon May 4 05:34:38 2009 }
ERROR:OemInit2: If the CMDiskFile is supposed to be a raw device,
please make sure that it has been created properly, tid =
main:182895169120 file = oem.c, line = 484 {Mon May 4 05:34:38 2009 }
--- End Dump ---
OCFS setup
-
[r...@s602749nj3el19 bin]# mounted.ocfs2 -f
DeviceFS Nodes
/dev/sdc ocfs2 s602749nj3el18, s602749nj3el19,
s602749nj3el21, s602749nj3el20
/dev/sdd ocfs2 s602749nj3el18, s602749nj3el19,
s602749nj3el21, s602749nj3el20
/dev/sde ocfs2 s602749nj3el18, s602749nj3el19,
s602749nj3el21, s602749nj3el20
/dev/sdf ocfs2 s602749nj3el18, s602749nj3el19,
s602749nj3el21, s602749nj3el20
[r...@s602749nj3el19 bin]# df -kh
FilesystemSize Used Avail Use% Mounted on
/dev/mapper/VolGroup00-LogVol00
2.0G 368M 1.6G 20% /
/dev/sda1 61M 24M 35M 41% /boot
/dev/mapper/VolGroup00-LogVol05
19G 11G 7.6G 58% /data01
none 7.9G 0 7.9G 0% /dev/shm
[Ocfs2-users] Fwd: mount.ocfs2: Error when attempting to run /sbin/ocfs2_hb_ctl: Operation not permitted.
Hi, Check in /etc/ocfs2/cluster.conf the instance number. For example, If you have two node: node: ip_port = ip_address = 10.0.0.1 number = 0 name = priamus cluster = ocfs2 node: ip_port = ip_address = 10.0.0.2 number = 1 - name = hektor cluster = ocfs2 cluster: node_count = 2 name = ocfs2 -- Forwarded message -- From: Nandkumar Mane nandkum...@gmail.com Date: Wed, Sep 10, 2008 at 5:17 PM Subject: [Ocfs2-users] mount.ocfs2: Error when attempting to run /sbin/ocfs2_hb_ctl: Operation not permitted. To: ocfs2-users@oss.oracle.com Hi, I am trying to configure a two node cluster on SLES10SP2 using user level heartbeat. Here is my configuration. ocfs2-tools-1.4.0-0.3 **user level heartbeat** - lsmod | grep ocfs ocfs2_user_heartbeat 20992 1 ocfs2_dlmfs 37776 1 ocfs2_dlm 204456 1 ocfs2_dlmfs ocfs2_nodemanager 223384 6 ocfs2_user_heartbeat,ocfs2_dlmfs,ocfs2_dlm configfs 44700 3 ocfs2_user_heartbeat,ocfs2_nodemanager mounted filesystem list contains following two lines which are required for o2cb. configfs on /sys/kernel/config type configfs (rw) ocfs2_dlmfs on /dlm type ocfs2_dlmfs (rw) /etc/ocfs2/cluster.conf file is created on one node using ocfs2console and then propogated changes to other host. -/etc/init.d/o2cb status Module configfs: Loaded Filesystem configfs: Mounted Module ocfs2_nodemanager: Loaded Module ocfs2_dlm: Loaded Module ocfs2_dlmfs: Loaded Filesystem ocfs2_dlmfs: Mounted Checking O2CB cluster ocfs2: Online Network idle timeout: 3 Network keepalive delay: 2000 Network reconnect delay: 2000 Checking O2CB heartbeat: Not active Everything looks fine till this point. I am able to configure and start o2cb successfully. Now when I try to mount a ocfs2 filesystem, it give me following error. -mount /dev/mapper/360a980004334637558344a7863755656 /hdmnt1 ocfs2_hb_ctl: Unable to access cluster service while starting heartbeat mount.ocfs2: Error when attempting to run /sbin/ocfs2_hb_ctl: Operation not permitted As per my opnion, I have followed proper stepts to configure. (I had done same with kernel level heartbeat successfully.) Is user level heartbeat supported in sles10sp2? Can somebody please give me some direction? Thanks Nand ___ Ocfs2-users mailing list Ocfs2-users@oss.oracle.com http://oss.oracle.com/mailman/listinfo/ocfs2-users ___ Ocfs2-users mailing list Ocfs2-users@oss.oracle.com http://oss.oracle.com/mailman/listinfo/ocfs2-users
[Ocfs2-users] Version of ocfs2 in vanilla? (Follow up)
Hi, Concerning http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commi tdiff;h=4d0ddb2ce25db2254d468233d942276ecf40bff8 Inode allocation is modified to look in other nodes allocators during extreme out of space situations. We retry our own slot when space is freed back to the global bitmap, or whenever we've allocated more than 1024 inodes from another slot. Why is this limited to 1024 inodes? After upgrading the Kernel to 2.6.26. the result is, that the no space left on device inode Problem still exists, if a new file is larger than about 1MB blocks. So writing 1000 files each about 972 blocks large or smaller works fine now, but not trying to write one file 973 blocks large, which still results in no space left on device $ for (( a=0 ; a 1000 ; a++ )) ; do dd if=/dev/zero of=$a bs=1024 count=972 || break; done; echo $a files created 972+0 records in 972+0 records out 995328 bytes (995 kB) copied, 0.010832 seconds, 91.9 MB/s 972+0 records in 972+0 records out 995328 bytes (995 kB) copied, 0.0108682 seconds, 91.6 MB/s ... ... And so on ... 1000 files created $ for (( a=0 ; a 1000 ; a++ )) ; do dd if=/dev/zero of=$a bs=1024 count=973 || break; done; echo $a files created dd: writing `0': No space left on device 973+0 records in 972+0 records out 995328 bytes (995 kB) copied, 0.263264 seconds, 3.8 MB/s 0 files created What's the reason? Tanks + Best regards Dirk Sunil Mushran wrote: That fix went into 2.6.26. http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=comm itdiff;h=ffda89a3bf3b968bdc268584c6bc1da5c173cf12 http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=comm itdiff;h=a4a4891164d4f6f383cc17e7c90828a7ca6a1146 http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=comm itdiff;h=4d0ddb2ce25db2254d468233d942276ecf40bff8 Alex wrote: Hi, which version of ocfs2 is in the current sources of the vanilla kernel. The only version string i found was OCFS2_BUILD_VERSION 1.5.0 in ver.c I am affected by no space left on device inode Problem.posted to ocfs2-users by Feite Brekeveld at Feb 27 and whant to be shure that the problem isn`t present in current vanilla kernel. I am using 2.6.25. OCFS2 statically build into kernel.. Thanks Alex ___ ___ Ocfs2-users mailing list Ocfs2-users@oss.oracle.com http://oss.oracle.com/mailman/listinfo/ocfs2-users
Re: [Ocfs2-users] [CentOS] Unexplained reboots in DRBD82 + OCFS2 setup
On Jun 25, 2009, at 5:44 AM, Kris Buytaert m...@inuits.be wrote: /dev/console is a serial device connected to a terminal server, so far the best I got was a partial timestamp before I saw the output of the reboot again .. It tries to log .. but doesn't finish writing it :( But mostly there is no activity at all on the serial console :( Any other ideas ? Set up the crash kernel and get a core dump of the system at the time of the crash. It's the only way to find the culprit. -Ross ___ Ocfs2-users mailing list Ocfs2-users@oss.oracle.com http://oss.oracle.com/mailman/listinfo/ocfs2-users
Re: [Ocfs2-users] migration methods (ocfs - ocfs2)
No, the fscat tools can only read certain unmounted file systems. They cannot write. You can use it to copy data from ocfs to ocfs2 on a box running the 2.6 kernel (sles9/10, el4/5). And when we tried to use fscat about a year ago to read our OCFS volumes on a RHEL4 machine it wasn't working. The source code itself had to be updated and as far I know that has not happened. I had email contact with Joel Becker and he said he would look into it, but it never happened. Mehmet Can ÖNAL wrote: Hi everyone; we have a production system with 6 nodes of RAC upon ocfs file system. We will upgrade our production system that we prefer and (also should) to migrate our data to ocfs2. Both methods of migration, fscat and backup/restore could be useful for us but one thing that we could not find is 1) If we are using fscp fort he migration method can we use fscp to pass data from ocfs to ocfs2. is fscp biwise, it can copy either ocfs to ocfs2 and also ocfs2 to ocfs? 2) For backup/restore the doubt is the same. We can restore ocfs backup to an ocfs2, could we also restore ocfs2 backup to an ocfs volume? Thanx a lot Ulf Zimmermann | Senior System Architect OPENLANE 4600 Bohannon Drive, Suite 100 Menlo Park, CA 94025 O: 650-532-6382 M: (510) 396-1764 F: (510) 580-0929 Email: u...@openlane.com | Web: www.openlane.com ___ Ocfs2-users mailing list Ocfs2-users@oss.oracle.com http://oss.oracle.com/mailman/listinfo/ocfs2-users
Re: [Ocfs2-users] FW: Oracle 9204 installation on linux x86-64 on ocfs
Appears the volumes are not mounted with the datavolume mount option.
Refer to the FAQ for more in this.
On May 4, 2009, at 7:37 AM, keyur patel keyur.pa...@oracle.com wrote:
Hello All,
I have installed Oracle Cluster Manager on linux x86-64 nit. I am
using ocfs file system for quorum file. But I am getting following
error. Please see ocfs configureation below. I would appreciate, if
someone could help me to understand if I am doing something wrong.
Thanks in advance.
--cm.log file
oracm, version[ AMD64.9.2.0.4.0.00 ] started {Mon May 4 05:34:38
2009 }
TRACE:Can't read registry value for HeartBeat, tid = main:182895169120
file = unixinc.c, line = 1077 {Mon May 4 05:34:38 2009 }
TRACE:Can't read registry value for PollInterval, tid = main:182895169120
file = unixinc.c, line = 1077 {Mon May 4 05:34:38 2009 }
TRACE:Can't read registry value for WatchdogTimerMargin, tid =
main:182895169120 file = unixinc.c, line = 1077 {Mon May 4 05:34:38
2009 }
TRACE:Can't read registry value for WatchdogSafetyMargin, tid =
main:182895169120 file = unixinc.c, line = 1077 {Mon May 4 05:34:38
2009 }
KernelModuleName is hangcheck-timer {Mon May 4 05:34:38 2009 }
TRACE:Can't read registry value for ClientTimeout, tid = main:182895169120
file = unixinc.c, line = 1077 {Mon May 4 05:34:38 2009 }
TRACE:InitNMInfo: setting clientTimeout to 143s based on
MissCount 215 and PollInterval 1000ms, tid = main:182895169120 file
= nmconfig.c, line = 138 {Mon May 4 05:34:38 2009 }
TRACE:InitClusterDb(): getservbyname on CMSrvr failed - 0 :
assigning 9998, tid = main:182895169120 file = nmconfig.c, line =
208 {Mon May 4 05:34:38 2009 }
OemNodeConfig(): Network Address of node0: 1.1.1.1 (port 9998)
{Mon May 4 05:34:38 2009 }
OemNodeConfig(): Network Address of node1: 1.1.1.2 (port 9998)
{Mon May 4 05:34:38 2009 }
TRACE:OemCreateListenPort: bound at 9998, tid = main:182895169120
file = oem.c, line = 858 {Mon May 4 05:34:38 2009 }
TRACE:InitClusterDb(): found my node info at 1 name
s602749nj3el19, priv s602749nj3el19priv, port 3623, tid = main:182895169120
file = nmconfig.c, line = 261 {Mon May 4 05:34:38 2009 }
OemNodeConfig(): Network Address of node2: 1.1.1.3 (port 9998)
{Mon May 4 05:34:38 2009 }
OemNodeConfig(): Network Address of node3: 1.1.1.4 (port 9998)
{Mon May 4 05:34:38 2009 }
TRACE:InitClusterDb(): Local Node(1) NodeName
[s602749nj3el19priv], tid = main:182895169120 file = nmconfig.c,
line = 279 {Mon May 4 05:34:38 2009 }
TRACE:InitClusterDb(): Cluster(Oracle) with (4) Defined Nodes,
tid = main:182895169120 file = nmconfig.c, line = 282 {Mon May 4
05:34:38 2009 }
TRACE:OEMInits(): CM Disk File (/u04/quorum/quorum.dbf), tid =
main:182895169120 file = oem.c, line = 243 {Mon May 4 05:34:38 2009 }
ERROR:OemInit2: Attempting to open the CMDiskFile for a multi-
node RAC on a non-NFS, non-OCFS, or non-raw device cluster, tid =
main:182895169120 file = oem.c, line = 482 {Mon May 4 05:34:38 2009 }
ERROR:OemInit2: If the CMDiskFile is supposed to be an NFS or
OCFS file, please make sure that the relevant shared file system is
mounted properly, tid = main:182895169120 file = oem.c, line = 483
{Mon May 4 05:34:38 2009 }
ERROR:OemInit2: If the CMDiskFile is supposed to be a raw
device, please make sure that it has been created properly, tid =
main:182895169120 file = oem.c, line = 484 {Mon May 4 05:34:38 2009 }
--- End Dump ---
OCFS setup
-
[r...@s602749nj3el19 bin]# mounted.ocfs2 -f
DeviceFS Nodes
/dev/sdc ocfs2 s602749nj3el18, s602749nj3el19,
s602749nj3el21, s602749nj3el20
/dev/sdd ocfs2 s602749nj3el18, s602749nj3el19,
s602749nj3el21, s602749nj3el20
/dev/sde ocfs2 s602749nj3el18, s602749nj3el19,
s602749nj3el21, s602749nj3el20
/dev/sdf ocfs2 s602749nj3el18, s602749nj3el19,
s602749nj3el21, s602749nj3el20
[r...@s602749nj3el19 bin]# df -kh
FilesystemSize Used Avail Use% Mounted on
/dev/mapper/VolGroup00-LogVol00
2.0G 368M 1.6G 20% /
/dev/sda1 61M 24M 35M 41% /boot
/dev/mapper/VolGroup00-LogVol05
19G 11G 7.6G 58% /data01
none 7.9G 0 7.9G 0% /dev/shm
/dev/mapper/VolGroup00-LogVol04
2.0G 53M 1.9G 3% /tmp
/dev/mapper/VolGroup00-LogVol02
3.0G 1.8G 1.1G 64% /usr
/dev/mapper/VolGroup00-LogVol03
2.0G 94M 1.8G 5% /var
/dev/mapper/VolGroup01-u01
148G 93M 141G 1% /u01
/dev/sdc 600G 1.1G 599G 1% /u02
/dev/sdd 300G 1.1G 299G 1% /u03
/dev/sde 1.0G 274M 751M 27% /u04/quorum
/dev/sdf 1.0G 262M 763M
