It seems you are not running any High Availability software like
"heartbeat". The startup script of drbd simply takes care of whether the
disks are in sync. After this is accomplished it switches the master to
secondary. Then it is up to the management SW which side of the mirror
should become primary.
If you do not have such software installed it will remain that state.
/Wolfram
>>> -----Original Message-----
>>> From: Chris Anderson [mailto:chris.anderson@example.com]
>>> Sent: Montag, 10. Dezember 2001 08:06
>>> To: DRBD dev list
>>> Subject: [DRBD-dev] primary drops back to secondary when secondary
>>> restarted (on 2.2.19 and 2.4.16)
>>>
>>>
>>> Now I'm trying the CVS code with kernel 2.4.16 and reiserfs
>>> (the version
>>> built into the kernel).
>>>
>>> > > If I restart on the secondary while it is in a
>>> SyncingAll state, the
>>> > > secondary begins the sync again and the primary keeps going.
>>>
>>> This is still the case.
>>>
>>> > > If I restart on the secondary while it is in a
>>> Connected state, it starts
>>> > > up, does a quick sync, and then both nodes become secondary.
>>> >
>>> > This happens with the latest CVS code (as at Dec 12).
>>>
>>> This is also still the case. Reproducible 100% of the time.
>>>
>>> Does anyone have any ideas? I really need this fixed, and I
>>> don't know
>>> where to start...
>>>
>>> Chris.
>>>
>>> --
>>> ____________________________________________________________
>>> ____________
>>> Disclaimer:
>>>
>>> This e-mail is confidential and intended solely for the
>>> named recipient.
>>> Any views expressed in this e-mail are those of the
>>> individual sender,
>>> and not of dotWAP.com Pty Ltd. Any unauthorised use, dissemination,
>>> forwarding or reproduction of this e-mail is strictly prohibited.
>>>
>>> dotWAP.com Pty Ltd does not warrant that this e-mail is
>>> free from viruses
>>> or other corruptions and is not liable to the recipient or any other
>>> party should any virus or other corruption be present in
>>> this e-mail.
>>>
>>> _______________________________________________
>>> DRBD-devel mailing list
>>> DRBD-devel@example.com
>>> https://lists.sourceforge.net/lists/listinfo/drbd-devel
>>>
"heartbeat". The startup script of drbd simply takes care of whether the
disks are in sync. After this is accomplished it switches the master to
secondary. Then it is up to the management SW which side of the mirror
should become primary.
If you do not have such software installed it will remain that state.
/Wolfram
>>> -----Original Message-----
>>> From: Chris Anderson [mailto:chris.anderson@example.com]
>>> Sent: Montag, 10. Dezember 2001 08:06
>>> To: DRBD dev list
>>> Subject: [DRBD-dev] primary drops back to secondary when secondary
>>> restarted (on 2.2.19 and 2.4.16)
>>>
>>>
>>> Now I'm trying the CVS code with kernel 2.4.16 and reiserfs
>>> (the version
>>> built into the kernel).
>>>
>>> > > If I restart on the secondary while it is in a
>>> SyncingAll state, the
>>> > > secondary begins the sync again and the primary keeps going.
>>>
>>> This is still the case.
>>>
>>> > > If I restart on the secondary while it is in a
>>> Connected state, it starts
>>> > > up, does a quick sync, and then both nodes become secondary.
>>> >
>>> > This happens with the latest CVS code (as at Dec 12).
>>>
>>> This is also still the case. Reproducible 100% of the time.
>>>
>>> Does anyone have any ideas? I really need this fixed, and I
>>> don't know
>>> where to start...
>>>
>>> Chris.
>>>
>>> --
>>> ____________________________________________________________
>>> ____________
>>> Disclaimer:
>>>
>>> This e-mail is confidential and intended solely for the
>>> named recipient.
>>> Any views expressed in this e-mail are those of the
>>> individual sender,
>>> and not of dotWAP.com Pty Ltd. Any unauthorised use, dissemination,
>>> forwarding or reproduction of this e-mail is strictly prohibited.
>>>
>>> dotWAP.com Pty Ltd does not warrant that this e-mail is
>>> free from viruses
>>> or other corruptions and is not liable to the recipient or any other
>>> party should any virus or other corruption be present in
>>> this e-mail.
>>>
>>> _______________________________________________
>>> DRBD-devel mailing list
>>> DRBD-devel@example.com
>>> https://lists.sourceforge.net/lists/listinfo/drbd-devel
>>>