From owner-freebsd-hackers@FreeBSD.ORG Thu Aug 11 18:59:34 2011 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 9FB011065674 for ; Thu, 11 Aug 2011 18:59:34 +0000 (UTC) (envelope-from aduane@juniper.net) Received: from exprod7og118.obsmtp.com (exprod7og118.obsmtp.com [64.18.2.8]) by mx1.freebsd.org (Postfix) with ESMTP id 3CF1F8FC0A for ; Thu, 11 Aug 2011 18:59:34 +0000 (UTC) Received: from P-EMHUB02-HQ.jnpr.net ([66.129.224.36]) (using TLSv1) by exprod7ob118.postini.com ([64.18.6.12]) with SMTP ID DSNKTkQmlUBa11k3fYTQq7VUsNOC5ixsOASR@postini.com; Thu, 11 Aug 2011 11:59:34 PDT Received: from p-emfe02-wf.jnpr.net (172.28.145.25) by P-EMHUB02-HQ.jnpr.net (172.24.192.36) with Microsoft SMTP Server (TLS) id 8.2.254.0; Thu, 11 Aug 2011 10:31:14 -0700 Received: from EMBX01-WF.jnpr.net ([fe80::1914:3299:33d9:e43b]) by p-emfe02-wf.jnpr.net ([fe80::c126:c633:d2dc:8090%11]) with mapi; Thu, 11 Aug 2011 13:31:14 -0400 From: Andrew Duane To: FreeBSD Hackers Date: Thu, 11 Aug 2011 13:31:13 -0400 Thread-Topic: Dumping core over NFS Thread-Index: AcxYTHdb7pugXhZ+QuWAzWW2uGOemg== Message-ID: Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: acceptlanguage: en-US MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Subject: Dumping core over NFS X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 11 Aug 2011 18:59:34 -0000 We have a strange problem in 6.2 that we're wondering if anyone else has se= en. If a process is dumping core to an NFS-mounted directory, sending SIGIN= T, SIGTERM, or SIGKILL to that process causes NFS to wedge. The nfs_asyncio= starts complaining that 20 iods are already processing the mount, but noth= ing makes any forward progress. Sending SIGUSR1, SIGUSR2, or SIGABRT seem to work fine, as does any signal = if the core dump is going to a local filesystem. Before I dig into this apparent deadlock, just wondering if it's been seen = before. ................................... Andrew Duane Juniper Networks o +1 978 589 0551 m +1 603-770-7088 aduane@juniper.net