[Gluster-devel] Is this a transient failure?

2014-07-11 Thread Anders Blomdell
In http://build.gluster.org/job/rackspace-regression-2GB-triggered/297/consoleFull, I have one failure: No volumes present read failed: No data available read returning junk fd based file operation 1 failed read failed: No data available read returning junk fstat failed : No data available fd

[Gluster-devel] gerrit accepts patches that are not signed off

2014-07-11 Thread Anders Blomdell
http://www.gluster.org/community/documentation/index.php/Simplified_dev_workflow says: It is essential that you commit with the '-s' option, which will sign-off the commit with your configured email, as gerrit is configured to reject patches which are not signed-off. this does not seem

Re: [Gluster-devel] Small note on 'dd' and cross platform block sizes

2014-07-11 Thread Justin Clift
On 11/07/2014, at 2:30 PM, Jeff Darcy wrote: On Fri, Jul 11, 2014 at 11:48:18AM +0100, Justin Clift wrote: It turns out that with the 'dd' command, the block size parameter (bs=) needs a bit of special treatment to work cross-platform. Instead of using the 'M' suffix (eg 1M for 1MB), it's

Re: [Gluster-devel] Is this a transient failure?

2014-07-11 Thread Justin Clift
On 11/07/2014, at 11:36 AM, Anders Blomdell wrote: In http://build.gluster.org/job/rackspace-regression-2GB-triggered/297/consoleFull, I have one failure: No volumes present read failed: No data available read returning junk fd based file operation 1 failed read failed: No data

Re: [Gluster-devel] Small note on 'dd' and cross platform block sizes

2014-07-11 Thread Jeff Darcy
Maybe we should 2/dev/null ? I don't like that approach because it might mask real errors as well. If we're stuck with it then c'est la vie, but wherever possible I recommend status=none instead. ___ Gluster-devel mailing list

[Gluster-devel] Update on setting and maintaining a trackable status for bugs

2014-07-11 Thread Niels de Vos
Hi all, we (sub-maintainers and component owners) will be trying to enforce a more trackable status of the various bugs that we have and get reported. In order to get everyone on one line, we will follow a documented life-cycle for the bugs: -

Re: [Gluster-devel] Small note on 'dd'�and cross platform block sizes

2014-07-11 Thread Emmanuel Dreyfus
Jeff Darcy jda...@redhat.com wrote: Does the BSD version also support status=none It seems to be msgfmt=quiet We can define a dd shell function that does /bin/dd status=none or /bin/dd msgfmt=quiet depending of the system -- Emmanuel Dreyfus http://hcpnet.free.fr/pubz m...@netbsd.org

Re: [Gluster-devel] Small note on 'dd'�and cross platform block sizes

2014-07-11 Thread Jeff Darcy
Does the BSD version also support status=none It seems to be msgfmt=quiet We can define a dd shell function that does /bin/dd status=none or /bin/dd msgfmt=quiet depending of the system That definitely looks like the way to go. Thanks! ___

Re: [Gluster-devel] Update on setting and maintaining a trackable status for bugs

2014-07-11 Thread Humble Devassy Chirammal
Hi, Refer # http://www.gluster.org/community/documentation/index.php/Bug_triage for more information on bug triaging process. --Humble On Sat, Jul 12, 2014 at 1:40 AM, Niels de Vos nde...@redhat.com wrote: Hi all, we (sub-maintainers and component owners) will be trying to enforce a more

Re: [Gluster-devel] Small note on 'dd'?and cross platform block sizes

2014-07-11 Thread Emmanuel Dreyfus
Jeff Darcy jda...@redhat.com wrote: We can define a dd shell function that does /bin/dd status=none or /bin/dd msgfmt=quiet depending of the system That definitely looks like the way to go. Thanks! Or a shell alias. I see we already define some in tests/include.rc -- Emmanuel Dreyfus