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, Jul 19, 2016 at 2:50 PM, T.J. Yang <tjyang2001 at gmail.com> wrote:
> I have VMWare ESXi/Workstation Centos 7.2(or Ubuntu 16.04) VMs to test
> out drbd9. I will try to duplicate your procedure to see if same issue
> comes up. Something to do for the upcoming weekend.
>
I tested with latest linbit ppa repo for unbuntu 16.04 on ESXi OS. No sign
of BUG message after running Roland's test.sh 10 {notall|all} on 2nd node.
>From past experience with Google Cloud(GCP), I think this issue need to be
raised to GCP support team to rule rout their Linux kernel modification is
not the cause.
>
> On Tue, Jul 19, 2016 at 2:37 PM, Jason Dillon <jason at planet57.com> wrote:
>
>> I will give it a shot and let you know.
>>
>> BTW I have not tested with a local xenial VM, only remote google-cloud,
>> so thats likely why you can’t reproduce the problem if you haven’t actually
>> tried on google-cloud. I may see if I can find some time to setup with
>> local (parallels) vms.
>>
>> * * *
>>
>> I also wanted to isolate from ubuntu, but since there are no centos7 rpms
>> for this I basically couldn’t _easily_ spin up that environment to see if
>> maybe it was just something in the xenial google-cloud dist that was
>> messing it up.
>>
>> FTR the only configuration I’ve been able to get working properly on
>> google-cloud is on centos7 using drbd 8.4 (from elrepo.org). Though
>> obviously this is 8.4 not 9.0 and lots has changed.
>>
>> —jason
>>
>>
>> On July 19, 2016 at 2:35:30 AM, Roland Kammerer (
>> roland.kammerer at linbit.com) wrote:
>>
>> On Sun, Jul 17, 2016 at 11:01:50PM +0200, Roland Kammerer wrote:
>> > On Sat, Jul 16, 2016 at 11:34:41AM -0700, Jason Dillon wrote:
>> > >
>> > > FTR I’m using just the standard gcloud ubuntu 16.04 image:
>> > >
>> > > FTR I tried this a bunch of times and it worked as expected once or
>> > > twice, then freaked out. :-(
>> >
>> > Hi Jason,
>> >
>> > so far I have not been able to reproduce it in my xenial VMs, but we
>> > will investigate that ASAP. For now, thanks for reporting!
>>
>> Hi Jason,
>>
>> still no luck with reproducing (and from the trace it looks like the bug
>> is below DRBD).
>>
>> Could you help us to reproduce it? Make sure that there are no
>> drbdmanage resource and then start with a 200MB volume:
>> "drbdmanage nv testres 200M -d2"
>>
>> Make sure there are no other resources, so the testres/volume should get
>> /dev/drbd100.
>>
>> Then run that (sloppy) bash script[1], start with:
>> ./test.sh 10 all
>>
>> You can trigger a mount/umount test only with:
>> ./test.sh 10 notall
>>
>> I executed 50 test runs with "all" and 100 "mount/umount" without any
>> issues. The only difference is see for now is that I execute it in my
>> local xenial VMs and that my volume size might be much smaller.
>>
>> If that works, please remove the resource and create a new one with the
>> size you started with originally (and adapt the "dd count").
>>
>> Thanks, rck
>> [1]
>> ----------8<----------8<----------
>> #!/bin/bash
>>
>> for i in $(seq $1); do
>> echo "Test: $i"
>> if [ "$2" = "all" ]; then
>> mkfs.ext4 -F -E discard /dev/drbd100
>> fi
>> mount /dev/drbd100 /mnt
>> if [ "$2" = "all" ]; then
>> dd if=/dev/urandom of=/mnt/test.bin bs=1M count=150
>> fi
>> umount /mnt
>> dmesg | egrep BUG
>> if [ "$?" = "0" ]; then
>> echo "triggered bug"
>> break
>> fi
>> done
>> ----------8<----------8<----------
>> _______________________________________________
>> drbd-user mailing list
>> 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
>>
>>
>
>
> --
> T.J. Yang
>
--
T.J. Yang
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.linbit.com/pipermail/drbd-user/attachments/20160720/9126ee13/attachment.htm>