Note: "permalinks" may not be as permanent as we would like,
direct links of old sources may well be a few messages off.
Il 08/09/2017 10:45, Roland Kammerer ha scritto: > On Fri, Sep 08, 2017 at 09:17:18AM +0200, Roberto Resoli wrote: ... > It would be great if you could post the *.res file. You can find it attached here; i included also in the tgz the global_common file; i suspect that some resync configuration could play a role here, I think they are the only deviation form default automatic configuration. The segfault is systematic on any resource i try unto. Regarding resource files, I retried this morning to reboot a node; drbdmanaged takes very long to settle down (drbdmanage commands going timout); in the meanwhile, very few .res are generated, so I have to wait for issuing drbdmanage down && up . At last, I successfully shutdown and restart drbdmanaged , and from then things improved gradually. When all .res are in place, it's only matter to take resources up and down. > So far I was not > able to reproduce that in my setup (with the given versions and > peer-device options). The res file should be at: > /var/lib/drbd.d/drbdmanage_vm-105-disk-1.res> Thanks, rck Bye, rob > _______________________________________________ > drbd-user mailing list > drbd-user at lists.linbit.com > http://lists.linbit.com/mailman/listinfo/drbd-user > -------------- next part -------------- A non-text attachment was scrubbed... Name: drbdadm-segfault-data.tgz Type: application/x-compressed-tar Size: 710 bytes Desc: not available URL: <http://lists.linbit.com/pipermail/drbd-user/attachments/20170908/cf0ff74f/attachment.bin>