Note: "permalinks" may not be as permanent as we would like,
direct links of old sources may well be a few messages off.
On Tue, Jan 11, 2011 at 4:04 PM, Lars Ellenberg <lars.ellenberg at linbit.com>wrote: > On Tue, Jan 11, 2011 at 04:58:46PM +0100, Alex Kuehne wrote: > > Quoting Lars Ellenberg <lars.ellenberg at linbit.com>: > > > > >On Mon, Jan 10, 2011 at 04:07:12PM +0100, Alex Kuehne wrote: > > >>Quoting Alex Kuehne <alex at movx.de>: > > >> > > >>>Hi guys, > > >>> > > >>>This is another report of DRBD not working with Xenserver 5.6 FP1. > > >>>I tried version 8.3.9 and 8.3.8.1. With Xenserver 5.6 (without > > >>>FP1) at least version 8.3.8.1 is working. > > > > > >For your drbdadm segfault with 8.3.10rc1, > > >please send me the config file it segfaults with (PM or to the list) > > > > Here it is: http://p.0wnz.at/205018 > > The global_common.conf is used as shipped. This is the same config I > > use with lower versions. > > Ok thanks. I guess that's some bogon in drbdadm that has been fixed > already and will be pushed public tomorrow together with a bunch of > other updates, probably labled "rc2" . I've been running 8.3.10rc1 for about a week. When I upgraded, I also got segfaults. drbdadm would segfault when starting the service: Jan 6 13:26:10 pubmaster01 kernel: drbdadm[24497]: segfault at 0000000000000000 rip 000000000040aaa8 rsp 00007fff5546a360 error 4 However, as near as I can determine, it was caused from something not being properly cleaned with the kernel modules loading/unloading. Uninstalled DRBD, rebooting, and installing DRBD cleanly took care of the drbdadm segfault. After the clean install, I didn't have any more segfaults. -JR -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.linbit.com/pipermail/drbd-user/attachments/20110111/d4f50b43/attachment.htm>