From owner-freebsd-stable@FreeBSD.ORG  Tue Mar 31 08:54:37 2015
Return-Path: <owner-freebsd-stable@FreeBSD.ORG>
Delivered-To: freebsd-stable@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org
 [IPv6:2001:1900:2254:206a::19:1])
 (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits))
 (No client certificate requested)
 by hub.freebsd.org (Postfix) with ESMTPS id B36BDF71
 for <freebsd-stable@freebsd.org>; Tue, 31 Mar 2015 08:54:37 +0000 (UTC)
Received: from smarthost1.greenhost.nl (smarthost1.greenhost.nl
 [195.190.28.81]) (using TLSv1 with cipher AES256-SHA (256/256 bits))
 (Client did not present a certificate)
 by mx1.freebsd.org (Postfix) with ESMTPS id 740F6FD5
 for <freebsd-stable@freebsd.org>; Tue, 31 Mar 2015 08:54:37 +0000 (UTC)
Received: from smtp.greenhost.nl ([213.108.104.138])
 by smarthost1.greenhost.nl with esmtps (TLS1.0:RSA_AES_256_CBC_SHA1:32)
 (Exim 4.72) (envelope-from <ronald-lists@klop.ws>)
 id 1YcrwF-0006dL-VY
 for freebsd-stable@freebsd.org; Tue, 31 Mar 2015 10:54:29 +0200
Content-Type: text/plain; charset=iso-8859-15; format=flowed; delsp=yes
To: freebsd-stable@freebsd.org
Subject: Re: hanging processes, nfs, automount
References: <551A59A5.5070303@bsdforen.de>
Date: Tue, 31 Mar 2015 10:54:22 +0200
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
From: "Ronald Klop" <ronald-lists@klop.ws>
Message-ID: <op.xwctowkykndu52@ronaldradial.radialsg.local>
In-Reply-To: <551A59A5.5070303@bsdforen.de>
User-Agent: Opera Mail/1.0 (Win32)
X-Authenticated-As-Hash: 398f5522cb258ce43cb679602f8cfe8b62a256d1
X-Virus-Scanned: by clamav at smarthost1.samage.net
X-Spam-Level: /
X-Spam-Score: -0.2
X-Spam-Status: No, score=-0.2 required=5.0 tests=ALL_TRUSTED, BAYES_50,
 URIBL_BLOCKED autolearn=disabled version=3.3.2
X-Scan-Signature: 8b3222cd26cce149ddb9ffa05c4da76e
X-BeenThere: freebsd-stable@freebsd.org
X-Mailman-Version: 2.1.18-1
Precedence: list
List-Id: Production branch of FreeBSD source code <freebsd-stable.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-stable>,
 <mailto:freebsd-stable-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-stable/>
List-Post: <mailto:freebsd-stable@freebsd.org>
List-Help: <mailto:freebsd-stable-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
 <mailto:freebsd-stable-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Tue, 31 Mar 2015 08:54:37 -0000

On Tue, 31 Mar 2015 10:24:05 +0200, Dominic Fandrey <kamikaze@bsdforen.de>  
wrote:

> I don't know where to ask this, so I'm putting it out here.
>
> Introductions first:
> FreeBSD AprilRyan.norad 10.1-STABLE FreeBSD 10.1-STABLE #2 r280373: Mon  
> Mar 23 17:43:09 CET 2015      
> root@AprilRyan.norad:/usr/obj/S403/amd64/usr/src/sys/S403  amd64
>
> I have an nfs-share that I access via automount in /net/<host>/<share>.
>
> The following scenario:
> - cd /net/<host>/<share> inside tmux
> - Do stuff
> - S4 the laptop and take it to work the next morning
> - Resume and the tmux session hangs infinitely
> - Kill all shells belonging to the tmux session
> - tmux server process hangs in state "rpcrec"
>
> It's bad enough that there apparently is no path for NFS to fail
> and reanimate the shell that accesses the share.
>
> But the really bad problem is, that tmux in rpcrec state is not
> killable. I.e. not kill -9 able. And as long as that process is around
> any new tmux server I try to start just hangs.

For this killable stuff there is the 'intr' mount option. See also the  
'soft' mount option if you don't want NFS to wait indefinitely for a lost  
server.
man mount_nfs describes this all.

Regards,
Ronald.


>
> My only recourse so far is a reboot.