Re: [Gluster-devel] netbsd smoke tests fail when code patches are backported to release-3.6

[Kremmyda, Olympia (Nokia - GR/Athens)]

Hi Niels, 

Thank you for your response. So is it possible to disable it from the review 
process of patches on release 3.6?
It seems that it is blocking issue for the reviews.
Here are all the requests for the release 
http://review.gluster.org/#/q/glusterfs+branch:release-3.6  
Please check that none of the latest ones have progress due to these smoke 
tests' failures.

Thank you,
Olia


-Original Message-
From: Niels de Vos [mailto:nde...@redhat.com] 
Sent: Friday, June 10, 2016 3:28 AM
To: Kremmyda, Olympia (Nokia - GR/Athens) <olympia.kremm...@nokia.com>
Cc: Gluster Devel <gluster-devel@gluster.org>
Subject: Re: [Gluster-devel] netbsd smoke tests fail when code patches are 
backported to release-3.6

On Thu, Jun 09, 2016 at 09:39:29AM +0000, Kremmyda, Olympia (Nokia - GR/Athens) 
wrote:
> Hi,
> 
> Is there any update on this issue?

Not really. This failure is not critical for the 3.6 release, and the
maintainer normally ignores it. There is no requirement to have it pass
for the 3.6 version.

It is not an urgent issue for us to fix, no users or developers seem
very interested in the FreeBSD support. The problem does not happen with
newer versions, and that seems to make this failure acceptible.

HTH,
Niels


> 
> Thank you,
> Olia
> 
> From: gluster-devel-boun...@gluster.org 
> [mailto:gluster-devel-boun...@gluster.org] On Behalf Of Atin Mukherjee
> Sent: Friday, May 20, 2016 7:11 PM
> To: Emmanuel Dreyfus <m...@netbsd.org>
> Cc: Gluster Devel <gluster-devel@gluster.org>
> Subject: Re: [Gluster-devel] netbsd smoke tests fail when code patches are 
> backported to release-3.6
> 
> 
> No, we didn't solve this problem yet. Niels had a patch up for review to fix 
> it but unfortunately it didn't. Kaushal also tried to reproduce it on a 
> netbsd machine, but nothing failed for him.
> 
> -Atin
> Sent from one plus one
> On 20-May-2016 9:25 PM, "Emmanuel Dreyfus" 
> <m...@netbsd.org<mailto:m...@netbsd.org>> wrote:
> On Fri, May 20, 2016 at 05:43:07PM +0300, Angelos SAKELLAROPOULOS wrote:
> > May I ask why following review requests are not submitted to release-3.6 ?
> > It seems that they fail in netbsd, freebsd smoke tests which are not
> > related to code changes.
> 
> There are build errors. I am note sur how you could have inherited
> them from git checkout, since previous changes were supposed to
> pass smoke too. If you are sure the error are not yours, you
> can try to rebase.
> 
> --
> Emmanuel Dreyfus
> m...@netbsd.org<mailto:m...@netbsd.org>
> ___
> Gluster-devel mailing list
> Gluster-devel@gluster.org<mailto:Gluster-devel@gluster.org>
> http://www.gluster.org/mailman/listinfo/gluster-devel

> ___
> Gluster-devel mailing list
> Gluster-devel@gluster.org
> http://www.gluster.org/mailman/listinfo/gluster-devel

___
Gluster-devel mailing list
Gluster-devel@gluster.org
http://www.gluster.org/mailman/listinfo/gluster-devel

Re: [Gluster-devel] netbsd smoke tests fail when code patches are backported to release-3.6

[Kremmyda, Olympia (Nokia - GR/Athens)]

Hi,

Is there any update on this issue?

Thank you,
Olia

From: gluster-devel-boun...@gluster.org 
[mailto:gluster-devel-boun...@gluster.org] On Behalf Of Atin Mukherjee
Sent: Friday, May 20, 2016 7:11 PM
To: Emmanuel Dreyfus 
Cc: Gluster Devel 
Subject: Re: [Gluster-devel] netbsd smoke tests fail when code patches are 
backported to release-3.6


No, we didn't solve this problem yet. Niels had a patch up for review to fix it 
but unfortunately it didn't. Kaushal also tried to reproduce it on a netbsd 
machine, but nothing failed for him.

-Atin
Sent from one plus one
On 20-May-2016 9:25 PM, "Emmanuel Dreyfus" 
> wrote:
On Fri, May 20, 2016 at 05:43:07PM +0300, Angelos SAKELLAROPOULOS wrote:
> May I ask why following review requests are not submitted to release-3.6 ?
> It seems that they fail in netbsd, freebsd smoke tests which are not
> related to code changes.

There are build errors. I am note sur how you could have inherited
them from git checkout, since previous changes were supposed to
pass smoke too. If you are sure the error are not yours, you
can try to rebase.

--
Emmanuel Dreyfus
m...@netbsd.org
___
Gluster-devel mailing list
Gluster-devel@gluster.org
http://www.gluster.org/mailman/listinfo/gluster-devel
___
Gluster-devel mailing list
Gluster-devel@gluster.org
http://www.gluster.org/mailman/listinfo/gluster-devel

[Gluster-devel] Memory usage behavior for nested directories

[Kremmyda, Olympia (Nokia - GR/Athens)]

Hi,

We use Gluster 3.6.9 in one replicated volume (named "log"), with two bricks.
Our tests include Nested Directory Creation operations (Creation from 1000 up 
to 25 Directory Trees) with 396 depth and no deletion is performed.

We have observed the following memory usage statistics shown in the images:
https://bugzilla.redhat.com/attachment.cgi?id=1162032
https://bugzilla.redhat.com/attachment.cgi?id=1162033
https://bugzilla.redhat.com/attachment.cgi?id=1162034
(statedumps are in https://bugzilla.redhat.com/attachment.cgi?id=1162035 )

and we would like your opinion if this memory usage is normal for glusterfs.
Also after our tests, we delete these directories and the memory  is not 
released.
Can you describe us the expected memory behaviour in these cases?


Thank you,
Olia









___
Gluster-devel mailing list
Gluster-devel@gluster.org
http://www.gluster.org/mailman/listinfo/gluster-devel

[Gluster-devel] Falling tests for glusterfs 3.6.9

[Kremmyda, Olympia (Nokia - GR/Athens)]

Hi,

I have tested glusterfs 3.6.9  in Fedora 21 (64-bit version), on a VirtualBox 
(version 5.0.18 r106667)
with 5.8 GiB Memory and an  Intel(r) Core(tm) i5-4300M CPU @ 2.60GHz Processor

and the following tests are failing in the clean version, with no further 
changes in the code:

Test Summary Report
---
./tests/bugs/afr-quota-xattr-mdata-heal.t  (Wstat: 
0 Tests: 101 Failed: 26)
  Failed tests:  38-39, 42-45, 47-48, 51-54, 62, 70-71, 74-77
79-80, 83-86, 92
./tests/bugs/bug-1045333.t (Wstat: 
0 Tests: 16 Failed: 1)
  Failed test:  15
./tests/bugs/bug-1049323.t (Wstat: 
0 Tests: 14 Failed: 1)
  Failed test:  12
./tests/bugs/bug-1117851.t (Wstat: 
0 Tests: 24 Failed: 1)
  Failed test:  15
./tests/bugs/bug-1161621.t (Wstat: 
0 Tests: 16 Failed: 1)
  Failed test:  14
./tests/bugs/bug-1161886/bug-1161886.t (Wstat: 
0 Tests: 16 Failed: 4)
  Failed tests:  13-16
./tests/bugs/bug-1167580-set-proper-uid-and-gid-during-nfs-access.t (Wstat: 
0 Tests: 44 Failed: 8)
  Failed tests:  11-14, 20-21, 24-25
./tests/bugs/bug-882278.t  (Wstat: 
0 Tests: 19 Failed: 12)
  Failed tests:  6-12, 14-18
./tests/bugs/bug-889996.t  (Wstat: 
0 Tests: 6 Failed: 1)
  Failed test:  6
./tests/bugs/bug-905864.t  (Wstat: 
0 Tests: 9 Failed: 1)
  Failed test:  9
./tests/bugs/bug-913555.t  (Wstat: 
0 Tests: 20 Failed: 3)
  Failed tests:  12, 16, 19
./tests/bugs/bug-921072.t  (Wstat: 
0 Tests: 67 Failed: 4)
  Failed tests:  30-31, 39, 42
./tests/bugs/bug-990028.t  (Wstat: 
0 Tests: 183 Failed: 2)
  Failed tests:  164-165
./tests/bugs/replicate/bug-1297695.t   (Wstat: 
0 Tests: 22 Failed: 1)
  Failed test:  21
./tests/features/ssl-authz.t   (Wstat: 
0 Tests: 21 Failed: 2)
  Failed tests:  11, 18
Files=308, Tests=8684, 7483 wallclock secs ( 2.62 usr  1.31 sys + 242.22 
cusr 433.86 csys = 680.01 CPU)
Result: FAIL

Did I missed anything during configuration or is this behavior normal for this 
version?

Thank you,
Olia



___
Gluster-devel mailing list
Gluster-devel@gluster.org
http://www.gluster.org/mailman/listinfo/gluster-devel

[Gluster-devel] Questions on Statedump results

[Kremmyda, Olympia (Nokia - GR/Athens)]

Hi,

We have observed in some statedumps, these entries during our tests:
We use Gluster 3.6.9 and our tests include the creation of 4000 files, 1MB 
each, in one replicated volume, with two bricks.
  pool-name=fuse:dentry_t
  hot-count=78
  cold-count=32690
  padded_sizeof=84
  alloc-count=40121
  max-alloc=32768
  pool-misses=7347
  cur-stdalloc=0
  max-stdalloc=7347
  -=-
  pool-name=fuse:inode_t
  hot-count=87
  cold-count=32681
  padded_sizeof=156
  alloc-count=165684
  max-alloc=32768
  pool-misses=19253
  cur-stdalloc=1
  max-stdalloc=7350
Are these values of pool-misses expected? Is there an indication of memory leak?

Also in the data structure allocation stats:
  [mount/fuse.fuse - usage-type gf_fuse_mt_gids_t memusage]
  size=968
  num_allocs=1024
  max_size=8200
  max_num_allocs=1025
  total_allocs=106176
If the size is “num_allocs times the sizeof(data‐type) i.e. num_allocs * sizeof 
(data‐type)”, how can it be in this case the num_allocs to be 1024 and the size 
to be smaller than 1024?

And one other question, can you explain to us what is the gf_common_mt_long 
pool, and why it is initialized only in production code (#ifndef DEBUG) in 
function mem_pool_new_fn?

Thank you for your time,
Olia



___
Gluster-devel mailing list
Gluster-devel@gluster.org
http://www.gluster.org/mailman/listinfo/gluster-devel

[Gluster-devel] FEATURE: Lock revocation for features/locks xlator

[Kremmyda, Olympia (Nokia - GR/Athens)]

Hi,

Will this feature for Automatic lock-revocation be included in the official 
version of Gluster?
Here is the Bugzilla report: https://bugzilla.redhat.com/show_bug.cgi?id=1301401

Thank you,
Olia


___
Gluster-devel mailing list
Gluster-devel@gluster.org
http://www.gluster.org/mailman/listinfo/gluster-devel