-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Herbert van den Bergh [27.04.2010 18:23]: > > If you're not even in control of the RAC environment, then I doubt > the administrator of that cluster would be happy to have your > application servers as part of their database cluster. I don't know > how many nodes you have, but let's say you have a 2 node RAC cluster > and 4 application servers. When there is a network connectivity > problem between the app servers and the database servers, let's say > because the switch in the app server rack failed, the app servers > will have quorum, and the database servers will reboot themselves. > All of them. Do you think that will make your DBA happy?
I do not plan to make them happy. Why should I? They don't make me happy, either. The OCFS2 cluster is for sharing a volume between the RAC and SAP only. The machines are connected to the same switch. Maybe they'll even get an interconnect with a separate subnet outside of switches. Since it is a "political" decision to put all SAP databases into RAC and SAP orders that in this case we have to share a filesystem between SAP and RAC, I don't have big choices. > Also, you mentioned that you were using VM's for your app servers. > Do you intend to cluster the VM's with the RAC servers, or were you > using them just for building the OCFS2 module? At the moment, I'm just trying to compile. I have to transport all my physical SAP servers into virtal machines until end of august because the hardware support ends then. > What is the requirement for this shared filesystem? Why do you > believe OCFS2 is the only option? I know the SAP notes. SAP note 527843 tells me that I may use the following combinations: RAC 11.2.0.1: * Oracle Clusterware 11.2.0.1 + OCFS2 1.2.x (x>=9) or * Oracle Clusterware 11.2.0.1 + Network Appliance NFS or * Oracle Clusterware 11.2.0.1 + EMC Celerra NFS RAC 9.2/10.2: * Oracle Clusterware + OCFS2 1.2.x (x>=3) or * Oracle Clusterware + Network Appliance NFS oder * Oracle Clusterware + EMC Celerra NFS or * From SLES 10 SP2 or RHEL 5.2 on: Oracle Clusterware + OCFS2 1.4.x We do not use any of "Network Appliance NFS" or "EMC Celerra NFS". But there already is a OCFS2 cluster between the SLES9 machines running SAP, so there's basical knowledge of this FS. > As for the source code only building on {RH,O}EL, that's a backport > of the mainline code. Oracle backports to RedHat / Oracle Enterprise > Linux, and Novell backports to SLES. The kernels are different, so > the code is different. > > Thanks, Herbert. Regads, Werner > > On 04/27/2010 01:28 AM, Werner Flamme wrote: Unfortunately, I do not > run the Oracle RAC. The RAC runs with Oracle Unbreakable Linux. I am > sorry for that decision, but I can't change it. > > SAP does not forbid to use Oracle's version of Linux. SAP only says > that SAP systems are fully supported on RHEL or SLES only (concerning > Linux). It was simpler to have me change from SLES to RHEL, but since > RHEL support is not as detailed as Novell/SUSE's (SAP priority > support) plus it is a lot more expensive, I cannot convince my boss > to change. > > And I still do not understand why you provide sourcecode that will > compile on RHEL only. Especially when you provide ready binaries for > RHEL at the same time. Or did Larry buy RedHat in between? There was > such a noise about Sun one may have just not registerd this... ;-) > > Regards, Werner > > Herbert van den Bergh [26.04.2010 18:21]: > >>>> Also, if you were to call Novell Support with an OCFS2 related >>>> issue, they most likely would ask you to reproduce it without >>>> the EL5 nodes in the OCFS2 cluster. And the same thing with >>>> Oracle. It's not a supported configuration, so you're on your >>>> own. >>>> >>>> Since the Oracle database is certified on SLES, why not use it >>>> for both database and application servers, if you believe you >>>> must use OCFS2 to share storage between the two? >>>> >>>> Thanks, Herbert. >>>> >>>> >>>> On 04/26/2010 09:12 AM, Herbert van den Bergh wrote: >>>> >>>>> In order for the application servers and database servers to >>>>> share an OCFS2 filesystem, they must be members of the same >>>>> cluster. Unless of course you stop OCFS2 on one server and >>>>> start it on the other. Then you might as well just use ext3. >>>>> Also, I don't think your configuration would be supported by >>>>> Oracle, so you may want to get confirmation before you put >>>>> such a setup in production. >>>>> >>>>> Thanks, Herbert. >>>>> >>>>> >>>>> On 04/26/2010 08:46 AM, Werner Flamme wrote: >>>>> >>>>> >>>> I wonder why the OCFS2 versions provided by Oracle and Novell >>>> are not necessarily kept compatible. Some strange policy at >>>> Novell's, I guess. Or not enough money^Wmanpower to go along >>>> with every new version. >>>> >>>> My application servers aren't a part of RAC. I just have to >>>> share a filesystem between RAC and SAP application servers. >>>> Since we are migrating from single box SAP servers to the RAC >>>> solution, we need a cluster file system. SAP only allows OCFS2 >>>> and Veritas filesystems. >>>> >>>> Regards, Werner >>>> >>>> >>>> Herbert van den Bergh [26.04.2010 17:29]: >>>> >>>> >>>> >>>>>>>> The OCFS2 versions provided by Oracle and Novell are >>>>>>>> not necessarily kept compatible. So there is always a >>>>>>>> risk of losing access to the filesystem when you update >>>>>>>> one or the other. Also, do you really want to have >>>>>>>> your application servers be part of your database >>>>>>>> cluster? You wouldn't want some network issue to cause >>>>>>>> your database servers to be rebooted, would you? >>>>>>>> >>>>>>>> Thanks, Herbert. >>>>>>>> >>>>>>>> >>>>>>>> On 04/26/2010 08:25 AM, Werner Flamme wrote: That's a >>>>>>>> bad idea. I do not like file systems that hang all >>>>>>>> clients when the server is on reboot or unreachable. >>>>>>>> I'd rather a shared filesystem. >>>>>>>> >>>>>>>> Regards, Werner >>>>>>>> >>>>>>>> Herbert van den Bergh [26.04.2010 17:13]: >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>>>>> That's a bad idea. Use NFS instead. >>>>>>>>>>> >>>>>>>>>>> Thanks, Herbert. >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> On 04/26/2010 01:48 AM, Werner Flamme wrote: >>>>>>>>>>> Sunil Mushran [20.04.2010 18:28]: >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>>>>> 1.4 tree is only meant to be build against >>>>>>>>>>>>>> EL5 U2+. Not SLES nor any other kernel >>>>>>>>>>>>>> tree. SLES9/10/11 already includes ocfs2. >>>>>>>>>>>>>> >>>>>>>>>>>>>> >>>>>>>>>>>>>> >>>>>>>>>>>>>> >>>>>>>>>>>>>> >>>>>>>>>>> For RHEL there are readyly built packages, why >>>>>>>>>>> would I build my own packages then? The build >>>>>>>>>>> worked fine with another SLES10. >>>>>>>>>>> >>>>>>>>>>> Yes, ocfs2 is included by SLES. Not SLES 11, of >>>>>>>>>>> course - it is in the separately sold "High >>>>>>>>>>> Availability" package. But the version included >>>>>>>>>>> in SLES9/10 does not allow to mount a volume that >>>>>>>>>>> has been created by RHEL (or, in that case, the >>>>>>>>>>> software that is sold as Oracle Unbreakable >>>>>>>>>>> Linux). It refuses to mount with "mount.ocfs2: >>>>>>>>>>> Unsupported feature(s) found while opening device >>>>>>>>>>> /dev/sdb". >>>>>>>>>>> >>>>>>>>>>> This sure is a feature, I know. However, I do >>>>>>>>>>> have to share a volume between the Oracle RAC >>>>>>>>>>> running on the "Oracle Unbreakable Linux" boxes >>>>>>>>>>> and my SAP servers running with SLES. How can I >>>>>>>>>>> do that? Do I really have to delete the >>>>>>>>>>> filesystems on the RAC an re-create them with >>>>>>>>>>> the (older) versions on SLES? >>>>>>>>>>> >>>>>>>>>>> Regards, Werner >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>>>>> Werner Flamme wrote: Hi, >>>>>>>>>>>>>> >>>>>>>>>>>>>> next VM, next trouble :-( >>>>>>>>>>>>>> >>>>>>>>>>>>>> Now I work inside a VM with SLES 11. >>>>>>>>>>>>>> Configuring ocfs2-1.4.7 (via LANG=C >>>>>>>>>>>>>> ./configure >>>>>>>>>>>>>> --with-kernel-source=/usr/src/linux-2.6.27.45-0.1) >>>>>>>>>>>>>> was successful, but compiling fails: >>>>>>>>>>>>>> >>>>>>>>>>>>>> ---snip--- # LANG=C make make -C fs >>>>>>>>>>>>>> make[1]: Entering directory >>>>>>>>>>>>>> `/usr/local/src/ocfs2-1.4.7/fs' make -C >>>>>>>>>>>>>> ocfs2 stamp-md5 make[2]: Entering directory >>>>>>>>>>>>>> `/usr/local/src/ocfs2-1.4.7/fs/ocfs2' >>>>>>>>>>>>>> make[2]: Leaving directory >>>>>>>>>>>>>> `/usr/local/src/ocfs2-1.4.7/fs/ocfs2' make >>>>>>>>>>>>>> -C ocfs2/cluster stamp-md5 make[2]: >>>>>>>>>>>>>> Entering directory >>>>>>>>>>>>>> `/usr/local/src/ocfs2-1.4.7/fs/ocfs2/cluster' >>>>>>>>>>>>>> >>>>>>>>>>>>>> make[2]: Leaving directory `/usr/local/src/ocfs2-1.4.7/fs/ocfs2/cluster' >>>>>>>>>>>>>> make -C ocfs2/dlm stamp-md5 make[2]: >>>>>>>>>>>>>> Entering directory >>>>>>>>>>>>>> `/usr/local/src/ocfs2-1.4.7/fs/ocfs2/dlm' >>>>>>>>>>>>>> make[2]: Leaving directory >>>>>>>>>>>>>> `/usr/local/src/ocfs2-1.4.7/fs/ocfs2/dlm' >>>>>>>>>>>>>> make -C >>>>>>>>>>>>>> /lib/modules/2.6.27.45-0.1-default/build >>>>>>>>>>>>>> M=/usr/local/src/ocfs2-1.4.7/fs modules >>>>>>>>>>>>>> make[2]: Entering directory >>>>>>>>>>>>>> `/usr/src/linux-2.6.27.45-0.1-obj/x86_64/default' >>>>>>>>>>>>>> >>>>>>>>>>>>>> make -C ../../../linux-2.6.27.45-0.1 >>>>>>>>>>>>>> O=/usr/src/linux-2.6.27.45-0.1-obj/x86_64/default/. >>>>>>>>>>>>>> modules CC [M] >>>>>>>>>>>>>> /usr/local/src/ocfs2-1.4.7/fs/ocfs2/compat_should_remove_suid.o >>>>>>>>>>>>>> >>>>>>>>>>>>>> CC [M] >>>>>>>>>>>>>> /usr/local/src/ocfs2-1.4.7/fs/ocfs2/compat_generic_segment_checks.o >>>>>>>>>>>>>> >>>>>>>>>>>>>> CC [M] /usr/local/src/ocfs2-1.4.7/fs/ocfs2/alloc.o >>>>>>>>>>>>>> CC [M] >>>>>>>>>>>>>> /usr/local/src/ocfs2-1.4.7/fs/ocfs2/aops.o >>>>>>>>>>>>>> CC [M] >>>>>>>>>>>>>> /usr/local/src/ocfs2-1.4.7/fs/ocfs2/buffer_head_io.o >>>>>>>>>>>>>> >>>>>>>>>>>>>> CC [M] /usr/local/src/ocfs2-1.4.7/fs/ocfs2/dcache.o >>>>>>>>>>>>>> CC [M] >>>>>>>>>>>>>> /usr/local/src/ocfs2-1.4.7/fs/ocfs2/dir.o >>>>>>>>>>>>>> /usr/local/src/ocfs2-1.4.7/fs/ocfs2/dir.c: >>>>>>>>>>>>>> In function 'ocfs2_readdir': >>>>>>>>>>>>>> /usr/local/src/ocfs2-1.4.7/fs/ocfs2/dir.c:865: >>>>>>>>>>>>>> warning: passing argument 2 of >>>>>>>>>>>>>> 'ocfs2_dir_foreach_blk' from incompatible >>>>>>>>>>>>>> pointer type CC [M] >>>>>>>>>>>>>> /usr/local/src/ocfs2-1.4.7/fs/ocfs2/dlmglue.o >>>>>>>>>>>>>> >>>>>>>>>>>>>> CC [M] /usr/local/src/ocfs2-1.4.7/fs/ocfs2/export.o >>>>>>>>>>>>>> /usr/local/src/ocfs2-1.4.7/fs/ocfs2/export.c: >>>>>>>>>>>>>> In function 'ocfs2_decode_fh': >>>>>>>>>>>>>> /usr/local/src/ocfs2-1.4.7/fs/ocfs2/export.c:302: >>>>>>>>>>>>>> error: 'struct export_operations' has no >>>>>>>>>>>>>> member named 'find_exported_dentry' >>>>>>>>>>>>>> /usr/local/src/ocfs2-1.4.7/fs/ocfs2/export.c: >>>>>>>>>>>>>> At top level: >>>>>>>>>>>>>> /usr/local/src/ocfs2-1.4.7/fs/ocfs2/export.c:311: >>>>>>>>>>>>>> error: unknown field 'decode_fh' specified >>>>>>>>>>>>>> in initializer >>>>>>>>>>>>>> /usr/local/src/ocfs2-1.4.7/fs/ocfs2/export.c:311: >>>>>>>>>>>>>> warning: initialization from incompatible >>>>>>>>>>>>>> pointer type >>>>>>>>>>>>>> /usr/local/src/ocfs2-1.4.7/fs/ocfs2/export.c:315: >>>>>>>>>>>>>> error: unknown field 'get_dentry' specified >>>>>>>>>>>>>> in initializer >>>>>>>>>>>>>> /usr/local/src/ocfs2-1.4.7/fs/ocfs2/export.c:315: >>>>>>>>>>>>>> warning: excess elements in struct >>>>>>>>>>>>>> initializer >>>>>>>>>>>>>> /usr/local/src/ocfs2-1.4.7/fs/ocfs2/export.c:315: >>>>>>>>>>>>>> warning: (near initialization for >>>>>>>>>>>>>> 'ocfs2_export_ops') make[6]: *** >>>>>>>>>>>>>> [/usr/local/src/ocfs2-1.4.7/fs/ocfs2/export.o] >>>>>>>>>>>>>> Error 1 make[5]: *** >>>>>>>>>>>>>> [/usr/local/src/ocfs2-1.4.7/fs/ocfs2] Error >>>>>>>>>>>>>> 2 make[4]: *** >>>>>>>>>>>>>> [_module_/usr/local/src/ocfs2-1.4.7/fs] >>>>>>>>>>>>>> Error 2 make[3]: *** [sub-make] Error 2 >>>>>>>>>>>>>> make[2]: *** [all] Error 2 make[2]: Leaving >>>>>>>>>>>>>> directory >>>>>>>>>>>>>> `/usr/src/linux-2.6.27.45-0.1-obj/x86_64/default' >>>>>>>>>>>>>> >>>>>>>>>>>>>> make[1]: *** [build-modules] Error 2 >>>>>>>>>>>>>> make[1]: Leaving directory >>>>>>>>>>>>>> `/usr/local/src/ocfs2-1.4.7/fs' make: *** >>>>>>>>>>>>>> [fs] Error 2 ---pins--- >>>>>>>>>>>>>> >>>>>>>>>>>>>> Quite the same with ocfs2-1.4.4: >>>>>>>>>>>>>> ---snip--- # LANG=C make make -C fs >>>>>>>>>>>>>> make[1]: Entering directory >>>>>>>>>>>>>> `/usr/local/src/ocfs2-1.4.4/fs' make -C >>>>>>>>>>>>>> ocfs2 stamp-md5 make[2]: Entering directory >>>>>>>>>>>>>> `/usr/local/src/ocfs2-1.4.4/fs/ocfs2' >>>>>>>>>>>>>> make[2]: Leaving directory >>>>>>>>>>>>>> `/usr/local/src/ocfs2-1.4.4/fs/ocfs2' make >>>>>>>>>>>>>> -C ocfs2/cluster stamp-md5 make[2]: >>>>>>>>>>>>>> Entering directory >>>>>>>>>>>>>> `/usr/local/src/ocfs2-1.4.4/fs/ocfs2/cluster' >>>>>>>>>>>>>> >>>>>>>>>>>>>> make[2]: Leaving directory `/usr/local/src/ocfs2-1.4.4/fs/ocfs2/cluster' >>>>>>>>>>>>>> make -C ocfs2/dlm stamp-md5 make[2]: >>>>>>>>>>>>>> Entering directory >>>>>>>>>>>>>> `/usr/local/src/ocfs2-1.4.4/fs/ocfs2/dlm' >>>>>>>>>>>>>> make[2]: Leaving directory >>>>>>>>>>>>>> `/usr/local/src/ocfs2-1.4.4/fs/ocfs2/dlm' >>>>>>>>>>>>>> make -C >>>>>>>>>>>>>> /lib/modules/2.6.27.45-0.1-default/build >>>>>>>>>>>>>> M=/usr/local/src/ocfs2-1.4.4/fs modules >>>>>>>>>>>>>> make[2]: Entering directory >>>>>>>>>>>>>> `/usr/src/linux-2.6.27.45-0.1-obj/x86_64/default' >>>>>>>>>>>>>> >>>>>>>>>>>>>> make -C ../../../linux-2.6.27.45-0.1 >>>>>>>>>>>>>> O=/usr/src/linux-2.6.27.45-0.1-obj/x86_64/default/. >>>>>>>>>>>>>> modules CC [M] >>>>>>>>>>>>>> /usr/local/src/ocfs2-1.4.4/fs/ocfs2/compat_should_remove_suid.o >>>>>>>>>>>>>> >>>>>>>>>>>>>> CC [M] >>>>>>>>>>>>>> /usr/local/src/ocfs2-1.4.4/fs/ocfs2/compat_generic_segment_checks.o >>>>>>>>>>>>>> >>>>>>>>>>>>>> CC [M] /usr/local/src/ocfs2-1.4.4/fs/ocfs2/alloc.o >>>>>>>>>>>>>> CC [M] >>>>>>>>>>>>>> /usr/local/src/ocfs2-1.4.4/fs/ocfs2/aops.o >>>>>>>>>>>>>> CC [M] >>>>>>>>>>>>>> /usr/local/src/ocfs2-1.4.4/fs/ocfs2/buffer_head_io.o >>>>>>>>>>>>>> >>>>>>>>>>>>>> CC [M] /usr/local/src/ocfs2-1.4.4/fs/ocfs2/dcache.o >>>>>>>>>>>>>> CC [M] >>>>>>>>>>>>>> /usr/local/src/ocfs2-1.4.4/fs/ocfs2/dir.o >>>>>>>>>>>>>> /usr/local/src/ocfs2-1.4.4/fs/ocfs2/dir.c: >>>>>>>>>>>>>> In function 'ocfs2_readdir': >>>>>>>>>>>>>> /usr/local/src/ocfs2-1.4.4/fs/ocfs2/dir.c:865: >>>>>>>>>>>>>> warning: passing argument 2 of >>>>>>>>>>>>>> 'ocfs2_dir_foreach_blk' from incompatible >>>>>>>>>>>>>> pointer type CC [M] >>>>>>>>>>>>>> /usr/local/src/ocfs2-1.4.4/fs/ocfs2/dlmglue.o >>>>>>>>>>>>>> >>>>>>>>>>>>>> CC [M] /usr/local/src/ocfs2-1.4.4/fs/ocfs2/export.o >>>>>>>>>>>>>> /usr/local/src/ocfs2-1.4.4/fs/ocfs2/export.c: >>>>>>>>>>>>>> In function 'ocfs2_decode_fh': >>>>>>>>>>>>>> /usr/local/src/ocfs2-1.4.4/fs/ocfs2/export.c:233: >>>>>>>>>>>>>> error: 'struct export_operations' has no >>>>>>>>>>>>>> member named 'find_exported_dentry' >>>>>>>>>>>>>> /usr/local/src/ocfs2-1.4.4/fs/ocfs2/export.c: >>>>>>>>>>>>>> At top level: >>>>>>>>>>>>>> /usr/local/src/ocfs2-1.4.4/fs/ocfs2/export.c:242: >>>>>>>>>>>>>> error: unknown field 'decode_fh' specified >>>>>>>>>>>>>> in initializer >>>>>>>>>>>>>> /usr/local/src/ocfs2-1.4.4/fs/ocfs2/export.c:242: >>>>>>>>>>>>>> warning: initialization from incompatible >>>>>>>>>>>>>> pointer type >>>>>>>>>>>>>> /usr/local/src/ocfs2-1.4.4/fs/ocfs2/export.c:246: >>>>>>>>>>>>>> error: unknown field 'get_dentry' specified >>>>>>>>>>>>>> in initializer >>>>>>>>>>>>>> /usr/local/src/ocfs2-1.4.4/fs/ocfs2/export.c:246: >>>>>>>>>>>>>> warning: excess elements in struct >>>>>>>>>>>>>> initializer >>>>>>>>>>>>>> /usr/local/src/ocfs2-1.4.4/fs/ocfs2/export.c:246: >>>>>>>>>>>>>> warning: (near initialization for >>>>>>>>>>>>>> 'ocfs2_export_ops') make[6]: *** >>>>>>>>>>>>>> [/usr/local/src/ocfs2-1.4.4/fs/ocfs2/export.o] >>>>>>>>>>>>>> Error 1 make[5]: *** >>>>>>>>>>>>>> [/usr/local/src/ocfs2-1.4.4/fs/ocfs2] Error >>>>>>>>>>>>>> 2 make[4]: *** >>>>>>>>>>>>>> [_module_/usr/local/src/ocfs2-1.4.4/fs] >>>>>>>>>>>>>> Error 2 make[3]: *** [sub-make] Error 2 >>>>>>>>>>>>>> make[2]: *** [all] Error 2 make[2]: Leaving >>>>>>>>>>>>>> directory >>>>>>>>>>>>>> `/usr/src/linux-2.6.27.45-0.1-obj/x86_64/default' >>>>>>>>>>>>>> >>>>>>>>>>>>>> make[1]: *** [build-modules] Error 2 >>>>>>>>>>>>>> make[1]: Leaving directory >>>>>>>>>>>>>> `/usr/local/src/ocfs2-1.4.4/fs' make: *** >>>>>>>>>>>>>> [fs] Error 2 ---pins--- >>>>>>>>>>>>>> >>>>>>>>>>>>>> What can I do? Some software missing? >>>>>>>>>>>>>> >>>>>>>>>>>>>> Regards, Werner >>>>>>>>>>>>>> >>>>>>>>>>>>>> >>>>>>>>>>>>>> >>>>>>>>>>>>>> >>>>>>>>>>>>>> >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.12 (GNU/Linux) Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org/ iEYEARECAAYFAkvYEgAACgkQk33Krq8b42OJmwCdEkfjgscApJO0xiYk1lR/jSPm /2EAniUlTeA033T/VFOqNd8SU1hhmbNT =Vq0y -----END PGP SIGNATURE----- _______________________________________________ Ocfs2-users mailing list Ocfs2-users@oss.oracle.com http://oss.oracle.com/mailman/listinfo/ocfs2-users