ankalagon wrote: > Hi, > > I've the following problem: > > I want to mount 2 directories from my NAS for use in LMS. > I added the mounts in the Web-UI, and it works ..... BUT when I boot the > piCorePlayer and the NAS isn't online pcp tries to mount it several > times, despite of that it shouldn't, according to the options > Code: -------------------- > > retrans=1,retry=1 -------------------- > > > So it seems to me that the options simply get ignored. > > Then I added these lines to the bootlocal.sh, but they don't seem to > be executed, log shows nothing: > > > Code: -------------------- > > sudo mkdir /mnt/Musik > sudo mkdir /mnt/Hoerspiele > sudo mount -o addr=192.168.1.77,nolock,retrans=1,retry=1 -t nfs 192.168.1.77:/export/Musik /mnt/Musik > sudo mount -o addr=192.168.1.77,nolock,retrans=1,retry=1 -t nfs 192.168.1.77:/export/Hoerspiele /mnt/Hoerspiele -------------------- > > > > So, has anyone an idea to solve this problem?
>From the manpage for nfs: retrans=n The number of times the NFS client retries a request before it attempts further recovery action. If the retrans option is not specified, the NFS client tries each UDP request three times and each TCP request twice. The NFS client generates a "server not responding" message after retrans retries, then attempts further recovery (depending on whether the hard mount option is in effect). retry=n The number of minutes that the mount(8) command retries an NFS mount operation in the foreground or background before giving up. If this option is not specified, the default value for foreground mounts is 2 minutes, and the default value for background mounts is 10000 minutes (80 minutes shy of one week). If a value of zero is specified, the mount(8) command exits immediately after the first failure. Note that this only affects how many retries are made and doesn't affect the delay caused by each retry. For UDP each retry takes the time determined by the timeo and retrans options, which by default will be about 7 seconds. For TCP the default is 3 minutes, but system TCP connection timeouts will sometimes limit the timeout of each retransmission to around 2 minutes. soft / hard Determines the recovery behavior of the NFS client after an NFS request times out. If neither option is specified (or if the hard option is specified), NFS requests are retried indefinitely. If the soft option is specified, then the NFS client fails an NFS request after retrans retransmissions have been sent, causing the NFS client to return an error to the calling application. NB: A so-called "soft" timeout can cause silent data corruption in certain cases. As such, use the soft option only when client responsiveness is more important than data integrity. Using NFS over TCP or increasing the value of the retrans option may mitigate some of the risks of using the soft option. Maybe adding "soft" to the options will cause the behavior you want? 2 Touch, 2 Picoreplayer v6.0.0-b9 on RaspBerry 3B, 1 Raspian and squeezelite 1.8 on PiZero LMS 8.0.0 on Ubuntu 18.04.4 on Intel Core2 Duo E4500 @ 2.20GHz, 2GB. All wired Main audio system: Magnepan 3.6, amp "Gdis 400", DAC & pre: NAD M51, streamers: SB Touch // NAD M50 ------------------------------------------------------------------------ BosseJ's Profile: http://forums.slimdevices.com/member.php?userid=67378 View this thread: http://forums.slimdevices.com/showthread.php?t=112547 _______________________________________________ unix mailing list [email protected] http://lists.slimdevices.com/mailman/listinfo/unix
