search for: _log_if_unknown_option

Displaying 20 results from an estimated 37 matches for "_log_if_unknown_option".

2017 Oct 24
2
brick is down but gluster volume status says it's fine
...7:19:04.611815] W [MSGID: 101002] > [options.c:954:xl_opt_validate] 0-digitalcorpora-server: option > 'listen-port' is deprecated, preferred is 'transport.socket.listen-port', > continuing with correction > [2017-10-24 17:19:04.615974] W [MSGID: 101174] > [graph.c:361:_log_if_unknown_option] 0-digitalcorpora-server: option > 'rpc-auth.auth-glusterfs' is not recognized > [2017-10-24 17:19:04.616033] W [MSGID: 101174] > [graph.c:361:_log_if_unknown_option] 0-digitalcorpora-server: option > 'rpc-auth.auth-unix' is not recognized > [2017-10-24 17:19:04.61607...
2017 Oct 24
0
brick is down but gluster volume status says it's fine
...815] W [MSGID: 101002] [options.c:954:xl_opt_validate] >> 0-digitalcorpora-server: option 'listen-port' is deprecated, preferred is >> 'transport.socket.listen-port', continuing with correction >> [2017-10-24 17:19:04.615974] W [MSGID: 101174] >> [graph.c:361:_log_if_unknown_option] 0-digitalcorpora-server: option >> 'rpc-auth.auth-glusterfs' is not recognized >> [2017-10-24 17:19:04.616033] W [MSGID: 101174] >> [graph.c:361:_log_if_unknown_option] 0-digitalcorpora-server: option >> 'rpc-auth.auth-unix' is not recognized >> [2017-...
2018 Jan 23
6
parallel-readdir is not recognized in GlusterFS 3.12.4
...stable in version 3.11.0, and is now recommended for small file workloads in the Red Hat Gluster Storage Server documentation[2]. I've successfully enabled this on one of my volumes but I notice the following in the client mount log: [2018-01-23 10:24:24.048055] W [MSGID: 101174] [graph.c:363:_log_if_unknown_option] 0-homes-readdir-ahead-1: option 'parallel-readdir' is not recognized [2018-01-23 10:24:24.048072] W [MSGID: 101174] [graph.c:363:_log_if_unknown_option] 0-homes-readdir-ahead-0: option 'parallel-readdir' is not recognized The GlusterFS version on the client and server is 3.12.4. W...
2017 Aug 16
0
Is transport=rdma tested with "stripe"?
...8-16 10:59:24.142207] I [MSGID: 121050] [ctr-helper.c:259:extract_ctr_options] 0-gfdbdatastore: CTR Xlator is disabled. [2017-08-16 10:59:24.237783] I [trash.c:2493:init] 0-gv0-trash: no option specified for 'eliminate', using NULL [2017-08-16 10:59:24.239129] W [MSGID: 101174] [graph.c:361:_log_if_unknown_option] 0-gv0-server: option 'rpc-auth.auth-glusterfs' is not recognized [2017-08-16 10:59:24.239189] W [MSGID: 101174] [graph.c:361:_log_if_unknown_option] 0-gv0-server: option 'rpc-auth.auth-unix' is not recognized [2017-08-16 10:59:24.239203] W [MSGID: 101174] [graph.c:361:_log_if_unkno...
2017 Aug 15
2
Is transport=rdma tested with "stripe"?
On Tue, Aug 15, 2017 at 01:04:11PM +0000, Hatazaki, Takao wrote: > Ji-Hyeon, > > You're saying that "stripe=2 transport=rdma" should work. Ok, that > was firstly I wanted to know. I'll put together logs later this week. Note that "stripe" is not tested much and practically unmaintained. We do not advise you to use it. If you have large files that you
2018 Jan 27
0
parallel-readdir is not recognized in GlusterFS 3.12.4
...d is now recommended for > small file workloads in the Red Hat Gluster Storage Server > documentation[2]. I've successfully enabled this on one of my volumes but I > notice the following in the client mount log: > > [2018-01-23 10:24:24.048055] W [MSGID: 101174] > [graph.c:363:_log_if_unknown_option] 0-homes-readdir-ahead-1: option > 'parallel-readdir' is not recognized > [2018-01-23 10:24:24.048072] W [MSGID: 101174] > [graph.c:363:_log_if_unknown_option] 0-homes-readdir-ahead-0: option > 'parallel-readdir' is not recognized > > The GlusterFS version on the c...
2017 Aug 18
1
Is transport=rdma tested with "stripe"?
...:24.142207] I [MSGID: 121050] [ctr-helper.c:259:extract_ctr_options] 0-gfdbdatastore: CTR Xlator is disabled. > [2017-08-16 10:59:24.237783] I [trash.c:2493:init] 0-gv0-trash: no option specified for 'eliminate', using NULL > [2017-08-16 10:59:24.239129] W [MSGID: 101174] [graph.c:361:_log_if_unknown_option] 0-gv0-server: option 'rpc-auth.auth-glusterfs' is not recognized > [2017-08-16 10:59:24.239189] W [MSGID: 101174] [graph.c:361:_log_if_unknown_option] 0-gv0-server: option 'rpc-auth.auth-unix' is not recognized > [2017-08-16 10:59:24.239203] W [MSGID: 101174] [graph.c:361:_lo...
2018 Jan 29
2
parallel-readdir is not recognized in GlusterFS 3.12.4
...is now recommended for small > file workloads in the Red Hat Gluster Storage Server documentation[2]. I've > successfully enabled this on one of my volumes but I notice the following in > the client mount log: > > [2018-01-23 10:24:24.048055] W [MSGID: 101174] > [graph.c:363:_log_if_unknown_option] 0-homes-readdir-ahead-1: option > 'parallel-readdir' is not recognized > [2018-01-23 10:24:24.048072] W [MSGID: 101174] > [graph.c:363:_log_if_unknown_option] 0-homes-readdir-ahead-0: option > 'parallel-readdir' is not recognized > This is fixed by patch: https://r...
2018 Jan 24
0
parallel-readdir is not recognized in GlusterFS 3.12.4
...d is now recommended for > small file workloads in the Red Hat Gluster Storage Server > documentation[2]. I've successfully enabled this on one of my volumes but I > notice the following in the client mount log: > > [2018-01-23 10:24:24.048055] W [MSGID: 101174] > [graph.c:363:_log_if_unknown_option] 0-homes-readdir-ahead-1: option > 'parallel-readdir' is not recognized > [2018-01-23 10:24:24.048072] W [MSGID: 101174] > [graph.c:363:_log_if_unknown_option] 0-homes-readdir-ahead-0: option > 'parallel-readdir' is not recognized > > The GlusterFS version on the c...
2018 Jan 30
0
parallel-readdir is not recognized in GlusterFS 3.12.4
...file workloads in the Red Hat Gluster Storage Server documentation[2]. > I've > > successfully enabled this on one of my volumes but I notice the > following in > > the client mount log: > > > > [2018-01-23 10:24:24.048055] W [MSGID: 101174] > > [graph.c:363:_log_if_unknown_option] 0-homes-readdir-ahead-1: option > > 'parallel-readdir' is not recognized > > [2018-01-23 10:24:24.048072] W [MSGID: 101174] > > [graph.c:363:_log_if_unknown_option] 0-homes-readdir-ahead-0: option > > 'parallel-readdir' is not recognized > > > >...
2018 Jan 30
1
parallel-readdir is not recognized in GlusterFS 3.12.4
...file workloads in the Red Hat Gluster Storage Server documentation[2]. I've > > successfully enabled this on one of my volumes but I notice the following > > in > > the client mount log: > > > > [2018-01-23 10:24:24.048055] W [MSGID: 101174] > > [graph.c:363:_log_if_unknown_option] 0-homes-readdir-ahead-1: option > > 'parallel-readdir' is not recognized > > [2018-01-23 10:24:24.048072] W [MSGID: 101174] > > [graph.c:363:_log_if_unknown_option] 0-homes-readdir-ahead-0: option > > 'parallel-readdir' is not recognized > > > &gt...
2018 Jan 25
2
parallel-readdir is not recognized in GlusterFS 3.12.4
...>> small file workloads in the Red Hat Gluster Storage Server >> documentation[2]. I've successfully enabled this on one of my volumes but I >> notice the following in the client mount log: >> >> [2018-01-23 10:24:24.048055] W [MSGID: 101174] >> [graph.c:363:_log_if_unknown_option] 0-homes-readdir-ahead-1: option >> 'parallel-readdir' is not recognized >> [2018-01-23 10:24:24.048072] W [MSGID: 101174] >> [graph.c:363:_log_if_unknown_option] 0-homes-readdir-ahead-0: option >> 'parallel-readdir' is not recognized >> >> The Gl...
2018 Jan 26
0
parallel-readdir is not recognized in GlusterFS 3.12.4
...workloads in the Red Hat Gluster Storage Server documentation[2]. >>> I've successfully enabled this on one of my volumes but I notice the >>> following in the client mount log: >>> >>> [2018-01-23 10:24:24.048055] W [MSGID: 101174] >>> [graph.c:363:_log_if_unknown_option] 0-homes-readdir-ahead-1: option >>> 'parallel-readdir' is not recognized >>> [2018-01-23 10:24:24.048072] W [MSGID: 101174] >>> [graph.c:363:_log_if_unknown_option] 0-homes-readdir-ahead-0: option >>> 'parallel-readdir' is not recognized >>...
2018 Jan 26
1
parallel-readdir is not recognized in GlusterFS 3.12.4
...ter Storage Server > documentation[2]. > >>> I've successfully enabled this on one of my volumes but I notice the > >>> following in the client mount log: > >>> > >>> [2018-01-23 10:24:24.048055] W [MSGID: 101174] > >>> [graph.c:363:_log_if_unknown_option] 0-homes-readdir-ahead-1: option > >>> 'parallel-readdir' is not recognized > >>> [2018-01-23 10:24:24.048072] W [MSGID: 101174] > >>> [graph.c:363:_log_if_unknown_option] 0-homes-readdir-ahead-0: option > >>> 'parallel-readdir' is not...
2018 Jan 12
0
Creating cluster replica on 2 nodes 2 bricks each.
---------- Forwarded message ---------- From: Jose Sanchez <josesanc at carc.unm.edu> Date: 11 January 2018 at 22:05 Subject: Re: [Gluster-users] Creating cluster replica on 2 nodes 2 bricks each. To: Nithya Balachandran <nbalacha at redhat.com> Cc: gluster-users <gluster-users at gluster.org> Hi Nithya Thanks for helping me with this, I understand now , but I have few
2018 Jan 11
3
Creating cluster replica on 2 nodes 2 bricks each.
Hi Nithya Thanks for helping me with this, I understand now , but I have few questions. When i had it setup in replica (just 2 nodes with 2 bricks) and tried to added , it failed. > [root at gluster01 ~]# gluster volume add-brick scratch replica 2 gluster01ib:/gdata/brick2/scratch gluster02ib:/gdata/brick2/scratch > volume add-brick: failed: /gdata/brick2/scratch is already part of a
2013 Mar 25
1
A problem when mount glusterfs via NFS
HI: I run glusterfs with four nodes, 2x2 Distributed-Replicate. I mounted it via fuse and did some test, it was ok. However when I mounted it via nfs, a problem was found: When I copied 200G files to the glusterfs, the glusterfs process in the server node(mounted by client) was killed because of OOM, and all terminals of the client were hung. Trying to test for many times, I got the
2018 Apr 09
2
volume start: gv01: failed: Quorum not met. Volume operation not allowed.
...I [MSGID: 101190] [event-epoll.c:613:event_dispatch_epoll_worker] 0-epoll: Started thread with index 7 [2018-04-09 05:08:13.738742] I [MSGID: 101190] [event-epoll.c:613:event_dispatch_epoll_worker] 0-epoll: Started thread with index 8 [2018-04-09 05:08:13.739460] W [MSGID: 101174] [graph.c:363:_log_if_unknown_option] 0-gv01-readdir-ahead: option 'parallel-readdir' is not recognized [2018-04-09 05:08:13.739787] I [MSGID: 114020] [client.c:2360:notify] 0-gv01-client-0: parent translators are ready, attempting connect on transport [2018-04-09 05:08:13.747040] W [socket.c:3216:socket_connect] 0-gv01-cl...
2018 Apr 09
0
volume start: gv01: failed: Quorum not met. Volume operation not allowed.
...epoll.c:613:event_dispatch_epoll_worker] 0-epoll: Started thread > with index 7 > [2018-04-09 05:08:13.738742] I [MSGID: 101190] > [event-epoll.c:613:event_dispatch_epoll_worker] 0-epoll: Started thread > with index 8 > [2018-04-09 05:08:13.739460] W [MSGID: 101174] > [graph.c:363:_log_if_unknown_option] 0-gv01-readdir-ahead: option > 'parallel-readdir' is not recognized > [2018-04-09 05:08:13.739787] I [MSGID: 114020] [client.c:2360:notify] > 0-gv01-client-0: parent translators are ready, attempting connect on > transport > [2018-04-09 05:08:13.747040] W [socket.c:3216:sock...
2018 Feb 13
2
Failed to get quota limits
...237] I [MSGID: 101190] [event-epoll.c:629:event_dispatch_epoll_worker] 0-epoll: Started thread with index 4 [2018-02-13 08:16:13.945247] I [MSGID: 101190] [event-epoll.c:629:event_dispatch_epoll_worker] 0-epoll: Started thread with index 3 [2018-02-13 08:16:13.945941] W [MSGID: 101174] [graph.c:361:_log_if_unknown_option] 0-myvolume-readdir-ahead: option 'parallel-readdir' is not recognized [2018-02-13 08:16:13.946342] I [MSGID: 114020] [client.c:2352:notify] 0-myvolume-client-0: parent translators are ready, attempting connect on transport [2018-02-13 08:16:13.946789] I [MSGID: 114020] [client.c:2352:notif...