https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=289711
Peter Much <[email protected]> changed:
What |Removed |Added
----------------------------------------------------------------------------
Summary|NFS4 access to symlinks is |NFS4 access is very slow -
|very slow |"Request couldn't be
| |completed in time"
--- Comment #2 from Peter Much <[email protected]> ---
I finally found a place where the issue appears somehow reproducible, so that
debugging can be put in place.
Running "git commit" in a nfs-mounted /usr/ports gets all the way through until
near the end when it tries to
rename("/usr/ports/.git/HEAD.lock","/usr/ports/.git/HEAD"). That rename() then
takes 136 seconds:
208.557521019 0.001095461
openat(AT_FDCWD,".git/logs/HEAD",O_WRONLY|O_APPEND|O_CREAT,0666) = 3 (0x3)
208.574163154 0.016549171 write(3,"3754f93cb84ba98cab6af9197debbe22"...,192) =
192 (0xc0)
208.574516583 0.000263536 close(3) = 0 (0x0)
208.574873362 0.000260186 fstatat(AT_FDCWD,"/usr/ports/.git/HEAD",{
mode=-rw-r--r-- ,inode=98432,size=41,blksize=4096 },AT_SYMLINK_NOFOLLOW) = 0
(0x0)
345.013475256 136.438519818
rename("/usr/ports/.git/HEAD.lock","/usr/ports/.git/HEAD") = 0 (0x0)
345.017156753 0.003254916 access(".git/hooks/reference-transaction",X_OK) ERR#2
'No such file or directory'
345.018147271 0.000731442
fstatat(AT_FDCWD,".git/CHERRY_PICK_HEAD",0x820dea580,AT_SYMLINK_NOFOLLOW) ERR#2
'No such file or directory'
More interesting is the network traffic between nfs client and server during
these 136 seconds, which repeatedly goes like this:
18:35:19.260807 IP 192.168.97.5.900 > 192.168.97.17.2049: Flags [P.], seq
125136848:125137132, ack 430758341, win 22032, options [nop,nop,TS val
885962725 ecr 1618335444], length 284: NFS request xid 1784465120 280 getattr
fh 0,6/2
18:35:19.261091 IP 192.168.97.17.2049 > 192.168.97.5.900: Flags [P.], seq
430758341:430758537, ack 125137132, win 29128, options [nop,nop,TS val
1618343639 ecr 885962725], length 196: NFS reply xid 1784465120 reply ok 192
getattr ERROR: Request couldn't be completed in time
18:35:19.301145 IP 192.168.97.5.900 > 192.168.97.17.2049: Flags [.], ack
430758537, win 22032, options [nop,nop,TS val 885962765 ecr 1618343639], length
0
18:35:34.265610 IP 192.168.97.5.900 > 192.168.97.17.2049: Flags [P.], seq
125137132:125137416, ack 430758537, win 22032, options [nop,nop,TS val
885977731 ecr 1618343639], length 284: NFS request xid 1784465121 280 getattr
fh 0,6/2
18:35:34.265914 IP 192.168.97.17.2049 > 192.168.97.5.900: Flags [P.], seq
430758537:430758733, ack 125137416, win 29128, options [nop,nop,TS val
1618358644 ecr 885977731], length 196: NFS reply xid 1784465121 reply ok 192
getattr ERROR: Request couldn't be completed in time
18:35:34.305678 IP 192.168.97.5.900 > 192.168.97.17.2049: Flags [.], ack
430758733, win 22032, options [nop,nop,TS val 885977771 ecr 1618358644], length
0
I have no idea why the server cannot complete a request here. The exported
filesystem was on-demand created (zfs clone) exclusively for this client, there
cannot be any conflicting access.
--
You are receiving this mail because:
You are the assignee for the bug.
lmpx.com only provides a reader for public news (NNTP) servers. It is not
affiliated with the servers or forums shown here and is not responsible for
the content of articles, which is written by their respective authors.