From owner-freebsd-bugs@FreeBSD.ORG Tue Nov 7 12:30:27 2006 Return-Path: X-Original-To: freebsd-bugs@hub.freebsd.org Delivered-To: freebsd-bugs@hub.freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0A14516A417 for ; Tue, 7 Nov 2006 12:30:24 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6910643D66 for ; Tue, 7 Nov 2006 12:30:24 +0000 (GMT) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (gnats@localhost [127.0.0.1]) by freefall.freebsd.org (8.13.4/8.13.4) with ESMTP id kA7CUOM0063278 for ; Tue, 7 Nov 2006 12:30:24 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.13.4/8.13.4/Submit) id kA7CUObW063277; Tue, 7 Nov 2006 12:30:24 GMT (envelope-from gnats) Resent-Date: Tue, 7 Nov 2006 12:30:24 GMT Resent-Message-Id: <200611071230.kA7CUObW063277@freefall.freebsd.org> Resent-From: FreeBSD-gnats-submit@FreeBSD.org (GNATS Filer) Resent-To: freebsd-bugs@FreeBSD.org Resent-Reply-To: FreeBSD-gnats-submit@FreeBSD.org, Roger Jørgensen Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id AEE6516A417 for ; Tue, 7 Nov 2006 12:29:04 +0000 (UTC) (envelope-from nobody@FreeBSD.org) Received: from www.freebsd.org (www.freebsd.org [216.136.204.117]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7087F43D66 for ; Tue, 7 Nov 2006 12:29:04 +0000 (GMT) (envelope-from nobody@FreeBSD.org) Received: from www.freebsd.org (localhost [127.0.0.1]) by www.freebsd.org (8.13.1/8.13.1) with ESMTP id kA7CT4WG063942 for ; Tue, 7 Nov 2006 12:29:04 GMT (envelope-from nobody@www.freebsd.org) Received: (from nobody@localhost) by www.freebsd.org (8.13.1/8.13.1/Submit) id kA7CT4ES063941; Tue, 7 Nov 2006 12:29:04 GMT (envelope-from nobody) Message-Id: <200611071229.kA7CT4ES063941@www.freebsd.org> Date: Tue, 7 Nov 2006 12:29:04 GMT From: Roger Jørgensen To: freebsd-gnats-submit@FreeBSD.org X-Send-Pr-Version: www-3.0 Cc: Subject: misc/105241: problem with Linux NFS server up/down combined with zombied umount process and a manual mount request X-BeenThere: freebsd-bugs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Bug reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 07 Nov 2006 12:30:27 -0000 >Number: 105241 >Category: misc >Synopsis: problem with Linux NFS server up/down combined with zombied umount process and a manual mount request >Confidential: no >Severity: serious >Priority: low >Responsible: freebsd-bugs >State: open >Quarter: >Keywords: >Date-Required: >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Tue Nov 07 12:30:23 GMT 2006 >Closed-Date: >Last-Modified: >Originator: Roger Jørgensen >Release: 6.1-RELEASE-p6 FreeBSD 6.1-RELEASE-p6 #7 >Organization: >Environment: FreeBSD lime.nhn.no 6.1-RELEASE-p6 FreeBSD 6.1-RELEASE-p6 #7: Fri Sep 8 15:29:31 CEST 2006 root@lime.nhn.no:/usr/obj/usr/src/sys/NHN-PE2650_lime i386 But also seen on FreeBSD 6.0 boxes... >Description: Not sure how to describe this or document it but we've seen it several times here and always related to the NFS server going down/up again, AND maybe most important. A zombie umount command, and then someone issuing mount, not on the same filesystem but on another NFS mounts This just cause the entire system to freeze up, it respond on all ports, ping and everything, and as long as you are not try to access any disk devices, or commands that access any disks you're fine. If you access any disks the command just freeze like the rest of the system. And there are nothing in the logs that give any hints that there are troubles somewhere, guess the disk-layer freeze before it can be logged :/ You can not log onto the system on the console, not through ssh, nothing work basicly and only way out are a hard poweroff/on. >How-To-Repeat: Have no clear idea howto recreate it but can give some idea on howto trigger it... * linux nfs server exporting any directory, freebsd box mounting it. * Take down the linux NFS server hard or whatever way you wish * issue a umount request or try to access a nfs share that aren't available anymore, that command MUST be zombied, not possible to kill it * get the NFS server up and try to remount all shares manual, umount and mount etc. And with some luck you might be able to trigger this. Might be just a simple error somewhere that aren't catched and handled correctly. >Fix: reboot the box :} >Release-Note: >Audit-Trail: >Unformatted: