From owner-freebsd-questions@FreeBSD.ORG  Sun Feb 26 07:48:08 2006
Return-Path: <owner-freebsd-questions@FreeBSD.ORG>
X-Original-To: freebsd-questions@freebsd.org
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 54E6C16A420
	for <freebsd-questions@freebsd.org>;
	Sun, 26 Feb 2006 07:48:08 +0000 (GMT) (envelope-from jonw@whoweb.com)
Received: from whoweb.com (whoweb.com [66.180.172.55])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 2E6DB43D62
	for <freebsd-questions@freebsd.org>;
	Sun, 26 Feb 2006 07:48:07 +0000 (GMT) (envelope-from jonw@whoweb.com)
Received: from whoweb.com (localhost.netsonic.net [127.0.0.1])
	by whoweb.com (8.13.5/8.12.11) with ESMTP id k1Q7mKaM037278
	for <freebsd-questions@freebsd.org>;
	Sun, 26 Feb 2006 02:48:20 -0500 (EST)
Received: (from root@localhost)
	by whoweb.com (8.13.5/8.12.11/Submit) id k1Q7mK0W037277
	for freebsd-questions@freebsd.org; Sun, 26 Feb 2006 02:48:20 -0500 (EST)
Date: Sun, 26 Feb 2006 02:48:20 -0500 (EST)
From: Jonathan Wallace <jonw@whoweb.com>
Message-Id: <200602260748.k1Q7mK0W037277@whoweb.com>
To: freebsd-questions@freebsd.org
Subject: Smbfs hang when connection broken
X-BeenThere: freebsd-questions@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: User questions <freebsd-questions.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-questions>, 
	<mailto:freebsd-questions-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-questions>
List-Post: <mailto:freebsd-questions@freebsd.org>
List-Help: <mailto:freebsd-questions-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-questions>, 
	<mailto:freebsd-questions-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Sun, 26 Feb 2006 07:48:08 -0000


Processes that access a share from a remote machine hang if the connection
goes away.  I'm using FBSD V5.4 and mount_smbfs.  This can be replicated
by the following sequence:

1) Share a file system from a remote Windows machine.
2) Mount the share using mount_smbfs
3) Start a tar() command to copy the data from the windows share.
4) Unplug the network cable from the windows box

The ps() command shows that smbiod has a stat of SL (sleeping and waiting to
acquire a lock) and the tar() process stat is D (uniterruptable wait).  If
you kill smbiod, the FBSD system hangs and has to be rebooted.

Is there any workaround to this issue?

Thanks,
Jon