[Gluster-devel] Selfheal on mount process (disperse)

Hi, Glusterfs ver 3.7.10 Volume : disperse (4+2) Client on separate machine. 1 brick offline. Error happens after about 60 seconds of starting write. When checked the online brick's .glusterfs/indices/xattrop , I could see a gfid entry. Why the mount process starts healing ? How to prevent

Re: [Gluster-devel] Slow volume, gluster volume status bug

Emmanuel Dreyfus wrote: > What happens if I remove the trusted.gfid2path.* attributes? Are > they just re-created? After reading the source, I concluded I could safely remover the trusted.gfid2path.* attributes. It fixed the (NetBSD specific) performance problem. -- Emmanuel

[Gluster-devel] Agenda for Nov 15th Maintainers meeting

# Meeting date: 11/15/2017 (Nov 15th, 19:30IST, 14:00UTC, 09:00EST) BJ Link - Bridge: https://bluejeans.com/205933580 - Download: Attendance - [Sorry Note] misc, -

Re: [Gluster-devel] Slow volume, gluster volume status bug

On Tue, Nov 14, 2017 at 06:38:44PM +0530, Atin Mukherjee wrote: > So this is the origin of why the peers don't understand they are connected. > Friend handshaking got stuck in the middle and it never recovered back. > Restarting the glusterd services ideally should fix the state, if not then >

Re: [Gluster-devel] Slow volume, gluster volume status bug

On Tue, Nov 14, 2017 at 2:47 PM, Emmanuel Dreyfus wrote: > On Tue, Nov 14, 2017 at 12:17:05PM +0530, Atin Mukherjee wrote: > > > gluster volume status also exhibits trouble: each server will only > > > list its bricks, but not the other's one. I suspect it could just > > > be

Re: [Gluster-devel] Slow volume, gluster volume status bug

On Tue, Nov 14, 2017 at 10:43:39AM +, Emmanuel Dreyfus wrote: > What happens if I remove the trusted.gfid2path.* attributes? Are > they just re-created? > > Some hint on how to disable the feature? gluster volume set gfs gfid2path off Can I jst delete the trusted.gfid2path.* attributes

[Gluster-devel] Coverity covscan for 2017-11-14-6e2ce373 (master branch)

GlusterFS Coverity covscan results are available from http://download.gluster.org/pub/gluster/glusterfs/static-analysis/master/glusterfs-coverity/2017-11-14-6e2ce373 ___ Gluster-devel mailing list Gluster-devel@gluster.org

Re: [Gluster-devel] Slow volume, gluster volume status bug

On Tue, Nov 14, 2017 at 09:17:35AM +, Emmanuel Dreyfus wrote: > In the meantime I tracked the performance problem to exteded atributes > system calls. The root of the problem is outside of glusterfs, but fixing > the consequuences would be nice. I think I found the problem: listxattr() scales

Re: [Gluster-devel] Slow volume, gluster volume status bug

On Tue, Nov 14, 2017 at 12:17:05PM +0530, Atin Mukherjee wrote: > > gluster volume status also exhibits trouble: each server will only > > list its bricks, but not the other's one. I suspect it could just > > be some tiemout because of slow answer from the peer. > Have you checked the output of