From owner-freebsd-fs@FreeBSD.ORG Sat Sep 5 01:05:24 2009 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 3BDB4106566C for ; Sat, 5 Sep 2009 01:05:24 +0000 (UTC) (envelope-from spawk@acm.poly.edu) Received: from acm.poly.edu (acm.poly.edu [128.238.9.200]) by mx1.freebsd.org (Postfix) with ESMTP id CF2008FC12 for ; Sat, 5 Sep 2009 01:05:23 +0000 (UTC) Received: (qmail 31839 invoked from network); 5 Sep 2009 01:05:22 -0000 Received: from unknown (HELO ?192.168.0.2?) (spawk@69.123.45.64) by acm.poly.edu with AES256-SHA encrypted SMTP; 5 Sep 2009 01:05:22 -0000 Message-ID: <4AA1B920.1090301@acm.poly.edu> Date: Fri, 04 Sep 2009 21:04:32 -0400 From: Boris Kochergin User-Agent: Thunderbird 2.0.0.19 (X11/20090108) MIME-Version: 1.0 To: rondzierwa@comcast.net References: <398426296.7593551252104906444.JavaMail.root@sz0128a.westchester.pa.mail.comcast.net> In-Reply-To: <398426296.7593551252104906444.JavaMail.root@sz0128a.westchester.pa.mail.comcast.net> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-fs@freebsd.org Subject: Re: zfs:lo lockup 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, 05 Sep 2009 01:05:24 -0000 It has very likely been fixed in ZFS version 13, which is available in RELENG_7, RELENG_8, and CURRENT. Have a look at the thread at http://lists.freebsd.org/pipermail/freebsd-fs/2009-August/006694.html for more information. -Boris rondzierwa@comcast.net wrote: > I'm running zfs on FreeBSD 7.2-RELEASE-p2. i csup'ed sys src 4 weeks ago. I have > a 3Ware raid card with 8 1tb drives in raid5. I put the whole space in zfs as a tank and > created several file systems from it. these are served to windoze clients via samba 3.0.34. > > several times a week i have to forcibly reset and reboot the system because one of the > smbd processes is stuck in zfs:lo state (as displayed by "top"), and cannot be killed. > > Typically this happens when there is more than one client machine accessing the zfs > shares. It happens when they are both accessing the same share, or different ones. > > is this something that has already been fixed? if so, what do i have to upgrade to get > the fix? if not, what information can i provide to help somebody find a fix? > > thanks much > ron. > > > > > _______________________________________________ > 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" >