On Tue, Jul 25 2017, Phil Kauffman wrote: > On 07/14/2017 01:51 AM, NeilBrown wrote: >> Please try this (against a clean nfs-utils. i.e. remove the previous >> patch). >> It is a hack and would need to be totally re-written, but hopely the >> measurements you make and strace that you report could be useful. >> Also, for the strace, please use "-ttt" rather than "-tt" like I asked >> before. It is easier to find the difference between two times with >> -ttt. And add -T as well. > > Sorry this took so long but I had to be sure of my results. It is worth being thorough. > > With your latest patch applied I am unable to mount my NFS shares and > thus continue with the tests from before. Weird. You are experiencing a bug that was very recently fixed, where if mount.nfs4 gets the error ENOENT from the server, it falls back to NFSv3. That explains some of the noise, but doesn't explain why you get ENOENT for the v4 mount. The strace output you've provided doesn't even show any attempts to read /etc/mtab, which my patch doesn't change at all. So it seems like the context is different in some way. Your nfs_test_notes.txt doesn't show /etc/export.d getting filled in ... maybe that it done automatically somehow... Can you try with unpatches 2.1.1? Also maybe provide an strace starting before any attempt to mount anything, and with an extra option "-s 1000".. Thanks, NeilBrown
Attachment:
signature.asc
Description: PGP signature
