search for: 3.12.1

Hi all, I'm taking a stab at deploying a storage cluster to explore the Halo AFR feature and running into some trouble. In GCE, I have 4 instances, each with one 10gb brick. 2 instances are in the US and the other 2 are in Asia (with the hope that it will drive up latency sufficiently). The bricks make up a Replica-4 volume. Before I enable halo, I can mount to volume and r/w files. The

I think the problem here is by default the quorum is playing around here, to get rid of this you can change quorum type as fixed and the value as 2 , or you can disable the quorum. Regards Rafi KC On 11/08/2017 04:03 AM, Jon Cope wrote: > Hi all, > > I'm taking a stab at deploying a storage cluster to explore the Halo > AFR feature and running into some trouble. In GCE, I

CentOS Errata and Bugfix Advisory 2020:5031 Upstream details at : https://access.redhat.com/errata/RHBA-2020:5031 The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) x86_64: de3aeef4443f60aa6795ee64bd6c2d7bf33a2b82ff3b9119c255830faa49f4c4 opencryptoki-3.12.1-3.el7_9.i686.rpm

On 02/26/2018 02:03 PM, Shyam Ranganathan wrote: > Hi, > > RC1 is tagged in the code, and the request for packaging the same is on > its way. > > We should have packages as early as today, and request the community to > test the same and return some feedback. > > We have about 3-4 days (till Thursday) for any pending fixes and the > final release to happen, so

Hi, When I upgraded my cluster, df started returning some odd numbers for my legacy volumes. Newly created volumes after the upgrade, df works just fine. I have been researching since Monday and have not found any reference to this symptom. "vm-images" is the old legacy volume, "test" is the new one. [root at st-srv-03 ~]# (df -h|grep bricks;ssh st-srv-02 'df -h|grep

I found the following memory leak present in 3.13, 4.0 and master: https://bugzilla.redhat.com/show_bug.cgi?id=1550078 I will clone/port to 4.0 as soon as the patch is merged. On Wed, Feb 28, 2018 at 5:55 PM, Javier Romero <xavinux at gmail.com> wrote: > Hi all, > > Have tested on CentOS Linux release 7.4.1708 (Core) with Kernel > 3.10.0-693.17.1.el7.x86_64 > > This

CentOS Errata and Bugfix Advisory 2014:1907 Upstream details at : https://rhn.redhat.com/errata/RHBA-2014-1907.html The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) x86_64: d74b5e836e648e18acac3df8cfa94b13e2f774ef7400f9bbe1b83751fa3c4f66 selinux-policy-3.12.1-153.el7_0.12.noarch.rpm

CentOS Errata and Bugfix Advisory 2014:1996 Upstream details at : https://rhn.redhat.com/errata/RHBA-2014-1996.html The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) x86_64: df417c53ae850df24a70b10e5f7e770446699f60f721295ef3804b0fe8b16c88 selinux-policy-3.12.1-153.el7_0.13.noarch.rpm

CentOS Errata and Bugfix Advisory 2014:1301 Upstream details at : https://rhn.redhat.com/errata/RHBA-2014-1301.html The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) x86_64: 138e956218f4d7ebb9a2103811219c498178d603dd5157f9c27aef83c4094d4d selinux-policy-3.12.1-153.el7_0.11.noarch.rpm

The Gluster community is pleased to announce the release of Gluster 3.12.1 (packages available at [1,2,3]). Release notes for the release can be found at [4]. We still carry a major issue that is reported in the release-notes as follows, - Expanding a gluster volume that is sharded may cause file corruption Sharded volumes are typically used for VM images, if such volumes are expanded

We're trying to setup 3 PRDM partitions (VMware) across 2 nodes. As long as only one is configured in cluster.conf, there's not problem. As soon as we try to use 2 or more we get issues. It looks the same as bug 636: http://oss.oracle.com/bugzilla/show_bug.cgi?id=636 I posted my cluster.conf and command line results there. I'm including them here in the hopes that someone on this

Hi all, Have tested on CentOS Linux release 7.4.1708 (Core) with Kernel 3.10.0-693.17.1.el7.x86_64 This package works ok http://cbs.centos.org/kojifiles/work/tasks/1548/311548/centos-release-gluster40-0.9-1.el7.centos.x86_64.rpm # yum install http://cbs.centos.org/kojifiles/work/tasks/1548/311548/centos-release-gluster40-0.9-1.el7.centos.x86_64.rpm # yum install glusterfs-server # systemctl

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

I've recently upgraded my project-local copy of LLVM from 3.1svn to the latest 3.2svn, and all hell broke loose in my attempts to build OCaml projects. Trying to narrow it down, I tried testing examples/OCaml-Kaleidoscope and eventually test/Bindings, only to discover that literally nothing in the repository which uses the OCaml bindings seems to build in the current trunk: -

Hi, I have been struggling with this OOM issue and so far nothing has helped. So we are running 10TB archive volume which stores bit more than 7M files. The problem is that due to the way we are managing this archive, we are forced to run daily "full scans" of file system to discover new uncompressed files. I know, i know, this is not optimal solution but it is as it is right now. So

On Sep 7, 2012, at 3:40 PM, Nuno Lopes wrote: > The linking issue is a recent breakage. > I traced it back to r163175. Basically LLVMConstInlineAsm() got an additional parameter, but the C headers and the OCaml bindings were not updated accordingly. r163175 was my change. I'm not familiar with the OCaml project. If I'm responsible for updating said C headers/OCaml bindings, would

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

Thanks Milind, Yes I?m hanging out for CentOS?s Storage / Gluster SIG to release the packages for 3.12.1, I can see the packages were built a week ago but they?re still not on the repo :( -- Sam > On 18 Sep 2017, at 9:57 pm, Milind Changire <mchangir at redhat.com> wrote: > > Sam, > You might want to give glusterfs-3.12.1 a try instead. > > > >> On Fri, Sep

I have a ISO that I have remaster for some custom recovery procedures. I tried using the same rootfs (initrd) that works with kernel 3.1.2 on older hardware, but not newer. So I downloaded the 3.12.1 kernel tree to a Ubuntu 10 server. Builded the 3.12.1 kernel and tried it with the older rootfs. Now the new hardware and old hardware will fire up the network, but when I try and mount.cifs I get a

The linking issue is a recent breakage. I traced it back to r163175. Basically LLVMConstInlineAsm() got an additional parameter, but the C headers and the OCaml bindings were not updated accordingly. About the miscompilations, can you provide further details? Nuno ----- Original Message ----- > I've recently upgraded my project-local copy of LLVM from 3.1svn to the > latest