On 05/08/2013, at 9:12 PM, Thomas Glanzmann <[email protected]> wrote:
> Hello Andrew, > >> did they ensure everything was flushed to disk first? > > (apache-03) [/var] cat /proc/sys/vm/dirty_expire_centisecs > 3000 > > So dirty data should be flushed within 3 seconds. But I lost at least 24 > hours maybe even more. So it seems that pacemaker / heartbeat does not > do persistant changes when I changed the config, which is strange but > I'll try to reproduce that in a lab, too. Aug 4 19:03:55 apache-03 cib: [3226]: ERROR: cib_diskwrite_complete: Disk write failed: status=134, signo=6, exitcode=0 Aug 4 19:03:55 apache-03 cib: [3226]: ERROR: cib_diskwrite_complete: Disabling disk writes after write failure Aug 4 19:03:56 apache-04-intern cib: [3197]: ERROR: cib_diskwrite_complete: Disk write failed: status=134, signo=6, exitcode=0 Aug 4 19:03:56 apache-04-intern cib: [3197]: ERROR: cib_diskwrite_complete: Disabling disk writes after write failure That is the point at which changes stopped going to disk. As I said "The cluster only stops doing this if writing to disk fails at some point - but there would have been an error in your logs if that were the case." >> thats not where recent versions of pacemaker keep the cib by default. >> check /var/lib/pacemaker/cib too > > The directory does not exist. Oh, right. It didn't exist in 1.1.7 yet > I'll provide you with the logs this > evening. _______________________________________________ Linux-HA mailing list [email protected] http://lists.linux-ha.org/mailman/listinfo/linux-ha See also: http://linux-ha.org/ReportingProblems
