On Fri, Sep 1, 2017 at 9:42 AM, Michael Scherer wrote:
> Le vendredi 01 septembre 2017 à 14:02 +0100, Michael Scherer a écrit :
>> Le mercredi 30 août 2017 à 12:11 +0530, Nigel Babu a écrit :
>> > Hello,
>> >
>> > To reduce confusion, we've setup docs.gluster.org pointing to
>> > gluster.readthedo
On Fri, Sep 1, 2017 at 1:27 AM, Amar Tumballi wrote:
> Disclaimer: This email is long, and did take significant time to write. Do
> take time and read, review and give feedback, so we can have some metrics
> related tasks done by Gluster 4.0
>
> ---
> ** History:*
>
> To understand what is happen
Le vendredi 01 septembre 2017 à 14:02 +0100, Michael Scherer a écrit :
> Le mercredi 30 août 2017 à 12:11 +0530, Nigel Babu a écrit :
> > Hello,
> >
> > To reduce confusion, we've setup docs.gluster.org pointing to
> > gluster.readthedocs.org. Both URLs will continue to work for the
> > forseeable
How about getting some of the things currently in xdata into the
protocol instead? There are literally hundreds of instances of
'dict_set.*xdata' but here are some that stand out as likely candidates.
* "gfid-req" (everywhere)
* GLUSTERFS_WRITE_IS_APPEND (AFR, arbiter, posix)
* "check-zero-fi
Le mercredi 30 août 2017 à 12:11 +0530, Nigel Babu a écrit :
> Hello,
>
> To reduce confusion, we've setup docs.gluster.org pointing to
> gluster.readthedocs.org. Both URLs will continue to work for the
> forseeable
> future.
>
> Please update any references that you control to point to
> docs.gl
GlusterFS Coverity covscan results are available from
http://download.gluster.org/pub/gluster/glusterfs/static-analysis/master/glusterfs-coverity/2017-09-01-75223c0a
___
Gluster-devel mailing list
Gluster-devel@gluster.org
http://lists.gluster.org/mailman
Hi Mathew,
The other option is to explicitly remove the size and contri xattr at the
brick path and then do a stat from the mount point.
#setfattr -x
trusted.glusterfs.quota.----0001.contri.1
#setfattr -x trusted.glusterfs.quota.size.1
#stat
Stat would heal the
On Fri, Sep 01, 2017 at 10:57:37AM +0530, Amar Tumballi wrote:
> Disclaimer: This email is long, and did take significant time to write. Do
> take time and read, review and give feedback, so we can have some metrics
> related tasks done by Gluster 4.0
>
> ---
> ** History:*
>
> To understand what
If we plan to fix, bz [1] is another candidate that has to be targeted for
4.0.
Gluster's XDR does not conform to RFC spec
Description of problem: In an attempt to generate bindings to
Gluster's XDR with Rust I've run into a few problems. It appears the
XDR .x spec files are using keywords that
On 08/11/2017 06:04 PM, Amar Tumballi wrote:
Hi All,
Below are the proposed protocol changes (ie, XDR changes on the wire) we
are thinking for Gluster 4.0.
Poornima and I were discussing if we can include volume uuid as part of
Handshake protocol between protocol/client and protocol/server
Not sure how many of you have gone through the email! As we are done with
3.12 release, gluster project is entering into a territory where goal is
4.0 but branch cut dates are not yet decided.
As protocol changes are one of the required feature for Gluster 4.0, I
propose doing a day long hackathon
Hi Amar,
I don't have time to review the changes in experimental branch yet, but
here are some comments about these ideas...
On 01/09/17 07:27, Amar Tumballi wrote:
Disclaimer: This email is long, and did take significant time to write.
Do take time and read, review and give feedback, so we c
12 matches
Mail list logo
