[Gluster-devel] snapshot tests cause coredump in dmeventd
It seems that a snaphot regression test managed to trigger a core dump in dmeventd. Because our regression tests check for cores, the test was marked as a failure (mostly a 'good' thing). I'd appreciate it if one of the developers of snapshot can have a look at the core from dmeventd and maybe check with the LVM developers if this is a known bug. The core can be downloaded from the bottom of this link: https://build.gluster.org/job/rackspace-regression-2GB-triggered/20315/console Thanks, Niels signature.asc Description: PGP signature ___ Gluster-devel mailing list Gluster-devel@gluster.org http://www.gluster.org/mailman/listinfo/gluster-devel
Re: [Gluster-devel] snapshot tests cause coredump in dmeventd
On Mon, May 2, 2016 at 3:04 AM, Niels de Vos wrote: > It seems that a snaphot regression test managed to trigger a core dump > in dmeventd. Because our regression tests check for cores, the test was > marked as a failure (mostly a 'good' thing). > > I'd appreciate it if one of the developers of snapshot can have a look > at the core from dmeventd and maybe check with the LVM developers if > this is a known bug. The core can be downloaded from the bottom of this > link: > > https://build.gluster.org/job/rackspace-regression-2GB-triggered/20315/console > > The slave machine is not accessible therefore could not download the core file. Is it possible to get access to this machine? Thanks & Regards, Rajesh ___ Gluster-devel mailing list Gluster-devel@gluster.org http://www.gluster.org/mailman/listinfo/gluster-devel
Re: [Gluster-devel] snapshot tests cause coredump in dmeventd
Le mercredi 04 mai 2016 à 10:42 +0530, Rajesh Joseph a écrit : > On Mon, May 2, 2016 at 3:04 AM, Niels de Vos wrote: > > > It seems that a snaphot regression test managed to trigger a core dump > > in dmeventd. Because our regression tests check for cores, the test was > > marked as a failure (mostly a 'good' thing). > > > > I'd appreciate it if one of the developers of snapshot can have a look > > at the core from dmeventd and maybe check with the LVM developers if > > this is a known bug. The core can be downloaded from the bottom of this > > link: > > > > https://build.gluster.org/job/rackspace-regression-2GB-triggered/20315/console > > > > > The slave machine is not accessible therefore could not download the core > file. Is it > possible to get access to this machine? I opened the firewall for that port, didn't see it was not before. So you can now download the tarball. I will add it to the automation to open the others too. -- Michael Scherer Sysadmin, Community Infrastructure and Platform, OSAS signature.asc Description: This is a digitally signed message part ___ Gluster-devel mailing list Gluster-devel@gluster.org http://www.gluster.org/mailman/listinfo/gluster-devel
Re: [Gluster-devel] snapshot tests cause coredump in dmeventd
On Wed, May 4, 2016 at 7:19 PM, Michael Scherer wrote: > Le mercredi 04 mai 2016 à 10:42 +0530, Rajesh Joseph a écrit : > > On Mon, May 2, 2016 at 3:04 AM, Niels de Vos wrote: > > > > > It seems that a snaphot regression test managed to trigger a core dump > > > in dmeventd. Because our regression tests check for cores, the test was > > > marked as a failure (mostly a 'good' thing). > > > > > > I'd appreciate it if one of the developers of snapshot can have a look > > > at the core from dmeventd and maybe check with the LVM developers if > > > this is a known bug. The core can be downloaded from the bottom of this > > > link: > > > > > > > https://build.gluster.org/job/rackspace-regression-2GB-triggered/20315/console > > > > > > > > The slave machine is not accessible therefore could not download the core > > file. Is it > > possible to get access to this machine? > > I opened the firewall for that port, didn't see it was not before. > So you can now download the tarball. > > I will add it to the automation to open the others too. > Thanks Michael for looking into this. The machine is still not accessible. Thanks & Regards, Rajesh > -- > Michael Scherer > Sysadmin, Community Infrastructure and Platform, OSAS > > > ___ Gluster-devel mailing list Gluster-devel@gluster.org http://www.gluster.org/mailman/listinfo/gluster-devel
Re: [Gluster-devel] snapshot tests cause coredump in dmeventd
Le lundi 09 mai 2016 à 16:16 +0530, Rajesh Joseph a écrit : > On Wed, May 4, 2016 at 7:19 PM, Michael Scherer wrote: > > > Le mercredi 04 mai 2016 à 10:42 +0530, Rajesh Joseph a écrit : > > > On Mon, May 2, 2016 at 3:04 AM, Niels de Vos wrote: > > > > > > > It seems that a snaphot regression test managed to trigger a core dump > > > > in dmeventd. Because our regression tests check for cores, the test was > > > > marked as a failure (mostly a 'good' thing). > > > > > > > > I'd appreciate it if one of the developers of snapshot can have a look > > > > at the core from dmeventd and maybe check with the LVM developers if > > > > this is a known bug. The core can be downloaded from the bottom of this > > > > link: > > > > > > > > > > https://build.gluster.org/job/rackspace-regression-2GB-triggered/20315/console > > > > > > > > > > > The slave machine is not accessible therefore could not download the core > > > file. Is it > > > possible to get access to this machine? > > > > I opened the firewall for that port, didn't see it was not before. > > So you can now download the tarball. > > > > I will add it to the automation to open the others too. > > > > Thanks Michael for looking into this. The machine is still not accessible. Seems something did clean the firewall (potentially a reboot). i was on PTO for the last days, so I didn't see it earlier. I opened it and will fix the root cause. -- Michael Scherer Sysadmin, Community Infrastructure and Platform, OSAS signature.asc Description: This is a digitally signed message part ___ Gluster-devel mailing list Gluster-devel@gluster.org http://www.gluster.org/mailman/listinfo/gluster-devel
Re: [Gluster-devel] snapshot tests cause coredump in dmeventd
On Tue, May 10, 2016 at 2:25 PM, Michael Scherer wrote: > Le lundi 09 mai 2016 à 16:16 +0530, Rajesh Joseph a écrit : > > On Wed, May 4, 2016 at 7:19 PM, Michael Scherer > wrote: > > > > > Le mercredi 04 mai 2016 à 10:42 +0530, Rajesh Joseph a écrit : > > > > On Mon, May 2, 2016 at 3:04 AM, Niels de Vos > wrote: > > > > > > > > > It seems that a snaphot regression test managed to trigger a core > dump > > > > > in dmeventd. Because our regression tests check for cores, the > test was > > > > > marked as a failure (mostly a 'good' thing). > > > > > > > > > > I'd appreciate it if one of the developers of snapshot can have a > look > > > > > at the core from dmeventd and maybe check with the LVM developers > if > > > > > this is a known bug. The core can be downloaded from the bottom of > this > > > > > link: > > > > > > > > > > > > > > https://build.gluster.org/job/rackspace-regression-2GB-triggered/20315/console > > > > > > > > > > > > > > The slave machine is not accessible therefore could not download the > core > > > > file. Is it > > > > possible to get access to this machine? > > > > > > I opened the firewall for that port, didn't see it was not before. > > > So you can now download the tarball. > > > > > > I will add it to the automation to open the others too. > > > > > > > Thanks Michael for looking into this. The machine is still not > accessible. > > Seems something did clean the firewall (potentially a reboot). > > i was on PTO for the last days, so I didn't see it earlier. > > I opened it and will fix the root cause. > > Thanks Michael. Its working now. -Rajesh ___ Gluster-devel mailing list Gluster-devel@gluster.org http://www.gluster.org/mailman/listinfo/gluster-devel