On Thu, Jun 29, 2017 at 10:58 AM, Amar Tumballi wrote:
> All,
>
> Thanks for participating actively in the discussions. With all your
> co-operation we now have a update on maintainers 2.0 proposal. Vijay Bellur
> sent a patch last week [1] capturing all the discussions.
>
>
Hi All,
As we know in glusterfs we have one known issue specific to preserve
metadata consistency for directory in
pure distributed environment.
Problem:
After brick stop if application do any metadata operation(like
permission,uid/gid change, xattr change) on directory and restart
Netbsd runs don't go through. add-brick-self-heal.t seems to be generating
core.
-- Forwarded message -
From:
Date: Fri, 21 Jul 2017 at 06:20
Subject: [Gluster-Maintainers] Build failed in Jenkins: netbsd-periodic #98
To: ,
On Thu, Jul 20, 2017 at 9:21 PM, Niels de Vos wrote:
> On Thu, Jul 20, 2017 at 08:25:23PM +0530, Amar Tumballi wrote:
> > On Thu, Jul 20, 2017 at 7:36 PM, Niels de Vos wrote:
> >
> > > On Thu, Jul 20, 2017 at 07:11:29PM +0530, Amar Tumballi wrote:
> > > >
On Thu, Jul 20, 2017 at 08:25:23PM +0530, Amar Tumballi wrote:
> On Thu, Jul 20, 2017 at 7:36 PM, Niels de Vos wrote:
>
> > On Thu, Jul 20, 2017 at 07:11:29PM +0530, Amar Tumballi wrote:
> > > Hi,
> > >
> > > I was working on subdir mount for fuse clients [1], and was able to
On Thu, Jul 20, 2017 at 7:36 PM, Niels de Vos wrote:
> On Thu, Jul 20, 2017 at 07:11:29PM +0530, Amar Tumballi wrote:
> > Hi,
> >
> > I was working on subdir mount for fuse clients [1], and was able to
> handle
> > pieces just fine in filesystem part of gluster. [2]
> >
> >
On Thu, Jul 20, 2017 at 07:11:29PM +0530, Amar Tumballi wrote:
> Hi,
>
> I was working on subdir mount for fuse clients [1], and was able to handle
> pieces just fine in filesystem part of gluster. [2]
>
> What is pending is, how will we handle the authentication options for this
> at each
Hi,
I was working on subdir mount for fuse clients [1], and was able to handle
pieces just fine in filesystem part of gluster. [2]
What is pending is, how will we handle the authentication options for this
at each subdir level?
I propose to keep the current option and extending it to handle new
GlusterFS Coverity covscan results are available from
http://download.gluster.org/pub/gluster/glusterfs/static-analysis/master/glusterfs-coverity/2017-07-20-8a09d780
___
Gluster-devel mailing list
Gluster-devel@gluster.org
The following generally means it is not able to connect to any of the
glusterds in the cluster.
[1970-01-02 10:54:04.420406] E [glusterfsd-mgmt.c:1818:mgmt_rpc_notify]
0-glusterfsd-mgmt: failed to connect with remote-host: 128.224.95.140
(Success)
[1970-01-02 10:54:04.420422] I [MSGID: 101190]
10 matches
Mail list logo