January 2021 - Support - Nfs Ganesha List Archives

NFSv3 active-passive cluster with FSAL CephFS and keepalived - Stale file handle after restart and also failover

by rainer.stumbaum＠gmail.com

Hi, I configured five unrestriced LXC containers on Proxmox and also set lxc.seccomp.profile to empty. This is my configuration: root@nfsshares-a:~# egrep -v '^[[:blank:]]*#|^[[:blank:]]*$' /etc/ganesha/ganesha.conf NFS_CORE_PARAM { Enable_NLM = false; Enable_RQUOTA = false; Protocols = 3,4; mount_path_pseudo = true; } NFS_KRB5 { Active_krb5 = false; } NFSv4 { RecoveryBackend = rados_ng; Minor_Versions = 1,2; } MDCACHE { Dir_Chunk = 0; } EXPORT_DEFAULTS { SecType = "sys"; Squash = No_Root_Squash; Attr_Expiration_Time = 0; } CEPH { } RADOS_KV { UserId = "ganesharecov"; } RADOS_URLS { UserId = "ganeshaurls"; watch_url = "rados://nfs-ganesha/ganesha-namespace/conf-nfsshares"; } %url rados://nfs-ganesha/ganesha-namespace/conf-nfsshares root@nfsshares-a:~# And this is an example export. The other exports just have different clients for the other paths. root@proxmox07:~# cat /tmp/export-1 EXPORT { FSAL { secret_access_key = "AQDm7eFfJWvhIBAAuI++d0SNkdylNkMx5t/N8w=="; user_id = "ganesha"; name = "CEPH"; filesystem = "cephfs"; } CLIENT { clients = 10.20.56.254; squash = "no_root_squash"; access_type = "RW"; } pseudo = "/"; squash = "no_root_squash"; access_type = "NONE"; path = "/"; export_id = 1; transports = "TCP"; protocols = 3, 4; } Mounting filesystems works fine, but as soon as I restart the nfs-ganesha daemon I get a stale file handle on the client. Looking at root@nfsshares-a:~# ganesha-rados-grace --userid ganesharecov --pool nfs-ganesha --ns namespace-ganesha dump cur=1 rec=0 ====================================================== nfsshares-a E nfsshares-b E nfsshares-c E nfsshares-d E nfsshares-e E root@nfsshares-a:~# The nodes never loose the E state. These are the permissions on ceph: root@proxmox07:~# cat /etc/pve/priv/ceph.client.ganesha*.keyring [client.ganesha] key = <removed> caps mds = "allow r path=/, allow rw path=/vol" caps mon = "allow r" caps osd = "allow class-read object_prefix rbd_children, allow rw pool=cephfs_data, allow rw pool=nfs-ganesha" [client.ganesharecov] key = <removed> caps mon = "allow r" caps osd = "allow class-read object_prefix rbd_children, allow rw pool=nfs-ganesha" [client.ganeshaurls] key = <removed> caps mon = "allow r" caps osd = "allow class-read object_prefix rbd_children, allow rw pool=nfs-ganesha" root@proxmox07:~# Which service account is used to remove the E state on ceph? Do I have a permission problem? Best regards Rainer Log from a restart: ---- 21/01/2021 10:48:08 : epoch 60095be8 : nfsshares-a : ganesha.nfsd-239[main] main :MAIN :EVENT :ganesha.nfsd Starting: Ganesha Version 3.4 21/01/2021 10:48:08 : epoch 60095be8 : nfsshares-a : ganesha.nfsd-246[main] nfs_set_param_from_conf :NFS STARTUP :EVENT :Configuration file successfully parsed 21/01/2021 10:48:08 : epoch 60095be8 : nfsshares-a : ganesha.nfsd-246[main] init_server_pkgs :NFS STARTUP :EVENT :Initializing ID Mapper. 21/01/2021 10:48:08 : epoch 60095be8 : nfsshares-a : ganesha.nfsd-246[main] init_server_pkgs :NFS STARTUP :EVENT :ID Mapper successfully initialized. 21/01/2021 10:48:08 : epoch 60095be8 : nfsshares-a : ganesha.nfsd-246[main] rados_ng_init :CLIENT ID :EVENT :Rados kv store init done 21/01/2021 10:48:08 : epoch 60095be8 : nfsshares-a : ganesha.nfsd-246[main] nfs_start_grace :STATE :EVENT :NFS Server Now IN GRACE, duration 90 21/01/2021 10:48:08 : epoch 60095be8 : nfsshares-a : ganesha.nfsd-246[main] nfs_lift_grace_locked :STATE :EVENT :NFS Server Now NOT IN GRACE 21/01/2021 10:48:22 : epoch 60095be8 : nfsshares-a : ganesha.nfsd-246[main] lower_my_caps :NFS STARTUP :EVENT :CAP_SYS_RESOURCE was successfully removed for proper quota management in FSAL 21/01/2021 10:48:22 : epoch 60095be8 : nfsshares-a : ganesha.nfsd-246[main] lower_my_caps :NFS STARTUP :EVENT :currenty set capabilities are: = cap_chown,cap_dac_override,cap_dac_read_search,cap_fowner,cap_fsetid,cap_kill,cap_setgid,cap_setuid,cap_setpcap,cap_linux_immutable,cap_net_bind_service,cap_net_broadcast,cap_net_admin,cap_net_raw,cap_ipc_lock,cap_ipc_owner,cap_sys_chroot,cap_sys_ptrace,cap_sys_pacct,cap_sys_admin,cap_sys_boot,cap_sys_nice,cap_sys_tty_config,cap_mknod,cap_lease,cap_audit_write,cap_audit_control,cap_setfcap,cap_syslog,cap_wake_alarm,cap_block_suspend,cap_audit_read+ep 21/01/2021 10:48:22 : epoch 60095be8 : nfsshares-a : ganesha.nfsd-246[main] nfs_Init_admin_thread :NFS CB :EVENT :Admin thread initialized 21/01/2021 10:48:22 : epoch 60095be8 : nfsshares-a : ganesha.nfsd-246[main] nfs_rpc_cb_init_ccache :NFS STARTUP :WARN :gssd_refresh_krb5_machine_credential failed (-1765328160:22) 21/01/2021 10:48:22 : epoch 60095be8 : nfsshares-a : ganesha.nfsd-246[main] nfs_Start_threads :THREAD :EVENT :Starting delayed executor. 21/01/2021 10:48:22 : epoch 60095be8 : nfsshares-a : ganesha.nfsd-246[main] nfs_Start_threads :THREAD :EVENT :gsh_dbusthread was started successfully 21/01/2021 10:48:22 : epoch 60095be8 : nfsshares-a : ganesha.nfsd-246[main] nfs_Start_threads :THREAD :EVENT :admin thread was started successfully 21/01/2021 10:48:22 : epoch 60095be8 : nfsshares-a : ganesha.nfsd-246[main] nfs_Start_threads :THREAD :EVENT :reaper thread was started successfully 21/01/2021 10:48:22 : epoch 60095be8 : nfsshares-a : ganesha.nfsd-246[main] nfs_Start_threads :THREAD :EVENT :General fridge was started successfully 21/01/2021 10:48:22 : epoch 60095be8 : nfsshares-a : ganesha.nfsd-246[main] nfs_start :NFS STARTUP :EVENT :------------------------------------------------- 21/01/2021 10:48:22 : epoch 60095be8 : nfsshares-a : ganesha.nfsd-246[main] nfs_start :NFS STARTUP :EVENT : NFS SERVER INITIALIZED 21/01/2021 10:48:22 : epoch 60095be8 : nfsshares-a : ganesha.nfsd-246[main] nfs_start :NFS STARTUP :EVENT :------------------------------------------------- 22/01/2021 19:47:22 : epoch 600b2bca : nfsshares-a : ganesha.nfsd-236[main] main :MAIN :EVENT :ganesha.nfsd Starting: Ganesha Version 3.4 22/01/2021 19:47:22 : epoch 600b2bca : nfsshares-a : ganesha.nfsd-249[main] nfs_set_param_from_conf :NFS STARTUP :EVENT :Configuration file successfully parsed 22/01/2021 19:47:22 : epoch 600b2bca : nfsshares-a : ganesha.nfsd-249[main] init_server_pkgs :NFS STARTUP :EVENT :Initializing ID Mapper. 22/01/2021 19:47:22 : epoch 600b2bca : nfsshares-a : ganesha.nfsd-249[main] init_server_pkgs :NFS STARTUP :EVENT :ID Mapper successfully initialized. 22/01/2021 19:47:22 : epoch 600b2bca : nfsshares-a : ganesha.nfsd-249[main] rados_ng_init :CLIENT ID :EVENT :Rados kv store init done 22/01/2021 19:47:22 : epoch 600b2bca : nfsshares-a : ganesha.nfsd-249[main] nfs_start_grace :STATE :EVENT :NFS Server Now IN GRACE, duration 90 22/01/2021 19:47:22 : epoch 600b2bca : nfsshares-a : ganesha.nfsd-249[main] nfs_lift_grace_locked :STATE :EVENT :NFS Server Now NOT IN GRACE 22/01/2021 19:47:49 : epoch 600b2bca : nfsshares-a : ganesha.nfsd-249[main] lower_my_caps :NFS STARTUP :EVENT :CAP_SYS_RESOURCE was successfully removed for proper quota management in FSAL 22/01/2021 19:47:49 : epoch 600b2bca : nfsshares-a : ganesha.nfsd-249[main] lower_my_caps :NFS STARTUP :EVENT :currenty set capabilities are: = cap_chown,cap_dac_override,cap_dac_read_search,cap_fowner,cap_fsetid,cap_kill,cap_setgid,cap_setuid,cap_setpcap,cap_linux_immutable,cap_net_bind_service,cap_net_broadcast,cap_net_admin,cap_net_raw,cap_ipc_lock,cap_ipc_owner,cap_sys_chroot,cap_sys_ptrace,cap_sys_pacct,cap_sys_admin,cap_sys_boot,cap_sys_nice,cap_sys_tty_config,cap_mknod,cap_lease,cap_audit_write,cap_audit_control,cap_setfcap,cap_syslog,cap_wake_alarm,cap_block_suspend,cap_audit_read+ep 22/01/2021 19:47:49 : epoch 600b2bca : nfsshares-a : ganesha.nfsd-249[main] nfs_Init_admin_thread :NFS CB :EVENT :Admin thread initialized 22/01/2021 19:47:49 : epoch 600b2bca : nfsshares-a : ganesha.nfsd-249[main] nfs_rpc_cb_init_ccache :NFS STARTUP :WARN :gssd_refresh_krb5_machine_credential failed (-1765328160:22) 22/01/2021 19:47:49 : epoch 600b2bca : nfsshares-a : ganesha.nfsd-249[main] nfs_Start_threads :THREAD :EVENT :Starting delayed executor. 22/01/2021 19:47:49 : epoch 600b2bca : nfsshares-a : ganesha.nfsd-249[main] nfs_Start_threads :THREAD :EVENT :gsh_dbusthread was started successfully 22/01/2021 19:47:49 : epoch 600b2bca : nfsshares-a : ganesha.nfsd-249[main] nfs_Start_threads :THREAD :EVENT :admin thread was started successfully 22/01/2021 19:47:49 : epoch 600b2bca : nfsshares-a : ganesha.nfsd-249[main] nfs_Start_threads :THREAD :EVENT :reaper thread was started successfully 22/01/2021 19:47:49 : epoch 600b2bca : nfsshares-a : ganesha.nfsd-249[main] nfs_Start_threads :THREAD :EVENT :General fridge was started successfully 22/01/2021 19:47:49 : epoch 600b2bca : nfsshares-a : ganesha.nfsd-249[main] nfs_start :NFS STARTUP :EVENT :------------------------------------------------- 22/01/2021 19:47:49 : epoch 600b2bca : nfsshares-a : ganesha.nfsd-249[main] nfs_start :NFS STARTUP :EVENT : NFS SERVER INITIALIZED 22/01/2021 19:47:49 : epoch 600b2bca : nfsshares-a : ganesha.nfsd-249[main] nfs_start :NFS STARTUP :EVENT :------------------------------------------------- root@nfsshares-a:~#

3 years, 3 months

5
8
0 / 0

Ganesha 3.5

by Daniel Gryniewicz

Since Ceph Pacific has come out, with the changes that break building Ganesha 3.4 and earlier against it, I've released a 3.5 with just the fix to build against Ceph Pacific. There's no associated ntirpc release. Daniel

3 years, 3 months

2
2
0 / 0

Bind_address ignored in NFS Ganesha 2.7 to NFS Ganesha 3.4?

by TomK

Hello All, Bind_address appears to be ignored in NFS Ganesha 2.7 to NFS Ganesha 3.4? This used to work in Ganesha 2.6. Do I need to add a parameter to my config to make this work again? [root@nfs03 ~]# vi /etc/ganesha/ganesha.conf [root@nfs03 ~]# [root@nfs03 ~]# [root@nfs03 ~]# grep -Ei Bind_addr /etc/ganesha/ganesha.conf Bind_addr = 192.168.0.125; [root@nfs03 ~]# [root@nfs03 ~]# grep -EiB5 Bind_addr /etc/ganesha/ganesha.conf KeytabPath = /etc/krb5.keytab ; Active_krb5 = YES ; } NFS_Core_Param { Bind_addr = 192.168.0.125; [root@nfs03 ~]# [root@nfs03 ~]# [root@nfs03 ~]# netstat -pnltu|grep -Ei 2049 tcp 0 0 0.0.0.0:2049 0.0.0.0:* LISTEN 5412/ganesha.nfsd udp 0 0 192.168.0.125:2049 0.0.0.0:* 5412/ganesha.nfsd [root@nfs03 ~]# rpm -aq|grep -Ei ganesha nfs-ganesha-mount-9P-2.7.6-2.el7.x86_64 nfs-ganesha-utils-3.4-1.el7.x86_64 centos-release-nfs-ganesha28-1.0-3.el7.centos.noarch nfs-ganesha-3.4-1.el7.x86_64 nfs-ganesha-proxy-3.4-1.el7.x86_64 nfs-ganesha-vfs-3.4-1.el7.x86_64 centos-release-nfs-ganesha30-1.0-2.el7.centos.noarch nfs-ganesha-gluster-3.4-1.el7.x86_64 [root@nfs03 ~]# -- Thx, TK.

3 years, 3 months

1
0
0 / 0

Ganesha network switch ACLs

by Becker, Jeffrey C. (ARC-TN)[InuTeq, LLC]

Hi. I’d like to clamp down the network between my Ganesha server (using Proxy FSAL) and the server that Ganesha is acting as a Proxy for (the one serving directories over NFSv4). Can I limit the network to only allow NFSv4 traffic? Thanks. -Jeff

3 years, 3 months

2
1
0 / 0

FSAL :CRIT :This libcephfs version doesn't support named filesystems

by rainer.stumbaum＠gmail.com

Hi, I am running a Debian 10 with root@nfsshares-a:~# dpkg -l | grep ganesha ii nfs-ganesha 3.3-4 amd64 nfs-ganesha is a NFS server in User Space ii nfs-ganesha-ceph:amd64 3.3-4 amd64 nfs-ganesha fsal ceph libraries ii nfs-ganesha-rados-grace:amd64 3.3-4 amd64 nfs-ganesha ganesha-rados-grace program and root@nfsshares-a:~# dpkg -l | grep ceph ii ceph-common 14.2.16-pve1 amd64 common utilities to mount and interact with a ceph storage cluster ii libcephfs2 14.2.16-pve1 amd64 Ceph distributed file system client library ii nfs-ganesha-ceph:amd64 3.3-4 amd64 nfs-ganesha fsal ceph libraries ii python-ceph-argparse 14.2.16-pve1 all Python 2 utility libraries for Ceph CLI ii python-cephfs 14.2.16-pve1 amd64 Python 2 libraries for the Ceph libcephfs library The config looks like this: root@nfsshares-a:~# grep '^[[:blank:]]*[^[:blank:]#;]' /etc/ganesha/ganesha.conf NFS_CORE_PARAM { Enable_NLM = false; Enable_RQUOTA = false; Protocols = 3,4; mount_path_pseudo = true; } NFS_KRB5 { Active_krb5 = false; } NFSv4 { RecoveryBackend = rados_ng; Minor_Versions = 1,2; } MDCACHE { Dir_Chunk = 0; } EXPORT_DEFAULTS { SecType = "sys"; Squash = No_Root_Squash; Attr_Expiration_Time = 0; } CEPH { Ceph_Conf = /etc/ceph/ceph.conf; } RADOS_KV { Ceph_Conf = /etc/ceph/ceph.conf; UserId = "ganesharecov"; nodeid = "nfsshares-a"; } RADOS_URLS { Ceph_Conf = /etc/ceph/ceph.conf; UserId = "ganeshaurls"; watch_url = "rados://nfs-ganesha/ganesha-namespace/conf-nfsshares"; } %url rados://nfs-ganesha/ganesha-namespace/conf-nfsshares The Export configuration is created on the ceph dashboard and looks like this: root@proxmox07:~# cat /tmp/conf-nfsshares %url "rados://nfs-ganesha/ganesha-namespace/export-1" root@proxmox07:~# cat /tmp/export-1 EXPORT { FSAL { secret_access_key = "AQDm7eFfJWvhIBAAuI++d0SNkdylNkMx5t/N8w=="; user_id = "ganesha"; name = "CEPH"; filesystem = "cephfs"; } CLIENT { clients = 10.20.56.254; squash = "no_root_squash"; access_type = "RW"; } pseudo = "/"; squash = "no_root_squash"; access_type = "NONE"; path = "/"; export_id = 1; transports = "UDP", "TCP"; protocols = 4; } I get the following error message: .... 15/01/2021 12:47:30 : epoch 600180d2 : nfsshares-a : ganesha.nfsd-21185[main] register_callbacks :FSAL :WARN :This libcephfs does not support registering callbacks. Ganesha will be unable to respond to MDS cache pressure. 15/01/2021 12:47:30 : epoch 600180d2 : nfsshares-a : ganesha.nfsd-21185[main] select_filesystem :FSAL :CRIT :This libcephfs version doesn't support named filesystems. 15/01/2021 12:47:30 : epoch 600180d2 : nfsshares-a : ganesha.nfsd-21185[main] mdcache_fsal_create_export :FSAL :MAJ :Failed to call create_export on underlying FSAL Ceph 15/01/2021 12:47:30 : epoch 600180d2 : nfsshares-a : ganesha.nfsd-21185[main] fsal_cfg_commit :CONFIG :CRIT :Could not create export for (/) to (/) 15/01/2021 12:47:30 : epoch 600180d2 : nfsshares-a : ganesha.nfsd-21185[main] main :NFS STARTUP :WARN :No export entries found in configuration file !!! 15/01/2021 12:47:30 : epoch 600180d2 : nfsshares-a : ganesha.nfsd-21185[main] config_errs_to_log :CONFIG :CRIT :Config File ("rados://nfs-ganesha/ganesha-namespace/export-1":2): 1 validation errors in block FSAL 15/01/2021 12:47:30 : epoch 600180d2 : nfsshares-a : ganesha.nfsd-21185[main] config_errs_to_log :CONFIG :CRIT :Config File ("rados://nfs-ganesha/ganesha-namespace/export-1":2): Errors processing block (FSAL) 15/01/2021 12:47:30 : epoch 600180d2 : nfsshares-a : ganesha.nfsd-21185[main] config_errs_to_log :CONFIG :CRIT :Config File ("rados://nfs-ganesha/ganesha-namespace/export-1":1): 1 validation errors in block EXPORT 15/01/2021 12:47:30 : epoch 600180d2 : nfsshares-a : ganesha.nfsd-21185[main] config_errs_to_log :CONFIG :CRIT :Config File ("rados://nfs-ganesha/ganesha-namespace/export-1":1): Errors processing block (EXPORT) .... When I remove filesystem = "cephfs"; in export-1 it works. I believe my dashboard does not work together with its version or configuration of the libcephfs2 (both same source and version). Or did I misconfigure something here? Best regards and a healthy new year! Rainer

3 years, 3 months

3
8
0 / 0

Ganesha 3.4 startup error

by Becker, Jeffrey C. (ARC-TN)[InuTeq, LLC]

Hi. I’m seeing the following in my log. What is the problem with the clients? Thanks. -Jeff 21/01/2021 19:30:24 : epoch 6009d650 : ganesha : ganesha.nfsd-311[main] export_commit_common :CONFIG :INFO :Export 1001 created at pseudo (/BD_public) with path (/srv/rex/exports/BD_public_datasets) and tag ((null)) perms (options=033030a2/000001e7 root_squash , R-r-, , , , , , , ) 21/01/2021 19:30:24 : epoch 6009d650 : ganesha : ganesha.nfsd-311[main] export_commit_common :CONFIG :INFO :Export 1001 has 4 defined clients 21/01/2021 19:30:24 : epoch 6009d650 : ganesha : ganesha.nfsd-311[pxy_rcv_thread] pxy_rpc_recv :FSAL :DEBUG :Connected after 0 sleeps, resending outstanding calls 21/01/2021 19:30:24 : epoch 6009d650 : ganesha : ganesha.nfsd-311[pxy_clientid_renewer] pxy_clientid_renewer :FSAL :DEBUG :Need 1 new client id 21/01/2021 19:30:24 : epoch 6009d650 : ganesha : ganesha.nfsd-311[pxy_clientid_renewer] pxy_setclientid :FSAL :EVENT :Negotiating a new ClientId with the remote server 21/01/2021 19:30:24 : epoch 6009d650 : ganesha : ganesha.nfsd-311[pxy_clientid_renewer] pxy_compoundv4_call :FSAL :DEBUG :First attempt to send XID 1611257703 with 152 bytes 21/01/2021 19:30:24 : epoch 6009d650 : ganesha : ganesha.nfsd-311[pxy_rcv_thread] pxy_rpc_read_reply :FSAL :DEBUG :Recmark 80000014, xid 1611257703 21/01/2021 19:30:24 : epoch 6009d650 : ganesha : ganesha.nfsd-311[pxy_clientid_renewer] pxy_compoundv4_execute :FSAL :DEBUG :pxy_setclientid failed with 7 21/01/2021 19:30:24 : epoch 6009d650 : ganesha : ganesha.nfsd-311[pxy_clientid_renewer] pxy_setclientid :FSAL :DEBUG :Compound setclientid res request returned 7

3 years, 3 months

2
2
0 / 0

Initial testing with ESXi 6.7

by swarnock＠warnocksolutions.com

Hello All, I am attempting to get nfs-ganesha 3.0.3 under Ubuntu 20.04 working with ESXi. While I can successfully mount the NFS export I receive regular errors while performing any kind of file work through ESXi. The volume /vdb is just raw formatted with XFS and the environment is completely virtual. Any suggestions for debugging this farther as this is my first time trying out this configuration. Sean tail /var/log/ganesha/ganesha.log 08/01/2021 17:52:49 : epoch 5ff7ccb6 : ganesha : ganesha.nfsd-720[svc_584] fsal_common_is_referral :FSAL :EVENT :Failed to get attrs for referral, handle: 0x7f8a1800e830, valid_mask: 0, request_mask: 11d7ce, supported: 0, error: The file no longer exists 08/01/2021 17:52:49 : epoch 5ff7ccb6 : ganesha : ganesha.nfsd-720[svc_584] fsal_common_is_referral :FSAL :EVENT :Failed to get attrs for referral, handle: 0x7f8a0c00e200, valid_mask: 0, request_mask: 11d7ce, supported: 0, error: The file no longer exists 08/01/2021 17:52:49 : epoch 5ff7ccb6 : ganesha : ganesha.nfsd-720[svc_584] fsal_common_is_referral :FSAL :EVENT :Failed to get attrs for referral, handle: 0x7f8a0c0103b0, valid_mask: 0, request_mask: 11d7ce, supported: 0, error: The file no longer exists 08/01/2021 17:52:49 : epoch 5ff7ccb6 : ganesha : ganesha.nfsd-720[svc_584] fsal_common_is_referral :FSAL :EVENT :Failed to get attrs for referral, handle: 0x7f8a0c00f2d0, valid_mask: 0, request_mask: 11d7ce, supported: 0, error: The file no longer exists 08/01/2021 17:52:49 : epoch 5ff7ccb6 : ganesha : ganesha.nfsd-720[svc_584] fsal_common_is_referral :FSAL :EVENT :Failed to get attrs for referral, handle: 0x7f8a0c010510, valid_mask: 0, request_mask: 11d7ce, supported: 0, error: The file no longer exists 08/01/2021 17:52:49 : epoch 5ff7ccb6 : ganesha : ganesha.nfsd-720[svc_584] fsal_common_is_referral :FSAL :EVENT :Failed to get attrs for referral, handle: 0x7f8a0c010670, valid_mask: 0, request_mask: 11d7ce, supported: 0, error: The file no longer exists 08/01/2021 17:52:50 : epoch 5ff7ccb6 : ganesha : ganesha.nfsd-720[svc_584] fsal_common_is_referral :FSAL :EVENT :Failed to get attrs for referral, handle: 0x7f8a0c010510, valid_mask: 0, request_mask: 11d7ce, supported: 0, error: The file no longer exists 08/01/2021 17:52:50 : epoch 5ff7ccb6 : ganesha : ganesha.nfsd-720[svc_582] fsal_common_is_referral :FSAL :EVENT :Failed to get attrs for referral, handle: 0x7f8a0c010670, valid_mask: 0, request_mask: 11d7ce, supported: 0, error: The file no longer exists 08/01/2021 17:52:50 : epoch 5ff7ccb6 : ganesha : ganesha.nfsd-720[svc_582] fsal_common_is_referral :FSAL :EVENT :Failed to get attrs for referral, handle: 0x7f8a100109c0, valid_mask: 0, request_mask: 11d7ce, supported: 0, error: The file no longer exists 08/01/2021 17:55:18 : epoch 5ff7ccb6 : ganesha : ganesha.nfsd-720[dbus_heartbeat] nfs_health :DBUS :WARN :Health status is unhealthy. enq new: 9736, old: 9735; deq new: 9735, old: 9735 lsblk NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT loop0 7:0 0 55.4M 1 loop /snap/core18/1944 loop1 7:1 0 69M 1 loop /snap/lxd/14804 loop2 7:2 0 55M 1 loop /snap/core18/1705 loop3 7:3 0 71.3M 1 loop /snap/lxd/18772 loop4 7:4 0 31.1M 1 loop /snap/snapd/10492 loop5 7:5 0 31.1M 1 loop /snap/snapd/10707 sr0 11:0 1 1024M 0 rom vda 252:0 0 25G 0 disk ├─vda1 252:1 0 1M 0 part ├─vda2 252:2 0 1G 0 part /boot └─vda3 252:3 0 24G 0 part └─ubuntu--vg-ubuntu--lv 253:0 0 20G 0 lvm / vdb 252:16 0 200G 0 disk /nfs cat /etc/ganesha/ganesha.conf ################################################### # # Ganesha Config Example # # This is a commented example configuration file for Ganesha. It is not # complete, but only has some common configuration options. See the man pages # for complete documentation. # ################################################### ## These are core parameters that affect Ganesha as a whole. NFS_CORE_PARAM { ## Allow NFSv3 to mount paths with the Pseudo path, the same as NFSv4, ## instead of using the physical paths. #mount_path_pseudo = true; ## Configure the protocols that Ganesha will listen for. This is a hard ## limit, as this list determines which sockets are opened. This list ## can be restricted per export, but cannot be expanded. Protocols = 3,4; } ## These are defaults for exports. They can be overridden per-export. #EXPORT_DEFAULTS { ## Access type for clients. Default is None, so some access must be ## given either here or in the export itself. #Access_Type = RW; #} ## Configure settings for the object handle cache #MDCACHE { ## The point at which object cache entries will start being reused. #Entries_HWMark = 100000; #} ## Configure an export for some file tree #EXPORT #{ ## Export Id (mandatory, each EXPORT must have a unique Export_Id) #Export_Id = 12345; ## Exported path (mandatory) #Path = /nonexistant; ## Pseudo Path (required for NFSv4 or if mount_path_pseudo = true) #Pseudo = /nonexistant; ## Restrict the protocols that may use this export. This cannot allow ## access that is denied in NFS_CORE_PARAM. #Protocols = 3,4; ## Access type for clients. Default is None, so some access must be ## given. It can be here, in the EXPORT_DEFAULTS, or in a CLIENT block #Access_Type = RW; ## Whether to squash various users. #Squash = root_squash; ## Allowed security types for this export #Sectype = sys,krb5,krb5i,krb5p; ## Exporting FSAL #FSAL { #Name = VFS; #} #} EXPORT { Export_Id = 5; Path = /nfs; Pseudo = /nfs; Protocols = 4; Access_Type = RW; #Squash = root_squash; Sectype = none,sys; FSAL { Name = vfs; } } ## Configure logging. Default is to log to Syslog. Basic logging can also be ## configured from the command line #LOG { ## Default log level for all components # Default_Log_Level = INFO; ## Configure per-component log levels. # Components { # FSAL = INFO; # NFS4 = EVENT; # } ## Where to log # Facility { # name = FILE; # destination = "/var/log/ganecat /etc/ganesha/ganesha.conf ################################################### # # Ganesha Config Example # # This is a commented example configuration file for Ganesha. It is not # complete, but only has some common configuration options. See the man pages # for complete documentation. # ################################################### ## These are core parameters that affect Ganesha as a whole. NFS_CORE_PARAM { ## Allow NFSv3 to mount paths with the Pseudo path, the same as NFSv4, ## instead of using the physical paths. #mount_path_pseudo = true; ## Configure the protocols that Ganesha will listen for. This is a hard ## limit, as this list determines which sockets are opened. This list ## can be restricted per export, but cannot be expanded. Protocols = 3,4; } ## These are defaults for exports. They can be overridden per-export. #EXPORT_DEFAULTS { ## Access type for clients. Default is None, so some access must be ## given either here or in the export itself. #Access_Type = RW; #} ## Configure settings for the object handle cache #MDCACHE { ## The point at which object cache entries will start being reused. #Entries_HWMark = 100000; #} ## Configure an export for some file tree #EXPORT #{ ## Export Id (mandatory, each EXPORT must have a unique Export_Id) #Export_Id = 12345; ## Exported path (mandatory) #Path = /nonexistant; ## Pseudo Path (required for NFSv4 or if mount_path_pseudo = true) #Pseudo = /nonexistant; ## Restrict the protocols that may use this export. This cannot allow ## access that is denied in NFS_CORE_PARAM. #Protocols = 3,4; ## Access type for clients. Default is None, so some access must be ## given. It can be here, in the EXPORT_DEFAULTS, or in a CLIENT block #Access_Type = RW; ## Whether to squash various users. #Squash = root_squash; ## Allowed security types for this export #Sectype = sys,krb5,krb5i,krb5p; ## Exporting FSAL #FSAL { #Name = VFS; #} #} EXPORT { Export_Id = 5; Path = /nfs; Pseudo = /nfs; Protocols = 4; Access_Type = RW; #Squash = root_squash; Sectype = none,sys; FSAL { Name = vfs; } } ## Configure logging. Default is to log to Syslog. Basic logging can also be ## configured from the command line #LOG { ## Default log level for all components # Default_Log_Level = INFO; ## Configure per-component log levels. # Components { # FSAL = INFO; # NFS4 = EVENT; # } ## Where to log # Facility { # name = FILE; # destination = "/var/log/ganesha.log"; # enable = active; # } #} sha.log"; # enable = active; # } #}

3 years, 4 months

3
7
0 / 0

2024

2023

2022

2021

2020

2019

2018

Support January 2021