search for: 101174

...alue 64 > [2017-10-24 17: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...

...;> [2017-10-24 17: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.au...

...ersion 3.10.0, became 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...

...th correction [2017-08-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 [MSGI...

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

...able 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 recognize...

...gt; [2017-08-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.23920...

...ble 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 recognize...

...able 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 recognize...

...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-read...

...ecommended 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-read...

....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...

...mended 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 >>> ...

...mall 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: opt...

Hi, I finally got the serial cable for this CyberPower CP550SL / AE550, and have successfully tested the genericups type 7 driver. The shutdown delay is about 2 minutes after the shutdown signal, and that signal needs to be rather long, I got it to work with 20 seconds. I suspect that all CyberPower UPSes that are compatible with the Windows UPS service are type 7. All references to the

---------- 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

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

...4-09 05:08:13.738655] 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 [so...

...SGID: 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...

...18-02-13 08:16:13.945237] 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...