Announce Push of V4-rc3
by Frank Filz
Branch next
Tag:V4-rc3
Ganesha V4.0 is in sight!
Merge Highlights
* Keep pidfile locked while running
Signed-off-by: Frank S. Filz <ffilzlnx(a)mindspring.com>
Contents:
a4969e3d6 Frank S. Filz V4-rc3
ba923ef21 Olivier Garaud Keep pidfile locked while running
2 years, 5 months
proxyv3_getfd_blocking :FSAL :CRIT :Failed to ever acquire a new fd, dying
by Matthew Hess
I've set:
LimitAS=infinity
LimitRSS=infinity
LimitCORE=infinity
LimitNOFILE=infinity
in /usr/lib/systemd/system/nfs-ganesha.service and reloaded it then
restarted the service but I keep hitting that error when writing large
files.
I'm using last night's next branch and built rpms from that.
2 years, 5 months
having issues with setting up nfs-ganesha
by Matthew Hess
I'm currently using the centos 7 distribution and the centos-nfs-ganesha30
repo:
# rpm -q -a | grep nfs-ganesha
nfs-ganesha-vfs-3.5-2.el7.x86_64
nfs-ganesha-3.5-2.el7.x86_64
nfs-ganesha-proxy-3.5-2.el7.x86_64
centos-release-nfs-ganesha30-1.0-2.el7.centos.noarch
I've come across a strange need to get a nfsv3 share on a netapp talking
with a client that only understands nfsv4. I think I'm heading in the right
direction here but I'm having some trouble getting this setup for testing.
In the log I am getting:
init_export_root :EXPORT :CRIT :Lookup failed on path, ExportId=20
Path=/prod FSAL_ERROR=(Permission denied,13)
and it appears to give up on the /prod share
my export config is:
EXPORT {
Export_Id = 20;
Path = "/prod";
Pseudo = "/prod";
Access_Type = RW;
Squash = No_Root_Squash;
Transports = "TCP";
FSAL {
Name = proxy;
Srv_Addr = <netapp ip>;
Use_Privileged_Client_Port = false;
}
}
I am able to mount the netapp share from this same system and manage the
content of the share:
mount -v -t nfs -o proto=tcp,vers=3,nolock <netapp ip>:/prod /prod
not certain what I'm doing wrong, can anyone clue me in?
2 years, 5 months
