Note: "permalinks" may not be as permanent as we would like,
direct links of old sources may well be a few messages off.
> If you're doing 2 node ha configurations, then drbd9 really isnt for you That's why I still wonder why Proxmox removed 8.4. I think a lot of low-mid sized setups are two nodes only, at least in development labs. Re-upgrading to 9.x is not an option now: I got back to 8.4 (as described before) with nodes in production state, near-to-no documentation supporting me and no certainty of the result. DRBD 8.4 works perfectly for my needings, I won't relive that feeling in a short time ;) Maybe I'll try DRBD 9.1 when available... Il 11/04/2016 20:08, Chuck Smith ha scritto: > Claudio, et al; > I'm not rushing to the defense of various parties, but I've been > actively engaged in testing 9.0.x since its initial release and yes, > its been a bear to make it become stable. However the rewards out > weigh the troubles, a fully engaged mesh is very powerful approach and > auto-promote makes it so much easier than traditional ocf. If you're > doing 2 node ha configurations, then drbd9 really isnt for you, its > power is in multi-node, and its higher throughput with the new > networking stacks and auto-promote. > If you do want to realize the benefits and continue down the path, I'd > recommend going to top-of-tree and building 9.0.1++, I have seen a > quite a few fixes that the readme glosses over, and that may help you > progress. > Regards > -Chuck > > On 4/11/2016 3:08 AM, Jean-Laurent Ivars wrote: >> Hi Claudio, >> >> I wonder the same as you and I’m a little bit afraid about the >> production ready thing… >> >> I am wondering about downgrading my whole Proxmox installation to >> have a stable system rather than using something that can brake any >> day with a simple update… Do you think the version 4 features worth >> the risk and I should go your way ? >> >> Thank you for your answer again >> Best regards, >> >> ------------------------------------------------------------------------ >> >> *Jean-Laurent Ivars * >> *Responsable Technique | Technical Manager* >> 22, rue Robert - 13007 Marseille >> Tel: 09 84 56 64 30 - Mobile: 06.52.60.86.47 >> Linkedin <http://fr.linkedin.com/in/jlivars/> | Viadeo >> <http://www.viadeo.com/fr/profile/jean-laurent.ivars> | >> www.ipgenius.fr <https://www.ipgenius.fr> >> >> >>> Le 11 avr. 2016 à 10:13, Claudio Nicora <claudio.nicora at gmail.com> a >>> écrit : >>> >>> Welcome aboard, and thanks for bringing back an issue that nobody >>> took care of since now. >>> It means I was not the alone... >>> >>> I've had the same issue a few months ago, I've reported it here (and >>> on Proxmox forums) but the issue is still there. >>> >>> Linbit: nobody took care of it (however it's a kernel crash, should >>> be critical enough...) >>> Proxmox: a kernel with an updated DRBD module (still DRBD 9.0) was >>> released but the issue persisted. Still wondering how a >>> "non-production ready" feature could end up in a "production ready" >>> bundle like Proxmox 4 without a choice to get DRBD 8.4 back. >>> >>> I've sorted it out by downgrading DRBD module to 8.4 and building >>> the kernel module + DRBD tools on my own. >>> This is the post on Proxmox forum with a backlink to my blog post >>> where I detailed the actions to downgrade the module. >>> I've also set up a script to run after each Proxmox kernel upgrade, >>> just in case. >>> >>> PS: still waiting for a feedback from Linbit/Proxmox guys ;) >>> _______________________________________________ >>> drbd-user mailing list >>> drbd-user at lists.linbit.com <mailto:drbd-user at lists.linbit.com> >>> http://lists.linbit.com/mailman/listinfo/drbd-user >> >> >> >> _______________________________________________ >> 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/20160412/fa37e279/attachment.htm>