Re: [Gluster-devel] Spurious failure in tests/bugs/bug-948729/bug-948729-force.t

2014-12-24 Thread Emmanuel Dreyfus
On Wed, Dec 24, 2014 at 02:15:56PM +0530, Atin Mukherjee wrote: Can you please look into the spurious failure mentioned in $Subject @ http://build.gluster.org/job/rackspace-regression-2GB-triggered/3310/consoleFull I could see losetup is failing because of no free loop devices. Are we

[Gluster-devel] handling statfs call in USS

2014-12-24 Thread Raghavendra Bhat
Hi, I have a doubt. In user serviceable snapshots as of now statfs call is not implemented. There are 2 ways how statfs can be handled. 1) Whenever snapview-client xlator gets statfs call on a path that belongs to snapshot world, it can send the statfs call to the main volume itself, with

Re: [Gluster-devel] handling statfs call in USS

2014-12-24 Thread Vijaikumar M
On Wednesday 24 December 2014 02:30 PM, Raghavendra Bhat wrote: Hi, I have a doubt. In user serviceable snapshots as of now statfs call is not implemented. There are 2 ways how statfs can be handled. 1) Whenever snapview-client xlator gets statfs call on a path that belongs to snapshot

Re: [Gluster-devel] Spurious failure in tests/bugs/bug-948729/bug-948729-force.t

2014-12-24 Thread Emmanuel Dreyfus
Atin Mukherjee amukh...@redhat.com wrote: I also found a small problem in few functions in include.rc which I have tried to address @ http://review.gluster.org/9333. Not sure though whether this will fix this spurious failure. It seems it did not. Perhaps the build host needs a reboot? --

[Gluster-devel] Updates about DiSTAF - Multi Node test framework

2014-12-24 Thread M S Vishwanath Bhat
Hi, I had sent a mail about new multi node test framework for glusterfs (http://www.gluster.org/pipermail/gluster-users/2014-October/019211.html).This is an update about the same. * Have changed the name to distaf - https://github.com/msvbhat/distaf About the name: DiSTAF stand for

[Gluster-devel] Problems with graph switch in disperse

2014-12-24 Thread Xavier Hernandez
Hi, I'm experiencing a problem when gluster graph is changed as a result of a replace-brick operation (probably with any other operation that changes the graph) while the client is also doing other tasks, like writing a file. When operation starts, I see that the replaced brick is

Re: [Gluster-devel] Problems with graph switch in disperse

2014-12-24 Thread Raghavendra Gowdappa
Do you know the origins of EIO? fuse-bridge only fails a lookup fop with EIO (when NULL gfid is received in a successful lookup reply). So, there might be other xlator which is sending EIO. - Original Message - From: Xavier Hernandez xhernan...@datalab.es To: Gluster Devel

[Gluster-devel] Fwd: New Defects reported by Coverity Scan for GlusterFS

2014-12-24 Thread Vijay Bellur
A single bug reported by covscan this time. KP, Kaushal - can you please check this out? Thanks, Vijay Forwarded Message Subject: New Defects reported by Coverity Scan for GlusterFS Date: Wed, 24 Dec 2014 01:55:19 -0800 From: scan-ad...@coverity.com To: vbel...@redhat.com