Hi, Thanks for your mail, I read the patch and have some questions: 1. Is this bug easy to repeat (seems need lease owner committed by a host is not the lease leader)? 2. I find the commit 6501351b742 introduced bug is released with 3.6.0, if I want to fix it, which is recommend, make a master build or downgrade to 3.5.0? Thanks again, Damon On Fri, Oct 12, 2018 at 2:58 AM David Teigland <teigland@xxxxxxxxxx> wrote: > > > > 2018-10-09 20:49:16 4854717 [29802]: r2320 write_host_block host_id > > > 19 flags 1 gen 1 dblock 29802:510:140245418403952:140245440585933:140245418403840:4:RELEASED. > > > > Perfect, that shows exactly where the bug is. There's a case where it has > > missed saving the latest dblock values, so random values are being copied > > back to the dblock instead. I'll push out a patch once I've had a chance > > to test it. > > Here's the fix: > https://www.pagure.io/sanlock/c/1471e241a33abc1f0774ce7ec418a134b655f9ac?branch=master > > Thanks for the help finding that. > Dave _______________________________________________ linux-lvm mailing list linux-lvm@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/linux-lvm read the LVM HOW-TO at http://tldp.org/HOWTO/LVM-HOWTO/
