search for: gf_log_warning

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 for file %s", real_path); 3 op_ret = -1; 4 goto out; 5 } 6 if (!strcmp (GF_XATTR_VOL_ID_KEY, name)) { 7 gf_msg (this->name, GF_LOG_WAR...

...-users at gluster.org Subject: 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 for file %s", real_path); 3 op_ret = -1; 4 goto out; 5 } 6 if (!strcmp (GF_XATTR_VOL_ID_KEY, name)) { 7 gf_msg (this->name, GF...

...d 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 for file %s", > real_path); > 3 op_ret = -1; > > 4 goto out; > > 5 } > > 6 if (!strcmp (GF_XATTR_VOL_ID_KEY, name...

...r Program received signal SIGSEGV, Segmentation fault. 0x00000008008ef32f in gf_thread_create (thread=0x800be9500, attr=0x0, start_routine=0x80091e960 <pool_sweeper>, arg=0x0, name=0x8009c683b "memsweep") at common-utils.c:3754 3754 gf_msg (THIS->name, GF_LOG_WARNING, 0, I'm pretty weak with debugging tools, but if you could give me some hints on how to collect useful data I'd happy to provide it. Thank you in advance.

...rs at gluster.org> Subject: 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 for file %s", real_path); 3 op_ret = -1; 4 goto out; 5 } 6 if (!strcmp (GF_XATTR_VOL_ID_KEY, name)) { 7 gf_msg (this->name, GF...

...signal SIGSEGV, Segmentation fault. > 0x00000008008ef32f in gf_thread_create (thread=0x800be9500, attr=0x0, > start_routine=0x80091e960 <pool_sweeper>, arg=0x0, name=0x8009c683b > "memsweep") at common-utils.c:3754 > 3754 gf_msg (THIS->name, GF_LOG_WARNING, 0, > Hello Kaleb, Just a quick update: I've tried to compile and run the latest 4.0.2, and I experience the same issue. To successfully compile I had to apply your patch, however I do get the same segmentation fault with 4.0.2 as well. Many thanks.

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) trusted.glusterfs.volume-id We had to manually set these extended attributes to start the volume.

...d 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 for file %s", > real_path); > 3 op_ret = -1; > > 4 goto out; > > 5 } > > 6 if (!strcmp (GF_XATTR_VOL_ID_KEY, name...

...rs at gluster.org> Subject: 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 for file %s", real_path); 3 op_ret = -1; 4 goto out; 5 } 6 if (!strcmp (GF_XATTR_VOL_ID_KEY, name)) { 7 gf_msg (this->name, GF...

...d 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 for file %s", > real_path); > 3 op_ret = -1; > > 4 goto out; > > 5 } > > 6 if (!strcmp (GF_XATTR_VOL_ID_KEY, name...

...;> >> >> >> 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 for file %s", >> real_path); >> 3 op_ret = -1; >> >> 4 goto out; >> >> 5 } >> >> 6...

...> 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 for file %s", >>> real_path); >>> 3 op_ret = -1; >>> >>> 4 goto out; >>> >>> 5...

...ppen 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 for file %s", >>>> real_path); >>>> 3 op_ret = -1; >>>> >>>> 4 goto out; >>>...

...rs at gluster.org> Subject: 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 for file %s", real_path); 3 op_ret = -1; 4 goto out; 5 } 6 if (!strcmp (GF_XATTR_VOL_ID_KEY, name)) { 7 gf_msg (this->name, GF...

...d 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 for file %s", > real_path); > 3 op_ret = -1; > > 4 goto out; > > 5 } > > 6 if (!strcmp (GF_XATTR_VOL_ID_KEY, name...

On 05/07/2018 04:29 AM, Roman Serbski wrote: > Hello, > > Has anyone managed to successfully compile the latest 3.13.2 under > FreeBSD 11.1? ./autogen.sh and ./configure seem to work but make > fails: See https://review.gluster.org/19974 3.13 reached EOL with 4.0. There will be a fix posted for 4.0 soon. In the mean time I believe your specific problem with 3.13.2 should be

...Segmentation fault. >> 0x00000008008ef32f in gf_thread_create (thread=0x800be9500, attr=0x0, >> start_routine=0x80091e960 <pool_sweeper>, arg=0x0, name=0x8009c683b >> "memsweep") at common-utils.c:3754 >> 3754 gf_msg (THIS->name, GF_LOG_WARNING, 0, >> > > Hello Kaleb, > > Just a quick update: I've tried to compile and run the latest 4.0.2, > and I experience the same issue. To successfully compile I had to > apply your patch, That's certainly true. The issue hasn't been fixed in any version of glust...

Hello, Has anyone managed to successfully compile the latest 3.13.2 under FreeBSD 11.1? ./autogen.sh and ./configure seem to work but make fails: Making all in src CC glfs.lo cc: warning: argument unused during compilation: '-rdynamic' [-Wunused-command-line-argument] cc: warning: argument unused during compilation: '-rdynamic' [-Wunused-command-line-argument] fatal

Hi all, Gluster and Ganesha are amazing. Thank you for this great work! I?m struggling with one issue and I think that you might be able to help me. I spent some time by playing with Gluster and Ganesha and after I gain some experience I decided that I should go into production but I?m still struggling with one issue. I have 3x node CentOS 7.3 with the most current Gluster and Ganesha from