I still can't promote any of the nodes to primary, the output of cat
/proc/drbd on both machines are
[root@tdprodrepo02 ~]# cat /proc/drbd
version: 8.4.1 (api:1/proto:86-100)
GIT-hash: 91b4c048c1a0e06777b5f65d312b38d47abaea80 build by gardner@,
2012-08-25 00:57:01
0: cs:Connected ro:Secondary/Secondary ds:Diskless/Diskless C r-----
ns:0 nr:0 dw:0 dr:0 al:0 bm:0 lo:0 pe:0 ua:0 ap:0 ep:1 wo:b oos:0
[root@tdprodrepo01 /]# cat /proc/drbd
version: 8.4.1 (api:1/proto:86-100)
GIT-hash: 91b4c048c1a0e06777b5f65d312b38d47abaea80 build by gardner@,
2012-08-25 00:57:01
0: cs:Connected ro:Secondary/Secondary ds:Diskless/Diskless C r-----
ns:0 nr:0 dw:0 dr:0 al:0 bm:0 lo:0 pe:0 ua:0 ap:0 ep:1 wo:b oos:0
I'm able to mount the /dev/mapper/vg_drbd-lv:drbd01 /app01 on both machines
(so at least I'm able to make a backup of the directory in case I have to
run fdisk on that disk).
So if you have any other suggestions how I can come out of this situation,
it would be much appreciated
Kind regards
/Fredrik
On Wed, Aug 14, 2013 at 11:45 PM, Greg Woods <wo...@ucar.edu> wrote:
> On 08/14/2013 02:12 PM, Fredrik Hudner wrote:
> >
> > I have tried to make one node primary but only get:
> >
> > 0: State change failed: (-2) Need access to UpToDate data
> > Command 'drbdsetup primary 0' terminated with exit code 17
>
> When you've suffered a sudden disconnect, you can get into a situation
> where both sides think their information is outdated. To recover, you
> have to tell the cluster which node can throw away its data in favor of
> what the other node has.
>
> http://www.drbd.org/users-guide/s-resolve-split-brain.html
>
> --Greg
>
>
> _______________________________________________
> Linux-HA mailing list
> Linux-HA@lists.linux-ha.org
> http://lists.linux-ha.org/mailman/listinfo/linux-ha
> See also: http://linux-ha.org/ReportingProblems
>
_______________________________________________
Linux-HA mailing list
Linux-HA@lists.linux-ha.org
http://lists.linux-ha.org/mailman/listinfo/linux-ha
See also: http://linux-ha.org/ReportingProblems
