Re: [Gluster-devel] [master][FAILED] brick-mux-regression

2018-12-02 Thread Milind Changire 
On Mon, Dec 3, 2018 at 8:32 AM Raghavendra Gowdappa 
wrote:

> On Mon, Dec 3, 2018 at 8:25 AM Raghavendra Gowdappa 
> wrote:
>
>> On Sat, Dec 1, 2018 at 11:02 AM Milind Changire 
>> wrote:
>>
>>> failed brick-mux-regression job:
>>> https://build.gluster.org/job/regression-on-demand-multiplex/411/console
>>>
>>> patch:
>>> https://review.gluster.org/c/glusterfs/+/21719
>>>
>>
>> Does this happen only with the above patch? Does brick-mux regression
>> succeed on current master without this patch? Wondering whether the
>> parallelism introduced by bumping up event-threads to 2, is opening up some
>> races in multiplexed environment (though there were always more than one
>> event-thread when more than one brick is multiplexed).
>>
>
> Also, is this bug locally reproducible on your setup if you run test
> following test with brick-mux enabled (with and without your patch)?
>
> ./tests/bugs/glusterd/add-brick-and-validate-replicated-volume-options.t
>
> running the above test with brick-mux enabled works well with and without
the "event-threads bump" patch on my centos7 setup
so, the issue is not reproducible on my setup


>>
>>>
>>> stack trace:
>>> $ gdb -ex 'set sysroot ./' -ex 'core-file
>>> ./build/install/cores/glfs_epoll000-964.core'
>>> ./build/install/sbin/glusterfsd
>>> GNU gdb (GDB) Fedora 8.2-4.fc29
>>> Copyright (C) 2018 Free Software Foundation, Inc.
>>> License GPLv3+: GNU GPL version 3 or later <
>>> http://gnu.org/licenses/gpl.html>
>>> This is free software: you are free to change and redistribute it.
>>> There is NO WARRANTY, to the extent permitted by law.
>>> Type "show copying" and "show warranty" for details.
>>> This GDB was configured as "x86_64-redhat-linux-gnu".
>>> Type "show configuration" for configuration details.
>>> For bug reporting instructions, please see:
>>> .
>>> Find the GDB manual and other documentation resources online at:
>>> .
>>>
>>> For help, type "help".
>>> Type "apropos word" to search for commands related to "word"...
>>> Reading symbols from ./build/install/sbin/glusterfsd...done.
>>> [New LWP 970]
>>> [New LWP 992]
>>> [New LWP 993]
>>> [New LWP 1005]
>>> [New LWP 1241]
>>> [New LWP 964]
>>> [New LWP 968]
>>> [New LWP 996]
>>> [New LWP 995]
>>> [New LWP 994]
>>> [New LWP 967]
>>> [New LWP 969]
>>> [New LWP 1003]
>>> [New LWP 1181]
>>> [New LWP 1242]
>>> [New LWP 966]
>>> [New LWP 965]
>>> [New LWP 999]
>>> [New LWP 1000]
>>> [New LWP 1002]
>>> [New LWP 989]
>>> [New LWP 990]
>>> [New LWP 991]
>>> [New LWP 971]
>>> warning: Ignoring non-absolute filename: <./lib64/libz.so.1>
>>> Missing separate debuginfo for ./lib64/libz.so.1
>>> Try: dnf --enablerepo='*debug*' install
>>> /usr/lib/debug/.build-id/ea/8e45dc8e395cc5e26890470112d97a1f1e0b65.debug
>>> warning: Ignoring non-absolute filename: <./lib64/libuuid.so.1>
>>> Missing separate debuginfo for ./lib64/libuuid.so.1
>>> Try: dnf --enablerepo='*debug*' install
>>> /usr/lib/debug/.build-id/71/de190dc0c93504abacc17b9747cd772a1e4b0d.debug
>>> warning: Ignoring non-absolute filename: <./lib64/libm.so.6>
>>> Missing separate debuginfo for ./lib64/libm.so.6
>>> Try: dnf --enablerepo='*debug*' install
>>> /usr/lib/debug/.build-id/f4/cae74047f9aa2d5a71fdec67c4285d75753eba.debug
>>> warning: Ignoring non-absolute filename: <./lib64/librt.so.1>
>>> Missing separate debuginfo for ./lib64/librt.so.1
>>> Try: dnf --enablerepo='*debug*' install
>>> /usr/lib/debug/.build-id/d3/3989ec31efe745eb0d3b68a92d19e77d7ddfda.debug
>>> warning: Ignoring non-absolute filename: <./lib64/libdl.so.2>
>>> Missing separate debuginfo for ./lib64/libdl.so.2
>>> Try: dnf --enablerepo='*debug*' install
>>> /usr/lib/debug/.build-id/5c/db5a56336e7e2bd14ffa189411e44a834afcd8.debug
>>> warning: Ignoring non-absolute filename: <./lib64/libpthread.so.0>
>>> Missing separate debuginfo for ./lib64/libpthread.so.0
>>> Try: dnf --enablerepo='*debug*' install
>>> /usr/lib/debug/.build-id/f4/c04bce85d2d269d0a2af4972fc69805b50345b.debug
>>> warning: Expected absolute pathname for libpthread in the inferior, but
>>> got ./lib64/libpthread.so.0.
>>> warning: Unable to find libthread_db matching inferior's thread library,
>>> thread debugging will not be available.
>>> warning: Ignoring non-absolute filename: <./lib64/libcrypto.so.10>
>>> Missing separate debuginfo for ./lib64/libcrypto.so.10
>>> Try: dnf --enablerepo='*debug*' install
>>> /usr/lib/debug/.build-id/67/ceb4edd36bfe0eb31cd92da2694aca5377a599.debug
>>> warning: Ignoring non-absolute filename: <./lib64/libc.so.6>
>>> Missing separate debuginfo for ./lib64/libc.so.6
>>> Try: dnf --enablerepo='*debug*' install
>>> /usr/lib/debug/.build-id/cb/4b7554d1adbef2f001142dd6f0a5139fc9aa69.debug
>>> warning: Ignoring non-absolute filename: <./lib64/ld-linux-x86-64.so.2>
>>> Missing separate debuginfo for ./lib64/ld-linux-x86-64.so.2
>>> Try: dnf --enablerepo='*debug*' install
>>>

[Gluster-devel] Gluster Weekly Report : Static Analyser

2018-12-02 Thread Sunny Kumar 
Hello folks,

The current status of static analyser is below:

Coverity scan status:
We started from 84 (24th Nov scan) and we are waiting on coverity for
new scan to report new/closed issues during last week.

New scan report is not available as scan is not running since last
week. We have opened a bug that can be tracked here-
https://bugzilla.redhat.com/show_bug.cgi?id=1653147

Contributors - Rafi 2 patches Poornima & Sunny 1 patch each. We do not
have clear number of fixes due to scan failure.

Clang-scan status:
We started from 70 (build #522) and its 68 ( build #529)
Shyam's patch addressed these 2 fixes.

If you want to contribute in fixing coverity and clang-scan fixes
please follow these instruction:
* for coverity scan fixes:
https://lists.gluster.org/pipermail/gluster-devel/2018-August/055155.html
 * for clang-scan:
https://lists.gluster.org/pipermail/gluster-devel/2018-August/055338.html

Regards,
Sunny kumar
___
Gluster-devel mailing list
Gluster-devel@gluster.org
https://lists.gluster.org/mailman/listinfo/gluster-devel

Re: [Gluster-devel] [master][FAILED] brick-mux-regression

2018-12-02 Thread Raghavendra Gowdappa 
On Mon, Dec 3, 2018 at 8:25 AM Raghavendra Gowdappa 
wrote:

>
>
> On Sat, Dec 1, 2018 at 11:02 AM Milind Changire 
> wrote:
>
>> failed brick-mux-regression job:
>> https://build.gluster.org/job/regression-on-demand-multiplex/411/console
>>
>> patch:
>> https://review.gluster.org/c/glusterfs/+/21719
>>
>
> Does this happen only with the above patch? Does brick-mux regression
> succeed on current master without this patch? Wondering whether the
> parallelism introduced by bumping up event-threads to 2, is opening up some
> races in multiplexed environment (though there were always more than one
> event-thread when more than one brick is multiplexed).
>

Also, is this bug locally reproducible on your setup if you run test
following test with brick-mux enabled (with and without your patch)?

./tests/bugs/glusterd/add-brick-and-validate-replicated-volume-options.t


>
>>
>> stack trace:
>> $ gdb -ex 'set sysroot ./' -ex 'core-file
>> ./build/install/cores/glfs_epoll000-964.core'
>> ./build/install/sbin/glusterfsd
>> GNU gdb (GDB) Fedora 8.2-4.fc29
>> Copyright (C) 2018 Free Software Foundation, Inc.
>> License GPLv3+: GNU GPL version 3 or later <
>> http://gnu.org/licenses/gpl.html>
>> This is free software: you are free to change and redistribute it.
>> There is NO WARRANTY, to the extent permitted by law.
>> Type "show copying" and "show warranty" for details.
>> This GDB was configured as "x86_64-redhat-linux-gnu".
>> Type "show configuration" for configuration details.
>> For bug reporting instructions, please see:
>> .
>> Find the GDB manual and other documentation resources online at:
>> .
>>
>> For help, type "help".
>> Type "apropos word" to search for commands related to "word"...
>> Reading symbols from ./build/install/sbin/glusterfsd...done.
>> [New LWP 970]
>> [New LWP 992]
>> [New LWP 993]
>> [New LWP 1005]
>> [New LWP 1241]
>> [New LWP 964]
>> [New LWP 968]
>> [New LWP 996]
>> [New LWP 995]
>> [New LWP 994]
>> [New LWP 967]
>> [New LWP 969]
>> [New LWP 1003]
>> [New LWP 1181]
>> [New LWP 1242]
>> [New LWP 966]
>> [New LWP 965]
>> [New LWP 999]
>> [New LWP 1000]
>> [New LWP 1002]
>> [New LWP 989]
>> [New LWP 990]
>> [New LWP 991]
>> [New LWP 971]
>> warning: Ignoring non-absolute filename: <./lib64/libz.so.1>
>> Missing separate debuginfo for ./lib64/libz.so.1
>> Try: dnf --enablerepo='*debug*' install
>> /usr/lib/debug/.build-id/ea/8e45dc8e395cc5e26890470112d97a1f1e0b65.debug
>> warning: Ignoring non-absolute filename: <./lib64/libuuid.so.1>
>> Missing separate debuginfo for ./lib64/libuuid.so.1
>> Try: dnf --enablerepo='*debug*' install
>> /usr/lib/debug/.build-id/71/de190dc0c93504abacc17b9747cd772a1e4b0d.debug
>> warning: Ignoring non-absolute filename: <./lib64/libm.so.6>
>> Missing separate debuginfo for ./lib64/libm.so.6
>> Try: dnf --enablerepo='*debug*' install
>> /usr/lib/debug/.build-id/f4/cae74047f9aa2d5a71fdec67c4285d75753eba.debug
>> warning: Ignoring non-absolute filename: <./lib64/librt.so.1>
>> Missing separate debuginfo for ./lib64/librt.so.1
>> Try: dnf --enablerepo='*debug*' install
>> /usr/lib/debug/.build-id/d3/3989ec31efe745eb0d3b68a92d19e77d7ddfda.debug
>> warning: Ignoring non-absolute filename: <./lib64/libdl.so.2>
>> Missing separate debuginfo for ./lib64/libdl.so.2
>> Try: dnf --enablerepo='*debug*' install
>> /usr/lib/debug/.build-id/5c/db5a56336e7e2bd14ffa189411e44a834afcd8.debug
>> warning: Ignoring non-absolute filename: <./lib64/libpthread.so.0>
>> Missing separate debuginfo for ./lib64/libpthread.so.0
>> Try: dnf --enablerepo='*debug*' install
>> /usr/lib/debug/.build-id/f4/c04bce85d2d269d0a2af4972fc69805b50345b.debug
>> warning: Expected absolute pathname for libpthread in the inferior, but
>> got ./lib64/libpthread.so.0.
>> warning: Unable to find libthread_db matching inferior's thread library,
>> thread debugging will not be available.
>> warning: Ignoring non-absolute filename: <./lib64/libcrypto.so.10>
>> Missing separate debuginfo for ./lib64/libcrypto.so.10
>> Try: dnf --enablerepo='*debug*' install
>> /usr/lib/debug/.build-id/67/ceb4edd36bfe0eb31cd92da2694aca5377a599.debug
>> warning: Ignoring non-absolute filename: <./lib64/libc.so.6>
>> Missing separate debuginfo for ./lib64/libc.so.6
>> Try: dnf --enablerepo='*debug*' install
>> /usr/lib/debug/.build-id/cb/4b7554d1adbef2f001142dd6f0a5139fc9aa69.debug
>> warning: Ignoring non-absolute filename: <./lib64/ld-linux-x86-64.so.2>
>> Missing separate debuginfo for ./lib64/ld-linux-x86-64.so.2
>> Try: dnf --enablerepo='*debug*' install
>> /usr/lib/debug/.build-id/d2/66b1f6650927e18108323bcca8f7b68e68eb92.debug
>> warning: Ignoring non-absolute filename: <./lib64/libssl.so.10>
>> Missing separate debuginfo for ./lib64/libssl.so.10
>> Try: dnf --enablerepo='*debug*' install
>> /usr/lib/debug/.build-id/64/68a4e28a19cdd885a3cbc30e009589ca4c2e92.debug
>> warning: Ignoring non-absolute filename: <./lib64/libgssapi_krb5.so.2>

Re: [Gluster-devel] [master][FAILED] brick-mux-regression

2018-12-02 Thread Raghavendra Gowdappa 
On Sat, Dec 1, 2018 at 11:02 AM Milind Changire  wrote:

> failed brick-mux-regression job:
> https://build.gluster.org/job/regression-on-demand-multiplex/411/console
>
> patch:
> https://review.gluster.org/c/glusterfs/+/21719
>

Does this happen only with the above patch? Does brick-mux regression
succeed on current master without this patch? Wondering whether the
parallelism introduced by bumping up event-threads to 2, is opening up some
races in multiplexed environment (though there were always more than one
event-thread when more than one brick is multiplexed).


>
> stack trace:
> $ gdb -ex 'set sysroot ./' -ex 'core-file
> ./build/install/cores/glfs_epoll000-964.core'
> ./build/install/sbin/glusterfsd
> GNU gdb (GDB) Fedora 8.2-4.fc29
> Copyright (C) 2018 Free Software Foundation, Inc.
> License GPLv3+: GNU GPL version 3 or later <
> http://gnu.org/licenses/gpl.html>
> This is free software: you are free to change and redistribute it.
> There is NO WARRANTY, to the extent permitted by law.
> Type "show copying" and "show warranty" for details.
> This GDB was configured as "x86_64-redhat-linux-gnu".
> Type "show configuration" for configuration details.
> For bug reporting instructions, please see:
> .
> Find the GDB manual and other documentation resources online at:
> .
>
> For help, type "help".
> Type "apropos word" to search for commands related to "word"...
> Reading symbols from ./build/install/sbin/glusterfsd...done.
> [New LWP 970]
> [New LWP 992]
> [New LWP 993]
> [New LWP 1005]
> [New LWP 1241]
> [New LWP 964]
> [New LWP 968]
> [New LWP 996]
> [New LWP 995]
> [New LWP 994]
> [New LWP 967]
> [New LWP 969]
> [New LWP 1003]
> [New LWP 1181]
> [New LWP 1242]
> [New LWP 966]
> [New LWP 965]
> [New LWP 999]
> [New LWP 1000]
> [New LWP 1002]
> [New LWP 989]
> [New LWP 990]
> [New LWP 991]
> [New LWP 971]
> warning: Ignoring non-absolute filename: <./lib64/libz.so.1>
> Missing separate debuginfo for ./lib64/libz.so.1
> Try: dnf --enablerepo='*debug*' install
> /usr/lib/debug/.build-id/ea/8e45dc8e395cc5e26890470112d97a1f1e0b65.debug
> warning: Ignoring non-absolute filename: <./lib64/libuuid.so.1>
> Missing separate debuginfo for ./lib64/libuuid.so.1
> Try: dnf --enablerepo='*debug*' install
> /usr/lib/debug/.build-id/71/de190dc0c93504abacc17b9747cd772a1e4b0d.debug
> warning: Ignoring non-absolute filename: <./lib64/libm.so.6>
> Missing separate debuginfo for ./lib64/libm.so.6
> Try: dnf --enablerepo='*debug*' install
> /usr/lib/debug/.build-id/f4/cae74047f9aa2d5a71fdec67c4285d75753eba.debug
> warning: Ignoring non-absolute filename: <./lib64/librt.so.1>
> Missing separate debuginfo for ./lib64/librt.so.1
> Try: dnf --enablerepo='*debug*' install
> /usr/lib/debug/.build-id/d3/3989ec31efe745eb0d3b68a92d19e77d7ddfda.debug
> warning: Ignoring non-absolute filename: <./lib64/libdl.so.2>
> Missing separate debuginfo for ./lib64/libdl.so.2
> Try: dnf --enablerepo='*debug*' install
> /usr/lib/debug/.build-id/5c/db5a56336e7e2bd14ffa189411e44a834afcd8.debug
> warning: Ignoring non-absolute filename: <./lib64/libpthread.so.0>
> Missing separate debuginfo for ./lib64/libpthread.so.0
> Try: dnf --enablerepo='*debug*' install
> /usr/lib/debug/.build-id/f4/c04bce85d2d269d0a2af4972fc69805b50345b.debug
> warning: Expected absolute pathname for libpthread in the inferior, but
> got ./lib64/libpthread.so.0.
> warning: Unable to find libthread_db matching inferior's thread library,
> thread debugging will not be available.
> warning: Ignoring non-absolute filename: <./lib64/libcrypto.so.10>
> Missing separate debuginfo for ./lib64/libcrypto.so.10
> Try: dnf --enablerepo='*debug*' install
> /usr/lib/debug/.build-id/67/ceb4edd36bfe0eb31cd92da2694aca5377a599.debug
> warning: Ignoring non-absolute filename: <./lib64/libc.so.6>
> Missing separate debuginfo for ./lib64/libc.so.6
> Try: dnf --enablerepo='*debug*' install
> /usr/lib/debug/.build-id/cb/4b7554d1adbef2f001142dd6f0a5139fc9aa69.debug
> warning: Ignoring non-absolute filename: <./lib64/ld-linux-x86-64.so.2>
> Missing separate debuginfo for ./lib64/ld-linux-x86-64.so.2
> Try: dnf --enablerepo='*debug*' install
> /usr/lib/debug/.build-id/d2/66b1f6650927e18108323bcca8f7b68e68eb92.debug
> warning: Ignoring non-absolute filename: <./lib64/libssl.so.10>
> Missing separate debuginfo for ./lib64/libssl.so.10
> Try: dnf --enablerepo='*debug*' install
> /usr/lib/debug/.build-id/64/68a4e28a19cdd885a3cbc30e009589ca4c2e92.debug
> warning: Ignoring non-absolute filename: <./lib64/libgssapi_krb5.so.2>
> Missing separate debuginfo for ./lib64/libgssapi_krb5.so.2
> Try: dnf --enablerepo='*debug*' install
> /usr/lib/debug/.build-id/16/fe0dc6cefc5f444bc876516d02efe9cc2d432f.debug
> warning: Ignoring non-absolute filename: <./lib64/libkrb5.so.3>
> Missing separate debuginfo for ./lib64/libkrb5.so.3
> Try: dnf --enablerepo='*debug*' install
>

[Gluster-devel] Weekly Untriaged Bugs

2018-12-02 Thread jenkins 
[...truncated 6 lines...]
https://bugzilla.redhat.com/1654370 / bitrot: Bitrot: Scrub status say file is 
corrupted even it was just created AND 'path' in the output is broken
https://bugzilla.redhat.com/1654778 / build: Please update GlusterFS 
documentation to describe how to do a non-root install
https://bugzilla.redhat.com/1651246 / core: Failed to dispatch handler
https://bugzilla.redhat.com/1654021 / core: Gluster volume heal causes 
continuous info logging of "invalid argument"
https://bugzilla.redhat.com/1649906 / core: remove logs, which can be obtained 
by external tools like systemtap, or strace.
https://bugzilla.redhat.com/1654398 / core: 
tests/bugs/core/brick-mux-fd-cleanup.t is failing
https://bugzilla.redhat.com/1649037 / core: Translators allocate too much 
memory in their xlator_mem_acct_init()
https://bugzilla.redhat.com/1654753 / distribute: A distributed-disperse volume 
crashes when a symbolic link is renamed
https://bugzilla.redhat.com/1648169 / encryption-xlator: Fuse mount would crash 
if features.encryption is on in the version from 3.13.0 to 4.1.5
https://bugzilla.redhat.com/1653250 / encryption-xlator: memory-leak in crypt 
xlator (glusterfs client)
https://bugzilla.redhat.com/1649054 / eventsapi: glustereventsd does not start 
on Ubuntu 16.04 LTS
https://bugzilla.redhat.com/1650017 / eventsapi: glustereventsd ImportError: 
attempted relative import with no known parent package
https://bugzilla.redhat.com/1655333 / geo-replication: OSError: [Errno 116] 
Stale file handle due to rotated files
https://bugzilla.redhat.com/1647506 / glusterd: glusterd_brick_start wrongly 
discovers already-running brick
https://bugzilla.redhat.com/1654642 / gluster-smb: Very high memory usage with 
glusterfs VFS module
https://bugzilla.redhat.com/1653147 / project-infrastructure: Build Status: 
Failed - at scan.coverity.com
https://bugzilla.redhat.com/1653733 / project-infrastructure: ci-results@ does 
not have an archive
https://bugzilla.redhat.com/1650073 / project-infrastructure: Unable to 
subscribe to mailing lists under lists.gluster.org
https://bugzilla.redhat.com/1652598 / replicate: Gluster not healing files (
https://bugzilla.redhat.com/1652548 / sharding: Error reading some files - 
Stale file handle - distribute 2 - replica 3 volume with sharding
[...truncated 2 lines...]

build.log
Description: Binary data
___
Gluster-devel mailing list
Gluster-devel@gluster.org
https://lists.gluster.org/mailman/listinfo/gluster-devel