search for: gluster38

.../gluster/lock/lock 3 (result when starting on second note:data increment is changing from 1 to 2 - changing lock file locatin. Moving it to the root of the gluster share. I appreciate any help to get this up and running. Please see below list of installed packages centos-release-gluster38.noarch 1.0-1.el7.centos @extras glusterfs.x86_64 3.8.5-1.el7 @centos-gluster38 glusterfs-api.x86_64 3.8.5-1.el7 @centos-gluster38 glusterfs-cli.x86_64 3.8.5-1.el7 @centos-gluster38 glusterfs-client-xlators.x86_64 3.8.5-1.el7 @centos-gluster38...

...3.8.0 release notes: https://github.com/gluster/glusterfs/blob/release-3.8/doc/release-notes/3.8.0.md To install GlusterFS 3.8, only two commands are needed: # yum install centos-release-gluster # yum install glusterfs-server The centos-release-gluster content comes from the centos-release-gluster38 package delivered via CentOS Extras repos. This contains all the metadata and dependancy information, needed to install GlusterFS 3.8. Deployments that have centos-release-gluster36 or -gluster37 installed will not automatically upgrade to version 3.8. These installations will continue to stick to...

...3.8.0 release notes: https://github.com/gluster/glusterfs/blob/release-3.8/doc/release-notes/3.8.0.md To install GlusterFS 3.8, only two commands are needed: # yum install centos-release-gluster # yum install glusterfs-server The centos-release-gluster content comes from the centos-release-gluster38 package delivered via CentOS Extras repos. This contains all the metadata and dependancy information, needed to install GlusterFS 3.8. Deployments that have centos-release-gluster36 or -gluster37 installed will not automatically upgrade to version 3.8. These installations will continue to stick to...

...3.8.0 release notes: https://github.com/gluster/glusterfs/blob/release-3.8/doc/release-notes/3.8.0.md To install GlusterFS 3.8, only two commands are needed: # yum install centos-release-gluster # yum install glusterfs-server The centos-release-gluster content comes from the centos-release-gluster38 package delivered via CentOS Extras repos. This contains all the metadata and dependancy information, needed to install GlusterFS 3.8. Deployments that have centos-release-gluster36 or -gluster37 installed will not automatically upgrade to version 3.8. These installations will continue to stick to...

Hi On 09/29/2017 09:09 PM, Bernhard D?bi wrote: > Hi, > > I have a problem with nfs-ganesha serving gluster volumes > > I can read and write files but then one of the DBAs tried to dump an > Oracle DB onto the NFS share and got the following errors: > > > Export: Release 11.2.0.4.0 - Production on Wed Sep 27 23:27:48 2017 > > Copyright (c) 1982, 2011, Oracle

...of the now End-Of-Life Short-Term-Maintenance Gluster 3.11 will automatically get the update to Gluster 3.12, whereas users of Gluster 3.10 can stay on that Long-Term-Maintenance release for an other six months. Users of Gluster 3.8 will need to manually upgrade by uninstalling the centos-release-gluster38 package, and replacing it with either the Gluster 3.12 or 3.10 version. Additional details about the upgrade process are linked in the announcement from the Gluster Community: http://lists.gluster.org/pipermail/announce/2017-September/000082.html We have a quickstart guide specifically built aro...

...of the now End-Of-Life Short-Term-Maintenance Gluster 3.11 will automatically get the update to Gluster 3.12, whereas users of Gluster 3.10 can stay on that Long-Term-Maintenance release for an other six months. Users of Gluster 3.8 will need to manually upgrade by uninstalling the centos-release-gluster38 package, and replacing it with either the Gluster 3.12 or 3.10 version. Additional details about the upgrade process are linked in the announcement from the Gluster Community: http://lists.gluster.org/pipermail/announce/2017-September/000082.html We have a quickstart guide specifically built aro...

...SUPPORT_PRODUCT_VERSION="7" [root at chvirnfstst01 etc]# [root at chvirnfstst01 etc]# rpm -qa | grep ganesha | sort nfs-ganesha-2.3.3-1.el7.x86_64 nfs-ganesha-gluster-2.3.3-1.el7.x86_64 [root at chvirnfstst01 etc]# [root at chvirnfstst01 etc]# rpm -qa | grep gluster | sort centos-release-gluster38-1.0-1.el7.centos.noarch glusterfs-3.8.15-2.el7.x86_64 glusterfs-api-3.8.15-2.el7.x86_64 glusterfs-client-xlators-3.8.15-2.el7.x86_64 glusterfs-libs-3.8.15-2.el7.x86_64 nfs-ganesha-gluster-2.3.3-1.el7.x86_64 [root at chvirnfstst01 etc]# [root at chvirnfstst01 etc]# cat /etc/ganesha/ganesha.conf EXPO...

...of the now End-Of-Life Short-Term-Maintenance Gluster 3.11 will automatically get the update to Gluster 3.12, whereas users of Gluster 3.10 can stay on that Long-Term-Maintenance release for an other six months. Users of Gluster 3.8 will need to manually upgrade by uninstalling the centos-release-gluster38 package, and replacing it with either the Gluster 3.12 or 3.10 version. Additional details about the upgrade process are linked in the announcement from the Gluster Community: http://lists.gluster.org/pipermail/announce/2017-September/000082.html We have a quickstart guide specifically built aro...

Hi, I've created a 2 node glusterFS test (Gluster 3.8). Without enabling NFS-Ganesha, when I try to mount from a client using glusterfs option - everything works. However, after enabling NFS-Ganesha, when I try to mount from a client using the glusterfs option (fuse), it fails with the following output (when using the log-file option): [2017-12-28 08:15:30.109110] I [MSGID: 100030]

...-7" CENTOS_MANTISBT_PROJECT_VERSION="7" REDHAT_SUPPORT_PRODUCT="centos" REDHAT_SUPPORT_PRODUCT_VERSION="7" [root at chvirnfsprd10 etc]# cat centos-release CentOS Linux release 7.3.1611 (Core) [root at chvirnfsprd10 ~]# rpm -qa | grep gluster | sort centos-release-gluster38-1.0-1.el7.centos.noarch glusterfs-3.8.15-2.el7.x86_64 glusterfs-api-3.8.15-2.el7.x86_64 glusterfs-cli-3.8.15-2.el7.x86_64 glusterfs-client-xlators-3.8.15-2.el7.x86_64 glusterfs-fuse-3.8.15-2.el7.x86_64 glusterfs-ganesha-3.8.15-2.el7.x86_64 glusterfs-libs-3.8.15-2.el7.x86_64 glusterfs-resource-agent...

...of the now End-Of-Life Short-Term-Maintenance Gluster 3.11 will automatically get the update to Gluster 3.12, whereas users of Gluster 3.10 can stay on that Long-Term-Maintenance release for an other six months. Users of Gluster 3.8 will need to manually upgrade by uninstalling the centos-release-gluster38 package, and replacing it with either the Gluster 3.12 or 3.10 version. Additional details about the upgrade process are linked in the announcement from the Gluster Community: http://lists.gluster.org/pipermail/announce/2017-September/000082.html We have a quickstart guide specifically built aro...

Marcus, Please paste the name-version-release of the primary glusterfs package on your system. If possible, also describe the typical workload that happens at the mount via the user application. On Tue, Jan 23, 2018 at 7:43 PM, Marcus Peders?n <marcus.pedersen at slu.se> wrote: > Hi all, > I have problem pin pointing an error, that users of > my system experience processes that

Hi all, I have problem pin pointing an error, that users of my system experience processes that crash. The thing that have changed since the craches started is that I added a gluster cluster. Of cause the users start to attack my gluster cluster. I started looking at logs, starting from the client side. I just need help to understand how to read it in the right way. I can see that every ten