Hello, Many thanks for your message. Well, actually the article is from my blog... So, I already executed all steps described there, and much more ideas also. The synchronization solved the problem of single directly writing, but not **concurrent** access over gnbd. oopses_ok is a frigthning proposition... Read across RH docs, tried many cluster.conf configurations, enabled debug and collected some data. Unfortunately, I still have only some "suspects". It ***"seems"*** that the cluster locking (suite 1.03.02) is not so robust, and heavily depends on fast FC private networks, not implementing suitable semaphores and handshaking. I am trying to implement iscsi now (reading docs phase). But, maybe, the problems arise again if the real cause is at GFS / clvm locking coordination and not at gnbd itself. As RH docs suggests at fig. 1.13 [0] that the intended idea is feasible, I am trying it. do you have any additional ideas? How to spot the real cause? Regards. Andre Felipe Machado [0] http://elibrary.fultus.com/technical/topic/com.fultus.redhat.elinux5/manuals/Cluster_Suite_Overview/s2-ov-economy-CSO.html > > Maybe this URL would help you: > > http://www.techforce.com.br/index.php/news/linux_blog/red_hat_cluster_suite_debian_etch > > Best Regards > Maciej Bogucki -- Linux-cluster mailing list Linux-cluster@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/linux-cluster
