Re: [Gluster-devel] index_lookup segfault in glusterfsd brick process

Thanks for reply. 2018년 10월 4일 (목) 오후 5:31, Ravishankar N 님이 작성: > > > On 10/04/2018 01:57 PM, Pranith Kumar Karampuri wrote: > > it indicates that inode-table is NULL. Is there a possibility to upload > the core somewhere for us to take a closer look? > > This is core file.

Re: [Gluster-devel] index_lookup segfault in glusterfsd brick process

On 10/04/2018 01:57 PM, Pranith Kumar Karampuri wrote: On Wed, Oct 3, 2018 at 11:20 PM 김경표 > wrote: Hello folks. Few days ago I found my EC(4+2) volume was degraded. I am using 3.12.13-1.el7.x86_64. One brick was down, below is bricklog I am

Re: [Gluster-devel] index_lookup segfault in glusterfsd brick process

On Wed, Oct 3, 2018 at 11:20 PM 김경표 wrote: > Hello folks. > > Few days ago I found my EC(4+2) volume was degraded. > I am using 3.12.13-1.el7.x86_64. > One brick was down, below is bricklog > I am suspicious loc->inode bug in index.c (see attached picture) > In GDB, loc->inode is null > >>