5:51 a.m.
Hi all
this may already been answered (or commonly known) but I have a system where the standard
"mount -t nfs" will mount my export as NFS V4.1 but when trying the same
node/server with "mount -t nfs -o vers=3" the mount fails ....
Any pointers greatly appreciated ....
Regards, Torben
6:24 a.m.
post your /etc/ganesha/ganesha.conf file!
On Mon, Aug 15, 2022 at 6:51 AM <torben.klingpetersen(a)hpe.com> wrote:
Hi all
this may already been answered (or commonly known) but I have a system
where the standard "mount -t nfs" will mount my export as NFS V4.1 but when
trying the same node/server with "mount -t nfs -o vers=3" the mount fails
....
Any pointers greatly appreciated ....
Regards, Torben
_______________________________________________
Support mailing list -- support(a)lists.nfs-ganesha.org
To unsubscribe send an email to support-leave(a)lists.nfs-ganesha.org
--
Kaleb
6:32 a.m.
As instructed:
/etc/ganesha/ganesha.conf file
##################################################
#
# EXPORT
# To function, all that is required is an EXPORT
# Define the absolute minimal export
#
###################################################
EXPORT
{
# Export Id (mandatory, each EXPORT must have a unique Export_Id)
Export_Id = 99;
# Exported path (mandatory)
Path = "/mnt/lustre";
# Pseudo Path (required for NFS v4)
Pseudo = "/mnt/lustre";
# Required for access (default is None)
# Could use CLIENT blocks instead
Access_Type = "RW" ;
Protocols = "3" , "4" ;
Squash = "no_root_squash" ;
Transport = "UDP", "TCP" ;
# Exporting FSAL
FSAL {
Name = VFS;
}
}
NFS_Core_Param {
#Nb_Worker = 16;
Enable_Fast_Stats = true;
#Dispatch_Max_Reqs = 4096;
#Dispatch_Max_Reqs_Xprt = 512;
RPC_Ioq_ThrdMax = 512;
Enable_RQUOTA = false;
Rquota_Port = 42424;
}
LOG {
COMPONENTS {
ALL = INFO;
}
}
7:53 a.m.
This should work fine. NFSv3 definitely works here, so it's not
generally broken.
Which version of Ganesha are you using? You may have to turn on logging
and post logs, so we can see what's happening.
Daniel
On 8/15/22 07:32, torben.klingpetersen(a)hpe.com wrote:
As instructed:
/etc/ganesha/ganesha.conf file
##################################################
#
# EXPORT
# To function, all that is required is an EXPORT
# Define the absolute minimal export
#
###################################################
EXPORT
{
# Export Id (mandatory, each EXPORT must have a unique Export_Id)
Export_Id = 99;
# Exported path (mandatory)
Path = "/mnt/lustre";
# Pseudo Path (required for NFS v4)
Pseudo = "/mnt/lustre";
# Required for access (default is None)
# Could use CLIENT blocks instead
Access_Type = "RW" ;
Protocols = "3" , "4" ;
Squash = "no_root_squash" ;
Transport = "UDP", "TCP" ;
# Exporting FSAL
FSAL {
Name = VFS;
}
}
NFS_Core_Param {
#Nb_Worker = 16;
Enable_Fast_Stats = true;
#Dispatch_Max_Reqs = 4096;
#Dispatch_Max_Reqs_Xprt = 512;
RPC_Ioq_ThrdMax = 512;
Enable_RQUOTA = false;
Rquota_Port = 42424;
}
LOG {
COMPONENTS {
ALL = INFO;
}
}
_______________________________________________
Support mailing list -- support(a)lists.nfs-ganesha.org
To unsubscribe send an email to support-leave(a)lists.nfs-ganesha.org
9 a.m.
Using Ganesha 3.5 ...
Finally got it to work but I had to turn off the firewall ....
Seems strange that NFS 4.1 works through a firewall, and both "nfs" and
"nfs3" were added to the filewall lists ....
10:13 a.m.
NFS4 uses a fixed port that can be opened in the firewall. NFSv3 uses
portmapper (which is on a fixed port), but NFS uses a random port
generated by the portmapper. This makes it much much harder to allow
through a firewall (and it the main reason why NFSv4 uses a fixed port).
Daniel
On 8/15/22 10:00, torben.klingpetersen(a)hpe.com wrote:
Using Ganesha 3.5 ...
Finally got it to work but I had to turn off the firewall ....
Seems strange that NFS 4.1 works through a firewall, and both "nfs" and
"nfs3" were added to the filewall lists ....
_______________________________________________
Support mailing list -- support(a)lists.nfs-ganesha.org
To unsubscribe send an email to support-leave(a)lists.nfs-ganesha.org
10:41 a.m.
NFS4 uses a fixed port that can be opened in the firewall. NFSv3
uses
portmapper (which is on a fixed port), but NFS uses a random port generated by
the portmapper. This makes it much much harder to allow through a firewall
(and it the main reason why NFSv4 uses a fixed port).
To be a bit more specific:
The primary NFSv3 RPC program, NFS, does use a fixed port, 2049 (unless overridden),
however MOUNT, STATD, and LOCK all use dynamic port as assigned by the TCP stack (not
exactly random, and not assigned by rpcbind). With MOUNT not being on a well known port,
there must be additional configuration for it to work with firewall as you discovered.
Frank
859
days inactive
859
days old
7 comments
4 participants
participants (4)
-
Daniel Gryniewicz -
Frank Filz -
Kaleb Keithley -
torben.klingpetersen＠hpe.com