The most suspicious behaviour of mount is the double attempt at closing
the TCP socket it has opened to the NFS server. Notice this fragment in
the strace:
---
connect(3, {sa_family=AF_INET, sin_port=htons(2049),
sin_addr=inet_addr("192.168.1.1")}, 16) = 0
gettimeofday({1173993083, 563383}, NULL) = 0
write(3, "\200\0\0(V\303\313\334\0\0\0\0\0\0\0\2\0\1\206\243\0\0"..., 44) = 44
poll([{fd=3, events=POLLIN, revents=POLLIN}], 1, 20000) = 1
read(3, "\200\0\0\30V\303\313\334\0\0\0\1\0\0\0\0\0\0\0\0\0\0\0"..., 400) = 28
close(3) = 0
close(3) = -1 EBADF (Bad file descriptor)
---
This is clearly wrong.
--
add NFSv4 support
https://launchpad.net/bugs/27425
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
