I recompile my kernel without hugetlb .. and the result are the same..
My test program still resulting:
PATH=/dev/shm/teste123XX
page size=2
fd=3
ADDR_ORIG:0xe000a000 ADDR:0x
Erro
And Pacemaker still resulting because the mmap error:
Could not initialize Cluster Configuration Dat
On 06/01/2011 07:42 AM, william felipe_welter wrote:
> Steven,
>
> cat /proc/meminfo
> ...
> HugePages_Total: 0
> HugePages_Free:0
> HugePages_Rsvd:0
> HugePages_Surp:0
> Hugepagesize: 4096 kB
> ...
>
It definitely requires a kernel compile and setting the con
Hi,
I can't find how to configure pacemaker not to promote drbd on _any_
node when my slave node is not available during startup.
I've tried drbd fencing mechanisms
http://www.drbd.org/users-guide/s-pacemaker-fencing.html
but it works only for slaves only:
"(...) Pacemaker ensures that the Mas
Steven,
cat /proc/meminfo
...
HugePages_Total: 0
HugePages_Free:0
HugePages_Rsvd:0
HugePages_Surp:0
Hugepagesize: 4096 kB
...
Its 4MB..
How can i disable hugetlb ? ( passing CONFIG_HUGETLBFS=n at boot to kernel
?)
2011/6/1 Steven Dake
> On 06/01/2011 01:05
On 2011-05-31 16:04, Kulovits Christian - OS ITSC wrote:
> Sorry!! Yes, of course
>
> Corosync Cluster Engine, version '1.2.7' SVN revision '3008'
> CRM Version: 1.0.9 (da7075976b5ff0bee71074385f8fd02f296ec8a3)
> pacemaker 1.0.10-1.2.el5 - (none) x86_64
> corosync 1.2.7-1.1
Hi, Yan
An answer becomes slow, and really I'm sorry.
(2011/05/13 15:06), Gao,Yan wrote:
I understand that you think the improvement for the non-default
placement strategy makes sense to the "default" too. Though the
"default" is somewhat intended not to be affected by any "placement
strategy"
On 06/01/2011 01:05 AM, Steven Dake wrote:
> On 05/31/2011 09:44 PM, Angus Salkeld wrote:
>> On Tue, May 31, 2011 at 11:52:48PM -0300, william felipe_welter wrote:
>>> Angus,
>>>
>>> I make some test program (based on the code coreipcc.c) and i now i sure
>>> that are problems with the mmap systems
No,
We did the following:
Wget -O /etc/yum.repos.d/pacemaker.repo
http://clusterlabs.org/rpm/epel-5/clusterlabs.repo
yum install -y pacemaker.x86_64 corosync.x86_64 heartbeat.x86_64
regards, Christian
-Original Message-
From: Florian Haas [mailto:florian.h...@linbit.com]
Sent: Mittwoch
On 2011-05-31 16:04, Kulovits Christian - OS ITSC wrote:
> Sorry!! Yes, of course
>
> Corosync Cluster Engine, version '1.2.7' SVN revision '3008'
> CRM Version: 1.0.9 (da7075976b5ff0bee71074385f8fd02f296ec8a3)
> pacemaker 1.0.10-1.2.el5 - (none) x86_64
> corosync 1.2.7-1.1
On 05/31/2011 09:44 PM, Angus Salkeld wrote:
> On Tue, May 31, 2011 at 11:52:48PM -0300, william felipe_welter wrote:
>> Angus,
>>
>> I make some test program (based on the code coreipcc.c) and i now i sure
>> that are problems with the mmap systems call on sparc..
>>
>> Source code of my test prog
10 matches
Mail list logo