[Gluster-devel] NetBSD regression status upate

Sachin Pandit spandit at redhat.com
Mon May 4 07:24:38 UTC 2015



----- Original Message -----
> From: "Sachin Pandit" <spandit at redhat.com>
> To: "Emmanuel Dreyfus" <manu at netbsd.org>
> Cc: gluster-devel at gluster.org
> Sent: Monday, April 27, 2015 10:58:21 AM
> Subject: Re: [Gluster-devel] NetBSD regression status upate
> 
> 
> 
> ----- Original Message -----
> > From: "Emmanuel Dreyfus" <manu at netbsd.org>
> > To: gluster-devel at gluster.org
> > Sent: Sunday, April 26, 2015 9:33:20 AM
> > Subject: [Gluster-devel] NetBSD regression status upate
> > 
> > Hello
> > 
> > Here is the status of NetBSD regression so far. It would be nice if
> > people could help with quota-anon-fd-nfs.t, mgmt_v3-locks.t and tier.t.
> > 
> > The following tests are disabled for now:
> > 
> > - tests/basic/afr/split-brain-resolution.t
> >   Anuradha Talur is working on it, the change being still under review
> >   http://review.gluster.org/10134
> > 
> > - tests/basic/ec/
> >   This works but with rare spurious faiures. Nobody works on it.
> > 
> > - tests/basic/quota-anon-fd-nfs.t
> >   This test passed in the past and is now broken. Nobody works on it.
> 
> Vijaikumar and I have started looking into this problem. We haven't made
> any significant progress on this as of now. We will update once we find
> the root cause.

Quick update on this:

In NetBSD we are facing the failure of test case quota-anon-nfs.t

<code_snippet>

79 for j in $(seq 1 2); do
 80     for i in $(seq 3 6); do
 81         # failing writes indicate that we are enforcing quota set on /
 82         # even with anonymous fds.
 83         TEST_IN_LOOP ! fd_write $i "content"
 84         TEST_IN_LOOP sync
 85     done
 86 done


</code_snippet>

In this test case we are writing "content" into the files (fd's).
But for some reason the data "content" is not being written
into the files and because of that quota fails to account the
size. We have TEST "performance.nfs.write-behind off" in test case.
We suspect this could be because of NFS client caching.
Can you please let us know if there is any NFS client option which
we need to enable to resolve this issue.

Thanks,
Sachin Pandit.

> 
> Regards,
> Sachin.
> 
> > 
> > - tests/basic/mgmt_v3-locks.t
> >   This test passed in the past and is now broken. Nobody works on it
> > 
> > - tests/basic/tier/tier.t
> >   This test has always been broken on NetBSD. Nobody works on it
> > 
> > - tests/bugs
> >   Mostly uncharted terrirory
> > 
> > - tests/geo-rep
> >   All that tests have always failed.
> >   I started investigating and awaits input from Kotresh Hiremath
> >   Ravishankar.
> > 
> > - tests/features/trash.t
> >   Anoop C S, Jiffin Tony Thottan and I have been working on it. The
> >   change are pending review:
> >   http://review.gluster.org/10346
> >   http://review.gluster.org/10360
> >   http://review.gluster.org/10374
> > 
> > 
> > --
> > Emmanuel Dreyfus
> > http://hcpnet.free.fr/pubz
> > manu at netbsd.org
> > _______________________________________________
> > Gluster-devel mailing list
> > Gluster-devel at gluster.org
> > http://www.gluster.org/mailman/listinfo/gluster-devel
> > 
> 


More information about the Gluster-devel mailing list