proccess locks after touching large files over NFS (in first time only)
SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
proccess locks after touching large files over NFS (in first time only)
Hello, I have two linux boxes. One with Slack 10.1 (client) and one with Slack 10.2 (server). Kernels on both are 2.6.16.16.
All proccesses on client are hang after touching not small files (with 1kb files all ok, but if i try to execute
Code:
# file file_in_nfs_dir.mp3
my bash on client computer hangs (if i try to read this file from samba, samba hangs too). When bash hangs in /var/log/messages appears:
Code:
May 16 23:15:46 server-games kernel: nfs: server 192.168.0.4 not responding, still trying
May 16 23:15:51 server-games last message repeated 2 times
. But connection with server seems to be okay. I have tryed to ping it with
Code:
# rpcinfo -u 192.168.0.4 nfs
. I have no firewall & my hosts.allow and hosts.deny are empty. After process hangs I can login from another shell and execute
Code:
root@server-games:~# umount -f -a -t nfs
umount2: Device or resource busy
umount: /mnt/smuzd5: device is busy
. After this command server works OK (!!!). It really not umount anything, but bash on hanged console start to work again (??).
after recompiling kernel (snapshot 2.6.17-rc6-git2) UNhang effect (with umount) is dissappeared. it's seems like something wrong on my local network hardware with UDP packets (may be with large only UDP packets, i haven't tested it). Problem solved by compiling kernel (on server and client) with TCP support and mounting with "-o tcp" option.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.