similar to: Bug 1374166 or similar

Hi, yes, I mounted the Gluster volume and deleted the files from the volume not the brick mount -t glusterfs hostname:volname /mnt cd /mnt/some/directory rm -rf * restart of nfs-ganesha is planned for tomorrow. I'll keep you posted BTW: nfs-ganesha is running on a separate server in standalone configuration Best Regards Bernhard 2017-07-14 10:43 GMT+02:00 Jiffin Tony Thottan <jthottan

On 16/07/17 20:11, Bernhard D?bi wrote: > Hi, > > both Gluster servers were rebooted and now the unlink directory is clean. Following should have happened, If delete operation is performed gluster keeps file in .unlink directory if it has open fd. In this case since lazy umount is performed, ganesha server may still keep the fd's open by that client so gluster keeps the unlink

Hi, both Gluster servers were rebooted and now the unlink directory is clean. Best Regards Bernhard 2017-07-14 12:43 GMT+02:00 Bernhard D?bi <1linuxengineer at gmail.com>: > Hi, > > yes, I mounted the Gluster volume and deleted the files from the > volume not the brick > > mount -t glusterfs hostname:volname /mnt > cd /mnt/some/directory > rm -rf * > >

On 14/07/17 13:06, Bernhard D?bi wrote: > Hello everybody, > > I'm in a similar situation as described in > https://bugzilla.redhat.com/show_bug.cgi?id=1374166 The issue got fixed by https://review.gluster.org/#/c/14820 and is already available in 3.8 branch > > I have a gluster volume exported through ganesha. we had some problems > on the gluster server and the NFS

Hi Jiffin, I looked at the document, and there are 2 things: 1. In Gluster 3.8 it seems you don't need to do that at all, it creates this automatically, so why not in 3.10? 2. The step by step guide, in the last item, doesn't say where exactly do I need to create the nfs-ganesha directory. The copy/paste seems irrelevant as enabling nfs-ganesha creates automatically the ganesha.conf and

Thanks Jiffin, Btw, the nfs-ganesha part in the release notes is having a wrong header, so it's not highlighted. One thing that it is still mystery to me: gluster 3.8.x does all what the release notes of 3.9 says - automatically. Any chance that someone could port it to 3.9? Thanks for the links On Wed, Dec 6, 2017 at 7:28 AM, Jiffin Tony Thottan <jthottan at redhat.com> wrote: >

Hi, On Monday 04 December 2017 07:43 PM, Hetz Ben Hamo wrote: > Hi Jiffin, > > I looked at the document, and there are 2 things: > > 1. In Gluster 3.8 it seems you don't need to do that at all, it > creates this automatically, so why not in 3.10? Kindly please refer the mail[1] and release note [2] for glusterfs-3.9 Regards, Jiffin [1]

On Saturday 02 December 2017 07:00 PM, Hetz Ben Hamo wrote: > HI, > > I'm using CentOS 7.4 with Gluster 3.10.7 and Ganesha NFS 2.4.5. > > I'm trying to create a very simple 2 nodes cluster to be used with > NFS-ganesha. I've created the bricks and the volume. Here's the output: > > # gluster volume info > > Volume Name: cluster-demo > Type:

HI, I'm using CentOS 7.4 with Gluster 3.10.7 and Ganesha NFS 2.4.5. I'm trying to create a very simple 2 nodes cluster to be used with NFS-ganesha. I've created the bricks and the volume. Here's the output: # gluster volume info Volume Name: cluster-demo Type: Replicate Volume ID: 9c835a8e-c0ec-494c-a73b-cca9d77871c5 Status: Started Snapshot Count: 0 Number of Bricks: 1 x 2 = 2

----- Original Message ----- From: "hvjunk" <hvjunk at gmail.com> To: "Adam Ru" <ad.ruckel at gmail.com> Cc: gluster-users at gluster.org Sent: Monday, June 5, 2017 9:29:03 PM Subject: Re: [Gluster-users] Gluster and NFS-Ganesha - cluster is down after reboot Sorry, got sidetracked with invoicing etc.

Hi, after upgrading to 3.10.9 I'm seing ganesha.nfsd segfaulting all the time: [12407.918249] ganesha.nfsd[38104]: segfault at 0 ip 00007f872425fb00 sp 00007f867cefe5d0 error 4 in libglusterfs.so.0.0.1[7f8724223000+f1000] [12693.119259] ganesha.nfsd[3610]: segfault at 0 ip 00007f716d8f5b00 sp 00007f71367e15d0 error 4 in libglusterfs.so.0.0.1[7f716d8b9000+f1000] [14531.582667]

On 08/17/2016 09:56 AM, Kaleb S. KEITHLEY wrote: > I propose to present on one or more of the following topics: > > * NFS-Ganesha Architecture, Roadmap, and Status,Jiffin Thotton copresenter. > * Architecture of the High Availability Solution for Ganesha and Samba > - detailed walk through and demo of current implementation > - difference between the current and storhaug

I propose to present on one or more of the following topics: * NFS-Ganesha Architecture, Roadmap, and Status * Architecture of the High Availability Solution for Ganesha and Samba - detailed walk through and demo of current implementation - difference between the current and storhaug implementations * High Level Overview of autoconf/automake/libtool configuration (I gave a presentation in BLR

Hi Frank, It will be very easy to debug if u have core file with u. It looks like crash is coming from gfapi stack. If there is core file can u please share bt of the core file. Regards, Jiffin On Thursday 18 January 2018 11:18 PM, Frank Wall wrote: > Hi, > > after upgrading to 3.10.9 I'm seing ganesha.nfsd segfaulting all the time: > > [12407.918249] ganesha.nfsd[38104]:

Hi, It's time to prepare the 3.12.8 release, which falls on the 10th of each month, and hence would be 12-04-2018 this time around. This mail is to call out the following, 1) Are there any pending *blocker* bugs that need to be tracked for 3.12.7? If so mark them against the provided tracker [1] as blockers for the release, or at the very least post them as a response to this mail 2)

Hello! I am attempting to setup a Gluster install using Ganesha for NFS using the guide found here http://blog.gluster.org/2015/10/linux-scale-out-nfsv4-using-nfs-ganesha-and-glusterfs-one-step-at-a-time/ The Gluster portion is working fine, however when I try to setup Ganesha I have a problem. The guide says to run 'gluster nfs-ganesha enable' however when I do, I get the following

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

Hey Niels, Installed 3.12.4 from centos-gluster312-test on my dev ovirt hyper converged cluster. Everything looks good and is working as expected for storage, migration, & healing. Need any specifics? -D > From: Jiffin Tony Thottan <jthottan at redhat.com> > Subject: [Gluster-users] Announcing Glusterfs release 3.12.4 (Long Term Maintenance) > Date: December 19, 2017 at

Mabi, It looks like one of the patches is not a straight forward cherry-pick to the 3.12 branch. Even though the conflict might be easy to resolve, I don't think it is a good idea to hurry it for tomorrow. We will definitely have it ready by the next minor release (or if by chance the release is delayed and the back port is reviewed and merged before that). Hope that is acceptable.

After 3.10 you'd need to use storhaug.... Which.... doesn't work (yet). You need to use 3.10 for now. On 07/06/2017 12:53 PM, Anthony Valentine wrote: > I'm running this on CentOS 7.3 > > [root at glustertest1 ~]# cat /etc/redhat-release > CentOS Linux release 7.3.1611 (Core) > > > Here are the software versions I have installed. > > [root at