[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: NFS rename sometimes hangs for 15 seconds after upgrade to Debian 8



-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hello,

I tried to replicate your problem, but couldn't.

When mounted as NFS3 over UDP:
- ----
root@lab1# echo foo > file1
root@lab1# cp file1 file2

root@lab2# cat file2
foo

root@lab1# time mv file1 file2
real	0m0.004s
user	0m0.000s
sys	0m0.000s
- ----

Same with NFS4 over TCP:
root@lab1# time mv file1 file2
real	0m0.005s
user	0m0.000s
sys	0m0.000s

Any special mount options or export options you might be using?

Regards,
/peter

Am 22.09.2015 um 15:19 schrieb Vincent Lefevre:
> At my lab, with NFS accounts, some machines have been upgraded to 
> Debian 8, and I get regular hangs on these machines, while they 
> never occurred before on the same machine and still never occur on 
> a machine that is still under Debian 7.
> 
> This happens with one of my scripts, which does a lot of "mv", and 
> more often when the target has just been modified from another 
> machine.
> 
> A strace showed that it is the "rename" system call that hangs:
> 
> 52026      0.000208 execve("/bin/mv", ["mv", "-v", 
> "ssh/ssh-reconfigure", "/home/vlefevre/bin/ssh-reconfigu"...], [/* 
> 112 vars */]) = 0 [...] 52026      0.000097 
> rename("ssh/ssh-reconfigure",
> "/home/vlefevre/bin/ssh-reconfigure") = 0 52026     15.057725
> lseek(0, 0, SEEK_CUR) = -1 ESPIPE (Illegal seek) 52026
> 0.000189 close(0)            = 0 52026 0.000175 close(1)
> = 0 52026      0.000093 munmap(0x7fd5a610b000, 4096) = 0 52026
> 0.000079 close(2) = 0 52026      0.000106 exit_group(0)       = ?
> 52026      0.000307 +++ exited with 0 +++
> 
> The NFS server isn't particularly loaded.
> 
> Has anyone seen a problem like that? Where does it come from? And 
> why does it affect only Debian 8 machines? A new bug?
> 
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.22 (MingW32)

iQIcBAEBAgAGBQJWAsuuAAoJEM+6Ng5pbtyZGhMP/2yC/CgWhb5+yvA5jb/pd3sW
FwNw1mvH+FQikKVvvPgy5AMO3d2rQafh/fXQlfZRnC0Hu3jXn99K60mV//88KqGm
N+axMi5octq8s2zhF/K0/axsiPHAhgo9ggdlcdXE0ekQvgw5gzXJ6hDutnaFTaun
gay6HK6Ujp0JuvCxUQzq8uiv5VTPJiT0ftyBAF02dFqO0yBgGhDAt80NUtMGRwZB
nuya8pD7EhZH7x0vabnv3935+X0V1bpQhyKHWAbzCMY4Uce2wt0wtR9FEJVOyj4v
gQ7WHULo53fYOLdKw5REhgtEDqIFDz6MRsOup28gv7sZBW7/Ps3IbOi06/ovuR3W
WWZhYys+F/5Nmt8tKD7XWZfYQ7TnUN35Z1PS0xCK8+cEUWxSbI2OftyVBfI+iRCn
W3n0N2cvxyaRfWGwLs5ROO7/g+5xeNH5WiziaNZa5QfFae8j2J8lUIyG8aSZ/Axe
n0/HfwfA5vp9IIPVSOgsw+xmjkzCtIOtL+2cWBu5nTixD301hFRSuZCbUsz5f0Sq
tDUDzyYKYsUXJ5+YvBktgZ1dKD6nR3TuJdRl70gPJo6RuCxhvfRqHy47qrSOw6qL
HfKUZYnlgOMV1ufXLTI9sTq/YcDmJzKD+LDJUlumF88le58w5bq8KeR8uusGySSF
wQjgvRlwVkzvDsxm9b0z
=CCwk
-----END PGP SIGNATURE-----


Reply to: