Hi!
One of the main problems I identified with POSIX shared memory (/dev/shm) in Linux is that changes to the shared memory don't affect the i-node, so you cannot tell from a "ls -rtl" which segments are still active and which are not. You can only see the creation time.
Maybe there should be a tool that identifies and cleans up obsolete shared memory.
I don't understand the part talking about the size of /dev/shm: It's shared memory. See "kernel.shmmax" and "kernel.shmall" in you sysctl settings (/etc/sysctl.conf).
Regards,
Ulrich
>>> Nikhil Utane <nikhil.subscribed at gmail.com> schrieb am 16.05.2016 um 14:31 in
Nachricht
<CAGNWmJVSye5PJgkdbFAi5AzO+Qq-j=2fS1c+0rGnqS994vV48w at mail.gmail.com>:
> Thanks Ken.
>
> Could you also respond on the second question?
>
>> Also, in /dev/shm I see that it created around 300+ files of around
>> 250 MB.
>>
>> For e.g.
>> -rw-rw---- 1 hacluste hacluste 8232 May 6 13:03
>> qb-cib_rw-response-25035-25038-10-header
>> -rw-rw---- 1 hacluste hacluste 540672 May 6 13:03
>> qb-cib_rw-response-25035-25038-10-data
>> -rw------- 1 hacluste hacluste 8232 May 6 13:03
>> qb-cib_rw-response-25035-25036-12-header
>> -rw------- 1 hacluste hacluste 540672 May 6 13:03
>> qb-cib_rw-response-25035-25036-12-data
>> And many more..
>>
>> We have limited space in /dev/shm and all these files are filling it
>> up. Are these all needed? Any way to limit? Do we need to do any
>> clean-up if pacemaker termination was not graceful? What's the
> recommended size for this folder for Pacemaker? Our cluster will have
> maximum 6 nodes.
>
> -Regards
> Nikhil
>
> On Sat, May 14, 2016 at 3:11 AM, Ken Gaillot <kgaillot at redhat.com> wrote:
>
>> On 05/08/2016 11:19 PM, Nikhil Utane wrote:
>> > Moving these questions to a different thread.
>> >
>> > Hi,
>> >
>> > We have limited storage capacity in our system for different folders.
>> > How can I configure to use a different folder for /var/lib/pacemaker?
>>
>> ./configure --localstatedir=/wherever (defaults to /var or ${prefix}/var)
>>
>> That will change everything that normally is placed or looked for under
>> /var (/var/lib/pacemaker, /var/lib/heartbeat, /var/run, etc.).
>>
>> Note that while ./configure lets you change the location of nearly
>> everything, /usr/lib/ocf/resource.d is an exception, because it is
>> specified in the OCF standard.
>>
>> >
>> >
>> > Also, in /dev/shm I see that it created around 300+ files of around
>> > 250 MB.
>> >
>> > For e.g.
>> > -rw-rw---- 1 hacluste hacluste 8232 May 6 13:03
>> > qb-cib_rw-response-25035-25038-10-header
>> > -rw-rw---- 1 hacluste hacluste 540672 May 6 13:03
>> > qb-cib_rw-response-25035-25038-10-data
>> > -rw------- 1 hacluste hacluste 8232 May 6 13:03
>> > qb-cib_rw-response-25035-25036-12-header
>> > -rw------- 1 hacluste hacluste 540672 May 6 13:03
>> > qb-cib_rw-response-25035-25036-12-data
>> > And many more..
>> >
>> > We have limited space in /dev/shm and all these files are filling it
>> > up. Are these all needed? Any way to limit? Do we need to do any
>> > clean-up if pacemaker termination was not graceful?
>> >
>> > -Thanks
>> > Nikhil
>> >
>> >
>> >
>> >
>> > _______________________________________________
>> > Users mailing list: Users at clusterlabs.org
>> > http://clusterlabs.org/mailman/listinfo/users
>> >
>> > Project Home: http://www.clusterlabs.org
>> > Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf
>> > Bugs: http://bugs.clusterlabs.org
>> >
>>
>>
>> _______________________________________________
>> Users mailing list: Users at clusterlabs.org
>> http://clusterlabs.org/mailman/listinfo/users
>>
>> Project Home: http://www.clusterlabs.org
>> Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf
>> Bugs: http://bugs.clusterlabs.org
>>