Re: [Gluster-devel] [Gluster-Maintainers] Proposal: move glusterfs development to github workflow, completely

On Tue, Aug 27, 2019 at 12:10 AM Niels de Vos wrote: > On Mon, Aug 26, 2019 at 08:36:30PM +0530, Aravinda Vishwanathapura Krishna > Murthy wrote: > > On Mon, Aug 26, 2019 at 7:49 PM Joe Julian wrote: > > > > > > Comparing the changes between revisions is something > > > that GitHub does not

Re: [Gluster-devel] [RFC] alter inode table lock from mutex to rwlock

Hi Changwei Ge, On Thu, Aug 22, 2019 at 5:57 PM Changwei Ge wrote: > Hi, > > Now inode_table_t:lock is type of mutex which I think we can use > ‘pthread_rwlock' to replace it for a better concurrency. > > Because phread_rwlock allows more than one thread accessing inode table > at the same

[Gluster-devel] [Announcement] Gluster Community Update

Hello Gluster community, Today marks a new day in the 26-year history of Red Hat. IBM has finalized its acquisition of Red Hat , which will operate as a distinct

Re: [Gluster-devel] Migration of the builders to Fedora 30

On Thu, Jul 4, 2019 at 9:55 PM Amar Tumballi Suryanarayan < atumb...@redhat.com> wrote: > > > On Thu, Jul 4, 2019 at 9:37 PM Michael Scherer > wrote: > >> Hi, >> >> I have upgraded for testing some of the builder to F30 (because F28 is >> EOL and peop

Re: [Gluster-devel] Migration of the builders to Fedora 30

On Thu, Jul 4, 2019 at 9:37 PM Michael Scherer wrote: > Hi, > > I have upgraded for testing some of the builder to F30 (because F28 is > EOL and people did request newer version of stuff), and I was a bit > surprised to see the result of the test of the jobs. > > So we have 10 jobs that run on

Re: [Gluster-devel] Removing glupy from release 5.7

On Thu, Jun 20, 2019 at 2:35 PM Niels de Vos wrote: > On Thu, Jun 20, 2019 at 02:11:21PM +0530, Amar Tumballi Suryanarayan wrote: > > On Thu, Jun 20, 2019 at 1:13 PM Niels de Vos wrote: > > > > > On Thu, Jun 20, 2019 at 11:36:46AM +0530, Amar Tumballi Suryanarayan >

Re: [Gluster-devel] Removing glupy from release 5.7

On Thu, Jun 20, 2019 at 1:13 PM Niels de Vos wrote: > On Thu, Jun 20, 2019 at 11:36:46AM +0530, Amar Tumballi Suryanarayan wrote: > > Considering python3 is anyways the future, I vote for taking the patch we > > did in master for fixing regression tests with python3 int

Re: [Gluster-devel] Removing glupy from release 5.7

> > > > > > > > > > > > On Wed, Jun 12, 2019 at 10:43 AM Amar Tumballi Suryanarayan < > > > > > atumb...@redhat.com> wrote: > > > > > > > > > > > > > > > > > We recently n

Re: [Gluster-devel] [Gluster-Maintainers] Release 7: Gentle Reminder, Regression health for release-6.next and release-7

On Tue, Jun 18, 2019 at 12:07 PM Rinku Kothiya wrote: > Hi Team, > > We need to branch for release-7, but nightly builds failures are blocking > this activity. Please find test failures and respective test links below : > > The top tests that are failing are as below and need attention, > > >

Re: [Gluster-devel] Project Update: Containers-based distributed tests runner

This is a nice way to validate the patch for us. Question I have is did we measure the time benefit of running them in parallel with containers? Would be great to see the result in getting this tested in a cloud env, with 5 parallel threads and 10 parallel threads. -Amar On Fri, Jun 14, 2019

[Gluster-devel] Quick Update: a cleanup patch and subsequent build failures

I just merged a larger cleanup patch, which I felt is good to get in, but due to the order of its parents when it passed the regression and smoke, and the other patches which got merged in same time, we hit a compile issue for 'undefined functions'. Below patch fixes it: glfs: add

Re: [Gluster-devel] Seems like Smoke job is not voting

, 2019 at 5:16 PM Amar Tumballi Suryanarayan < atumb...@redhat.com> wrote: > I see patches starting from 10:45 AM IST (7hrs before) are not getting > smoke votes. > > For one of my patch, the smoke job is not triggered at all IMO. > > https://review.gluster.org/#/c/22863/ &g

[Gluster-devel] Seems like Smoke job is not voting

I see patches starting from 10:45 AM IST (7hrs before) are not getting smoke votes. For one of my patch, the smoke job is not triggered at all IMO. https://review.gluster.org/#/c/22863/ Would be good to check it. Regards, Amar ___ Community Meeting

Re: [Gluster-devel] Removing glupy from release 5.7

On Wed, Jun 12, 2019 at 8:42 PM Niels de Vos wrote: > On Wed, Jun 12, 2019 at 07:54:17PM +0530, Hari Gowtham wrote: > > We haven't sent any patch to fix it. > > Waiting for the decision to be made. > > The bz: https://bugzilla.redhat.com/show_bug.cgi?id=1719778 > > The link to the build log: > >

Re: [Gluster-devel] Linux 5.2-RC regression bisected, mounting glusterfs volumes fails after commit: fuse: require /dev/fuse reads to have enough buffer capacity

Thanks for the heads up! We will see how to revert / fix the issue properly for 5.2 kernel. -Amar On Tue, Jun 11, 2019 at 4:34 PM Sander Eikelenboom wrote: > L.S., > > While testing a linux 5.2 kernel I noticed it fails to mount my glusterfs > volumes. > > It repeatedly fails with: >

[Gluster-devel] Regression failure continues: 'tests/basic/afr/split-brain-favorite-child-policy.t`

Fails with: *20:56:58* ok 132 [ 8/ 82] < 194> 'gluster --mode=script --wignore volume heal patchy'*20:56:58* not ok 133 [ 8/ 80260] < 195> '^0$ get_pending_heal_count patchy' -> 'Got "2" instead of "^0$"'*20:56:58* ok 134 [ 18/ 2] < 197> '0 echo 0' Looks like when the

Re: [Gluster-devel] CI failure - NameError: name 'unicode' is not defined (related to changelogparser.py)

Update: The issue happened because python3 got installed on centos7.x series of builders due to other package dependencies. And considering GlusterFS picks python3 as priority even if python2 is default, the tests started to fail. We had completed the work of migrating the code to work smoothly

Re: [Gluster-devel] [Gluster-Maintainers] Fwd: Build failed in Jenkins: regression-test-with-multiplex #1359

Got time to test subdir-mount.t failing in brick-mux scenario. I noticed some issues, where I need further help from glusterd team. subdir-mount.t expects 'hook' script to run after add-brick to make sure the required subdirectories are healed and are present in new bricks. This is important as

[Gluster-devel] Update: GlusterFS code coverage

All, I just wanted to update everyone about one of the initiatives we have undertaken, ie, increasing the overall code coverage of GlusterFS above 70%. You can have a look at current code coverage here: https://build.gluster.org/job/line-coverage/lastCompletedBuild/Line_20Coverage_20Report/ (This

Re: [Gluster-devel] tests are timing out in master branch

Looks like after reverting a patch on RPC layer reconnection logic ( https://review.gluster.org/22750) things are back to normal. For those who submitted a patch in last 1 week, please resubmit. (which should take care of rebasing on top of this patch). This event proves that there are very

Re: [Gluster-devel] Release 6.2: Expected tagging on May 15th

Which are the patches? I can merge it for now. -Amar On Fri, May 17, 2019 at 1:10 PM Hari Gowtham wrote: > Thanks Sunny. > Have CCed Shyam. > > On Fri, May 17, 2019 at 1:06 PM Sunny Kumar wrote: > > > > Hi Hari, > > > > For this to pass regression other 3 patches needs to merge first, I > >

Re: [Gluster-devel] nightly builds are available again, with slightly different versioning

Thanks for noticing and correcting the issue Niels. Very helpful. On Wed, May 15, 2019 at 12:48 PM Niels de Vos wrote: > This is sort of an RCA and notification to anyone interested in using > nightly builds of GlusterFS. If you have any (automated) tests that > consume the nightly builds for

Re: [Gluster-devel] [Gluster-users] gluster-block v0.4 is alive!

On Thu, May 2, 2019 at 1:35 PM Prasanna Kalever wrote: > Hello Gluster folks, > > Gluster-block team is happy to announce the v0.4 release [1]. > > This is the new stable version of gluster-block, lots of new and > exciting features and interesting bug fixes are made available as part > of this

Re: [Gluster-devel] Coverity scan - how does it ignore dismissed defects & annotations?

On Fri, May 3, 2019 at 3:17 PM Atin Mukherjee wrote: > > > On Fri, 3 May 2019 at 14:59, Xavi Hernandez wrote: > >> Hi Atin, >> >> On Fri, May 3, 2019 at 10:57 AM Atin Mukherjee >> wrote: >> >>> I'm bit puzzled on the way coverity is reporting the open defects on GD1 >>> component. As you can

Re: [Gluster-devel] glusterfsd memory leak issue found after enable ssl

Hi Cynthia Zhou, Can you post the patch which fixes the issue of missing free? We will continue to investigate the leak further, but would really appreciate getting the patch which is already worked on land into upstream master. -Amar On Mon, Apr 22, 2019 at 1:38 PM Zhou, Cynthia (NSB -

Re: [Gluster-devel] Query regarding dictionary logic

Shreyas/Kevin tried to address it some time back using https://bugzilla.redhat.com/show_bug.cgi?id=1428049 ( https://review.gluster.org/16830) I vaguely remember the reason to keep the hash value 1 was done during the time when we had dictionary itself sent as on wire protocol, and in most other

Re: [Gluster-devel] [Gluster-users] One more way to contact Gluster team - Slack (gluster.slack.com)

cture needs, and has valid concerns from his perspective :-) I, on the other hand, bother more about code, users, and how to make sure we are up-to-date with other technologies and communities, from the engineering view point. > On Fri, Apr 26, 2019, 3:16 AM Michael Scherer wrote: >&g

[Gluster-devel] One more way to contact Gluster team - Slack (gluster.slack.com)

Hi All, We wanted to move to Slack from IRC for our official communication channel from sometime, but couldn't as we didn't had a proper URL for us to register. 'gluster' was taken and we didn't knew who had it registered. Thanks to constant ask from Satish, Slack team has now agreed to let us

Re: [Gluster-devel] [Gluster-users] Proposal: Changes in Gluster Community meetings

carve out an AI to get them fixed. <https://hackmd.io/OqZbh7gfQe6uvVUXUVKJ5g?both#RoundTable>RoundTable - ---- Regards, Amar On Mon, Mar 25, 2019 at 8:53 PM Amar Tumballi Suryanarayan < atumb...@redhat.com> wrote: > Thanks for the feedback Darrell, > > The new proposal is to hav

Re: [Gluster-devel] test failure reports for last 15 days

Thanks for the summary Atin. On Wed, Apr 10, 2019 at 7:30 PM Atin Mukherjee wrote: > And now for last 15 days: > > https://fstat.gluster.org/summary?start_date=2019-03-25_date=2019-04-10 > > ./tests/bitrot/bug-1373520.t 18 ==> Fixed through >

Re: [Gluster-devel] [Gluster-users] Proposal: Changes in Gluster Community meetings

ing 12 hours opposed to the one you’re proposing? > > -Darrell > > On Mar 25, 2019, at 4:25 AM, Amar Tumballi Suryanarayan < > atumb...@redhat.com> wrote: > > All, > > We currently have 3 meetings which are public: > > 1. Maintainer's Meeting > > -

[Gluster-devel] Proposal: Changes in Gluster Community meetings

All, We currently have 3 meetings which are public: 1. Maintainer's Meeting - Runs once in 2 weeks (on Mondays), and current attendance is around 3-5 on an avg, and not much is discussed. - Without majority attendance, we can't take any decisions too. 2. Community meeting - Supposed to happen

[Gluster-devel] GlusterFS v7.0 (and v8.0) roadmap discussion

Hello Gluster Members, We are now done with glusterfs-6.0 release, and the next up is glusterfs-7.0. But considering for many 'initiatives', 3-4 months are not enough time to complete the tasks, we would like to call for a road-map discussion meeting for calendar year 2019 (covers both

Re: [Gluster-devel] [Gluster-users] Proposal to mark few features as Deprecated / SunSet from Version 5.0

Hi Jim, On Tue, Mar 19, 2019 at 6:21 PM Jim Kinney wrote: > > Issues with glusterfs fuse mounts cause issues with python file open for > write. We have to use nfs to avoid this. > > Really want to see better back-end tools to facilitate cleaning up of > glusterfs failures. If system is going to

Re: [Gluster-devel] [Gluster-users] Proposal to mark few features as Deprecated / SunSet from Version 5.0

Hi Hans, Thanks for the honest feedback. Appreciate this. On Tue, Mar 19, 2019 at 5:39 PM Hans Henrik Happe wrote: > Hi, > > Looking into something else I fell over this proposal. Being a shop that > are going into "Leaving GlusterFS" mode, I thought I would give my two > cents. > > While

Re: [Gluster-devel] Github#268 Compatibility with Alpine Linux

I tried this recently, and the issue of rpcgen is real, and is not straight-forward is what I felt. Would like to pick this up after glusterfs-6.0 release. -Amar On Tue, Mar 12, 2019 at 8:17 AM Sankarshan Mukhopadhyay < sankarshan.mukhopadh...@gmail.com> wrote: > Saw some recent activity on >

Re: [Gluster-devel] [Gluster-users] Glusterfsd crashed with SIGSEGV

/5.4-r0/sysroot-destdir/usr/lib64/libglusterfs.so.0.0.1: >>> not a dynamic executable >>> pabhishe@arn-build3$ldd >>> ./5.4-r0/sysroot-destdir/usr/lib64/libglusterfs.so.0.0.1 >>> not a dynamic executable >>> >>> >>> For backtraces I ha

Re: [Gluster-devel] [Gluster-users] Glusterfsd crashed with SIGSEGV

more_data = 1 >> #22 0x3fffb7842ec0 in .xdr_gfx_dirplist () from >> /usr/lib64/libgfxdr.so.0 >> No symbol table info available. >> #23 0x3fffb7764c28 in __GI_xdr_reference (xdrs=0x3fffb1686d20, >> pp=0x3fffa81090f0, size=, proc=) at >> xdr_ref.c:84 >&g

Re: [Gluster-devel] [Gluster-users] Glusterfsd crashed with SIGSEGV

Hi Abhishek, Can you check and get back to us? ``` bash# ldd /usr/lib64/libglusterfs.so bash# ldd /usr/lib64/libgfrpc.so ``` Also considering you have the core, can you do `(gdb) thr apply all bt full` and pass it on? Thanks & Regards, Amar On Mon, Mar 11, 2019 at 3:41 PM ABHISHEK PALIWAL

Re: [Gluster-devel] GlusterFS - 6.0RC - Test days (27th, 28th Feb)

Thanks to those who participated. Update at present: We found 3 blocker bugs in upgrade scenarios, and hence have marked release as pending upon them. We will keep these lists updated about progress. -Amar On Mon, Feb 25, 2019 at 11:41 PM Amar Tumballi Suryanarayan < atumb...@redhat.com>

Re: [Gluster-devel] [Gluster-users] Version uplift query

GlusterD2 is not yet called out for standalone deployments. You can happily update to glusterfs-5.x (recommend you to wait for glusterfs-5.4 which is already tagged, and waiting for packages to be built). Regards, Amar On Wed, Feb 27, 2019 at 4:46 PM ABHISHEK PALIWAL wrote: > Hi, > > Could

[Gluster-devel] GlusterFS - 6.0RC - Test days (27th, 28th Feb)

Hi all, We are calling out our users, and developers to contribute in validating ‘glusterfs-6.0rc’ build in their usecase. Specially for the cases of upgrade, stability, and performance. Some of the key highlights of the release are listed in release-notes draft

Re: [Gluster-devel] GlusterFs v4.1.5: Need help on bitrot detection

Hi Chandranana, We are trying to find a BigEndian platform to test this out at the moment, will get back to you on this. Meantime, did you run the entire regression suit? Is it the only test failing? To run the entire regression suite, please run `run-tests.sh -c` from glusterfs source repo.

Re: [Gluster-devel] md-cache: May bug found in md-cache.c

Spisla wrote: > Hello Amar, > > > > no problem. How can I do that? Can you please tell me the procedure? > > > > Regards > > David > > > > *Von:* Amar Tumballi Suryanarayan > *Gesendet:* Mittwoch, 20. Februar 2019 14:18 > *An:* David Spisla >

Re: [Gluster-devel] md-cache: May bug found in md-cache.c

Hi David, Thanks for the patch, it got merged in master now. Can you please post it into release branches, so we can take them in release-6, release-5 branch, so next releases can have them. Regards, Amar On Tue, Feb 19, 2019 at 8:49 PM David Spisla wrote: > Hello, > > I already open a bug: >

Re: [Gluster-devel] Release 6: Branched and next steps

On Tue, Feb 19, 2019 at 1:37 AM Shyam Ranganathan wrote: > In preparation for RC0 I have put up an intial patch for the release > notes [1]. Request the following actions on the same (either a followup > patchset, or a dependent one), > > - Please review! > - Required GD2 section updated to

[Gluster-devel] Gluster Container Storage: Release Update

Hello everyone, We are announcing v1.0RC release of GlusterCS this week!** The version 1.0 is due along with *glusterfs-6.0* next month. Below are the Goals for v1.0: - RWX PVs - Scale and Performance - RWO PVs - Simple, leaner stack with Gluster’s Virtual Block. - Thin Arbiter (2

Re: [Gluster-devel] Failing test case ./tests/bugs/distribute/bug-1161311.t

On Wed, Feb 13, 2019 at 9:51 AM Nithya Balachandran wrote: > I'll take a look at this today. The logs indicate the test completed in > under 3 minutes but something seems to be holding up the cleanup. > > Just a look on some successful runs show output like below: -- *17:44:49* ok 57,

[Gluster-devel] Meeting minutes: Feb 04th, 2019

BJ Link - Bridge: https://bluejeans.com/217609845 - Watch: https://bluejeans.com/s/37SS6/ Attendance - Nigel Babu - Sunil Heggodu - Amar Tumballi - Aravinda VK - Atin Mukherjee

[Gluster-devel] Maintainer's meeting: Jan 21st, 2019

BJ Link - Bridge: https://bluejeans.com/217609845 - Watch: https://bluejeans.com/s/PAnE5 Attendance - Nigel Babu, Amar, Nithya, Shyam, Sunny, Milind (joined late). Agenda

Re: [Gluster-devel] FUSE directory filehandle

On Thu, Jan 10, 2019 at 8:17 AM Emmanuel Dreyfus wrote: > Hello > > This is not strictly a GlusterFS question since I came to it porting > LTFS to NetBSD, however I would like to make sure I will not break > GlusterFS by fixing NetBSD FUSE implementation for LTFS. > > Current NetBSD FUSE

Re: [Gluster-devel] Regression health for release-5.next and release-6

That is a good point Mohit, but do we know how many of these tests failed because of 'timeout' ? If most of these are due to timeout, then yes, it may be a valid point. -Amar On Thu, Jan 10, 2019 at 4:51 PM Mohit Agrawal wrote: > I think we should consider regression-builds after merged the

[Gluster-devel] Gluster Maintainer's meeting: 7th Jan, 2019 - Meeting minutes

2 more hours added, so full regression can be run. --- On Mon, Jan 7, 2019 at 9:04 AM Amar Tumballi Suryanarayan < atumb...@redhat.com> wrote: > > Meeting date: 2019-01-07 18:30 IST, 13:00 UTC, 08:00 EDTBJ Link > >- Bridge: https://bluejeans.com/217609845 >

Re: [Gluster-devel] https://review.gluster.org/#/c/glusterfs/+/19778/

On Tue, Jan 8, 2019 at 8:04 PM Shyam Ranganathan wrote: > On 1/8/19 8:33 AM, Nithya Balachandran wrote: > > Shyam, what is your take on this? > > An upstream user has tried it out and reported that it seems to fix the > > issue , however cpu utilization doubles. > > We usually do not backport

[Gluster-devel] Gluster Maintainer's meeting: 7th Jan, 2019 - Agenda

Meeting date: 2019-01-07 18:30 IST, 13:00 UTC, 08:00 EDTBJ Link - Bridge: https://bluejeans.com/217609845 Attendance Agenda - Welcome 2019: Discuss about goals : -