Am 03.08.2012 09:32, schrieb emmanuel segura:
> are you using ext3 for drbd active/active? UMMMMM
>
> 2012/8/3 Elvis Altherr <[email protected]>
>
>> Hello together
>>
>> On my gentoo  servers (2 Node Cluster with kernel 3.x) i use heartbeat
>> 3.0.5 and DRBD 8.4.0 for block replication between the two machines
>> which served apache, mysql and samba fileservices
>>
>> Everything works fine, except the automatic sync between the two drives
>> wich are both primarys
>>
>> What did i wrong?
>>
>>
>> conf files see below
>>
>> drbd.conf
>>
>> --------------------------------------------------------------------------------------------------------------------------------------------
>> resource r0 {
>>     # protocol to use; C is the the safest variant
>>       net {
>>       allow-two-primaries;
>>       }
>>       protocol C;
>>          startup {
>>          become-primary-on both;
>> #timeout (in seconds) for the connection on startup
>> wfc-timeout       90;
>> # timeout (in seconds) for the connection on startup
>> #after detection of data inconsistencies ("degraded mode")
>> degr-wfc-timeout  120;
>> }
>>    syncer {
>> # maximum bandwidth to use for this resource
>> rate 100M;
>> }
>> on mail2 {
>> ### options for master-server ###
>> # name of the allocated blockdevice
>> device     /dev/drbd0;
>> # underlying blockdevice
>> disk       /dev/sdb1;
>> #address and port to use for the synchronisation
>> # here we use the heartbeat network
>> address    10.0.0.1:7788;
>> # where to store DRBD metadata; here it's on the underlying device itself
>> meta-disk  internal;
>> }
>> on disthost3 {
>> device /dev/drbd1;
>> disk /dev/sda6;
>> address 10.0.0.2:7788;
>> meta-disk internal;
>> }
>>
>>
>> haresoures file for heartbeat
>>
>>
>> mail2 10.0.0.3 drbddisk::r0 Filesystem::/dev/drbd0::/drfs::ext3 apache2
>> mysql bind samba
>>
>> ha.cf
>>
>>
>>    # Logging
>>    debug                          1
>>    use_logd                       true
>> logfacility                     daemon
>>
>> # Misc Options
>> traditional_compression         off
>> compression                     bz2
>> coredumps                       true
>> auto_failback                   on
>>
>> # Communications
>> udpport                 694
>> #ucast                          eth1 10.0.0.1
>> bcast                           eth1
>> #autojoin                       any
>>
>> # Thresholds (in seconds)
>> keepalive                       2
>> warntime                        5
>> deadtime                        15
>> initdead                        60
>> crm                             no
>> node                            mail2
>> node                            disthost3
>> ~
>>
>>
>> thanks for your help
>>
>> --
>> Freundliche Grüsse
>>
>> Elvis Altherr
>> Brauerstrasse 83a
>> 9016 St. Gallen
>> 071 280 13 79 (Privat)
>> [email protected]
>>
>> _______________________________________________
>> Linux-HA mailing list
>> [email protected]
>> http://lists.linux-ha.org/mailman/listinfo/linux-ha
>> See also: http://linux-ha.org/ReportingProblems
>>
>
>
yes.. woud i better use GFS2 or OFCS (which both dosen't work under 
kernel 3.x) ?

Or which is the best file system porpouse for my case?



-- 
Freundliche Grüsse

Elvis Altherr
Brauerstrasse 83a
9016 St. Gallen
071 280 13 79 (Privat)
[email protected]

_______________________________________________
Linux-HA mailing list
[email protected]
http://lists.linux-ha.org/mailman/listinfo/linux-ha
See also: http://linux-ha.org/ReportingProblems

Reply via email to