Re: [Gluster-devel] gfid and volume-id extended attributes lost

Ram, As per the code, self-heal was the only candidate which *can* do it. Could you check logs of self-heal daemon and the mount to check if there are any metadata heals on root? +Sanoj Sanoj, Is there any systemtap script we can use to detect which process is removing these xattrs

Re: [Gluster-devel] [Gluster-users] gfid and volume-id extended attributes lost

Do you observe any event pattern (self-healing / disk failures / reboots etc.) after which the extended attributes are missing? Regards, Vijay On Fri, Jul 7, 2017 at 5:28 PM, Ankireddypalle Reddy wrote: > We lost the attributes on all the bricks on servers glusterfs2 and > glusterfs3 again. > >

Re: [Gluster-devel] gfid and volume-id extended attributes lost

We lost the attributes on all the bricks on servers glusterfs2 and glusterfs3 again. [root@glusterfs2 Log_Files]# gluster volume info Volume Name: StoragePool Type: Distributed-Disperse Volume ID: 149e976f-4e21-451c-bf0f-f5691208531f Status: Started Number of Bricks: 20 x (2 + 1) = 60 Transport-

Re: [Gluster-devel] gfid and volume-id extended attributes lost

On Fri, Jul 7, 2017 at 9:25 PM, Ankireddypalle Reddy wrote: > 3.7.19 > These are the only callers for removexattr and only _posix_remove_xattr has the potential to do removexattr as posix_removexattr already makes sure that it is not gfid/volume-id. And surprise surprise _posix_remove_xattr happ

Re: [Gluster-devel] gfid and volume-id extended attributes lost

3.7.19 Thanks and Regards, Ram From: Pranith Kumar Karampuri [mailto:pkara...@redhat.com] Sent: Friday, July 07, 2017 11:54 AM To: Ankireddypalle Reddy Cc: Gluster Devel (gluster-devel@gluster.org); gluster-us...@gluster.org Subject: Re: [Gluster-devel] gfid and volume-id extended attributes lost

Re: [Gluster-devel] gfid and volume-id extended attributes lost

On Fri, Jul 7, 2017 at 9:20 PM, Ankireddypalle Reddy wrote: > Pranith, > > Thanks for looking in to the issue. The bricks were > mounted after the reboot. One more thing that I noticed was when the > attributes were manually set when glusterd was up then on starting the > volume

Re: [Gluster-devel] gfid and volume-id extended attributes lost

Pranith, Thanks for looking in to the issue. The bricks were mounted after the reboot. One more thing that I noticed was when the attributes were manually set when glusterd was up then on starting the volume the attributes were again lost. Had to stop glusterd set attributes and

Re: [Gluster-devel] gfid and volume-id extended attributes lost

On Fri, Jul 7, 2017 at 9:15 PM, Pranith Kumar Karampuri wrote: > Did anything special happen on these two bricks? It can't happen in the > I/O path: > posix_removexattr() has: > 0 if (!strcmp (GFID_XATTR_KEY, name)) > { > > > 1 gf_msg (this->name, GF_LOG_WARNING, 0, >

Re: [Gluster-devel] gfid and volume-id extended attributes lost

Did anything special happen on these two bricks? It can't happen in the I/O path: posix_removexattr() has: 0 if (!strcmp (GFID_XATTR_KEY, name)) { 1 gf_msg (this->name, GF_LOG_WARNING, 0, P_MSG_XATTR_NOT_REMOVED, 2 "Remove xattr called on gfid

[Gluster-devel] gfid and volume-id extended attributes lost

Hi, We faced an issue in the production today. We had to stop the volume and reboot all the servers in the cluster. Once the servers rebooted starting of the volume failed because the following extended attributes were not present on all the bricks on 2 servers. 1) trusted.gfid 2)

Re: [Gluster-devel] geo-rep regression because of node-uuid change

On Fri, Jul 7, 2017 at 3:05 PM, Xavier Hernandez wrote: > On 07/07/17 11:25, Pranith Kumar Karampuri wrote: > >> >> >> On Fri, Jul 7, 2017 at 2:46 PM, Xavier Hernandez > > wrote: >> >> On 07/07/17 10:12, Pranith Kumar Karampuri wrote: >> >> >> >> On Fri,

[Gluster-devel] Coverity covscan for 2017-07-07-0ae38df6 (master branch)

GlusterFS Coverity covscan results are available from http://download.gluster.org/pub/gluster/glusterfs/static-analysis/master/glusterfs-coverity/2017-07-07-0ae38df6 ___ Gluster-devel mailing list Gluster-devel@gluster.org http://lists.gluster.org/mailman

Re: [Gluster-devel] is tests/basic/gfapi/libgfapi-fini-hang.t broken in NetBSD ?

On Fri, Jul 07, 2017 at 07:42:08AM -0400, Jeff Darcy wrote: > > > On Fri, Jul 7, 2017, at 03:36 AM, Niels de Vos wrote: > > The segfault is caused by GF_ASSERT() on > > https://review.gluster.org/#/c/17662/2/libglusterfs/src/mem-pool.c@563 . > > At the moment I'm not sure how this can happen, unl

Re: [Gluster-devel] is tests/basic/gfapi/libgfapi-fini-hang.t broken in NetBSD ?

On Fri, Jul 7, 2017, at 03:36 AM, Niels de Vos wrote: > The segfault is caused by GF_ASSERT() on > https://review.gluster.org/#/c/17662/2/libglusterfs/src/mem-pool.c@563 . > At the moment I'm not sure how this can happen, unless glfs_fini() is > called more than once on a glfs_t object. It's bec

Re: [Gluster-devel] geo-rep regression because of node-uuid change

On 07/07/17 11:25, Pranith Kumar Karampuri wrote: On Fri, Jul 7, 2017 at 2:46 PM, Xavier Hernandez mailto:xhernan...@datalab.es>> wrote: On 07/07/17 10:12, Pranith Kumar Karampuri wrote: On Fri, Jul 7, 2017 at 1:13 PM, Xavier Hernandez mailto:xhernan...@datalab.es>

Re: [Gluster-devel] geo-rep regression because of node-uuid change

On Fri, Jul 7, 2017 at 2:46 PM, Xavier Hernandez wrote: > On 07/07/17 10:12, Pranith Kumar Karampuri wrote: > >> >> >> On Fri, Jul 7, 2017 at 1:13 PM, Xavier Hernandez > > wrote: >> >> Hi Pranith, >> >> On 05/07/17 12:28, Pranith Kumar Karampuri wrote: >> >>

Re: [Gluster-devel] geo-rep regression because of node-uuid change

On 07/07/17 10:12, Pranith Kumar Karampuri wrote: On Fri, Jul 7, 2017 at 1:13 PM, Xavier Hernandez mailto:xhernan...@datalab.es>> wrote: Hi Pranith, On 05/07/17 12:28, Pranith Kumar Karampuri wrote: On Tue, Jul 4, 2017 at 2:26 PM, Xavier Hernandez mailto:xhernan...@

Re: [Gluster-devel] upstream regression suite is broken

On Fri, Jul 7, 2017 at 12:33 PM, Krutika Dhananjay wrote: > The patch[1] that introduced tests/basic/stats-dump.t was merged in > October 2015 and > my patch underwent (and passed too![2]) centos regression tests, including > stats-dump.t on 05 June, 2017. > The only change that the test script u

Re: [Gluster-devel] geo-rep regression because of node-uuid change

On Fri, Jul 7, 2017 at 1:13 PM, Xavier Hernandez wrote: > Hi Pranith, > > On 05/07/17 12:28, Pranith Kumar Karampuri wrote: > >> >> >> On Tue, Jul 4, 2017 at 2:26 PM, Xavier Hernandez > > wrote: >> >> Hi Pranith, >> >> On 03/07/17 08:33, Pranith Kumar Karampu

Re: [Gluster-devel] geo-rep regression because of node-uuid change

Hi Pranith, On 05/07/17 12:28, Pranith Kumar Karampuri wrote: On Tue, Jul 4, 2017 at 2:26 PM, Xavier Hernandez mailto:xhernan...@datalab.es>> wrote: Hi Pranith, On 03/07/17 08:33, Pranith Kumar Karampuri wrote: Xavi, Now that the change has been reverted, we ca

Re: [Gluster-devel] is tests/basic/gfapi/libgfapi-fini-hang.t broken in NetBSD ?

On Fri, Jul 07, 2017 at 09:37:35AM +0530, Atin Mukherjee wrote: > https://build.gluster.org/job/netbsd7-regression/4761/consoleFull mem_pool_fini() has recently been added. It suggests that there is a problem with the implementation, maybe not NetBSD specific. From the test console log: [01:24:1

Re: [Gluster-devel] upstream regression suite is broken

The patch[1] that introduced tests/basic/stats-dump.t was merged in October 2015 and my patch underwent (and passed too![2]) centos regression tests, including stats-dump.t on 05 June, 2017. The only change that the test script underwent during this time was this line in 2016, which is harmless: a