-
-
[6.12.14] Stopping array with open locks through NFS make unraid stuck
I have an immich instance having a nfs mount to an unraid share. When I stop the array while there is open files through NFS, it makes unraid stuck, not able to stop the array, unable to change any other settings in unraid, and the nfs clients are unable to unmount, probably because the nfs server or the exports are down before the array is stopped. It would be great to prevent the array to be stopped if any file is locked, to not block all the rest. I don't know how to prevent the stop depending on the locked files... Maybe with a user script, but it feels really hacky. Because of that, I lost data because of an array maintainance during a photo upload. The pictures upload was in progress while the array stop interrupted the upload, and as the files are locked, the app is not able to recover when the server is back. Client options : addr=10.253.0.0,rw,nolock,hard,nfsvers=4,tcp,noexec Btw, the nolock option seems to not be considered as the locks are still there Server export options: sec=sys,rw,no_root_squash,sync HOW TO REPRODUCE - prereq: nfs mount setup targeting a share inside the array, mount up and working - open a file and keep it open on the client side - ack that the file is locked using `lsof | grep /mnt/disk` - stop the array At this moment: - you should have in the logs `error: rmdir: /mnt/user resource busy`. - you cannot change any setting anywhere in unraid - you cannot unmount on the nfs client side I hope it's just a matter of nfs configuration...
-
Unable to mount nfs share through wireguard
Fix: just reboot and it worked...
-
Chuckame started following Unable to mount nfs share through wireguard
-
Unable to mount nfs share through wireguard
Hello there, I want to mount an UnRaid share using NFS on another machine in the same lan. I did setup the wireguard (in server-to-server mode). I'm able to ping from/to each host using the wireguard virtual ips, so the basics seems ok. I did setup nfs server on Unraid, and I'm able to mount the share using the real lan ip. Now I'm not able to nfs mount a share using the wireguard ip. May I miss something ? unraid real IP: 192.168.1.36 unraid virt IP: .1 client real IP: 192.168.1.90 client virt IP: .2 CLIENT wireguard client config: [Interface] PrivateKey = CLIENT_PRIV_KEY Address = 10.253.0.2/24 [Peer] PublicKey = UNRAID_PUB_KEY (from `Local public key` field in the unraid wireguard server GUI) AllowedIPs = 10.253.0.0/24 Endpoint = 192.168.1.36:51820 PersistentKeepalive = 20 nfs client options: addr=10.253.0.1,sync,nfsvers=4 UnRaid SERVER wireguard config: share nfs rules: *(sec=sys,rw) -> also tested with real ip (working) and virt wg ip (not working) What do I miss ?
Chuckame
Members
-
Joined
-
Last visited