From owner-freebsd-stable@FreeBSD.ORG Fri Nov 20 12:29:49 2009 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 77CC4106566B for ; Fri, 20 Nov 2009 12:29:49 +0000 (UTC) (envelope-from gerrit@pmp.uni-hannover.de) Received: from mrelay1.uni-hannover.de (mrelay1.uni-hannover.de [130.75.2.106]) by mx1.freebsd.org (Postfix) with ESMTP id E2A0C8FC0A for ; Fri, 20 Nov 2009 12:29:48 +0000 (UTC) Received: from www.pmp.uni-hannover.de (www.pmp.uni-hannover.de [130.75.117.2]) by mrelay1.uni-hannover.de (8.14.2/8.14.2) with ESMTP id nAKCTjMV026806 for ; Fri, 20 Nov 2009 13:29:47 +0100 Received: from pmp.uni-hannover.de (arc.pmp.uni-hannover.de [130.75.117.1]) by www.pmp.uni-hannover.de (Postfix) with SMTP id D388124 for ; Fri, 20 Nov 2009 13:29:45 +0100 (CET) Date: Fri, 20 Nov 2009 13:29:45 +0100 From: Gerrit =?ISO-8859-1?Q?K=FChn?= To: freebsd-stable@freebsd.org Message-Id: <20091120132945.e2031bfb.gerrit@pmp.uni-hannover.de> Organization: Albert-Einstein-Institut (MPI =?ISO-8859-1?Q?f=FCr?= Gravitationsphysik & IGP =?ISO-8859-1?Q?Universit=E4t?= Hannover) X-Mailer: Sylpheed 2.7.1 (GTK+ 2.12.11; i386-portbld-freebsd7.0) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-PMX-Version: 5.5.5.374460, Antispam-Engine: 2.7.1.369594, Antispam-Data: 2009.11.20.121528 Subject: zfs/nfs mkstemp() failure & subsequent hangs X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 20 Nov 2009 12:29:49 -0000 Hi all, I have a 8.0-PRERELEASE zfs/nfs server here that complains about i/o errors when using rsync on a nfs client: rsync: mkstemp "/usr/portage/metadata/cache/app-mobilephone/.ksms-0.1.2.4.BynVFw" failed: Input/output error (5) I found this to be quite similar to kern/135412. However, this one is said to be fixed and only applicable to 7-stable anyway. Furthermore, after this happened, I tried to access files on the server from the zfs filesystem concerned and found that I cannot access the fs anymore. ls hangs in state zfs, so do mountd and zfs unmount. Questions: Should I open a new PR for this? Are there any ideas how to recover access to the fs apart from rebooting the machine? Right now I still have it running, so I could get some more debugging information out of it. cu Gerrit