similar to: Empty info file preventing glusterd from starting

Hi Niels, No problem we wil try to backport that patch on 3.7.6. Could you please let me know in which release Gluster community is going to provide this patch and date of that release? Regards, Abhishek On Wed, May 31, 2017 at 10:05 PM, Niels de Vos <ndevos at redhat.com> wrote: > On Wed, May 31, 2017 at 04:08:06PM +0530, ABHISHEK PALIWAL wrote: > > We are using 3.7.6 and on

On Thu, Jun 01, 2017 at 01:03:25PM +0530, ABHISHEK PALIWAL wrote: > Hi Niels, > > No problem we wil try to backport that patch on 3.7.6. > > Could you please let me know in which release Gluster community is going to > provide this patch and date of that release? It really depends on when someone has time to work on it. Our releases are time based, and will happen even when a

Any suggestion.... On Dec 6, 2017 11:51, "ABHISHEK PALIWAL" <abhishpaliwal at gmail.com> wrote: > Hi Team, > > We are getting the crash in glusterd after start of it. When I tried to > debug in brick logs we are getting below errors: > > [2017-12-01 14:10:14.684122] E [MSGID: 100018] > [glusterfsd.c:1960:glusterfs_pidfile_update] 0-glusterfsd: pidfile >

I hope these logs were sufficient... please let me know if you require more logs. On Wed, Dec 6, 2017 at 3:26 PM, ABHISHEK PALIWAL <abhishpaliwal at gmail.com> wrote: > Hi Atin, > > Please find the backtrace and logs files attached here. > > Also, below are the BT from core. > > (gdb) bt > > #0 0x00003fff8834b898 in __GI_raise (sig=<optimized out>) at >

Without the glusterd log file and the core file or the backtrace I can't comment anything. On Wed, Dec 6, 2017 at 3:09 PM, ABHISHEK PALIWAL <abhishpaliwal at gmail.com> wrote: > Any suggestion.... > > On Dec 6, 2017 11:51, "ABHISHEK PALIWAL" <abhishpaliwal at gmail.com> wrote: > >> Hi Team, >> >> We are getting the crash in glusterd after

Hi Atin, Please find the backtrace and logs files attached here. Also, below are the BT from core. (gdb) bt #0 0x00003fff8834b898 in __GI_raise (sig=<optimized out>) at ../sysdeps/unix/sysv/linux/raise.c:55 #1 0x00003fff88350fd0 in __GI_abort () at abort.c:89 [**ALERT: The abort() might not be exactly invoked from the following function line. If the trail function

Hi Team, While mounting the gluster volume using 'mount -t glusterfs' command it is getting failed. When we checked the log file getting the below logs [1970-01-02 10:54:04.420065] E [MSGID: 101187] [event-epoll.c:391:event_register_epoll] 0-epoll: failed to add fd(=7) to epoll fd(=0) [Invalid argument] [1970-01-02 10:54:04.420140] W [socket.c:3095:socket_connect] 0-: failed to register

Hi,we have use glusterfs for two years. After upgraded to 3.2.5,we discover that when one of replicate node reboot and startup the glusterd daemon,the gluster will crash cause by the other replicate node cpu usage reach 100%. Our gluster info: Type: Distributed-Replicate Status: Started Number of Bricks: 5 x 2 = 10 Transport-type: tcp Options Reconfigured: performance.cache-size: 3GB

Any suggestion would be appreciated... On Sep 18, 2017 15:05, "ABHISHEK PALIWAL" <abhishpaliwal at gmail.com> wrote: > Any quick suggestion.....? > > On Mon, Sep 18, 2017 at 1:50 PM, ABHISHEK PALIWAL <abhishpaliwal at gmail.com > > wrote: > >> Hi Team, >> >> As you can see permission for the glusterfs logs in /var/log/glusterfs is >>

On 09/18/2017 09:22 PM, ABHISHEK PALIWAL wrote: > Any suggestion would be appreciated... > > On Sep 18, 2017 15:05, "ABHISHEK PALIWAL" <abhishpaliwal at gmail.com > <mailto:abhishpaliwal at gmail.com>> wrote: > > Any quick suggestion.....? > > On Mon, Sep 18, 2017 at 1:50 PM, ABHISHEK PALIWAL > <abhishpaliwal at gmail.com

Hi Team, I did some modification in glusterfs code and now able to modify the permission of maximum of files. But still 2 file's permission in 0600 1. cli.log 2. file which contains the mounting information for "mount -t glusterfs" command I will really appreciate, if some can point light on this area. Also is there any side effect of changing these permissions apart from other

Hi Team, As you can see permission for the glusterfs logs in /var/log/glusterfs is 600. drwxr-xr-x 3 root root 140 Jan 1 00:00 .. *-rw------- 1 root root 0 Jan 3 20:21 cmd_history.log* drwxr-xr-x 2 root root 40 Jan 3 20:21 bricks drwxr-xr-x 3 root root 100 Jan 3 20:21 . *-rw------- 1 root root 2102 Jan 3 20:21 etc-glusterfs-glusterd.vol.log* Due to that non-root user is not able to

Hi Team, Whenever I am performing the IO operation on gluster volume, the loads is getting increase on CPU which reaches upto 70-80 sometimes. when we started debugging, found that the io_worker thread is created to server the IO request and consume high CPU till that request gets completed. Could you please let me know why io_worker thread takes this much of CPU. Is there any way to resole

On Wed, Aug 30, 2017 at 01:52:59PM +0530, ABHISHEK PALIWAL wrote: > What is Gluster/NFS and how can we use this. Gluster/NFS (or gNFS) is the NFS-server that comes with GlusterFS. It is a NFSv3 server and can only be used to export Gluster volumes. You can enable it: - install the glusterfs-gnfs RPM (glusterfs >= 3.11) - the glusterfs-server RPM might contain the NFS-server (glusterfs

Could you please response? On Fri, Jul 28, 2017 at 5:55 PM, ABHISHEK PALIWAL <abhishpaliwal at gmail.com> wrote: > Hi Team, > > Whenever I am performing the IO operation on gluster volume, the loads is > getting increase on CPU which reaches upto 70-80 sometimes. > > when we started debugging, found that the io_worker thread is created to > server the IO request and

Any quick suggestion.....? On Mon, Sep 18, 2017 at 1:50 PM, ABHISHEK PALIWAL <abhishpaliwal at gmail.com> wrote: > Hi Team, > > As you can see permission for the glusterfs logs in /var/log/glusterfs is > 600. > > drwxr-xr-x 3 root root 140 Jan 1 00:00 .. > *-rw------- 1 root root 0 Jan 3 20:21 cmd_history.log* > drwxr-xr-x 2 root root 40 Jan 3 20:21 bricks

I have modified the source code and its working fine but only below two files permission is not getting change even after modification. 1. cli.log 2. file which contains the mounting information for "mount -t glusterfs" command On Wed, Sep 20, 2017 at 5:20 PM, Kaleb S. KEITHLEY <kkeithle at redhat.com> wrote: > On 09/18/2017 09:22 PM, ABHISHEK PALIWAL wrote: > > Any

Hi Team, I am facing one issue which is exactly same as mentioned on the below link https://bugzilla.redhat.com/show_bug.cgi?id=1408431 Also there are some patches available to fix the issue but seems those are not approved and still discussion is going on https://review.gluster.org/#/c/16279/ Currently the status is "Abandoned". Could you please let me know what is our plan to

On Thu, Aug 17, 2017 at 12:03:02PM +0530, ABHISHEK PALIWAL wrote: > Hi Team, > > I have an query regarding the usage of ACL on gluster volume. I have > noticed that when we use normal gluster volume (without ACL) CPU load is > low, but when we apply the ACL on gluster volume which internally uses Fuse > ACL, CPU load gets increase about 6x times. > > Could you please let

Do we have ACL support on nfs-ganesha? On Aug 30, 2017 3:08 PM, "Niels de Vos" <ndevos at redhat.com> wrote: > On Wed, Aug 30, 2017 at 01:52:59PM +0530, ABHISHEK PALIWAL wrote: > > What is Gluster/NFS and how can we use this. > > Gluster/NFS (or gNFS) is the NFS-server that comes with GlusterFS. It is > a NFSv3 server and can only be used to export Gluster