On 03/12/2012 05:27 PM, Chuck Lever wrote: > > On Mar 12, 2012, at 5:24 PM, Nikolaus Rath wrote: > >> Alright, it seems that this was the problem. With correct clientaddr, I >> haven't been able to produce any freezes for the last 15 minutes >> (usually it happens in ~20 seconds). >> >> The weird thing is that I cannot reproduce the wrong clientaddr >> autodetection when I mount the NFS volumes from the command line. It >> seems to happen only when the mounting is done by mountall during the >> boot sequence. >> >> In other words, this fstab entry results in freezes and a clientaddr of 0.0.0.0: >> >> spitzer:/opt /opt nfs4 bg 0 0 >> >> While this one, followed by a "mount /opt" on the console as soon as I'm >> able to log in, works just fine (and has a correct clientaddr): >> >> spitzer:/opt /opt nfs4 noauto 0 0 > > That's almost certainly because networking isn't up during boot. The "bg" option keeps trying the mount until it succeeds, but the system started the mount process before there was a source address on the system. Oh, so the clientaddr detection takes place only once at the beginning, and is not repeated if the mount attempts are repeated? This would explain what's happening. The VPN is not yet up when the system first attempts to mount the share. Is there a rationale behind this? It seems to me that if the mount is retried, it would be reasonable to expect that the clientaddr detection is retried as well. Best, -Nikolaus -- »Time flies like an arrow, fruit flies like a Banana.« PGP fingerprint: 5B93 61F8 4EA2 E279 ABF6 02CF A9AD B7F8 AE4E 425C -- To unsubscribe from this list: send the line "unsubscribe linux-nfs" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
