From owner-freebsd-stable@FreeBSD.ORG Tue Mar 31 08:32:22 2015 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 4DD93804 for ; Tue, 31 Mar 2015 08:32:22 +0000 (UTC) Received: from mail.server1.bsdforen.de (bsdforen.de [82.193.243.81]) by mx1.freebsd.org (Postfix) with ESMTP id 108B7DBA for ; Tue, 31 Mar 2015 08:32:21 +0000 (UTC) Received: from AprilRyan.norad (iz-aix-213a.HS-Karlsruhe.DE [193.196.64.213]) (using TLSv1 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by mail.server1.bsdforen.de (Postfix) with ESMTPSA id 1D63485FC2 for ; Tue, 31 Mar 2015 10:24:05 +0200 (CEST) Message-ID: <551A59A5.5070303@bsdforen.de> Date: Tue, 31 Mar 2015 10:24:05 +0200 From: Dominic Fandrey User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:31.0) Gecko/20100101 Thunderbird/31.5.0 MIME-Version: 1.0 To: freebsd-stable@freebsd.org Subject: hanging processes, nfs, automount Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 31 Mar 2015 08:32:22 -0000 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//. The following scenario: - cd /net// 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. My only recourse so far is a reboot. -- A: Because it fouls the order in which people normally read text. Q: Why is top-posting such a bad thing? A: Top-posting. Q: What is the most annoying thing on usenet and in e-mail?