From owner-freebsd-fs@FreeBSD.ORG Sat Jul 21 15:04:04 2012 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 4F7B8106566B for ; Sat, 21 Jul 2012 15:04:04 +0000 (UTC) (envelope-from peter.maloney@brockmann-consult.de) Received: from moutng.kundenserver.de (moutng.kundenserver.de [212.227.17.8]) by mx1.freebsd.org (Postfix) with ESMTP id E95AA8FC0A for ; Sat, 21 Jul 2012 15:04:03 +0000 (UTC) Received: from [192.168.179.45] (hmbg-4d069621.pool.mediaWays.net [77.6.150.33]) by mrelayeu.kundenserver.de (node=mreu2) with ESMTP (Nemesis) id 0LckK3-1TbJhz1wJj-00k1DZ; Sat, 21 Jul 2012 17:03:56 +0200 Message-ID: <500AC46D.309@brockmann-consult.de> Date: Sat, 21 Jul 2012 17:02:05 +0200 From: Peter Maloney User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:13.0) Gecko/20120601 Thunderbird/13.0 MIME-Version: 1.0 To: freebsd-fs@freebsd.org References: <500A9787.5060109@ugcs.caltech.edu> In-Reply-To: <500A9787.5060109@ugcs.caltech.edu> X-Provags-ID: V02:K0:OHlva2mWPTVIgsLQcEZ/GWF+460rc/7ptSvpT2mNNCe aI+XRS6+SEuocO0w0bJmyTENG4G/HmtYSHJD4bDLCtVT2lvkOI k4IirF1V0UvZifR69lI/NBF0iFLIvZyNTpj2IK13aGVn+N4gFh LaD06gSmCa9cDDY+ustVqymASWlpDHaDIC6j/Jkn47gRrQMopN q3pJzE3tMErapDa9DN8aLrSwhX8WDg8h40qS0aqfuKEOS7HxOm rVvJKXTeyO1LQqn8NAMyc0Y46W97CtvtrkDUzGmFvfviX7TSSe nlHjeDOOIX78CO5FBXDNaOZlWCZnGQBL3TVXwHMLMYL1HkWHwr 99xIakzfTPTLXPV+klLY8/HaHarDWnFph03Rn+Ku1 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Subject: Re: ZFS deadlock X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 21 Jul 2012 15:04:04 -0000 I've had the same thing happen. It only happens with Linux clients. My workaround is to mount an empty directory on top of .zfs. I submitted a PR about it also. And I can't reproduce it on other machines, including the replicated backup server with all the same snapshots. It only happens on the one production machine, possibly because it has more nfs clients active than what I created for my tests. Here's my forum thread: http://forums.freebsd.org/showthread.php?t=29648 Here's my PR: http://www.freebsd.org/cgi/query-pr.cgi?pr=kern/168947 On 07/21/2012 01:50 PM, Rafi Rubin wrote: > I have a small server with a mirrored pair of hard drives that handles > generally light loads for a number of linux machines over nfs v3. > > I've been seeing some deadlocks (and possibly worse) lately. I've > narrowed > down the freezing to a simple test run simultaneously on a number of the > client machines: > > mount host:/food/bar > ls bar/.zfs/snapshot > > When I do that, all the client machines hang on any access to the > server. On > the server, only the volume "bar" hangs, the rest are fine. > > This occurs even when there is no other load on the server. Also, after > rebooting the server, the client machines eventually complete the ls and > behave normally. > > > I think this doesn't happen if the directory is cached, either in > memory or on > an L2 ssd, but I need to rerun some tests. > > For now the machine seems to be stable with nfsd limited to a single > thread. > > > Any help debugging would be appreciated, > Rafi > _______________________________________________ > freebsd-fs@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-fs > To unsubscribe, send any mail to "freebsd-fs-unsubscribe@freebsd.org"