Re: [Xen-users] lvm+drbd+xen problem

["Daniel Asplund" <danielsaori@xxxxxxxxx>]

What other troubleshooting have you performed? Did you try DRBD over
another NIC?
Has this setup never worked on this hardware or did the problem appear
after an upgrade?

I have never used SLES and also never v0.7 drbd, only debian and
ubuntu. But I guess a basic config like this should work in any
system... ;) But have you checked the bug reports if something is
listed? What version of Xen are you using?

//Daniel



On Sun, Jun 15, 2008 at 8:39 AM, Gabriele kalus
<gabriele.kalus@xxxxxxxxxxx> wrote:
> Hi Daniel,
>
> I get this behaviour when the DomUs are installed on a drbd device as a
> block device and the DomUs are active on them. I can't use the
> "drbd:RESOURCE" since I'm using the drbd v0.7.22 shipped with SLES10 and not
> drbd 8.x. I am using "phy:/dev/drbdx" when the Xen host dies on me.
>
> I don't get anything in the log files since the Xen host hangs instantly, I
> don't get anything in the passive Xen host either, except some normal lines
> that it lost contact with the other Xen host.
>
> Jun 13 11:20:44 vh2 kernel: drbd0: PingAck did not arrive in time.
> Jun 13 11:20:44 vh2 kernel: drbd0: drbd0_asender [17646]: cstate Connected
> --> NetworkFailure
> Jun 13 11:20:44 vh2 kernel: drbd0: asender terminated
> Jun 13 11:20:44 vh2 kernel: drbd0: drbd0_receiver [17590]: cstate
> NetworkFailure --> BrokenPipe
> Jun 13 11:20:44 vh2 kernel: drbd0: short read expecting header on sock:
> r=-512
> Jun 13 11:20:44 vh2 kernel: drbd0: worker terminated
> Jun 13 11:20:44 vh2 kernel: drbd0: drbd0_receiver [17590]: cstate BrokenPipe
> --> Unconnected
> Jun 13 11:20:44 vh2 kernel: drbd0: Connection lost.
> Jun 13 11:20:44 vh2 kernel: drbd0: drbd0_receiver [17590]: cstate
> Unconnected --> WFConnection
>
> etc
>
> Gabriele
>

_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users