similar to: OCFS2-versions and SLES9/10, update

We are trying to install a 32-bit SLES9-SP4 paravirtual machine on a 64-bit SLES10-SP1 Dom0 host from scratch. We have two problems: 1. The YaST2 VM creation tool fails to create a vm if a network card is selected. 2. The initial vm boots from the SLES9-SP4 iso file, but then complains it can''t find the installation source. Here is the /etc/xen/vm/file (after manually editing for a

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi everyone, another problem I did not find a solution for... I ran "o2cb configure" and configured a cluster named "ocfs2". Lazy me, I did not invent a new name. Now this cluster must be renamed to avoid confusion, the name has to change to "sapcluster". I changed /etc/ocfs2/cluster.conf to the new name and ran

hi, i am trying to install oracle rac on fedora core 6 through iscsi. when i try to mount, mount.ocfs2: Invalid argument while mounting /dev/mapper/rac-crs on /mnt/crs. Check 'dmesg' for more information on this error. error log in dmesg, ocfs2: Unmounting device (253,11) on (node 255) (27354,0):ocfs2_parse_options:753 ERROR: Unrecognized mount option "datavolume" or missing

I'm using ocfs2 and all modules from Suse (SLES9), no self compilations. Here are the details: * 32-bit machine (writing to ocfs2 partition/LUN and where the corruption was reported): Kernel: 2.6.5-7.257-bigsmp #1 SMP i686 i386 GNU/Linux OCFS2 rpms: ocfs2console-1.2.1-4.2 ocfs2-tools-1.2.1-4.2 o2cb_ctl -V: o2cb_ctl version 1.2.1 /etc/init.d/o2cb status: Module "configfs":

Hi, we are using a SLES10 Patchlevel 3 with 12 Nodes hosting tomcat application servers. The cluster was running some time (about 200 days) without problems. Recently we needed to shutdown the cluster for maintenance and experianced very long times for the umount of the filesystem. It took something like 45 minutes each node and filesystem (12 x 45 minutes shutdown time). As a result the planned

Hey folks, I've been getting requests from the users that they want the OCFS2 filesystems aligned to 64k boundaries, however, when I began the project, the dummy of me, created the OCFS2 filesystem on top of the whole disk device (no partition) for example, one of the SAN devices would show up as /dev/dm-10, I created the filesystem using the following command: mkfs.ocfs2 -L SOMELABEL

I'm having some problems with ocfs2 and Suse 9.2. The documentation for ocfs2 says it comes with Suse 9.2. I've installed Suse and used YAST to get to SP2. # SPident -vv Summary (using 612 packages) Product/ServicePack conflict match update (shipped) SLES-9-x86_64 0 0% 293 47.9% 44 (1597 18.3%) SLES-9-x86_64-SP1 0 0% 110

All, We are pleased to announce the release of OCFS2 1.2.9-1 for RHEL4 and RHEL5 on x86, x86_64, ppc64 and ia64 architectures. This release includes bug fixes, most of which have been backported from the mainline kernel. Some of the more interesting ones have been described in detail. For the full list of changes, please refer to the news.

All, We are pleased to announce the release of OCFS2 1.2.9-1 for RHEL4 and RHEL5 on x86, x86_64, ppc64 and ia64 architectures. This release includes bug fixes, most of which have been backported from the mainline kernel. Some of the more interesting ones have been described in detail. For the full list of changes, please refer to the news.

Support for SLES9 seems to be pretty much lacking at the moment. The OCFS2 site [1] states OCFS2 is supported with SP2+. There actually does not exist a SP2+ for SLES9 (or should this rather read "will be supported in SP3" instead?). Latest RPMs that come with SLES9 SP2 are 0.99.14 which has critical known bugs and is unusable. Anybody got to compile current source on SLES9 x86_64?

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 This patch teaches the sles9 spec file to understand that configfs is built conditionally, and may not be present in the output. - -Jeff diff -ruNp ocfs2-1.2.5/vendor/sles9/ocfs2.spec-generic.in ocfs2-1.2.5.devel/vendor/sles9/ocfs2.spec-generic.in - --- ocfs2-1.2.5/vendor/sles9/ocfs2.spec-generic.in 2007-03-27 15:54:15.000000000 -0400 +++

My head hurts from trying to figure this out for the past several hours . . . I want to determine what provider to use based on a fact (thanks for the suse version fact btw) but I ain''t gettin it: What''s wrong? Am I going down the completely wrong path? Is there a better way? # suse-yum.pp case $suse_repo_name { #sled10-i586: {Package{ provider => rug}} sled10-i586:

Haven't really tried this yet, but I'm wondering what the direction is for official ocfs support on SLES9. Anyone know if there are plans to support OCFS 1.x on sles9 at some point? I know it's a 2.6 kernel instead of 2.4... thanks, Jeremy This message (including any attachments) contains confidential information intended for a specific individual(s) and purpose, and is protected

Hi, I'm new to this list and to the ocfs2 system and to clustering in general (3 strikes?--ack!). I have some problems with my first attempt at configuring an ocfs2 system and need some perspective. My setup is a Compaq Proliant CL380 2 node cluster with a shared storage array. Both nodes are currently running SLES 10. However, I am just trying to get one node working. I have read the

Hello, i want to install ocfs2-tools-1.2.0-1 on slackware 10.2 (up-to-date) with 2.6.17.2 kernel and i got error: ./configure checking build system type... i686-pc-linux-gnu checking host system type... i686-pc-linux-gnu checking for gcc... gcc checking for C compiler default output file name... a.out checking whether the C compiler works... yes checking whether we are cross compiling... no

Hello, i want to install ocfs2-tools-1.2.0-1 on slackware 10.2 (up-to-date) with 2.6.17.2 kernel and i got error: ./configure checking build system type... i686-pc-linux-gnu checking host system type... i686-pc-linux-gnu checking for gcc... gcc checking for C compiler default output file name... a.out checking whether the C compiler works... yes checking whether we are cross compiling... no

I received the following error messages in the system logs. Is this anything to be concerned with? kernel: (4074,0):ocfs2_populate_inode:234 ERROR: Invalid dinode: i_ino=1293597, i_blkno=1293597, signature = INODE01, flags = 0x0 kernel: (4074,0):ocfs2_read_locked_inode:389 ERROR: populate inode failed! i_blkno=1293597, i_ino=1293597 kernel: (4074,0):ocfs2_iget:131 ERROR: status = -116

Hello, First, thanks to all the people who helped to license this software under the GPL. This is a very important piece of work for the Free Software in the Enterprise Market. Just a few newbie questions. We've been thinking about implmenting a mail cluster with a Fiber SAN (IBM DS-4000) and OCFSv2 as the storage backend. The information on this volume will essentially be Postfix Maildirs,

I currenlty have the setup below, both nodes can see the shared drive ( confirmed with fdisk -l ) However I am unable to mount the shared device from node (2) after I mounted from node(1) I get the follwoign error mount.ocfs2: Transport endpoint is not connected while mounting /dev/sdb1 on /u02/oradata/orcl OS Red Hat uname -r --------------------------------- 2.6.9-22.ELsmp OCFS version

Thanks for the reply. Sorry I didn't provide more details, but, yes, these are HVM domains. I use PV domains whenever possible, but in the case of Windows XP, that isn't possible, so I have to use HVM. I haven't tried suspending to OCFS2 with a PV domain, but I may give that a shot. Still, I think it's strange that it works perfectly fine to my ext3 and reiser filesystems, but