Hi,
So I don't know if anyone else does this, but I have set up a replication of a Dataset that is used as a Plex Media Server library, both at the source and the target end.
Source and target are running FreeNAS 11.3-U4.1.
The target Plex Media Server is installed on an Ubuntu 18.04.5 Server VM with mounts set up pointing back to the (replication) target FreeNAS dataset presented as an NFS V3 share.
The mounts from Ubuntu work just fine initially - Plex can quite happily pick up the content and it can be played. The ZFS replication works just fine. However, during the ZFS replication cycle, the mounts on Ubuntu then stop working, although they still exist.
I've since worked out that the only way I can recover this situation so far, is to restart the NFS services on the FreeNAS target.
I've also tried changing the target dataset to readonly=off and ensuring the replication doesn't set readonly=on, but this makes no difference.
Does anyone know if there is a way to stop this from happening? Thanks
[edit.. a bit more info]
Here's what I get when I try to remount the shares, having force unmounted them;
andrew@firsplex01:/mnt$ sudo mount -av
/ : ignored
none : ignored
/mnt/Plex_Media_Files : already mounted
mount.nfs: trying text-based options 'nolock,bg,soft,intr,tcp,timeo=50,retrans=5,actimeo=10,retry=5,vers=4.2,addr=192.168.5.201,clientaddr=192.168.5.5'
mount.nfs: mount(2): Protocol not supported
mount.nfs: trying text-based options 'nolock,bg,soft,intr,tcp,timeo=50,retrans=5,actimeo=10,retry=5,vers=4.1,addr=192.168.5.201,clientaddr=192.168.5.5'
mount.nfs: mount(2): Protocol not supported
mount.nfs: trying text-based options 'nolock,bg,soft,intr,tcp,timeo=50,retrans=5,actimeo=10,retry=5,vers=4.0,addr=192.168.5.201,clientaddr=192.168.5.5'
mount.nfs: mount(2): Protocol not supported
mount.nfs: trying text-based options 'nolock,bg,soft,intr,tcp,timeo=50,retrans=5,actimeo=10,retry=5,addr=192.168.5.201'
mount.nfs: prog 100003, trying vers=3, prot=6
mount.nfs: trying 192.168.5.201 prog 100003 vers 3 prot TCP port 2049
mount.nfs: prog 100005, trying vers=3, prot=6
mount.nfs: trying 192.168.5.201 prog 100005 vers 3 prot TCP port 695
mount.nfs: mount(2): Stale file handle
mount.nfs: backgrounding "192.168.5.201:/mnt/vol1/Media/Movies"
mount.nfs: mount options: "ro,noatime,nolock,bg,soft,intr,tcp,timeo=50,retrans=5,actimeo=10,retry=5"
/mnt/Plex_Media_Movies : successfully mounted
mount.nfs: trying text-based options 'nolock,bg,soft,intr,tcp,timeo=50,retrans=5,actimeo=10,retry=5,vers=4.2,addr=192.168.5.201,clientaddr=192.168.5.5'
mount.nfs: mount(2): Protocol not supported
mount.nfs: trying text-based options 'nolock,bg,soft,intr,tcp,timeo=50,retrans=5,actimeo=10,retry=5,vers=4.1,addr=192.168.5.201,clientaddr=192.168.5.5'
mount.nfs: mount(2): Protocol not supported
mount.nfs: trying text-based options 'nolock,bg,soft,intr,tcp,timeo=50,retrans=5,actimeo=10,retry=5,vers=4.0,addr=192.168.5.201,clientaddr=192.168.5.5'
mount.nfs: mount(2): Protocol not supported
mount.nfs: trying text-based options 'nolock,bg,soft,intr,tcp,timeo=50,retrans=5,actimeo=10,retry=5,addr=192.168.5.201'
mount.nfs: prog 100003, trying vers=3, prot=6
mount.nfs: trying 192.168.5.201 prog 100003 vers 3 prot TCP port 2049
mount.nfs: prog 100005, trying vers=3, prot=6
mount.nfs: trying 192.168.5.201 prog 100005 vers 3 prot TCP port 695
mount.nfs: mount(2): Stale file handle
mount.nfs: backgrounding "192.168.5.201:/mnt/vol1/Media/Music"
mount.nfs: mount options: "ro,noatime,nolock,bg,soft,intr,tcp,timeo=50,retrans=5,actimeo=10,retry=5"
/mnt/Plex_Media_Music : successfully mounted
mount.nfs: trying text-based options 'nolock,bg,soft,intr,tcp,timeo=50,retrans=5,actimeo=10,retry=5,vers=4.2,addr=192.168.5.201,clientaddr=192.168.5.5'
mount.nfs: mount(2): Protocol not supported
mount.nfs: trying text-based options 'nolock,bg,soft,intr,tcp,timeo=50,retrans=5,actimeo=10,retry=5,vers=4.1,addr=192.168.5.201,clientaddr=192.168.5.5'
mount.nfs: mount(2): Protocol not supported
mount.nfs: trying text-based options 'nolock,bg,soft,intr,tcp,timeo=50,retrans=5,actimeo=10,retry=5,vers=4.0,addr=192.168.5.201,clientaddr=192.168.5.5'
mount.nfs: mount(2): Protocol not supported
mount.nfs: trying text-based options 'nolock,bg,soft,intr,tcp,timeo=50,retrans=5,actimeo=10,retry=5,addr=192.168.5.201'
mount.nfs: prog 100003, trying vers=3, prot=6
mount.nfs: trying 192.168.5.201 prog 100003 vers 3 prot TCP port 2049
mount.nfs: prog 100005, trying vers=3, prot=6
mount.nfs: trying 192.168.5.201 prog 100005 vers 3 prot TCP port 695
mount.nfs: mount(2): Stale file handle
mount.nfs: backgrounding "192.168.5.201:/mnt/vol1/Media/TV_Shows"
mount.nfs: mount options: "ro,noatime,nolock,bg,soft,intr,tcp,timeo=50,retrans=5,actimeo=10,retry=5"
/mnt/Plex_Media_TV_Shows : successfully mounted
The issue I believe is the "Stale file handle" errors that are in the log above.
Note also, that when I switch mountd logging on at the FreeNAS end, it comes out with the following;
Aug 30 19:06:14 freenas2 mountd[83635]: mount request succeeded from 192.168.5.5 for /mnt/vol1/Media/Movies
Aug 30 19:06:14 freenas2 mountd[83635]: mount request succeeded from 192.168.5.5 for /mnt/vol1/Media/Music
Aug 30 19:06:14 freenas2 mountd[83635]: mount request succeeded from 192.168.5.5 for /mnt/vol1/Media/TV_Shows
But when I subsequently try to unmount, I get;
andrew@firsplex01:/mnt$ sudo umount -f /mnt/Plex_Media_Movies
umount: /mnt/Plex_Media_Movies: not mounted.
That would suggest that FreeNAS is reporting a successful NFS mount operation, when in reality it failed (owing to the Stale File Handle)
Best Regards
Andy
So I don't know if anyone else does this, but I have set up a replication of a Dataset that is used as a Plex Media Server library, both at the source and the target end.
Source and target are running FreeNAS 11.3-U4.1.
The target Plex Media Server is installed on an Ubuntu 18.04.5 Server VM with mounts set up pointing back to the (replication) target FreeNAS dataset presented as an NFS V3 share.
The mounts from Ubuntu work just fine initially - Plex can quite happily pick up the content and it can be played. The ZFS replication works just fine. However, during the ZFS replication cycle, the mounts on Ubuntu then stop working, although they still exist.
I've since worked out that the only way I can recover this situation so far, is to restart the NFS services on the FreeNAS target.
I've also tried changing the target dataset to readonly=off and ensuring the replication doesn't set readonly=on, but this makes no difference.
Does anyone know if there is a way to stop this from happening? Thanks
[edit.. a bit more info]
Here's what I get when I try to remount the shares, having force unmounted them;
andrew@firsplex01:/mnt$ sudo mount -av
/ : ignored
none : ignored
/mnt/Plex_Media_Files : already mounted
mount.nfs: trying text-based options 'nolock,bg,soft,intr,tcp,timeo=50,retrans=5,actimeo=10,retry=5,vers=4.2,addr=192.168.5.201,clientaddr=192.168.5.5'
mount.nfs: mount(2): Protocol not supported
mount.nfs: trying text-based options 'nolock,bg,soft,intr,tcp,timeo=50,retrans=5,actimeo=10,retry=5,vers=4.1,addr=192.168.5.201,clientaddr=192.168.5.5'
mount.nfs: mount(2): Protocol not supported
mount.nfs: trying text-based options 'nolock,bg,soft,intr,tcp,timeo=50,retrans=5,actimeo=10,retry=5,vers=4.0,addr=192.168.5.201,clientaddr=192.168.5.5'
mount.nfs: mount(2): Protocol not supported
mount.nfs: trying text-based options 'nolock,bg,soft,intr,tcp,timeo=50,retrans=5,actimeo=10,retry=5,addr=192.168.5.201'
mount.nfs: prog 100003, trying vers=3, prot=6
mount.nfs: trying 192.168.5.201 prog 100003 vers 3 prot TCP port 2049
mount.nfs: prog 100005, trying vers=3, prot=6
mount.nfs: trying 192.168.5.201 prog 100005 vers 3 prot TCP port 695
mount.nfs: mount(2): Stale file handle
mount.nfs: backgrounding "192.168.5.201:/mnt/vol1/Media/Movies"
mount.nfs: mount options: "ro,noatime,nolock,bg,soft,intr,tcp,timeo=50,retrans=5,actimeo=10,retry=5"
/mnt/Plex_Media_Movies : successfully mounted
mount.nfs: trying text-based options 'nolock,bg,soft,intr,tcp,timeo=50,retrans=5,actimeo=10,retry=5,vers=4.2,addr=192.168.5.201,clientaddr=192.168.5.5'
mount.nfs: mount(2): Protocol not supported
mount.nfs: trying text-based options 'nolock,bg,soft,intr,tcp,timeo=50,retrans=5,actimeo=10,retry=5,vers=4.1,addr=192.168.5.201,clientaddr=192.168.5.5'
mount.nfs: mount(2): Protocol not supported
mount.nfs: trying text-based options 'nolock,bg,soft,intr,tcp,timeo=50,retrans=5,actimeo=10,retry=5,vers=4.0,addr=192.168.5.201,clientaddr=192.168.5.5'
mount.nfs: mount(2): Protocol not supported
mount.nfs: trying text-based options 'nolock,bg,soft,intr,tcp,timeo=50,retrans=5,actimeo=10,retry=5,addr=192.168.5.201'
mount.nfs: prog 100003, trying vers=3, prot=6
mount.nfs: trying 192.168.5.201 prog 100003 vers 3 prot TCP port 2049
mount.nfs: prog 100005, trying vers=3, prot=6
mount.nfs: trying 192.168.5.201 prog 100005 vers 3 prot TCP port 695
mount.nfs: mount(2): Stale file handle
mount.nfs: backgrounding "192.168.5.201:/mnt/vol1/Media/Music"
mount.nfs: mount options: "ro,noatime,nolock,bg,soft,intr,tcp,timeo=50,retrans=5,actimeo=10,retry=5"
/mnt/Plex_Media_Music : successfully mounted
mount.nfs: trying text-based options 'nolock,bg,soft,intr,tcp,timeo=50,retrans=5,actimeo=10,retry=5,vers=4.2,addr=192.168.5.201,clientaddr=192.168.5.5'
mount.nfs: mount(2): Protocol not supported
mount.nfs: trying text-based options 'nolock,bg,soft,intr,tcp,timeo=50,retrans=5,actimeo=10,retry=5,vers=4.1,addr=192.168.5.201,clientaddr=192.168.5.5'
mount.nfs: mount(2): Protocol not supported
mount.nfs: trying text-based options 'nolock,bg,soft,intr,tcp,timeo=50,retrans=5,actimeo=10,retry=5,vers=4.0,addr=192.168.5.201,clientaddr=192.168.5.5'
mount.nfs: mount(2): Protocol not supported
mount.nfs: trying text-based options 'nolock,bg,soft,intr,tcp,timeo=50,retrans=5,actimeo=10,retry=5,addr=192.168.5.201'
mount.nfs: prog 100003, trying vers=3, prot=6
mount.nfs: trying 192.168.5.201 prog 100003 vers 3 prot TCP port 2049
mount.nfs: prog 100005, trying vers=3, prot=6
mount.nfs: trying 192.168.5.201 prog 100005 vers 3 prot TCP port 695
mount.nfs: mount(2): Stale file handle
mount.nfs: backgrounding "192.168.5.201:/mnt/vol1/Media/TV_Shows"
mount.nfs: mount options: "ro,noatime,nolock,bg,soft,intr,tcp,timeo=50,retrans=5,actimeo=10,retry=5"
/mnt/Plex_Media_TV_Shows : successfully mounted
The issue I believe is the "Stale file handle" errors that are in the log above.
Note also, that when I switch mountd logging on at the FreeNAS end, it comes out with the following;
Aug 30 19:06:14 freenas2 mountd[83635]: mount request succeeded from 192.168.5.5 for /mnt/vol1/Media/Movies
Aug 30 19:06:14 freenas2 mountd[83635]: mount request succeeded from 192.168.5.5 for /mnt/vol1/Media/Music
Aug 30 19:06:14 freenas2 mountd[83635]: mount request succeeded from 192.168.5.5 for /mnt/vol1/Media/TV_Shows
But when I subsequently try to unmount, I get;
andrew@firsplex01:/mnt$ sudo umount -f /mnt/Plex_Media_Movies
umount: /mnt/Plex_Media_Movies: not mounted.
That would suggest that FreeNAS is reporting a successful NFS mount operation, when in reality it failed (owing to the Stale File Handle)
Best Regards
Andy
Last edited: