On Mon, Nov 2, 2015 at 12:00 PM, Jeenu Viswambharan <jeenuv@xxxxxxxxx> wrote: > On Fri, Oct 30, 2015 at 3:02 PM, Jeenu Viswambharan <jeenuv@xxxxxxxxx> wrote: >> On Fri, Oct 30, 2015 at 2:54 PM, Jeenu Viswambharan <jeenuv@xxxxxxxxx> wrote: >>> I've a development board whose root file system is shared via. NFS >>> from my PC (3.13.0-66-generic #108-Ubuntu SMP x86_64 GNU/Linux). The >>> behaviour at times is that board mounts the NFS share, but then soon >>> thereafter, while in execution, it started displaying NFS timeouts, >>> retries, and hangs. That's the end of it. >> >> I missed to mention that once this happens, the board won't boot >> again: it'll wait for the root file system to be mounted, fails, and >> then crashes. Even restarting NFS server doesn't help. > > I found signs that the NFS server is probably allowing access to the > said share, but for some reason Linux on my development board wouldn't > boot. I found the following traces in syslog, indicating retries from > the Linux boot: > > [...] For closure, looks like the cause of the problem was that I didn't specify "tcp" mount option in my nfsroot parameter. Also, if I don't additionally mention "v3", file system accesses seem to be particularly slow. With these options specified, file system is getting mounted fine. Oddly enough, this requirement turned mandatory out of the blue. I never used to use these before! -- Jeenu -- 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
