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

: Sanoj Unnikrishnan; Gluster Devel (gluster-devel@gluster.org); gluster-us...@gluster.org Subject: Re: [Gluster-devel] gfid and volume-id extended attributes lost Ram, I sent https://review.gluster.org/17765 to fix the possibility in bulk removexattr. But I am not sure if this is indeed

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

; > gluster-us...@gluster.org > > *Subject:* Re: [Gluster-devel] gfid and volume-id extended attributes lost > > > > Ram, > > If you see it again, you can use this. I am going to send out a > patch for the code path which can lead to removal of gfid/volume-id

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

...@gluster.org Subject: Re: [Gluster-devel] gfid and volume-id extended attributes lost Ram, If you see it again, you can use this. I am going to send out a patch for the code path which can lead to removal of gfid/volume-id tomorrow. On Mon, Jul 10, 2017 at 5:19 PM, Sanoj Unnikrishnan <su

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

5/ws_brick >>> >>> Brick48: glusterfs6sds.commvault.com:/ws/disk5/ws_brick >>> >>> Brick49: glusterfs4sds.commvault.com:/ws/disk6/ws_brick >>> >>> Brick50: glusterfs5sds.commvault.com:/ws/disk6/ws_brick >>> >>> Brick51: glust

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

usterfs5sds.commvault.com:/ws/disk7/ws_brick >> >> Brick54: glusterfs6sds.commvault.com:/ws/disk7/ws_brick >> >> Brick55: glusterfs4sds.commvault.com:/ws/disk8/ws_brick >> >> Brick56: glusterfs5sds.commvault.com:/ws/disk8/ws_brick >> >> Brick57: gl

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

ormance.readdir-ahead: on > > diagnostics.client-log-level: INFO > > auth.allow: glusterfs1sds,glusterfs2sds,glusterfs3sds,glusterfs4sds. > commvault.com,glusterfs5sds.commvault.com,glusterfs6sds.commvault.com > > > > Thanks and Regards, > > Ram > > *From:* Pranith Kumar

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

: Pranith Kumar Karampuri [mailto:pkara...@redhat.com] Sent: Friday, July 07, 2017 12:15 PM 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 On Fri, Jul 7, 2017 at 9:25 PM

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

st gfid/volume-id removal. > > 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.

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

nith Kumar Karampuri [mailto:pkara...@redhat.com] > *Sent:* Friday, July 07, 2017 11:46 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

: [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_REMO

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

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