Using a Path of "/" shouldn't be the problem. Also, that doesn't explain why
the FSAL_VFS export isn't working either.

Frank

> -----Original Message-----
> From: Soumya Koduri [mailto:skod...@redhat.com]
> Sent: Friday, April 24, 2015 11:18 AM
> To: Timofey Titovets; philippe.den...@cea.fr
> Cc: nfs-ganesha-supp...@lists.sourceforge.net; nfs-ganesha-
> de...@lists.sourceforge.net
> Subject: Re: [Nfs-ganesha-devel] [Nfs-ganesha-support] Troubles with
> configuration
> 
>  >>> # mount -o nfsvers=3 172.20.252.12:/ /mnt -v
> 
> Looks like you are trying to mount "/" via v3. "/" is reserved for psuedo
file
> system which can be mounted only via "v4" AFAIK.
> 
> Please try using a different path other than '/' in your Export Block.
> 
> 
>  >>> EXPORT
>  >>> {
>  >>>           # Export Id (mandatory, each EXPORT must have a unique
> Export_Id)
>  >>>           Export_Id = 77;
>  >>>           # Exported path (mandatory)
>  >>>           Path = /storage;
>  >>>           # Pseudo Path (required for NFS v4)
>  >>>           Pseudo = /cephfs;
>  >>>           Access_Type = RW;
>  >>>           NFS_Protocols = 3;
>  >>>           FSAL {
>  >>>                   Name = VFS;
>  >>>           }
>  >>> }
> In this case, the path exported is
> "/storage" for v3 and
> "/cephfs" for v4
> 
>  >>> Or
>  >>> EXPORT
>  >>> {
>  >>>          Export_ID = 1;
>  >>>          Path = "/";
>  >>>          Pseudo = "/cephfs";
>  >>>          Access_Type = RW;
>  >>>          NFS_Protocols = 3;
>  >>>          Transport_Protocols = TCP;
>  >>>          FSAL {
>  >>>                  Name = CEPH;
>  >>>          }
>  >>> }
> As I said, '/' is reserved, you may need to use different Path here.
> 
> Thanks,
> Soumya
> 
> On 04/24/2015 02:14 PM, Timofey Titovets wrote:
> > showmount -e 172.20.252.12
> > Export list for 172.20.252.12:
> > / (everyone)
> >
> > 2015-04-24 10:33 GMT+03:00 DENIEL Philippe <philippe.den...@cea.fr>:
> >> Hi,
> >>
> >> what does " showmount -e 172.20.252.12 " say ? This way, you'll see
> >> if Ganesha was capable of building the export entries.
> >> My knowledge of CEPH is weak, so I forward your question to
> >> nfs-gamesha-devel. In particular, I do not know if:
> >>       - CEPH support open_by_handle_at() syscall
> >>       - FSAL_CEPH can work on a "regular" CEPH distribution. I
> >> remember that Matt and Adam made some changes to CEPH to ease
> pNFS
> >> implementation, and I do not know if those commits went upstream.
> >> They will tell us about this.
> >>
> >>       Regards
> >>
> >>           Philippe
> >>
> >> On 04/24/15 09:18, Timofey Titovets wrote:
> >>> Good time of day, I've try to setup nfs-ganesha server on Ubuntu
> >>> 15.04 Builded by last source from master tree.
> >>>
> >>> 1. Can't be mounted with nfsv3
> >>> Config:
> >>> EXPORT
> >>> {
> >>>           # Export Id (mandatory, each EXPORT must have a unique
> Export_Id)
> >>>           Export_Id = 77;
> >>>           # Exported path (mandatory)
> >>>           Path = /storage;
> >>>           # Pseudo Path (required for NFS v4)
> >>>           Pseudo = /cephfs;
> >>>           Access_Type = RW;
> >>>           NFS_Protocols = 3;
> >>>           FSAL {
> >>>                   Name = VFS;
> >>>           }
> >>> }
> >>> Or
> >>> EXPORT
> >>> {
> >>>          Export_ID = 1;
> >>>          Path = "/";
> >>>          Pseudo = "/cephfs";
> >>>          Access_Type = RW;
> >>>          NFS_Protocols = 3;
> >>>          Transport_Protocols = TCP;
> >>>          FSAL {
> >>>                  Name = CEPH;
> >>>          }
> >>> }
> >>>
> >>> On client I've get:
> >>> # mount -o nfsvers=3 172.20.252.12:/ /mnt -v
> >>> mount.nfs: timeout set for Fri Apr 24 09:47:50 2015
> >>> mount.nfs: trying text-based options 'nfsvers=3,addr=172.20.252.12'
> >>> mount.nfs: prog 100003, trying vers=3, prot=6
> >>> mount.nfs: trying 172.20.252.12 prog 100003 vers 3 prot TCP port
> >>> 2049
> >>> mount.nfs: prog 100005, trying vers=3, prot=17
> >>> mount.nfs: trying 172.20.252.12 prog 100005 vers 3 prot UDP port
> >>> 40321
> >>> mount.nfs: mount(2): Permission denied
> >>> mount.nfs: access denied by server while mounting 172.20.252.12:/
> >>>
> >>> What's did I wrong? %)
> >>>
> >>
> >>
> >> ---------------------------------------------------------------------
> >> --------- One dashboard for servers and applications across
> >> Physical-Virtual-Cloud Widest out-of-the-box monitoring support with
> >> 50+ applications Performance metrics, stats and reports that give you
> >> Actionable Insights Deep dive visibility with transaction tracing
> >> using APM Insight.
> >> http://ad.doubleclick.net/ddm/clk/290420510;117567292;y
> >> _______________________________________________
> >> Nfs-ganesha-support mailing list
> >> nfs-ganesha-supp...@lists.sourceforge.net
> >> https://lists.sourceforge.net/lists/listinfo/nfs-ganesha-support
> >
> >
> >
> 
>
----------------------------------------------------------------------------
--
> One dashboard for servers and applications across Physical-Virtual-Cloud
> Widest out-of-the-box monitoring support with 50+ applications
> Performance metrics, stats and reports that give you Actionable Insights
> Deep dive visibility with transaction tracing using APM Insight.
> http://ad.doubleclick.net/ddm/clk/290420510;117567292;y
> _______________________________________________
> Nfs-ganesha-devel mailing list
> Nfs-ganesha-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/nfs-ganesha-devel


------------------------------------------------------------------------------
One dashboard for servers and applications across Physical-Virtual-Cloud 
Widest out-of-the-box monitoring support with 50+ applications
Performance metrics, stats and reports that give you Actionable Insights
Deep dive visibility with transaction tracing using APM Insight.
http://ad.doubleclick.net/ddm/clk/290420510;117567292;y
_______________________________________________
Nfs-ganesha-devel mailing list
Nfs-ganesha-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs-ganesha-devel

Reply via email to