<html><head><style type="text/css"><!-- DIV {margin:0px;} --></style></head><body><div style="font-family:times new roman, new york, times, serif;font-size:10pt"><DIV></DIV>
<DIV>Ok, we were able to mount the device on the existing standby node.</DIV>
<DIV> </DIV>
<DIV>Mounting on existing standby after upgrading succeeded</DIV>
<DIV>[root@guard2 ~]# mount -t ocfs2 -o datavolume,nointr /dev/emcpowern1 /orabackup1</DIV>
<DIV> </DIV>
<DIV>Now when we try to mount it on the new standby node, we get the following error</DIV>
<DIV>Mounting on New standby:</DIV>
<DIV>[root@guard0 /]# mount -t ocfs2 -o datavolume,nointr /dev/emcpowerf /orabackup<BR>mount.ocfs2: Bad magic number in superblock while opening device /dev/emcpowerf<BR></DIV>
<DIV>Note: /dev/emcpowerf on the new standby is the same storage as /dev/emcpowern1 on the old standby.</DIV>
<DIV>Also old standby and new standby are not in the same ocfs2 cluster. </DIV>
<DIV>Does it have to be in the same cluster? Or can different ocfs2 clusters mount the same device as long as the ocfs2 versions match?<BR> </DIV>Regards,<BR>
<DIV>Saranya Sivakumar
<DIV><BR></DIV>
<DIV style="FONT-SIZE: 10pt; FONT-FAMILY: times new roman, new york, times, serif"><BR>
<DIV style="FONT-SIZE: 13px; FONT-FAMILY: arial, helvetica, sans-serif"><FONT face=Tahoma size=2>
<HR SIZE=1>
<B><SPAN style="FONT-WEIGHT: bold">From:</SPAN></B> Sunil Mushran <sunil.mushran@oracle.com><BR><B><SPAN style="FONT-WEIGHT: bold">To:</SPAN></B> Saranya Sivakumar <sarlavk@yahoo.com><BR><B><SPAN style="FONT-WEIGHT: bold">Sent:</SPAN></B> Wednesday, August 5, 2009 12:05:53 PM<BR><B><SPAN style="FONT-WEIGHT: bold">Subject:</SPAN></B> Re: ocfs2 question<BR></FONT><BR>Always email ocfs2-users. Others can help you too.<BR><BR>You have mismatching modules. Not sure how that can happen.<BR>Well, if one were to copy the modules around, it could happen.<BR><BR>1. Shutdown o2cb<BR># service o2cb stop<BR>Ensure no ocfs2 modules are still loaded in memory.<BR><BR>2. Remove the ocfs2 kernel pacakge.<BR># rpm --erase the ocfs2-2.6.9-42.0.3.ELsmp-1.2.9-1... package.<BR><BR>3. See if an ocfs2 module is still around.<BR># find /lib/modules/`uname -r` -name \*ocfs2\*<BR><BR>If so, then someone has been copying modules. Clean that up<BR>and
reinstall.<BR><BR>If you need more help, call oracle support.<BR><BR>Sunil<BR><BR>Saranya Sivakumar wrote:<BR>> Hi<BR>> We upgraded ocfs2 to 1.2.9 on the machine, but having errors trying to mount with the new version now.<BR>> /etc/init.d/o2cb status<BR>> Module "configfs": Loaded<BR>> Filesystem "configfs": Mounted<BR>> Module "ocfs2_nodemanager": Loaded<BR>> Module "ocfs2_dlm": Not loaded<BR>> Module "ocfs2_dlmfs": Not loaded<BR>> Filesystem "ocfs2_dlmfs": Not mounted<BR>> error while trying to mount<BR>> mount.ocfs2: No such device while mounting /dev/emcpowern1 on /orabackup1. Check 'dmesg' for more information on this error.<BR>> Aug 5 11:40:18 guard2 modprobe: FATAL: Error inserting ocfs2 (/lib/modules/2.6.9-42.0<BR>> .3.ELsmp/kernel/fs/ocfs2/ocfs2.ko): Unknown symbol in module, or unknown parameter (se<BR>> e dmesg)<BR>> Aug 5 11:41:09 guard2 kernel: ocfs2_dlm: disagrees
about version of symbol o2net_regi<BR>> ster_handler<BR>> Aug 5 11:41:09 guard2 kernel: ocfs2_dlm: Unknown symbol o2net_register_handler<BR>> Aug 5 11:41:09 guard2 kernel: ocfs2: Unknown symbol dlm_print_one_lock<BR>> Aug 5 11:41:09 guard2 kernel: ocfs2: Unknown symbol dlm_errmsg<BR>> Aug 5 11:41:09 guard2 kernel: ocfs2: Unknown symbol dlmlock<BR>> Aug 5 11:41:09 guard2 kernel: ocfs2: Unknown symbol dlm_unregister_eviction_cb<BR>> Aug 5 11:41:09 guard2 kernel: ocfs2: Unknown symbol dlm_unregister_domain<BR>> Aug 5 11:41:09 guard2 kernel: ocfs2: Unknown symbol dlm_register_domain<BR>> Aug 5 11:41:09 guard2 kernel: ocfs2: Unknown symbol dlm_register_eviction_cb<BR>> Aug 5 11:41:09 guard2 kernel: ocfs2: Unknown symbol dlm_setup_eviction_cb<BR>> Aug 5 11:41:09 guard2 kernel: ocfs2: disagrees about version of symbol o2net_register<BR>> _handler<BR>> Aug 5
11:41:09 guard2 kernel: ocfs2: Unknown symbol o2net_register_handler<BR>> Aug 5 11:41:09 guard2 kernel: ocfs2: Unknown symbol dlm_errname<BR>> Aug 5 11:41:09 guard2 kernel: ocfs2: Unknown symbol dlmunlock<BR>> <BR>> Please advice<BR>> Saranya<BR>> <BR>> <BR>> <BR>> ------------------------------------------------------------------------<BR>> *From:* Sunil Mushran <<A href="mailto:sunil.mushran@oracle.com" ymailto="mailto:sunil.mushran@oracle.com">sunil.mushran@oracle.com</A>><BR>> *To:* Saranya Sivakumar <<A href="mailto:sarlavk@yahoo.com" ymailto="mailto:sarlavk@yahoo.com">sarlavk@yahoo.com</A>><BR>> *Cc:* <A href="mailto:ocfs2-users@oss.oracle.com" ymailto="mailto:ocfs2-users@oss.oracle.com">ocfs2-users@oss.oracle.com</A><BR>> *Sent:* Tuesday, August 4, 2009 5:35:21 PM<BR>> *Subject:* Re: ocfs2 question<BR>> <BR>> ocfs2 1.2.3 is 3 years old. Suggest you upgrade that to
1.2.9.<BR>> <BR>> 1.2.3 and 1.2.9 are not network compatible. The mount will fail.<BR>> <BR>> Saranya Sivakumar wrote:<BR>> > Hi,<BR>> > We have a shared backup storage that resides on EMC storage and mounted using ocfs2 1.2.3 on a physical standby database in production.<BR>> > We are in the process of adding another physical standby database and need to mount the backup storage on the new physical standby as well,<BR>> > to be able to recover a backup that resides on it.<BR>> > But the new standby has ocfs2 1.2.9 installed.<BR>> > Eventually we will be removing the current physical standby from the configuration, but for a period of time both physical standby may be using the same backup storage.<BR>> > Is it ok to mount the shared storage using different ocfs2 versions on different machines?<BR>> > Please advice.<BR>> ><BR>> > Thanks,<BR>> > Sincerely,<BR>> >
Saranya Sivakumar<BR>> ><BR>> ><BR>> ><BR>> <BR>> <BR>> <BR><BR></DIV></DIV></DIV></div><br>
</body></html>