Date: Fri, 11 Nov 2005 13:08:53 +0300 (MSK) From: "Roman V. Palagin" <romanp@unshadow.net> To: FreeBSD-gnats-submit@FreeBSD.org Subject: kern/88833: NFS mounts stuck Message-ID: <Pine.SOC.4.64.0511111300200.9422@hurricane> Resent-Message-ID: <200511111010.jABAAJlJ017098@freefall.freebsd.org>
index | next in thread | raw e-mail
>Number: 88833 >Category: kern >Synopsis: NFS mounts stuck >Confidential: no >Severity: critical >Priority: high >Responsible: freebsd-bugs >State: open >Quarter: >Keywords: >Date-Required: >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Fri Nov 11 10:10:18 GMT 2005 >Closed-Date: >Last-Modified: >Originator: Roman V. Palagin >Release: FreeBSD 6.0-20051108-STABLE i386 >Organization: N/A >Environment: System: FreeBSD kreator6.wuppy.net.ru 6.0-20051108-STABLE FreeBSD 6.0-20051108-STABLE #0: Tue Nov 8 12:43:38 UTC 2005 romanp@kreator5.wuppy.net.ru:/usr/obj/u00/sys-releng_6/KREATOR6 i386 NFS server: Solaris 10/IA32 >Description: Same as described in http://lists.freebsd.org/pipermail/freebsd-current/2005-November/057815.html but for "simple" mounts. Solaris NFS server tends to close connection after some period of inactivity, but FreeBSD NFS client doesn't close local socket and try to send data over existing half-closed connection. >How-To-Repeat: Mount fs via NFS-TCP from Solaris server, wait some time and you will see connection to server in CLOSE_WAIT state. From now all ops on mounted fs will stuck. >Fix: >Release-Note: >Audit-Trail: >Unformatted:home | help
Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.SOC.4.64.0511111300200.9422>
