Note: "permalinks" may not be as permanent as we would like,
direct links of old sources may well be a few messages off.
Thank you for the response!
Here is the output of cat /proc/drbd for both node1 and node2 before and
after node1(primary) gets rebooted.
Before reboot:
[root at node1 ~]# cat /proc/drbd
version: 8.0.16 (api:86/proto:86)
GIT-hash: d30881451c988619e243d6294a899139eed1183d build by
mockbuild at v20z-x86-64.home.local, 2009-08-22 13:26:57
1: cs:Connected st:Primary/Secondary ds:UpToDate/UpToDate C r---
ns:0 nr:0 dw:0 dr:0 al:0 bm:0 lo:0 pe:0 ua:0 ap:0
resync: used:0/61 hits:0 misses:0 starving:0 dirty:0 changed:0
act_log: used:0/127 hits:0 misses:0 starving:0 dirty:0 changed:0
[root at node2 ~]# cat /proc/drbd
version: 8.0.16 (api:86/proto:86)
GIT-hash: d30881451c988619e243d6294a899139eed1183d build by
mockbuild at v20z-x86-64.home.local, 2009-08-22 13:26:57
1: cs:Connected st:Secondary/Primary ds:UpToDate/UpToDate C r---
ns:0 nr:4493035 dw:4493035 dr:0 al:0 bm:0 lo:0 pe:0 ua:0 ap:0
resync: used:0/61 hits:0 misses:0 starving:0 dirty:0 changed:0
act_log: used:0/127 hits:0 misses:0 starving:0 dirty:0 changed:0
After reboot of node1:
[root at node1 ~]# cat /proc/drbd
version: 8.0.16 (api:86/proto:86)
GIT-hash: d30881451c988619e243d6294a899139eed1183d build by
mockbuild at v20z-x86-64.home.local, 2009-08-22 13:26:57
1: cs:WFConnection st:Secondary/Unknown ds:UpToDate/DUnknown C r---
ns:0 nr:0 dw:0 dr:0 al:0 bm:0 lo:0 pe:0 ua:0 ap:0
resync: used:0/61 hits:0 misses:0 starving:0 dirty:0 changed:0
act_log: used:0/127 hits:0 misses:0 starving:0 dirty:0 changed:0
[root at node2 ~]# cat /proc/drbd
version: 8.0.16 (api:86/proto:86)
GIT-hash: d30881451c988619e243d6294a899139eed1183d build by
mockbuild at v20z-x86-64.home.local, 2009-08-22 13:26:57
1: cs:StandAlone st:Secondary/Unknown ds:UpToDate/DUnknown r---
ns:0 nr:4493035 dw:4493043 dr:85 al:1 bm:1 lo:0 pe:0 ua:0 ap:0
resync: used:0/61 hits:0 misses:0 starving:0 dirty:0 changed:0
act_log: used:0/127 hits:1 misses:1 starving:0 dirty:0 changed:1
I am using heartbeat and this is my haresources contents:
node1.example.com drbddisk::r0 Filesystem::/dev/drbd1::/data::ext3
10.10.2.21 mysqld httpd
Should there be anything else in the haresources file that forces node1 to
primary on reboot?
Thank you,
Cameron
On Sun, Mar 21, 2010 at 6:14 PM, Reindy <reindy at gmail.com> wrote:
> hi, what is your current status? please brief us the details so that we can
> help you.
>
> Example: give your output of "cat /proc/drbd"
>
> you need to make sure that both of your nodes are sync and in WFConnection
> status,.. I still don't have the clear picture on your current situation,
> please let us know therefore we would able to help you.
>
> Thanks!
>
> On Fri, Mar 19, 2010 at 12:50 AM, Cameron Smith <velvetpixel at gmail.com>wrote:
>
>> I have two nodes.
>>
>> Node one I set to proimary with:
>> drbdadm -- --overwrite-data-of-peer primary r0
>>
>> That command does not survive a reboot of node1 so How do get get node1 to
>> regain primary status after it comes back online?
>>
>> When node1 comes back online will node2 write the data to node1 that was
>> written during the downtime for node1?
>>
>> Thanks!
>> Cameron
>>
>> _______________________________________________
>> drbd-user mailing list
>> drbd-user at lists.linbit.com
>> http://lists.linbit.com/mailman/listinfo/drbd-user
>>
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.linbit.com/pipermail/drbd-user/attachments/20100323/c66afa7b/attachment.htm>