search for: pcmk

Displaying 20 results from an estimated 20 matches for "pcmk".

Did you mean: pcm
2011 Nov 23
1
Corosync init-script broken on CentOS6
.../usr/lib64/heartbeat/attrd /usr/lib64/heartbeat/pengine Observed: corosync My install options are: %packages @base @core @ha @nfs-file-server @network-file-system-client @resilient-storage @server-platform @server-policy @storage-client-multipath @system-admin-tools pax oddjob sgpio pacemaker dlm-pcmk screen lsscsi -rgmanager %end The logs from the server aren't terribly helpful either: Nov 23 12:13:45 cheapo4 corosync[2509]: [pcmk ] info: spawn_child: Forked child 2515 for process stonith-ng Nov 23 12:13:45 cheapo4 corosync[2509]: [pcmk ] info: spawn_child: Forked child 2516 for proc...
2012 Jul 10
1
live migration
Hello, everybody.? ? ?I use?NFS to do live migration?After input ?virsh --connect=qemu:///system --quiet migrate --live vm12 qemu+tcp://pcmk-1/system ?(vm12 ?is vm name,/pcmk-1 is host name)it use almost 10s for preparation.?During the 10s,the vm is still runing and can ping other vm. But if i input mkdir pcmk-6 in vm during the 10s,it say :mkdir: cannot create directory `pcmk-6': Read-only file system.? ? ?Anybody can tell me this...
2010 Apr 12
0
ocfs2/o2cb problem with openais/pacemaker
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 globally-unique="false" interleave="true" colocation...
2011 Nov 17
0
OCFS2 + CMAN/PCMK Kernel Error
Hello Everyone, Coming accross this once in a while. It's the test environemnt so not very important, and it does take a lot of abuse. Maybe it's of interest to someone. Starting cluster: Checking if cluster has been disabled at boot... [ OK ] Checking Network Manager... [ OK ] Global setup... [ OK ] Loading kernel modules... [ OK ] Mounting configfs... [ OK ]
2023 May 09
1
[PATCH 2/2] ocfs2: add error handling path when jbd2 enter ABORT status
...> Looked back the history, it is designed to panic in cluster mode: >> a2f2ddbf2baf ocfs2: __ocfs2_abort() should not enable panic for local mounts > > About the panic action from ocfs2_abort(), in my view, it's too scared to > acceptable. I am not familar with o2cb stack, in pcmk stack, there is > resource-agents RA Filesystem[1], which includes two level to detect fs abormal: > - Filesystem_monitor_10 : read the device > - Filesystem_monitor_20 : write and read a status file > > if ocfs2 enters abort status, Filesystem RA will detect it and trigger HA stack...
2009 Jun 15
1
Is Pacemaker integration ready to go?
I have seen many references online to being able to use OCFS2 with Pacemaker, but the documentation I have been able to find is very Sparse. I have kernel 2.6.29, and the latest DLM and Pacemaker (using openais) and OCFS2-Tools from GIT. (As of June 13). I was able to build ocfs2_controld.pcmk ... (With some minor changes to the makefile for my install) I noticed the OCF version of o2cb is not in the latest git snapshot of OCFS2-Tools I downloaded. (I found it at http://oss.oracle.com/pipermail/ocfs2-devel/2008-November/003400.html) Is the OCF o2cb not there because Pacemaker integrati...
2012 Aug 15
1
ocfs2_controld binary
...nyone ever built Cluster stack (openAIS, pacemaker, corosync + OCFS2 1.4) from source and got o2cb agent working with pacemaker? Got this from messages: /var/log/messages:Aug 14 15:05:20 ip-172-16-2-12 o2cb(resO2CB:0)[4239]: ERROR: Setup problem: couldn't find command: /usr/sbin/ocfs2_controld.pcmk Then I realized that the binary is really missing but when I tried to compile getting dlm source I got a issue once I am using corosync 1.4 and not 2.0 as dlm notice says. Pacemaker - 1.1.5 Thanks a lot in advance. -------------- next part -------------- An HTML attachment was scrubbe...
2011 Dec 20
1
OCFS2 problems when connectivity lost
Hello, We are having a problem with a 3-node cluster based on Pacemaker/Corosync with 2 primary DRBD+OCFS2 nodes and a quorum node. Nodes run on Debian Squeeze, all packages are from the stable branch except for Corosync (which is from backports for udpu functionality). Each node has a single network card. When the network is up, everything works without any problems, graceful shutdown of
2011 Jul 14
1
mount.ocfs2: Invalid argument while mounting /dev/mapper/xenconfig_part1 on /etc/xen/vm/. Check 'dmesg' for more information on this error.
...robin 0' prio=0 status=enabled |- 3:0:1:1 sde 8:64 active ghost running `- 4:0:1:1 sdi 8:128 active ghost running 4)Then I've create the first partition on /dev/mapper/xenconfig. 5)format the partition as ocfs2 mkfs.ocfs2 -F /dev/mapper/xenconfig_part1 mkfs.ocfs2 1.8.0 Cluster stack: pcmk Cluster name: pacemaker Stack Flags: 0x0 NOTE: Feature extended slot map may be enabled Label: Features: sparse extended-slotmap backup-super unwritten inline-data strict- journal-super xattr indexed-dirs refcount discontig-bg Block size: 4096 (12 bits) Cluster size: 4096 (12 bits) Volume size: 200...
2009 Mar 04
1
Patch to Pacemaker hooks in ocfs2_controld
Hi Guys, I overhauled and simplified the Pacemaker hooks recently. This patch: - Reuses more code from the Pacemaker libraries - Escalates fencing to the cluster manager instead of initiating it directly Attached patch is against master, or you can pull the original patch which is against an older version used by SUSE:
2023 May 08
1
[PATCH 2/2] ocfs2: add error handling path when jbd2 enter ABORT status
.... > > > > Looked back the history, it is designed to panic in cluster mode: > a2f2ddbf2baf ocfs2: __ocfs2_abort() should not enable panic for local mounts About the panic action from ocfs2_abort(), in my view, it's too scared to acceptable. I am not familar with o2cb stack, in pcmk stack, there is resource-agents RA Filesystem[1], which includes two level to detect fs abormal: - Filesystem_monitor_10 : read the device - Filesystem_monitor_20 : write and read a status file if ocfs2 enters abort status, Filesystem RA will detect it and trigger HA stack to do the handover resou...
2023 Apr 21
1
[PATCH] ocfs2: Fix wrong search logic in __ocfs2_resv_find_window
...ccess & download the URL [1] (I wrote it in patch commit log) without register SUSE account. Please check attachment file, which I downloaded from [1] and modified under the BZ comment 1. The trigger method is also in comment 1, I copy here: ./defragfs_test.sh -d /dev/vdf -m /mnt -n ocfstst -s pcmk -o /tmp -b 1024 -c 8192 note: you may modify '-n' (cluster name) & -s' (cluster stack). [1]: https://bugzilla.suse.com/show_bug.cgi?id=1131931 Thanks, Heming > > On 4/6/23 11:40 PM, Heming Zhao wrote: > > ** problem ** > > > > Current code triggers a de...
2009 Apr 24
1
ocfs2 1.4 and openais
Howdy! I have ocfs2 set up on a cluster running pacemaker and openais. When setting up ocfs2 using service o2cb configure, do I need to specify a different cluster stack besides o2cb? Thanks, -K -------------- next part -------------- An HTML attachment was scrubbed... URL: http://oss.oracle.com/pipermail/ocfs2-users/attachments/20090424/c97c81fc/attachment.html
2012 Jul 10
0
[Clustering] No OCFS2 Clusters with Pacemaker/Corosync?
Hello Fellow CentOS users. I was hoping to get some information on Pacemaker clusters using OCFS2 on CentOS 6.x. In my initial attempts to get this to work, I realized that Pacemaker is packaged much differently on CentOS than it is on Debian or SUSE. For example, /usr/sbin/dlm_controld.pcmk is missing and ocfs2-tools is nowhere to be found. Users could of course pull in packages from say Oracle Enterprise Linux, but I was curious as to why this is the case? Is OCFS2 not supported on CentOS? Thanks for the insight.
2012 Nov 14
0
fcntl(F_SETLK) returning ENOSYS
Hi all, tracing a couple of reports here (on a somewhat older version of OCFS2, with a user-space/pacemaker/dlm_controld.pcmk stack) where we see fnctl(F_SETLK) return ENOSYS. This happens after a node has failed/been fenced and recovered. It affects only individual mounts, not the whole system. The only code path that I can see so far that could lead to ENOSYS being returned here is from within dlm_controld:process_ploc...
2010 Dec 09
1
[PATCH] Call userspace script when self-fencing
Hi, According to comments in file fs/ocfs2/cluster/quorum.c:70 about the self-fencing operations : /* It should instead flip the file ?* system RO and call some userspace script. */ So, I tried to add it (but i did'nt find a way to flip the fs in RO). Here is a proposal for this functionnality, based on ocfs2-1.4.7. This patch add an entry 'fence_cmd' in /sys to specify an
2009 May 08
1
question of dentry number
I observer interesting dentry number during the dlm stress testing. The ocfs2 cluster stack is user space "pcmk". creating a empty directory, ls -al: total 8 drwxr-xr-x 2 root root 4096 2009-05-08 15:29 . drwxr-xr-x 4 root root 4096 2009-05-08 15:29 .. run script make_panic on single node, for 10 seconds, ls -al: total 12 drwxr-xr-x 2 root root 4096 2009-05-08 15:33 . drwxr-xr-x 4 root root...
2010 Jun 14
3
Diagnosing some OCFS2 error messages
Hello. I am experimenting with OCFS2 on Suse Linux Enterprise Server 11 Service Pack 1. I am performing various stress tests. My current exercise involves writing to files using a shared-writable mmap() from two nodes. (Each node mmaps and writes to different files; I am not trying to access the same file from multiple nodes.) Both nodes are logging messages like these: [94355.116255]
2023 Apr 21
2
[PATCH] ocfs2: Fix wrong search logic in __ocfs2_resv_find_window
Hi, Could you please share a reproducer? Thanks, Joseph On 4/6/23 11:40 PM, Heming Zhao wrote: > ** problem ** > > Current code triggers a defragfs bug [1]: > > ``` > tw-tst:~ # defragfs.ocfs2 /mnt/test_from_dd1 > defragfs.ocfs2 1.8.7 > [ERROR]Move extent failed:"/mnt/test_from_dd1" - No space left on device > [ERROR]"/mnt/test_from_dd1":No space
2023 May 05
1
[PATCH 2/2] ocfs2: add error handling path when jbd2 enter ABORT status
On 5/5/23 12:20 AM, Heming Zhao wrote: > On Thu, May 04, 2023 at 05:41:29PM +0800, Joseph Qi wrote: >> >> >> On 5/4/23 4:02 PM, Heming Zhao wrote: >>> On Thu, May 04, 2023 at 03:34:49PM +0800, Joseph Qi wrote: >>>> >>>> >>>> On 5/4/23 2:21 PM, Heming Zhao wrote: >>>>> On Thu, May 04, 2023 at 10:27:46AM +0800, Joseph