search for: _posix_remove_xattr

...7-12-01 14:10:16.947623] I [MSGID: 115063] [server-rpc-fops.c:1317:server_ftruncate_cbk] > 0-c_glusterfs-server: 70: FTRUNCATE 0 (8f9c8054-b0d7-4b93-a95b-cd3ab249c56d)==> > (No space left on device) [No space left on device] > [2017-12-01 14:10:16.968515] E [MSGID: 113001] [posix.c:4616:_posix_remove_xattr] > 0-c_glusterfs-posix: removexattr failed on /opt/lvmdir/c2/brick/. > glusterfs/00/00/00000000-0000-0000-0000-000000000001/configuration (for > trusted.glusterfs.dht) [No space left on device] > [2017-12-01 14:10:16.968589] I [MSGID: 115058] > [server-rpc-fops.c:740:server_removexat...

On Fri, Jul 7, 2017 at 9:25 PM, Ankireddypalle Reddy <areddy at commvault.com> 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 happens only from healing code of afr/ec. And this can only happen if the source brick doesn't have gfid, which doesn't seem to match with the...

...rg); gluster-users at gluster.org Subject: Re: [Gluster-devel] gfid and volume-id extended attributes lost On Fri, Jul 7, 2017 at 9:25 PM, Ankireddypalle Reddy <areddy at commvault.com<mailto:areddy at commvault.com>> 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 happens only from healing code of afr/ec. And this can only happen if the source brick doesn't have gfid, which doesn't seem to match with the...

...Subject:* Re: [Gluster-devel] gfid and volume-id extended attributes lost > > > > > > > > On Fri, Jul 7, 2017 at 9:25 PM, Ankireddypalle Reddy <areddy at commvault.com> > 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 > happens only from healing code of afr/ec. And this can only happen if the > source brick doesn't have gfid, which doesn't se...

...gt;> lost >> >> >> >> >> >> >> >> On Fri, Jul 7, 2017 at 9:25 PM, Ankireddypalle Reddy < >> areddy at commvault.com> 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 >> happens only from healing code of afr/ec. And this can only happen if the >> source brick doesn't have gfid, whic...

...> >>> >>> >>> >>> On Fri, Jul 7, 2017 at 9:25 PM, Ankireddypalle Reddy < >>> areddy at commvault.com> 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 >>> happens only from healing code of afr/ec. And this can only happen if the >>> source brick doesn't...

3.7.19 Thanks and Regards, Ram From: Pranith Kumar Karampuri [mailto:pkarampu at redhat.com] Sent: Friday, July 07, 2017 11:54 AM To: Ankireddypalle Reddy Cc: Gluster Devel (gluster-devel at gluster.org); gluster-users at gluster.org Subject: Re: [Gluster-devel] gfid and volume-id extended attributes lost On Fri, Jul 7, 2017 at 9:20 PM, Ankireddypalle Reddy <areddy at

...GID: 115063] >> [server-rpc-fops.c:1317:server_ftruncate_cbk] 0-c_glusterfs-server: 70: >> FTRUNCATE 0 (8f9c8054-b0d7-4b93-a95b-cd3ab249c56d)==> (No space left on >> device) [No space left on device] >> [2017-12-01 14:10:16.968515] E [MSGID: 113001] >> [posix.c:4616:_posix_remove_xattr] 0-c_glusterfs-posix: removexattr >> failed on /opt/lvmdir/c2/brick/.glusterfs/00/00/00000000-0000-0000- >> 0000-000000000001/configuration (for trusted.glusterfs.dht) [No space >> left on device] >> [2017-12-01 14:10:16.968589] I [MSGID: 115058] >> [server-rpc-fops.c:...

...gt;>> >>>> On Fri, Jul 7, 2017 at 9:25 PM, Ankireddypalle Reddy < >>>> areddy at commvault.com> 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 >>>> happens only from healing code of afr/ec. And this can only happen if the >>>> source b...

...:gluster-users at gluster.org> Subject: Re: [Gluster-devel] gfid and volume-id extended attributes lost On Fri, Jul 7, 2017 at 9:25 PM, Ankireddypalle Reddy <areddy at commvault.com<mailto:areddy at commvault.com>> 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 happens only from healing code of afr/ec. And this can only happen if the source brick doesn't have gfid, which doesn't seem to match with the...

...Subject:* Re: [Gluster-devel] gfid and volume-id extended attributes lost > > > > > > > > On Fri, Jul 7, 2017 at 9:25 PM, Ankireddypalle Reddy <areddy at commvault.com> > 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 > happens only from healing code of afr/ec. And this can only happen if the > source brick doesn't have gfid, which doesn't se...

On Fri, Jul 7, 2017 at 9:20 PM, Ankireddypalle Reddy <areddy at commvault.com> 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 the attributes were again lost. Had to stop glusterd

...;> [server-rpc-fops.c:1317:server_ftruncate_cbk] 0-c_glusterfs-server: 70: >>> FTRUNCATE 0 (8f9c8054-b0d7-4b93-a95b-cd3ab249c56d)==> (No space left on >>> device) [No space left on device] >>> [2017-12-01 14:10:16.968515] E [MSGID: 113001] >>> [posix.c:4616:_posix_remove_xattr] 0-c_glusterfs-posix: removexattr >>> failed on /opt/lvmdir/c2/brick/.glusterfs/00/00/00000000-0000-0000-0000-000000000001/configuration >>> (for trusted.glusterfs.dht) [No space left on device] >>> [2017-12-01 14:10:16.968589] I [MSGID: 115058] >>> [server-rpc-f...

...c-fops.c:1317:server_ftruncate_cbk] 0-c_glusterfs-server: >>>> 70: FTRUNCATE 0 (8f9c8054-b0d7-4b93-a95b-cd3ab249c56d)==> (No space >>>> left on device) [No space left on device] >>>> [2017-12-01 14:10:16.968515] E [MSGID: 113001] >>>> [posix.c:4616:_posix_remove_xattr] 0-c_glusterfs-posix: removexattr >>>> failed on /opt/lvmdir/c2/brick/.glusterfs/00/00/00000000-0000-0000-0000-000000000001/configuration >>>> (for trusted.glusterfs.dht) [No space left on device] >>>> [2017-12-01 14:10:16.968589] I [MSGID: 115058] >>>&g...