From owner-freebsd-fs@FreeBSD.ORG Wed Feb 13 16:54:48 2013 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 2530C852 for ; Wed, 13 Feb 2013 16:54:48 +0000 (UTC) (envelope-from ronald-freebsd8@klop.yi.org) Received: from cpsmtpb-ews09.kpnxchange.com (cpsmtpb-ews09.kpnxchange.com [213.75.39.14]) by mx1.freebsd.org (Postfix) with ESMTP id 8B7721000 for ; Wed, 13 Feb 2013 16:54:46 +0000 (UTC) Received: from cpsps-ews13.kpnxchange.com ([10.94.84.180]) by cpsmtpb-ews09.kpnxchange.com with Microsoft SMTPSVC(7.5.7601.17514); Wed, 13 Feb 2013 17:53:21 +0100 Received: from CPSMTPM-TLF102.kpnxchange.com ([195.121.3.5]) by cpsps-ews13.kpnxchange.com with Microsoft SMTPSVC(7.5.7601.17514); Wed, 13 Feb 2013 17:53:22 +0100 Received: from sjakie.klop.ws ([212.182.167.131]) by CPSMTPM-TLF102.kpnxchange.com with Microsoft SMTPSVC(7.5.7601.17514); Wed, 13 Feb 2013 17:54:39 +0100 Received: from 212-182-167-131.ip.telfort.nl (localhost [127.0.0.1]) by sjakie.klop.ws (Postfix) with ESMTP id A6A6E46C8 for ; Wed, 13 Feb 2013 17:54:39 +0100 (CET) Content-Type: text/plain; charset=us-ascii; format=flowed; delsp=yes To: freebsd-fs@freebsd.org Subject: Re: FreeBSD 9.1 ZFS-Related Crash References: Date: Wed, 13 Feb 2013 17:54:38 +0100 MIME-Version: 1.0 Content-Transfer-Encoding: 7bit From: "Ronald Klop" Message-ID: In-Reply-To: User-Agent: Opera Mail/12.14 (FreeBSD) X-OriginalArrivalTime: 13 Feb 2013 16:54:39.0682 (UTC) FILETIME=[D00D8220:01CE0A0A] X-RcptDomain: freebsd.org X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 13 Feb 2013 16:54:48 -0000 On Wed, 13 Feb 2013 17:37:01 +0100, Tim Gustafson wrote: > Hi, > > I'm not sure how to report this as an official bug, or if it even > qualifies as one. > > We're running ZFS on a FreeBSD 9.1 machine. Our zpool is version 28 > and our zfs file systems are version 5. > > Some of our users still have individual ZFS file systems for their > home directories. One in particular also has a bunch of cron jobs > that run every few minutes on different systems that access his home > directory via NFSv3. In order to take his home directory off-line, I > removed him from /etc/exports and re-started mountd. When I attempted > to change the mount point of his ZFS file system, the server crashed. > When the server came back up and I attempted to change the mount point > a second time, the server crashed again. > > I've done this hundreds of times for other users, and have had maybe 5 > or 6 other crashes on other people's home directories as well. So, > it's a somewhat reproducible bug, but it's not very consistent. > > My best guess is that if you attempt to un-mount a ZFS file system > when there is still some sort of NFS activity, it causes the system to > crash. But, most of the time it seems that if you attempt to unmount > a file system that is still in use, the unmount command returns an > error stating that the file system is still in use. So there's some > certain type of NFS activity that seems to cause the issue - whether > it's perhaps trying to open a file right as the file system is being > unmounted, or maybe having a file locked but not open...I just don't > know which condition is the culprit. > > I have some spare hardware that I could use to attempt to reproduce > this crash, but I wanted to ping the group first to see if anyone else > has seen this issue. Is this a known issue? Has anyone else seen > this sort of behavior? > What do you mean by crash? Does it hang, does it reboot, does it panic? If it panics, did you get a dump of the kernel after the panic? Ronald.