From owner-freebsd-questions Sun Oct 13 19: 9:38 2002 Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 3A99837B401 for ; Sun, 13 Oct 2002 19:09:35 -0700 (PDT) Received: from infinity.aesredfish.net (ns1.aesredfish.net [65.168.0.12]) by mx1.FreeBSD.org (Postfix) with ESMTP id 53F4243E7B for ; Sun, 13 Oct 2002 19:09:34 -0700 (PDT) (envelope-from wmoran@potentialtech.com) Received: from potentialtech.com (mhope-dhcp-65-168-1-181.dashfast.com [65.168.1.181]) by infinity.aesredfish.net (8.11.6/8.11.0) with ESMTP id g9E29NW29204; Sun, 13 Oct 2002 22:09:23 -0400 Message-ID: <3DAA2936.4050207@potentialtech.com> Date: Sun, 13 Oct 2002 22:17:26 -0400 From: Bill Moran User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.0rc1) Gecko/20020502 X-Accept-Language: en-us, en MIME-Version: 1.0 To: cool46 cool46 Cc: neuhauser@bellavista.cz, FreeBSD-questions@FreeBSD.ORG Subject: Re: how to kill nfs-blocked process References: Content-Type: text/plain; charset=GB2312 Content-Transfer-Encoding: 7bit Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG [please stop top-posting] cool46 cool46 wrote: > thanks for your reply.i'm sorry,this doesn't work for me,the problem is > still in. > this time i do the same experiment as before except using: > mount_nfs -i -R 1 -s 10.0.0.1:/home /usr/home > the process blocked by nfs cann't return or be interrupted,and i also > can't kill it. > i tried in freebsd 4.5 and 4.6 > is it works for FreeBSD 4.7-RC? > any sugguestions else? > thanks again. I'm running 4.7-RELEASE and using the mount options you describe, I am able to abort with a TERM signal. The exact steps followed: 1. Mount NFS with options as shown above 2. Start large-scale copy operation from NFS server to local machine 3. Unplug network cable - copy is stalled 4. "killall cp" 5. cp process is terminated. You're going to have to do a little more research into the problem, as what you are describing doesn't happen to me. >> From: Roman Neuhauser >> To: Bill Moran >> CC: cool46 cool46 ,questions > > > >> Subject: Re: how to kill nfs-blocked process >> Date: Fri, 11 Oct 2002 15:50:39 +0200 >> >> # wmoran@potentialtech.com / 2002-10-11 09:39:38 -0400: >> > cool46 cool46 wrote: >> > > thanks for your reply,but it is not work for me.i tried to mount nfs >> > > with options -i,-R,but the problem is as before.The details of my > > test > >> > > is as follows: >> > > my nfs server(IP:10.0.0.1) is a RedHat 7.3 with kernel of 2.4.19 >> > > version,my nfs client(IP:10.0.0.2) is freebsd 4.5 >> > > 10.0.0.2: >> > > mount_nfs -i -R 1 10.0.0.1:/home /usr/home >> > > cp a_big_file /usr/home >> > > >> > > in the course of doing this,i disabled network between these two > > machine > >> > > by using iptables in 10.0.0.1 >> > > /sbin/iptables -I INPUT -p udp -s 10.0.0.2 -j DROP >> > > >> > > so the process 'cp' in 10.0.0.2 is blocked,I can't kill or interrupt > > it > >> > > in any way.According to mount_nfs's manual ,it should failed and > > return > >> > > in a few minutes because i set -R equal to 1,but the fact is not. >> > > Could you help me? >> > > thanks agains.i'm a chinese and glad to make friends with you. >> > >> > That should be the solution. I'm not an NFS "expert" so you may want > > to > >> > consult with some others as well. (I've put this email back on the > > mailing > >> > list) >> >> -i Make the mount interruptible, which implies that file system >> calls that are delayed due to an unresponsive server will > > fail > >> with EINTR when a termination signal is posted for the > > process. > >> >> the above makes it look like you should be able to kill the process >> with your settings. but see below. >> >> -R Set the mount retry count to the specified value. The >> default is a retry count of zero, which means to keep >> retrying forever. There is a 60 second delay between each >> attempt. >> >> this is probably what you're missing. works for me. >> >> -s A soft mount, which implies that file system calls will fail >> after Retry round trip timeout intervals. -- Bill Moran Potential Technologies http://www.potentialtech.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message