similar to: CEBA-2018:2444 CentOS 7 glusterfs BugFix Update

Hi, I have a KVM server running on Centos 7.5. [root at kvm2 ~]# cat /etc/redhat-release CentOS Linux release 7.5.1804 (Core) Qemu packages are from Centos repository. [root at kvm2 ~]# rpm -qa|grep qemu libvirt-daemon-driver-qemu-3.9.0-14.el7_5.7.x86_64 qemu-img-1.5.3-156.el7_5.5.x86_64 qemu-kvm-common-1.5.3-156.el7_5.5.x86_64 ipxe-roms-qemu-20170123-1.git4e85b27.el7_4.1.noarch

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

+gluster-users Another guideline we can provide is to disable all performance xlators for workloads requiring strict metadata consistency (even for non gluster-block usecases like native fuse mount etc). Note that we might still can have few perf xlators turned on. But, that will require some experimentation. The safest and easiest would be to turn off following xlators: * performance.read-ahead

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]

Hi Team, I am trying to setup a samba CTDB cluster to export gluster volme as samba share. While CTDB cluster works well, I ran into an issue with creating subdirectories and also creating files/directories within subdictories when accessing the share from both linux and windows servers. Setup details : We have a three node cluster with nodes snode1, snode2 and snode3. I have a gluster

I am trying to install glusterfs on a Linux machine. glusterfs version 3.3.2 *uname -orm* *GNU/Linux 2.6.22-6.4.3-amd64-2527508 x86_64* * * Ran* **./configure --prefix=mytempdir* * * No errors reported here. When I ran make, get this error. Any help appreciated. I am a newbie. Thanks, CR * make --no-print-directory --quiet all-recursive Making all in argp-standalone Making all in . Making all

Hi Team, I am trying to setup a samba CTDB cluster to export gluster volme as samba share. While CTDB cluster works well, I ran into an issue with creating subdirectories and also creating files/directories within subdictories when accessing the share from both linux and windows servers. Setup details : We have a three node cluster with nodes snode1, snode2 and snode3. I have a

Hi all: I saw the thread "Netboot / PXE-Boot from glusterfs?" in the online list archives and decided to subscribe to the mailing-list and share some notes I have. Sorry for not being able to thread my reply in. Anyway, I have recently added experimental support for GlusterFS to Perceus, which is a provisioning system which supports stateful (with disk) and stateless (diskless)

CentOS Errata and BugFix Advisory 2016:C001 Upstream details at : https://bugs.centos.org/view.php?id=10538 The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) x86_64: 96963d839797a7601ef6a4922c94e7ef82b42fcb70533f9a31c43adceee2fb19 glusterfs-3.7.1-16.0.1.el7.centos.x86_64.rpm

Hi All, anyone had the same experience? Could you provide me some information about this error? It happens only on GlusterFS file system. Thank you, Mauro > Il giorno 20 dic 2017, alle ore 16:57, Mauro Tridici <mauro.tridici at cmcc.it> ha scritto: > > > Dear Users, > > I?m experiencing a random problem ( "file changed as we read it? error) during tar files

On 02/19/2018 10:24 AM, TomK wrote: > On 2/19/2018 2:39 AM, TomK wrote: > + gluster users as well.? Just read another post on the mailing lists > about a similar ask from Nov which didn't really have a clear answer. That's funny because I've answered questions like this several times. Gluster+Ganesha+Pacemaker-based HA is available up to GlusterFS 3.10.x. If you need HA,

Dear Users, I?m experiencing a random problem ( "file changed as we read it? error) during tar files creation on a distributed dispersed Gluster file system. The tar files seem to be created correctly, but I can see a lot of message similar to the following ones: tar: ./year1990/lffd1990050706p.nc.gz: file changed as we read it tar: ./year1990/lffd1990052106p.nc.gz: file changed as we read

On 2/19/2018 2:39 AM, TomK wrote: + gluster users as well. Just read another post on the mailing lists about a similar ask from Nov which didn't really have a clear answer. Perhaps there's a way to get NFSv4 work with GlusterFS without NFS Ganesha then? Cheers, Tom > Hey All, > > I've setup GlusterFS on two virtuals and enabled NFS Ganesha on each > node.? ATM the

I cannot touch or cp files to glusterfs filesystem with bdb backend. orion31 is glusterfs server, orion28 is glusterfs client. ------------------------------------------------------------------------------------------- [root at orion28 ~]# mount -t glusterfs /etc/glusterfs/glusterfs-bdb.vol /mnt [root at orion28 ~]# touch /mnt/a touch: cannot touch `/mnt/a': No such file or directory [root

[From http://blog.nixpanic.net/2017/07/glusterfs-3814-is-here.html and also on https://planet.gluster.org/] GlusterFS 3.8.14 is here, 3.8 even closer to End-Of-Life The 10th of the month has passed again, that means a 3.8.x update can't be far out. So, here it is, we're announcing the [9]availability of glusterfs-3.8.14. Note that this is one of the last updates in the 3.8

Hi Nithya, thank you very much for your support and sorry for the late. Below you can find the output of ?gluster volume info tier2? command and the gluster software stack version: gluster volume info Volume Name: tier2 Type: Distributed-Disperse Volume ID: a28d88c5-3295-4e35-98d4-210b3af9358c Status: Started Snapshot Count: 0 Number of Bricks: 6 x (4 + 2) = 36 Transport-type: tcp Bricks:

Hi Ravi, thank you very much for your support and explanation. If I understand, the ctime xlator feature is not present in the current gluster package but it will be in the future release, right? Thank you again, Mauro > Il giorno 02 gen 2018, alle ore 12:53, Ravishankar N <ravishankar at redhat.com> ha scritto: > > I think it is safe to ignore it. The problem exists due to the

I think it is safe to ignore it. The problem exists? due to the minor difference in file time stamps in the backend bricks of the same sub volume (for a given file) and during the course of tar, the timestamp can be served from different bricks causing it to complain . The ctime xlator[1] feature once ready should fix this issue by storing time stamps as xattrs on the bricks. i.e. all bricks

On 02/19/2018 11:37 AM, TomK wrote: > On 2/19/2018 10:55 AM, Kaleb S. KEITHLEY wrote: > Yep, I noticed a couple of pages including this for 'storhaug > configuration' off google.? Adding 'mailing list' to the search didn't > help alot: > > https://sourceforge.net/p/nfs-ganesha/mailman/message/35929089/ > >

Spam detection software, running on the system "mail.montanhydraulik.com", has identified this incoming email as possible spam. The original message has been attached to this so you can view it (if it isn't spam) or label similar future email. If you have any questions, see postmaster for details. Content preview: -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1