[Linux-cluster] gnbd server as shared storage

Cristiano da Costa cristiano at develop.com.br
Thu Feb 3 19:10:28 UTC 2005


Hello list
Im trying to configure Red Hat Cluster Suite in an enviroment without shared storage to learn how to admin and configure this. Then I using gnbd to simulate a shared storage and I mapped the exported devices in other two RHEL, that are members of the cluster, and bind gnbd devices imported to raw devices to use as quorum shared storage, but when start clumanager the machines reboot, informing the following error in log: 
Feb  3 14:40:55 parati clusvcmgrd[5133]: <crit> Couldn't read configuration from shared state: Success
Feb  3 14:40:55 parati clusvcmgrd[5133]: <alert> Shared State Error: REBOOTING

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.
There are other way to configure RHCS without a shared storage like EMC storages or Sun storages?
That are my configuration files for gnbd
[root at ilhabela mnt]# cat /etc/sistina/ccs-build/angra.cca
#CCA:angra
#nigeb=cluster.ccs mtime=1107192495 size=147
cluster {
  name = "angra"
        lock_gulm {
             servers = ["angra"]
             heartbeat_rate = 0.3
             allowed_misses = 1
         }
}
#dne=cluster.ccs hash=BD5C824C
#nigeb=nodes.ccs mtime=1107192495 size=177
nodes {
  angra {
    ip_interfaces {
      eth0 = "192.168.1.52"
    }
    fence {
      server {
        gnbd0 {
        ipaddr = "192.168.1.52"
        }
      }
    }
  }
}
#dne=nodes.ccs hash=72704281
#nigeb=fence.ccs mtime=1107192495 size=78
fence_devices {
  gnbd0 {
    agent = "fence_gnbd"
    server = "angra"
  }
}
#dne=fence.ccs hash=9E0446A4

[root at ilhabela mnt]# cat /root/angra/cluster.ccs
cluster {
  name = "angra"
        lock_gulm {
             servers = ["angra"]
             heartbeat_rate = 0.3
             allowed_misses = 1
         }
}

[root at ilhabela mnt]# cat /root/angra/fence.ccs
fence_devices {
  gnbd0 {
    agent = "fence_gnbd"
    server = "angra"
  }
}

[root at ilhabela mnt]# cat /root/angra/nodes.ccs
nodes {
  angra {
    ip_interfaces {
      eth0 = "192.168.1.52"
    }
    fence {
      server {
        gnbd0 {
        ipaddr = "192.168.1.52"
        }
      }
    }
  }
  parati.localdomain {
    ip_interfaces {
      eth0 = "192.168.1.56"
    }
    fence {
      server {
        gnbd0 {
        ipaddr = "192.168.1.52"
        }
      }
    }
  }
  ilhabela.localdomain {
    ip_interfaces {
      eth0 = "192.168.1.57"
    }
    fence {
      server {
        gnbd0 {
        ipaddr = "192.168.1.52"
        }
      }
    }
  }
}

This is the output of gnbd_import -l in both nodes of the cluster
[root at ilhabela root]# gnbd_import -l
gnbd_import: Device name : hda10
----------------------
    Minor # : 1
  Proc name : gnbdb
         IP : 192.168.1.52
       Port : 14243
      State : Close Disconnected Clear
   Readonly : No
gnbd_import: Device name : hda9
----------------------
    Minor # : 2
  Proc name : gnbdc
         IP : 192.168.1.52
       Port : 14243
      State : Close Disconnected Clear
   Readonly : No
gnbd_import: Device name : hda11
----------------------
    Minor # : 3
  Proc name : gnbdd
         IP : 192.168.1.52
       Port : 14243
      State : Open Connected Clear
   Readonly : No

This is the content of /etc/sysconfig/rawdevices
[root at ilhabela root]# cat /etc/sysconfig/rawdevices
# raw device bindings
# format:  <rawdev> <major> <minor>
#          <rawdev> <blockdev>
# example: /dev/raw/raw1 /dev/sda1
#          /dev/raw/raw2 8 5
/dev/raw/raw1 /dev/gnbd/hda9
/dev/raw/raw2 /dev/gnbd/hda10

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.
Grateful




_________________________ 
Cristiano da Costa 
Consultor 
Develop IT Solutions 
www.develop.com.br 
Fone: (51) 3386-6620 
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://listman.redhat.com/archives/linux-cluster/attachments/20050203/dcfb6636/attachment.htm>


More information about the Linux-cluster mailing list