Re: [Gluster-devel] NFS Ganesha (Storage SIG) node fails to boot after fencing

Hi Kaleb, I have opened https://github.com/gluster/glusterfs/issues/1830 . I was not sure where to open it ,as I saw that 'nfs-ganesha-selinux-3.3-2.el8.noarch' rpm provided by the storage SIG repo  'centos-nfs-ganesha3'. I'm adding the Gluster devel here,as the current version of NFS Ganesha

Re: [Gluster-devel] NFS Ganesha fails to export a volume

Hm... In such case , we got only 1 real problem left -> ocf:heartbeat:portblock supports only IPTABLES. In my EL8 tests , NFS-Ganesha works if firewalld is disabled and I install iptables & iptables-services, yet this is highly unrecommended by Red Hat. I got a feature request opened 

Re: [Gluster-devel] NFS Ganesha fails to export a volume

Thanks for bringing this to our attention @Strahil [1] and [2] were discretely worked handling different issues at the same span of time. Merging [2] was to be done before [1], which was done otherwise. [1] https://review.gluster.org/#/c/glusterfs/+/23039/ [2]

Re: [Gluster-devel] NFS Ganesha fails to export a volume

Nope, it's a deeper s**t. I had to edit the ".spec.in" file so it has Source0 point to local tar.gz. The I edit the requires in both ".spec" & ".spec.in" and also I had to remove an obsolete stanza in the glusterfs section. In the end, I got the source - extracted, copied the spec & spec.in ,

Re: [Gluster-devel] NFS Ganesha fails to export a volume

On 18/11/20 12:17 pm, Strahil Nikolov wrote: Nope, it's a deeper s**t. I had to edit the ".spec.in" file so it has Source0 point to local tar.gz. The I edit the requires in both ".spec" & ".spec.in" and also I had to remove an obsolete stanza in the glusterfs section. In the end, I got the

Re: [Gluster-devel] NFS Ganesha fails to export a volume

Hi Ravi, Any idea how to make the glusterfs-ganesha.x86_64 require resource-agents >= 4.1.0 (instead of 4.2.0) ? I 've replaced every occurance I found and still it tries to grab resource-agents 4.2 (which is not available on EL8). Best Regards, Strahil Nikolov В понеделник, 16 ноември

Re: [Gluster-devel] NFS Ganesha fails to export a volume

Hi Strahil, I would have imagined editing the 'Requires' section in glusterfs.spec.in would have sufficed. Do you need rpms though? A source install is not enough? Regards, Ravi On 17/11/20 5:32 pm, Strahil Nikolov wrote: Hi Ravi, Any idea how to make the glusterfs-ganesha.x86_64 require

Re: [Gluster-devel] NFS Ganesha fails to export a volume

I was thinking about an automatic way for testing ... I will use my notes to rebuild a fresh cluster on EL8 and I will give feedback if the patch is fixing it . Thanks all for the assitance. Best Regards, Strahil Nikolov В понеделник, 16 ноември 2020 г., 13:15:54 Гринуич+2, Ravishankar

Re: [Gluster-devel] NFS Ganesha fails to export a volume

I can try to help with the testing (I'm quite new to that). Can someone share documentation of that process ? yet we have another problem -> ganesha is deployed with ocf:heartbeat:portblock which supports only IPTABLES, while EL8 uses NFTABLES ... Best Regards, Strahil Nikolov В

Re: [Gluster-devel] NFS Ganesha fails to export a volume

On Mon, 16 Nov 2020 at 16:45, Ravishankar N wrote: > I am surprised too that it wasn't caught earlier. > There have been sporadic requests around maintaining v3 but of late I haven't heard a lot around NFS-Ganesha. I am not surprised to learn that there is tests lacking - this is unlikely to be

Re: [Gluster-devel] NFS Ganesha fails to export a volume

I am surprised too that it wasn't caught earlier. Steps: 1. Clone the gluster repo 2. Compile  the source https://docs.gluster.org/en/latest/Developer-guide/Building-GlusterFS/ 3. Make the changes (in a different branch if you prefer), compile again and install 4.  Test it out:

Re: [Gluster-devel] NFS Ganesha fails to export a volume

On Mon, Nov 16, 2020 at 10:26 AM Ravishankar N wrote: > > On 15/11/20 8:24 pm, Strahil Nikolov wrote: > > Hello All, > > > > did anyone get a chance to look at > https://github.com/gluster/glusterfs/issues/1778 ? > > A look at > >

Re: [Gluster-devel] NFS Ganesha fails to export a volume

On 15/11/20 8:24 pm, Strahil Nikolov wrote: Hello All, did anyone get a chance to look at  https://github.com/gluster/glusterfs/issues/1778 ? A look at https://review.gluster.org/#/c/glusterfs/+/23648/4/xlators/mgmt/glusterd/src/glusterd-op-sm.c@1117 seems to indicate this could be due to

[Gluster-devel] NFS Ganesha fails to export a volume

Hello All, did anyone get a chance to look at  https://github.com/gluster/glusterfs/issues/1778 ? It's really strange that NFS Ganesha has ever passed the tests. How do we test NFS Ganesha exporting ? Best Regards, Strahil Nikolov ___ Community

[Gluster-devel] NFS Ganesha on EL8 needs redesign

Hello All, I have been playing around with Ganesha on CentOS 8 and I have noticed some issues so far. Could you assist me in pinpointing the correct location for tracking the issues: - 'gluster nfs-ganesha enable' builds pacemaker groups that use 'ocf:heartbeat:portblock', but that resource is

Re: [Gluster-devel] [NFS-Ganesha-Devel] Re: Problems about cache virtual glusterfs ACLs for ganesha in md-cache

On 10/12/18 5:55 PM, Kinglong Mee wrote: On 2018/10/12 14:34, Soumya Koduri wrote:> On 10/12/18 7:22 AM, Kinglong Mee wrote: On 2018/10/11 19:09, Soumya Koduri wrote: NFS-Ganesha's md-cache layer already does extensive caching of attributes and ACLs of each file looked upon. Do you see any

Re: [Gluster-devel] [NFS-Ganesha-Devel] Re: Problems about cache virtual glusterfs ACLs for ganesha in md-cache

On 2018/10/12 14:34, Soumya Koduri wrote:> On 10/12/18 7:22 AM, Kinglong Mee wrote: >> On 2018/10/11 19:09, Soumya Koduri wrote: >>> NFS-Ganesha's md-cache layer already does extensive caching of attributes >>> and ACLs of each file looked upon. Do you see any additional benefit with >>>

Re: [Gluster-devel] [NFS-Ganesha-Devel] Re: Problems about cache virtual glusterfs ACLs for ganesha in md-cache

On 10/12/18 12:04 PM, Soumya Koduri wrote: 1. Cache it separately as posix ACLs (a new option maybe "cache-glusterfs-acl" is added); And make sure _posix_xattr_get_set fills them when lookup requests. I am not sure if posix layer can handle it. Virtual xattrs are in-memory and not

Re: [Gluster-devel] [NFS-Ganesha-Devel] Re: Problems about cache virtual glusterfs ACLs for ganesha in md-cache

On 10/12/18 7:22 AM, Kinglong Mee wrote: On 2018/10/11 19:09, Soumya Koduri wrote: NFS-Ganesha's md-cache layer already does extensive caching of attributes and ACLs of each file looked upon. Do you see any additional benefit with turning on gluster md-cache as well?  More replies inline..

Re: [Gluster-devel] [Nfs-ganesha-devel] nfsv3 client writing file gets Invalid argument on glusterfs with quota on

On Thu, Mar 8, 2018 at 10:17 PM Daniel Gryniewicz wrote: > On 03/07/2018 10:21 PM, Kinglong Mee wrote: > > On 2018/3/7 21:10, Daniel Gryniewicz wrote: > >> On 03/06/2018 10:10 PM, Kinglong Mee wrote: > >>> On 2018/3/7 10:59, Kinglong Mee wrote: > When using nfsv3 on

Re: [Gluster-devel] [Nfs-ganesha-devel] nfsv3 client writing file gets Invalid argument on glusterfs with quota on

On 03/06/2018 10:10 PM, Kinglong Mee wrote: On 2018/3/7 10:59, Kinglong Mee wrote: When using nfsv3 on glusterfs-3.13.1-1.el7.x86_64 and nfs-ganesha-2.6.0-0.2rc3.el7.centos.x86_64, I gets strange "Invalid argument" when writing file. 1. With quota disabled; nfs client mount nfs-ganesha share,

Re: [Gluster-devel] [Nfs-ganesha-devel] Device or resource busy when runltp cleanup test-files

Sorry for the late reply. On 4/16/2017 22:31, Vijay Bellur wrote: > > > On Wed, Apr 12, 2017 at 10:37 PM, Kinglong Mee > wrote: > > Yes, this one is silly rename, > > >>> rm: cannot remove >

Re: [Gluster-devel] [Nfs-ganesha-devel] Device or resource busy when runltp cleanup test-files

On Wed, Apr 12, 2017 at 10:37 PM, Kinglong Mee wrote: > Yes, this one is silly rename, > > >>> rm: cannot remove ‘/mnt/nfs/ltp-JEYAuky2dz/.nfsaa46457a6a72f8ea14f5’: > Device or resource busy > > But, the other one isn't client's silly rename, > > rm: cannot

Re: [Gluster-devel] [Nfs-ganesha-devel] Device or resource busy when runltp cleanup test-files

Sorry, I missed your note below. This is definitely due to an NFS client's silly rename. All ".nfs" are due to silly rename implementation in NFS client. You might want to read about it. >> rm: cannot remove ‘/mnt/nfs/ltp-JEYAuky2dz/.nfsaa46457a6a72f8ea14f5’: >> Device or resource busy On

Re: [Gluster-devel] [Nfs-ganesha-devel] Device or resource busy when runltp cleanup test-files

Yes, this one is silly rename, >>> rm: cannot remove ‘/mnt/nfs/ltp-JEYAuky2dz/.nfsaa46457a6a72f8ea14f5’: >>> Device or resource busy But, the other one isn't client's silly rename, rm: cannot remove ‘/mnt/nfs/ltp-JEYAuky2dz/rmderQsjV’: Directory not empty Also, the second

Re: [Gluster-devel] [Nfs-ganesha-devel] Device or resource busy when runltp cleanup test-files

What are the file names under the directory? What does "ls -la" show both at the client and at the server in that directory? On Thu, Apr 13, 2017 at 5:13 AM, Kinglong Mee wrote: > There are some files under "rmderQsjV" (that's not a silly rename dir) really > at underlying

Re: [Gluster-devel] [Nfs-ganesha-devel] Device or resource busy when runltp cleanup test-files

There are some files under "rmderQsjV" (that's not a silly rename dir) really at underlying filesystem, but the nfs client shows empty. Are there some problems in MDCACHE or cache timeouts? On 4/12/2017 22:48, Malahal Naineni wrote: > Could be due to NFS client silly rename. > > On Apr 12,

Re: [Gluster-devel] [Nfs-ganesha-devel] Device or resource busy when runltp cleanup test-files

Could be due to NFS client silly rename. On Apr 12, 2017 8:06 PM, "Kinglong Mee" wrote: > When I testing ganesha nfs bases on glusterfs, the runltp always warning > as, > > rm: cannot remove ‘/mnt/nfs/ltp-JEYAuky2dz/.nfsaa46457a6a72f8ea14f5’: > Device or resource busy

[Gluster-devel] NFS-Ganesha last week update

Brief update on progress we made on NFS-Ganesha In last week NFS-Ganesha with FSAL_GLUSTER was tested in Bakeathon- Boston 2016 and found issues in ACL, solaris client and pNFS. There were four different test environment used with default configuration, kerberos configured, ACLs enabled

Re: [Gluster-devel] [NFS-ganesha] unlink file remains in ./glusterfs/unlinks after delete file

FYI - "http://review.gluster.org/#/c/14840 " contains the fix for 3.7 branch. Thanks, Soumya On 07/01/2016 11:38 AM, Soumya Koduri wrote: Hi, On 06/30/2016 11:56 AM, 梁正和 wrote: Hi, I'm trying to export gluster-volume by nfs-ganesha. After create --> Some I/O --> delete file from nfs mount

Re: [Gluster-devel] [NFS-ganesha] unlink file remains in ./glusterfs/unlinks after delete file

Hi, On 06/30/2016 11:56 AM, 梁正和 wrote: Hi, I'm trying to export gluster-volume by nfs-ganesha. After create --> Some I/O --> delete file from nfs mount point. The file has been moved to ./glusterfs/unlinkls. There was an fd leak when a file is created using gfapi handleops (which

[Gluster-devel] [NFS-ganesha] unlink file remains in ./glusterfs/unlinks after delete file

Hi, I'm trying to export gluster-volume by nfs-ganesha. After create --> Some I/O --> delete file from nfs mount point. The file has been moved to ./glusterfs/unlinkls. Excepted result: no files in the unlink folder. Environment: single gluster server with nfs-ganesha version: 2.2.0-6

Re: [Gluster-devel] [Nfs-ganesha-devel] pNFS server for FreeBSD using GlusterFS

> > On 22/04/16 04:18, Rick Macklem wrote: > > > Jiffin Tony Thottan wrote: > > >> > > >> On 21/04/16 04:43, Rick Macklem wrote: > > >>> Hi, > > >>> > > >>> Just to let you know, I did find the email responses to my queries > > >>> some months ago helpful and I now have a pNFS server for FreeBSD >

[Gluster-devel] nfs/bug-904065.t fails test 22

Niels, snip Test 22: 81: EXPECT '4' count_lines $M0/rmtab not ok 22 Got 2 instead of 4 snip The above failure was observed with http://review.gluster.com/10445. For more details - http://build.gluster.org/job/rackspace-regression-2GB-triggered/11321/consoleFull How should I proceed with

[Gluster-devel] NFS

My NFS stopped working after upgrading to 3.6.3. When I do a gluster volume status homegfs_bkp, it shows as N/A and I cannot mount the volume using NFS instead of FUSE. Any suggestions for how to fix? [root@gfs01bkp glusterfs]# gluster volume status homegfs_bkp Status of volume: homegfs_bkp

Re: [Gluster-devel] NFS

On Fri, Jun 12, 2015 at 03:17:08PM +, David Robinson wrote: My NFS stopped working after upgrading to 3.6.3. When I do a gluster volume status homegfs_bkp, it shows as N/A and I cannot mount the volume using NFS instead of FUSE. Any suggestions for how to fix? [root@gfs01bkp

Re: [Gluster-devel] NFS-Ganesha demo link

On Mon, May 11, 2015 at 08:27:50AM -0400, Meghana Madhusudhan wrote: Hi everyone, Please find the link to the session Highly available NFS-Ganesha server with GlusterFS This session is aimed to provide an overview of the active/active NFS-Ganesha server using pacemaker/corosync. A

Re: [Gluster-devel] NFS-Ganesha features demo

-gane...@redhat.com Sent: Wednesday, April 29, 2015 8:50:20 PM Subject: Re: [Gluster-devel] NFS-Ganesha features demo Hi, Looks like the URL wasn't complete , sorry about that. Please find the correct link here, https://plus.google.com/events/c9omal6366f2cfkcd0iuee5ta1o Thanks Meghana

Re: [Gluster-devel] NFS-Ganesha features demo

On 04/30/2015 02:21 PM, Meghana Madhusudhan wrote: Hi all, The NFS-Ganesha features demo is scheduled from 7:00 PM to 8:00 PM tonight. 7:00 - 8:00 PM Indian Standard Time, 13:30 - 14:30 in UTC etc. Thanks, Vijay ___ Gluster-devel mailing list

[Gluster-devel] NFS-Ganesha features demo

Hi everyone, We've scheduled a Hangout session tomorrow about NFS-Ganesha features in GlusterFS 3.7. This session would include a preview of the features and a quick demo of active/active HA implementation. Please plan to join the Hangout session https://plus.google.com/events/c9omal636

[Gluster-devel] NFS-Ganesha features demo

Hi everyone, We've scheduled an Hangout session tomorrow about NFS-Ganesha features in GlusterFS 3.7. This session would include a preview of the features and a quick demo of active/active HA implementation. Please plan to join the Hangout session https://plus.google.com/events/c9omal636

Re: [Gluster-devel] NFS-Ganesha features demo

Hi, Looks like the URL wasn't complete , sorry about that. Please find the correct link here, https://plus.google.com/events/c9omal6366f2cfkcd0iuee5ta1o Thanks Meghana - Original Message - From: Meghana Madhusudhan mmadh...@redhat.com To: gluster-devel@gluster.org Cc:

Re: [Gluster-devel] NFS/glusterd bug? bug-918437-sh-mtime.t fails upstream

I have sent a patch to fix this - http://review.gluster.org/9851 This should address the test failure. - Original Message - tests/bugs/replicate/bug-918437-sh-mtime.t is failing upstream. It passes if I don't disable nfs: -TEST $CLI volume set $V0 nfs.disable on +#TEST $CLI volume

[Gluster-devel] NFS File handles change during upgrade from glusterfs version 3.4.2 to 3.5.3

Hello, After upgrading from 3.4.2 to 3.5.3, I noticed that all my NFS clients (mounted over tcp) on remote nodes turned stale. I investigated this and got the following recurrent logs from the NFS server: [2015-02-23 20:40:25.834071] W [nfs3-helpers.c:3401:nfs3_log_common_res] 0-nfs-nfsv3:

[Gluster-devel] NFS directory not empty log messages.

From what I can tell I incorrectly assumed that I was seeing a problem deleting directories as described in: https://bugzilla.redhat.com/show_bug.cgi?id=1121347#c4 This is definitely different than Anders is seeing in the duplicate entries email thread. Should I close my original issue and