Yes, ganesha Daemon doesn't use idmapd Daemon. In fact, some distros start
knfsd when you start idmapd Daemon so it is better not to start idmapd at
all.
On Tue, 16 Oct 2018, 5:26 pm Jiffin Tony Thottan,
wrote:
> CCing ganesha list as well
>
> On Monday 15 October 2018 07:44 PM, Renaud Fortier w
then wait for the upcall thread.
Regards, Malahal.
PS: GPFS has only one upcall thread for the entire file system image
(not for each export).
Alessandro De Salvo [alessandro.desa...@roma1.infn.it] wrote:
> Hi Malahal,
>
> > Il giorno 17/giu/2015, alle ore 19:51, Malahal Naineni
&g
Alessandro De Salvo [alessandro.desa...@roma1.infn.it] wrote:
> What’s more worrying is the problem with the dbus. Issuing a DisplayExport
> before the RemoveExport apparently fixes the problem, so something like this
> always works:
>
> # dbus-send --print-reply --system --dest=org.ganesha.nfsd
I have no knowledge of dbus-send.sh, is it GLUSTER fsal specific? I
don't see it in ganesha source code at all. I use ganesha_mgr command to
show/delete/remove exports. Can you try it and see if that works?
"ganesha_mgr remove_export 2" should be the correct call in your case.
Regards, Malahal.
Thank you Niels for your time to chase the issue. It is important to
have working files as people try, and "move on" if things don't work.
Not everyone is as persistent as Alessandro!
Regards, Malahal.
Niels de Vos [nde...@redhat.com] wrote:
> On Mon, Jun 15, 2015 at 06:50:2
Kaleb Keithley [kkeit...@redhat.com] wrote:
> But note that nfs-ganesha in EPEL[67] is built with a) glusterfs-api-3.6.x
> from Red Hat's "downstream" glusterfs, and b) the "bundled" static version of
> ntirpc, not the shared lib in the stand-along package above. If you're trying
> to use these
Alessandro De Salvo [alessandro.desa...@roma1.infn.it] wrote:
> OK, I think we are now closer to the end of the story.
> Recompiling with your instructions, and slightly changing the release name to
> match the convention in epel, the new RPMS produce something working!
> So it means essentially t
Alessandro De Salvo [alessandro.desa...@roma1.infn.it] wrote:
> Hi Malahal,
>
> --- nfs-ganesha.orig/src/nfs-ganesha.spec-in.cmake 2015-06-16
> 00:11:31.477442950 +0200
> +++ nfs-ganesha/src/nfs-ganesha.spec-in.cmake 2015-06-15 22:11:57.068726917
> +0200
> @@ -72,13 +72,13 @@
> @BCOND_GU
t;
> > Il giorno 15/giu/2015, alle ore 18:47, Malahal Naineni
> > ha scritto:
> >
> > We do run ganesha on RHEL7.0 (same as CentOS7.0), and I don't think 7.1
> > would be much different. We do run GPFS FSAL only (no VFS_FSAL).
> >
> > Regards, Malah
gt; > Wqe_LFlag_SyncDone)) and never exit from there.
> > I do not know if it's normal or not as I should read better the code.
> > Cheers,
> >
> > Alessandro
> >
> > On Fri, 2015-06-12 at 09:35 +0200, Alessandro De Salvo wrote:
> > > Hi M
rocess
> while I was executing the hanging showmount
> (ganesha-20150611.gstack.gz).
> Thanks,
>
> Alessandro
>
>
>
> On Thu, 2015-06-11 at 11:37 -0500, Malahal Naineni wrote:
> > Soumya Koduri [skod...@redhat.com] wrote:
> > > CCin ganesha-dev
Soumya Koduri [skod...@redhat.com] wrote:
> CCin ganesha-devel to get more inputs.
>
> In case of ipv6 enabled, only v6 interfaces are used by NFS-Ganesha.
I am not a network expert but I have seen IPv4 traffic over IPv6
interface while fixing few things before. This may be normal.
> commit - gi
12 matches
Mail list logo
