Force -f is improper in situations when NFS server is gone.
I have node intranet-test2 with nfs mount and nas-sync-test2 with NFS server
and export resources.
I made following experiment:
1. Paused the VM running nas-sync-test2 so cluster lost the member
2. Executed umount -f /folder
This is a multipart message in MIME format.
uwXgvNCO8H_related
Content-Type: text/html;
charset="utf-8"
Content-Transfer-Encoding: quoted-printable
Content-Type: multipart/related;
boundary="--uwXgvNCO8H_related" charset="utf-8"
What about umount -f -l ?From: Users
On 11.04.2023 17:35, Miro Igov wrote:
Hello,
I have a node nas-sync-test1 with NFS server and NFS export running and
another node intranet-test1 with data_1 fs mount:
primitive data_1 Filesystem \
params device="nas-sync-test1:/home/pharmya/NAS" fstype=nfs
options=v4
Hello,
I have a node nas-sync-test1 with NFS server and NFS export running and
another node intranet-test1 with data_1 fs mount:
primitive data_1 Filesystem \
params device="nas-sync-test1:/home/pharmya/NAS" fstype=nfs
options=v4 directory="/data/synology/pharmya_office/NAS_Sync/NAS"
