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 cliendaddr): > > 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. -- Chuck Lever chuck[dot]lever[at]oracle[dot]com -- 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
