Date: Tue, 18 Aug 2015 15:08:07 +0000 From: bugzilla-noreply@freebsd.org To: freebsd-bugs@FreeBSD.org Subject: [Bug 202419] Opening files hangs calling openat() while CWD is on a smbfs mount Message-ID: <bug-202419-8@https.bugs.freebsd.org/bugzilla/>
next in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=202419 Bug ID: 202419 Summary: Opening files hangs calling openat() while CWD is on a smbfs mount Product: Base System Version: 10.1-RELEASE Hardware: amd64 OS: Any Status: New Severity: Affects Only Me Priority: --- Component: kern Assignee: freebsd-bugs@FreeBSD.org Reporter: martin@sugioarto.com Scenario: - server serves files with Samba 3.6 - client mounts with smbfs Problem description: - change directory to the smbfs-mounted filesystem on client - try to start vim (not vi!), evince, libreoffice or similar (you don't need to open a file from smbfs!) - truss shows that it hangs calling openat in infinite loop truss output: openat(0xffffff9c,0x7fffffffc6b0,0x100000,0x0,0x7ff7fe43c39f,0x8080808080808080) = 499 (0x1f3) openat(0xffffff9c,0x7fffffffc6b0,0x100000,0x0,0x7ff7fe43c39f,0x8080808080808080) = 499 (0x1f3) openat(0xffffff9c,0x7fffffffc6b0,0x100000,0x0,0x7ff7fe43c39f,0x8080808080808080) = 499 (0x1f3) [ repeating infinitely ] Further details: - while current working directory is inside a smbfs-mountpoint, it is also not possible to open files on locally mounted filesystems Mount description in /etc/fstab: //username@servername/remotefs /net/server/remotefs smbfs rw,noauto,-N,-W=DOMAIN,-u=username,-g=groupname 0 0 (*) remark: I use noauto because there is a race condition with the network initialization which forces me to mount after a 10s sleep in /etc/rc.local (I think this problem is not related with the one described here) Disclaimer: It might be a samba misconfiguration. I am not fully sure what happens here. -- Martin -- You are receiving this mail because: You are the assignee for the bug.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-202419-8>