similar to: Is transport=rdma tested with "stripe"?

Forgot to mention that I was using CentOS7.3 and GlusterFS 3.10.3 that is the latest available. From: gluster-users-bounces at gluster.org [mailto:gluster-users-bounces at gluster.org] On Behalf Of Hatazaki, Takao Sent: Tuesday, August 15, 2017 2:32 AM To: gluster-users at gluster.org Subject: [Gluster-users] Is transport=rdma tested with "stripe"? Hi, I have 2 servers with Mellanox

looks like your rdma is not functional did you tested with qperf? On Mon, Aug 14, 2017 at 7:37 PM, Hatazaki, Takao <takao.hatazaki at hpe.com> wrote: > Forgot to mention that I was using CentOS7.3 and GlusterFS 3.10.3 that is > the latest available. > > > > *From:* gluster-users-bounces at gluster.org [mailto:gluster-users-bounces@ > gluster.org] *On Behalf Of

Hi, I did ib_write_lat in perftest. It worked fine. Between servers and between server and client, 2-byte latency was ~0.8us, 8MB bandwidth was ~6GB/s. Very normal with IB/FDR. -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.gluster.org/pipermail/gluster-users/attachments/20170815/4217c89e/attachment.html>

[ Hi Takao. Could you attach some logs which we can diagnostic? On 2017? 08? 15? 19:42, Hatazaki, Takao wrote: > > Hi, > > > > I did ib_write_lat in perftest. It worked fine. Between servers and > between server and client, 2-byte latency was ~0.8us, 8MB bandwidth > was ~6GB/s. Very normal with IB/FDR. > > > >

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

> Note that "stripe" is not tested much and practically unmaintained. Ah, this was what I suspected. Understood. I'll be happy with "shard". Having said that, "stripe" works fine with transport=tcp. The failure reproduces with just 2 RDMA servers (with InfiniBand), one of those acts also as a client. I looked into logs. I paste lengthy logs below with

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. Thank you. Takao

On Wed, Aug 16, 2017 at 4:44 PM, Hatazaki, Takao <takao.hatazaki at hpe.com> wrote: >> Note that "stripe" is not tested much and practically unmaintained. > > Ah, this was what I suspected. Understood. I'll be happy with "shard". > > Having said that, "stripe" works fine with transport=tcp. The failure reproduces with just 2 RDMA servers

Hi, I am new to GlusterFS. I have 2 computers with Intel Omni-Path hardware/software installed. RDMA is running ok on those according to "ibv_devices" output. GlusterFS "server" installed and set up ok on those. Peer probes on TCP-over-OPA worked ok. I created a replicated volume with transport=tcp, then tested them by mounting the volume on one of servers. Things worked

Did any RDMA/Ethernet users see this Gluster error? If so do you know what caused it and how to fix? If you haven't seen it, what RPMs and configuration do you use specific to RDMA/Ethernet? [2011-11-10 10:30:20.595801] C [rdma.c:2417:rdma_connect_qp]0-rpc-transport/rdma: Failed to modify QP to RTR [2011-11-10 10:30:20.595930] E [rdma.c:4159:rdma_handshake_pollin] 0-rpc-transport/rdma:

Hello All, I have this problem starting Centos7.3 - the official name escapes me at the moment. I often install Centos7 Minimal, then X Window System, then Mate desktop. This last step gives me trouble, and I have to run # yum groupinstall mate --skip-broken output: skipped packages: NetworkManager-I2tp ldns libreswan unbound-libs xl2tpd I realise this is probably an issue for EPEL

hello, I am getting such error: libvirtd[27218]: segfault at 0 ip 00007f4940725721 sp 00007f4930711740 error 4 in libvirt.so.0.2000.0[7f4940678000+353000] when I am trying to start VM with graphic spice/vnc console - in headless mode(without graphic console) it is running I noticed this after update oVirt 4.0 to oVirt 4.1 however I noticed that also libvirtd and related packages were upgraded

Hello All, updating from Centos7.3 to Centos7.4 rendered one of our laptops unbootable. EM: Failed to open \EFI\BOOT\grubx64.efi - Not Found Failed to load image \EFI\BOOT\grubx64.efi: Not Found start_image() returned Not Found How could this occur because of an update and how to fix this? What I tried is booting from centos usb, chroot to /mnt/sysimage and gave command: efibootmgr

hello, I attached core dump - not sure if it was what you have asked for I am rather just admin not developer :) Regards, Rafal Wojciechowski W dniu 20.04.2017 o 16:44, Pavel Hrdina pisze: > On Thu, Apr 20, 2017 at 07:36:42AM +0200, Rafał Wojciechowski wrote: >> hello, >> >> I am getting such error: >> libvirtd[27218]: segfault at 0 ip 00007f4940725721 sp

Hello I have two peers setup and working with x2 bricks each. They have been working via tcp for the last 4-5 months. I just got two Infiniband cards and put the on the peers. I want to change the transport type to rdma instead of tcp but I don't see an easy way to do this. Can you please help me with proper instructions. Best Regards Ivan Dimitrov

Hi everyone, I hope you can help me with some performance troubles I've been having. I'm doing some tests with gluster 3.2.0, and I can't understand some of the behavior I'm getting with gluster. The test is using a volume with 12 stripped bricks (each brick is an HD), with no replication, via RDMA. I'm doing random readings of 4GByte files with the FIO tool. Gluster

Hi, When can i download Centos 7.3 (1611) iso, what is the release date ? According to the link below, I can see an announcement for Centos 7.3 release notes:- https://wiki.centos.org/Manuals/ReleaseNotes/CentOS7.3#head-463e46d011f37a436554aca4d5d6c8dacc8f3d47 Regards Sudhanshu

On Tue, 13 Dec 2016 22:09:22 +0100 Reindl Harald via samba <samba at lists.samba.org> wrote: > > > Am 13.12.2016 um 21:58 schrieb Kris Lou via samba: > > "python-crypto" looks like it's also in EPEL. > > > > http://rpms.famillecollet.com/rpmphp/zoom.php?rpm=python-crypto > > looks so, "yum" is just too dumb to find it when the

Hi, In the past couple of weeks, we've sent the following fixes concerning VM corruption upon doing rebalance - https://review.gluster.org/#/q/status:merged+project:glusterfs+branch:master+topic:bug-1440051 These fixes are very much part of the latest 3.10.2 release. Satheesaran within Red Hat also verified that they work and he's not seeing corruption issues anymore. I'd like to

----- Oorspronkelijk bericht ----- Van: "Adrian Jenzer" <a.jenzer at herzogdemeuron.com> Aan: "CentOS mailing list" <centos at centos.org> Verzonden: Dinsdag 9 januari 2018 16:56:57 Onderwerp: Re: [CentOS] update to Centos7.4: Failed to open \EFI\BOOT\grubx64.efi - Not Found -----Original Message----- From: CentOS [mailto:centos-bounces at centos.org] On Behalf Of