similar to: CEBA-2014:0047 CentOS 6 glusterfs Update

Send CentOS-announce mailing list submissions to centos-announce at centos.org To subscribe or unsubscribe via the World Wide Web, visit http://lists.centos.org/mailman/listinfo/centos-announce or, via email, send a message with subject or body 'help' to centos-announce-request at centos.org You can reach the person managing the list at centos-announce-owner at centos.org When

Hi? If there was only one client, there were not any problems even the traffic was very heavy. But if I used several clients to write the same volume, then I could see the segmentation fault. I used gdb to debug, but the performance was much lower than the previous test results, and we couldn't see the errors. We thought that the problem only occurred when multiple clients wrote the same

Dear gluster team, I have installed glusterfs on my servers for the storage. Machine: x86_64-redhat-linux I have created volumes with rdma protocol for infiniband. I have mount with acl option on server and client. When I run setfacl for glusterfs mount point it works fine but when i do it for nfs mount it says. setfacl <dir> : operation not supported. The logs created in server are as

OK - finished some tests over tcp and ironed out a lot of problems. rdma is next; should be snap now.... [I must admit that this is my 1st foray into the land of IB, so some of the following may be obvious to a non-naive admin..] except that while I can create and start the volume with rdma as transport: ================================== root at pbs3:~ 622 $ gluster volume info glrdma

Hi ,all We found a strange problem. Some clients worked normally while some clients couldn't access sepcial files. For exmaple, Client A couldn't create the directory xxx, but Client B could. However, if Client B created the directory, Client A could acess it and even deleted it. But Client A still couldn't create the same directory later. If I changed the directory name, Client A

This looks like there could be some some problem requesting / leaking / whatever memory but without looking at the core its tought to tell for sure. Note: /usr/lib64/libglusterfs.so.0(_gf_msg_backtrace_nomem+0x78)[0x7f95bc54e618] Can you open up a bugzilla and get us the core file to review? -b ----- Original Message ----- > From: "???" <21291285 at qq.com> > To:

CentOS Errata and Security Advisory 2018:2892 Moderate Upstream details at : https://access.redhat.com/errata/RHSA-2018:2892 The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) i386: 131786837b080aba5234623fbd2277efe4873585ee2628b5e65bb26e99425c65 glusterfs-3.12.2-18.el6.i686.rpm

You can still get them from https://buildlogs.centos.org/centos/7/storage/x86_64/gluster-3.13/ (I don't know how much longer they'll be there. I suggest you copy them if you think you're going to need them in the future.) n 05/15/2018 04:58 AM, Davide Obbi wrote: > hi, > > i noticed that this repo for glusterfs 3.13 does not exists anymore at: > >

Hi, All, I used Infiniband to connect all GlusterFS nodes and the clients. Previously I run IP over IB and everything was OK. Now I used rdma transport mode instead. And then I ran the traffic. After I while, the glusterfs process exited because of segmentation fault. Here were the messages when I saw segmentation fault: pending frames: frame : type(0) op(0) frame : type(0) op(0)

Thanks Kaleb, any chance i can make the node working after the downgrade? thanks On Tue, May 15, 2018 at 2:02 PM, Kaleb S. KEITHLEY <kkeithle at redhat.com> wrote: > > You can still get them from > https://buildlogs.centos.org/centos/7/storage/x86_64/gluster-3.13/ > > (I don't know how much longer they'll be there. I suggest you copy them > if you think

On 05/15/2018 08:08 AM, Davide Obbi wrote: > Thanks Kaleb, > > any chance i can make the node working after the downgrade? > thanks Without knowing what doesn't work, I'll go out on a limb and guess that it's an op-version problem. Shut down your 3.13 nodes, change their op-version to one of the valid 3.12 op-versions (e.g. 31203) and restart. Then the 3.12 nodes should

CentOS Errata and Bugfix Advisory 2014:0138 Upstream details at : https://rhn.redhat.com/errata/RHBA-2014-0138.html The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) i386: 074cded096000092dfd80b9b85c440b53d591c21e70de7eee824ea23a526c0f9 yum-NetworkManager-dispatcher-1.1.30-17.el6_5.noarch.rpm

CentOS Errata and Security Advisory 2014:1307 Important Upstream details at : https://rhn.redhat.com/errata/RHSA-2014-1307.html The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) i386: e5ed74d34ab7b95fbba83147d8203e51d55991989bb752b41fc9c584fe2b3a87 nss-3.16.1-7.el6_5.i686.rpm

CentOS Errata and Bugfix Advisory 2014:0201 Upstream details at : https://rhn.redhat.com/errata/RHBA-2014-0201.html The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) i386: 727dc3b50f032ae08c8d130621aceb876cced3a08e182011d6f9c2dae1ea7c73 phonon-backend-gstreamer-4.6.2-28.el6_5.i686.rpm

CentOS Errata and Security Advisory 2014:0330 Moderate Upstream details at : https://rhn.redhat.com/errata/RHSA-2014-0330.html The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) i386: a9408ead92720322953d6138949e0a5570002d467c3d4d3a59993f41066865cb libsmbclient-3.6.9-168.el6_5.i686.rpm

CentOS Errata and Security Advisory 2014:0866 Moderate Upstream details at : https://rhn.redhat.com/errata/RHSA-2014-0866.html The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) i386: 0c0ec9a01e0e657d1a9e429e32752883eda95e668b5ce606c1523069b06c4cbf libsmbclient-3.6.9-169.el6_5.i686.rpm

CentOS Errata and Security Advisory 2014:0383 Moderate Upstream details at : https://rhn.redhat.com/errata/RHSA-2014-0383.html The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) i386: 09d5d0dc4df4320a41f727e305e1aa16d4a5131242f1396bdd0b8d89fb1efde3 samba4-4.0.0-61.el6_5.rc4.i686.rpm

CentOS Errata and Security Advisory 2014:1009 Important Upstream details at : https://rhn.redhat.com/errata/RHSA-2014-1009.html The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) i386: 2b5e0dbb1a0e11baff46f089b17b26165f3eb107cb42098a922d0965bfa0890d samba4-4.0.0-63.el6_5.rc4.i686.rpm

CentOS Errata and Security Advisory 2014:0255 Moderate Upstream details at : https://rhn.redhat.com/errata/RHSA-2014-0255.html The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) i386: fbcfb2bcf52bf8bbe142eaf4c1ff44b4423c2d1cd9ef5f5e6c6031ac7b0bd84b mod_dav_svn-1.6.11-10.el6_5.i686.rpm

CentOS Errata and Security Advisory 2014:0211 Important Upstream details at : https://rhn.redhat.com/errata/RHSA-2014-0211.html The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) i386: 6ca3a1beea5f113655e4abdf43ba3447ae836639bff9381e372bc6cc9d2172ab postgresql-8.4.20-1.el6_5.i686.rpm