Hi Ben Tanks in advance, really Im making wrong test, you are very right, but ... I update the clumager package to last version, and now the nodes aren't rebooting when start clumanager, but the quorum aren't not recognized and in this case Im using 2 raws that bind to 2 gnbd imported devices. There are the log of the cluster when start Feb 4 16:22:54 parati clumanager: [5283]: <notice> Starting Red Hat Cluster Manager... Feb 4 16:22:54 parati cluquorumd[5303]: <debug> changing loglevel from 5 to 7 Feb 4 16:22:54 parati cluquorumd[5303]: <info> IPv4-TB: 192.168.1.52 Feb 4 16:22:54 parati cluquorumd[5303]: <warning> STONITH: No drivers configured for host '192.168.1.56'! Feb 4 16:22:54 parati cluquorumd[5303]: <warning> STONITH: Data integrity may be compromised! Feb 4 16:22:54 parati cluquorumd[5303]: <warning> STONITH: No drivers configured for host '192.168.1.57'! Feb 4 16:22:54 parati cluquorumd[5303]: <warning> STONITH: Data integrity may be compromised! Feb 4 16:22:54 parati cluquorumd[5303]: <debug> spawn_daemon: starting /usr/sbin/clumembd. Feb 4 16:22:54 parati cluquorumd[5303]: <debug> IP tie-breaker in use, not starting disk thread. Feb 4 16:22:54 parati clumembd[5313]: <debug> Changing loglevel from 6 to 7 Feb 4 16:22:54 parati clumembd[5313]: <debug> Transmit thread set to ON Feb 4 16:22:54 parati clumembd[5313]: <debug> Overriding TKO count to be 20 Feb 4 16:22:54 parati clumembd[5313]: <debug> Broadcast hearbeating set to ON Feb 4 16:22:54 parati clumembd[5313]: <debug> Multicast heartbeat OFF Feb 4 16:22:54 parati clumembd[5313]: <debug> I am member #0 Feb 4 16:22:54 parati clumembd[5313]: <debug> Interface IP is 127.0.0.1 Feb 4 16:22:54 parati cluquorumd[5303]: <debug> Cluster I/F: eth0 [192.168.1.56] Feb 4 16:22:54 parati clumembd[5313]: <debug> broadcast is 127.255.255.255 Feb 4 16:22:54 parati clumembd[5313]: <debug> Interface IP is 192.168.1.56 Feb 4 16:22:54 parati clumembd[5313]: <debug> broadcast is 192.168.1.255 Feb 4 16:22:54 parati clumembd[5313]: <debug> Interface IP is 10.1.1.1 Feb 4 16:22:54 parati clumembd[5313]: <debug> broadcast is 10.255.255.255 Feb 4 16:22:54 parati clumembd[5313]: <debug> Cluster I/F: eth0 [192.168.1.56] Feb 4 16:22:54 parati clumembd[5313]: <debug> clumembd_start_watchdog: set duration to 14. Feb 4 16:22:54 parati clumembd[5313]: <debug> Waiting for requests. Feb 4 16:22:54 parati clumembd[5313]: <debug> Transmit thread: pulsar Feb 4 16:22:55 parati clumembd[5313]: <debug> Verified connect from member #0 (127.0.0.1) Feb 4 16:22:55 parati clumembd[5313]: <debug> MB: New connect: fd9 Feb 4 16:22:55 parati clumembd[5313]: <debug> MB: Received EV_REGISTER, fd9 Feb 4 16:22:55 parati cluquorumd[5303]: <debug> spawn_daemon: starting /usr/sbin/clulockd. Feb 4 16:22:55 parati clulockd[5316]: <debug> /usr/sbin/clulockd starting Feb 4 16:22:55 parati clulockd[5316]: <debug> Cluster I/F: eth0 [192.168.1.56] Feb 4 16:22:55 parati cluquorumd[5303]: <debug> Verified connect from member #0 (127.0.0.1) Feb 4 16:22:55 parati cluquorumd[5303]: <debug> Q: Received EV_REGISTER, fd6 Feb 4 16:22:55 parati cluquorumd[5303]: <debug> Q: Received EV_MEMB_UPDATE, fd5 Feb 4 16:22:55 parati clulockd[5316]: <debug> Quorum Event: NO QUORUM Feb 4 16:22:55 parati clulockd[5316]: <debug> Lock Keeper = Member #-1 Feb 4 16:23:05 parati clumembd[5313]: <notice> Member 192.168.1.56 UP Feb 4 16:23:05 parati clumembd[5313]: <debug> MB: Initiating vote on: 0x00000001 Feb 4 16:23:05 parati clumembd[5320]: <debug> VF: Connecting to member #0 Feb 4 16:23:05 parati clumembd[5313]: <debug> Verified connect from member #0 (192.168.1.56) Feb 4 16:23:05 parati clumembd[5313]: <debug> MB: New connect: fd11 Feb 4 16:23:05 parati clumembd[5320]: <debug> VF: Push 0.5320 #1 Feb 4 16:23:05 parati clumembd[5320]: <debug> VF: Sending to member #0 Feb 4 16:23:05 parati clumembd[5320]: <debug> VF: Checking for consensus... Feb 4 16:23:05 parati clumembd[5313]: <debug> MB: Received VF_MESSAGE, fd11 Feb 4 16:23:05 parati clumembd[5313]: <debug> VF_JOIN_VIEW from member #0! Key: 0x27456381 #1 Feb 4 16:23:05 parati clumembd[5313]: <debug> VF: Voting YES Feb 4 16:23:05 parati clumembd[5320]: <debug> VF: Member #0 voted YES Feb 4 16:23:05 parati clumembd[5320]: <debug> VF: Broadcasting FORMED Feb 4 16:23:05 parati clumembd[5320]: <debug> VF: Converge Time: 0.000000 Feb 4 16:23:05 parati clumembd[5313]: <debug> MB: Received VF_MESSAGE, fd11 Feb 4 16:23:05 parati clumembd[5313]: <debug> VF: Received VF_VIEW_FORMED, fd11 Feb 4 16:23:05 parati clumembd[5313]: <debug> VF: Commit Key 0x27456381 #1 from member #0 Feb 4 16:23:05 parati clumembd[5313]: <info> Membership View #1:0x00000001 Feb 4 16:23:06 parati clumembd[5313]: <debug> VF: pid 5320 exited, status 0 Feb 4 16:23:06 parati cluquorumd[5303]: <debug> Q: Received EV_MEMB_UPDATE, fd5 Feb 4 16:23:06 parati cluquorumd[5303]: <debug> Need 1 more members for quorum! Feb 4 16:23:06 parati cluquorumd[5303]: <debug> process_memb_update: Starting VF Feb 4 16:23:06 parati cluquorumd[5321]: <debug> VF: Connecting to member #0 Feb 4 16:23:06 parati cluquorumd[5303]: <debug> VF: Key 0x12345678 Still running Feb 4 16:23:06 parati cluquorumd[5303]: <debug> Verified connect from member #0 (192.168.1.56) Feb 4 16:23:06 parati cluquorumd[5303]: <debug> VF: Key 0x12345678 Still running Feb 4 16:23:06 parati cluquorumd[5321]: <debug> VF: Push 0.5321 #1 Feb 4 16:23:06 parati cluquorumd[5321]: <debug> VF: Sending to member #0 Feb 4 16:23:06 parati cluquorumd[5321]: <debug> VF: Checking for consensus... Feb 4 16:23:06 parati cluquorumd[5303]: <debug> Q: Received VF_MESSAGE, fd8 Feb 4 16:23:06 parati cluquorumd[5303]: <debug> VF_JOIN_VIEW from member #0! Key: 0x12345678 #1 Feb 4 16:23:06 parati cluquorumd[5303]: <debug> VF: Voting YES Feb 4 16:23:06 parati cluquorumd[5303]: <debug> VF: Key 0x12345678 Still running Feb 4 16:23:06 parati cluquorumd[5321]: <debug> VF: Member #0 voted YES Feb 4 16:23:06 parati cluquorumd[5321]: <debug> VF: Broadcasting FORMED Feb 4 16:23:06 parati cluquorumd[5321]: <debug> VF: Converge Time: 0.010000 Feb 4 16:23:06 parati cluquorumd[5303]: <debug> Q: Received VF_MESSAGE, fd8 Feb 4 16:23:06 parati cluquorumd[5303]: <debug> VF: Received VF_VIEW_FORMED, fd8 Feb 4 16:23:06 parati cluquorumd[5303]: <debug> VF: Commit Key 0x12345678 #1 from member #0 Feb 4 16:23:06 parati cluquorumd[5303]: <debug> Lack of Quorum Maintained Feb 4 16:23:06 parati clulockd[5316]: <debug> Quorum Event: NO QUORUM Feb 4 16:23:06 parati cluquorumd[5303]: <debug> VF: pid 5321 exited, status 0 Feb 4 16:23:06 parati clulockd[5316]: <debug> I am the new lock keeper Grateful Cristiano da Costa --- Original Message --- > On Thu, Feb 03, 2005 at 05:10:28PM -0200, > Cristiano da Costa wrote: > > Hello list > > <snip> > > > Then I make tests to simultaneos write data in > a gnbd device mapped and I note that the files > created by one node only appear to other node > when the device is reimported and remounted. > > <snip> > > > Partition /dev/gnbd/had11 is ext3 and are > mounted in both nodes, but the data write for > one node only is acessible to other when the > device is reimported and remounted. > > If you actually had shared storage, and did this > test, the results would be > the same. ext3 is not a clustered filesystem. > It never expects the data > on disk to change out from under it, so it > always trusts its cache. > In order to share storage between multiple > machines, you need a clustered > filesystem, like GFS. > > -Ben > > > Grateful > > > > > > > > > > _________________________ > > Cristiano da Costa > > Consultor > > Develop IT Solutions > > www.develop.com.br > > Fone: (51) 3386-6620 > > -- > > > > Linux-cluster@xxxxxxxxxx > > > http://www.redhat.com/mailman/listinfo/linux-cluster > > > -- > > Linux-cluster@xxxxxxxxxx > > http://www.redhat.com/mailman/listinfo/linux-cluster > >
