You have different versions of the file system on the two nodes. On both nodes, do: $ rpm -qa | grep ocfs2
Secondly, you should partition the devices. Features like mount-by-label do not work with unpartitioned devices. McKinley, Reid wrote: > Sunil, > Here is the output...(note: nyxlx1 is where we can mount the ocfs2 fs). > > [r...@nyclx2 ~]# mounted.ocfs2 -d > Device FS UUID Label > /dev/sda ocfs2 f350f4e5-2bf8-4930-ad55-4cb703e38e25 ocfs1 > /dev/sdb ocfs2 b5d03918-31f9-4280-a378-e0043c241517 > oracle_home > /dev/sdi ocfs2 f350f4e5-2bf8-4930-ad55-4cb703e38e25 ocfs1 > /dev/sdj ocfs2 b5d03918-31f9-4280-a378-e0043c241517 > oracle_home > > [r...@nyclx1 ~]# mounted.ocfs2 -d > Device FS UUID Label > /dev/sda ocfs2 f350f4e5-2bf8-4930-ad55-4cb703e38e25 ocfs1 > /dev/sdb ocfs2 b5d03918-31f9-4280-a378-e0043c241517 > oracle_home > /dev/sdi ocfs2 f350f4e5-2bf8-4930-ad55-4cb703e38e25 ocfs1 > /dev/sdj ocfs2 b5d03918-31f9-4280-a378-e0043c241517 > oracle_home > [r...@nyclx1 ~]# > > In the /var/log/messages, I see this at the time the mount fails: > > Apr 29 12:01:13 nyclx2 kernel: (12430,0):o2net_check_handshake:1163 node > nyclx1 (num 0) at 192.168.0.218:7777 advertised net protocol version 11 > but 103 is required, disconnecting > Apr 29 12:01:17 nyclx2 kernel: (16953,0):ocfs2_initialize_super:1454 > ERROR: couldn't mount because of unsupported optional features (10). > Apr 29 12:01:17 nyclx2 kernel: (16953,0):ocfs2_fill_super:578 ERROR: > status = -22 > Apr 29 12:01:17 nyclx2 kernel: ocfs2: Unmounting device (8,0) on (node > 255) > > Thanks again, > Reid > > -----Original Message----- > From: Sunil Mushran [mailto:sunil.mush...@oracle.com] > Sent: Wednesday, April 29, 2009 4:32 PM > To: McKinley, Reid > Cc: ocfs2-users@oss.oracle.com > Subject: Re: [Ocfs2-users] O2CB heartbeat: Not active > > What does "mounted.ocfs2 -d" say on both nodes? > > Not /var/log/dmesg. It is /var/log/messages. You could instead > run "dmesg". This is important as it will tell you why the > mount failed. > > Sunil > > > McKinley, Reid wrote: > >> Thank you! >> >> Everything appears to be fine then, except that we cannot mount an >> > OCFS2 > >> filesystem on our 2nd node. When I try to mount the fs using >> ocfs2console on the 2nd node, I receive this error message in a dialog >> box: >> "mount.ocfs2: Invalid argument while mounting /dev/sda on >> > /oracle_home. > >> Check 'dmesg' for more information on this error. : Could not mount >> /dev/sda" >> >> I do not see any related messages in /var/log/dmesg. >> Any help is greatly appreciated. >> Thanks, >> Reid >> >> The O2CB status is as follows on this 2nd node: >> >> [r...@nyclx2 ~]# lsmod | grep ocfs2 >> ocfs2 369640 0 >> ocfs2_dlmfs 55952 1 >> ocfs2_dlm 217104 2 ocfs2,ocfs2_dlmfs >> ocfs2_nodemanager 225416 6 ocfs2,ocfs2_dlmfs,ocfs2_dlm >> configfs 62301 2 ocfs2_nodemanager >> jbd 93873 2 ocfs2,ext3 >> [r...@nyclx2 ~]# service o2cb status >> Driver for "configfs": Loaded >> Filesystem "configfs": Mounted >> Driver for "ocfs2_dlmfs": Loaded >> Filesystem "ocfs2_dlmfs": Mounted >> Checking O2CB cluster tiaa: Online >> Heartbeat dead threshold: 31 >> Network idle timeout: 30000 >> Network keepalive delay: 2000 >> Network reconnect delay: 2000 >> Checking O2CB heartbeat: Not active >> [r...@nyclx2 ~]# >> > > ******************************************************************************************** > This message, including any attachments, contains confidential information > intended > for a specific individual and purpose, and is protected by law. If you are > not the intended > recipient, please contact the sender immediately by reply e-mail and destroy > all copies. > You are hereby notified that any disclosure, copying, or distribution of this > message, or > the taking of any action based on it, is strictly prohibited. > > TIAA-CREF > ******************************************************************************************** > > _______________________________________________ Ocfs2-users mailing list Ocfs2-users@oss.oracle.com http://oss.oracle.com/mailman/listinfo/ocfs2-users