Nikola Ciprich
2009-Apr-02 14:14 UTC
[Ocfs2-users] problem stopping o2cb service on one of nodes
Hi, I'm trying ocfs2 RHEL5 distro, 2.6.29 kernel, ocfstools-1.4.1. I'm using DRBD in primary/primary mode as shared storage... I've configured the service according to quickstart document, and everything works, but when I umount fs on both nodes, stopping o2cb service on one of the nodes always fails with: [root at vbox4 sysconfig]# /etc/rc.d/init.d/o2cb stop Stopping O2CB cluster vb34: Failed Unable to stop cluster as heartbeat region still active and configfs still contains: /sys/kernel/config/cluster/vb34/... I've tried it also with older kernels with same result. What can I be doing wrong? Could somebody advise me where should I look? thanks a lot in advance! best regards nik -- ------------------------------------- Nikola CIPRICH LinuxBox.cz, s.r.o. 28. rijna 168, 709 01 Ostrava tel.: +420 596 603 142 fax: +420 596 621 273 mobil: +420 777 093 799 www.linuxbox.cz mobil servis: +420 737 238 656 email servis: servis at linuxbox.cz -------------------------------------
Hi Nikola, Nikola Ciprich wrote:> Hi, > I'm trying ocfs2 RHEL5 distro, 2.6.29 kernel, ocfstools-1.4.1. I'm using DRBD in primary/primary mode > as shared storage... > > I've configured the service according to quickstart document, and everything works, > but when I umount fs on both nodes, stopping o2cb service on one of the nodes always > fails with: > > [root at vbox4 sysconfig]# /etc/rc.d/init.d/o2cb stop > Stopping O2CB cluster vb34: Failed > Unable to stop cluster as heartbeat region still activeIt looks that your disk heartbeat is still there. I don't know the specific reason, maybe http://oss.oracle.com/bugzilla/show_bug.cgi?id=1053 ? but you can stop it manually. 1. ocfs2_hb_ctl -I -d <device> or ocfs2_hb_ctl -I -u <uuid> this will tell you the reference number for the hearbeat. 2. ocfs2_hb_ctl -K -d <device> <service> or ocfs2_hb_ctl -K -u <uuid> <service> this will killed the heartbeat manually. service is the stack you used, and it should be "o2cb" in your case. btw, you can try cfs2_hb_ctl -K -u <uuid> <service> to see whether it is the same problem as bug 1053. Regards, Tao