similar to: re: is it possible for the o2cb stack to monitor multiple "clusternames" on the same box

We have a test 10gR2 RAC cluster using ocfs2 filesystems for the Clusterware files and the Database files. We need to increase the node slots to accomodate new RAC nodes. Is it true that we will need to umount these filesystems for the upgrade (i.e. Database and Clusterware also)? We are planning to use the following command format to perform the node slot increase: # tunefs.ocfs2 ?N 3

This is actually not required, because ovirtsdk4 will use the system's global trust store if necessary. Therefore we can make it optional in all cases. --- docs/virt-v2v-output-rhv.pod | 5 ++++- v2v/output_rhv_upload.ml | 2 -- 2 files changed, 4 insertions(+), 3 deletions(-) diff --git a/docs/virt-v2v-output-rhv.pod b/docs/virt-v2v-output-rhv.pod index 04a894268..4520c9184 100644 ---

Working more on my cluster class, I can see other things coming up. I''ve ended up creating custom functions to perform basic array-handling tasks (like ''join'' and extracting a single element). I''ve also had to create a template for /etc/hosts because I can''t use the ''host'' type and iterate over an array. I know Puppet is trying very

Hi everybody, My problem is that I want to add a new node to an existing RAC with ocfs2, without stop the database. If I add a new node to an existing ocfs cluster, do I need to stop the ocfs in the others nodes of the cluster? I've tried to do it without stop the ocfs in the others nodes but I get the following error:

By default, o2cb fences the box by calling emergency_restart(). While this scheme works well in production, it comes in the way during testing as it does not let the tester take stack/core dumps for analysis. This patch allows user to dynamically change the fence method to panic() by: # echo "panic" > /sys/kernel/config/cluster/<clustername>/fence_method Signed-off-by: Sunil

It makes little sense to require the oVirt certificate, especially when the verification of the connection (-oo rhv-verifypeer) is disabled by default. The only work done with the certificate in that case is checking that it is a valid certificate file. Hence, make -oo rhv-cafile optional, requiring it only when -oo rhv-verifypeer is enabled. --- v2v/output_rhv_upload.ml | 16

Hi All, Scenario: I'm trying to install 9i rac on a 2 node cluster on OCFS2 OS: Oracle enterprise linux To my understanding, OCFS2 supports shared home installs which to my knowledge is not only can i have datafile and control files but also clustermanager files and binaries (pretty much everything: no files or executables need to kept local to any nodes). I have one single shared file for

Dear all, (apologoies - this has nothing to do with 4.7 being out, but is rather a long-standing issue that regularly bites us). Is there anything I could do to further the case of https://bugzilla.mindrot.org/show_bug.cgi?id=1008 As a summary, GSSAPI auth against machine in a DNS load-balanced server farm fails. SSH-1 Kerberos works. DNS load-balanced farm: Individual machines in the farm

Hi Greg, The following two patches move /sys/o2cb into /sys/fs/o2cb as we previously discussed. A symlink is created to maintain compatibility with existing versions of ocfs2-tools. A patch to automatically search /sys/fs/o2cb has been committed to the ocfs2-tools repo and a release with that code shouldn't be too far out. Old versions of ocfs2-tools have been tested and work fine with the

Hi, as far as I understand the current situation with locking looks like this: - o2cb supports cluster-aware flock(2). fcntl(2) locks are only local. - Pacemaker and cman also support cluster-aware fcntl(2) - There is no way for a userspace program to check if fcntl(2) is cluster- aware or not Is this correct? We would like to stick with the o2cb cluster stack but there are applications like

Hi, I might be overlooking the obvious, but I have yet to find "/etc/init.d/o2cb" however, I read that configuration uses this init script. Where is it? From: ocfs2-tools-1.2.4/README.O2CB [Starting the OCFS2 Clustering Services] O2CB is comprised of a simple node manager, heartbeat, TCP protocol, and DLM. The basic steps in startup are as follows: 1) Load the nodemanager,

On Wed, Jan 15, 2020 at 3:01 PM Richard W.M. Jones <rjones@redhat.com> wrote: > This is actually not required, because ovirtsdk4 will use the system's > global trust store if necessary. Therefore we can make it optional in > all cases. > The only way to avoid the cafile is to set insecure=True both when creating sdk connection and when connecting to imageio. Otherwise the

It is obsoleted since Dec 2005. Signed-off-by: WANG Cong <amwang at redhat.com> --- Documentation/ABI/obsolete/o2cb | 11 ----------- Documentation/ABI/removed/o2cb | 10 ++++++++++ Documentation/feature-removal-schedule.txt | 10 ---------- fs/ocfs2/cluster/sys.c | 9 --------- 4 files changed, 10 insertions(+), 30 deletions(-) --- diff

hi! i'm on debian lenny and trying to run ocfs2 on a dual primary drbd device. the drbd device is already set up as msDRBD0. to get dlm_controld.pcmk i installed it from source (from cluster-suite-3.0.10) now i configured a resource "resDLM" with 2 clones: primitive resDLM ocf:pacemaker:controld op monitor interval="120s" clone cloneDLM resDLM meta

Hi, I have added heartbeat mode as global, but when I do a mkfs and mount, and then check the mount, it says I am in local mode. Even /sys/kernel/config/cluster/ocfs2/heartbeat/mode says local. I am running CentOS with 3.x kernel, with ocfs2-tools-1.6.4-1118. mkfs -t ocfs2 -b 4K -C 1M -N 16 --cluster-stack=o2cb /dev/sdb mount -t ocfs2 /dev/sdb /mnt -o

I was testing ocfs2 on a 2 node cluster set up. ocfs2-tools version is 1.6.3 ocfs2 kernel version is 2.6.36 Using cman on 2 nodes node02 dw # ping_pong -rwm /data/test.dat 3 data increment = 2 14 locks/sec node01 dw # ping_pong -rw /data/test.dat 3 data increment = 2 10 locks/sec node02 dw # ping_pong -r /data/test.dat 3 1980 locks/sec Using cman on 1 node node02 dw #

v5 was here: https://www.redhat.com/archives/libguestfs/2018-March/msg00032.html There is only a single patch in this version because the other patches went upstream. This patch adds the virt-v2v -o rhv-upload mode (https://bugzilla.redhat.com/show_bug.cgi?id=1557273). Compared to v5, this adds the ability to make zero, trim and flush requests to the oVirt imageio server

v7 was here: https://www.redhat.com/archives/libguestfs/2018-March/msg00143.html Since then: - Earlier patches are now upstream. - The to-do list is moved from the commit message to the TODO file. - This version forces -of raw + -oa sparse and gives an error in any other mode. We intend to lift these restrictions later. - Tested against latest imageio which supports longer timeouts,

v8 was here: https://www.redhat.com/archives/libguestfs/2018-April/msg00022.html v8 -> v9: - Addresses the only feedback from Tomáš. Rich.

Am 06.03.23 um 16:45 schrieb Aki Tuomi: >> On 06/03/2023 16:52 EET Tim Evers <te-ml-ext at artfiles.de> wrote: >> >> >> Am 06.03.23 um 15:29 schrieb Aki Tuomi: >>>> On 06/03/2023 15:56 EET Tim Evers <te-ml-ext at artfiles.de> wrote: >>>> >>>> >>>> Am 06.03.23 um 14:49 schrieb Aki Tuomi: