From owner-freebsd-fs@FreeBSD.ORG Tue Jun 8 04:47:36 2010 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 53E591065670 for ; Tue, 8 Jun 2010 04:47:36 +0000 (UTC) (envelope-from jurgen@ish.com.au) Received: from fish.ish.com.au (eth5921.nsw.adsl.internode.on.net [59.167.240.32]) by mx1.freebsd.org (Postfix) with ESMTP id 8B1B78FC1E for ; Tue, 8 Jun 2010 04:47:35 +0000 (UTC) Received: from ip-211.ish.com.au ([203.29.62.211]:29587 helo=ish.com.au) by fish.ish.com.au with esmtp (Exim 4.69) (envelope-from ) id 1OLqiq-0000C5-0l; Tue, 08 Jun 2010 14:47:32 +1000 Received: from [203.29.62.154] (HELO ip-154.ish.com.au) by ish.com.au (CommuniGate Pro SMTP 5.3.7) with ESMTP id 5951910; Tue, 08 Jun 2010 14:47:32 +1000 Message-ID: <4C0DCB64.5090002@ish.com.au> Date: Tue, 08 Jun 2010 14:47:32 +1000 From: Jurgen Weber User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; en-US; rv:1.9.1.8) Gecko/20100310 Shredder/3.0.4pre MIME-Version: 1.0 To: jhell References: <4C0C6B54.8020005@ish.com.au> <4C0CF27B.1050402@dataix.net> In-Reply-To: <4C0CF27B.1050402@dataix.net> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-fs@freebsd.org Subject: Re: zfs filesystem problem 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: Tue, 08 Jun 2010 04:47:36 -0000 Thanks I was able to reboot this machine last night which solved the immediate problem. I'll let you know how I go. On 7/06/10 11:22 PM, jhell wrote: > On 06/07/2010 01:46, Sergiy Suprun wrote: >> On Mon, Jun 7, 2010 at 06:45, Jurgen Weber wrote: >> >>> Hello >>> >>> I have a FreeBSD 8.0-p2 system, which runs two pools. One with 6 disks all >>> mirrored for our data and another mirrored pool for the OS. The system has >>> 16GB of RAM. >>> >>> I have a nightly cron script running which takes a snapshot of a particular >>> file system within the storage pool. This has been running for just over a >>> month now without any issues until this weekend. >>> >>> Now we can not access the mentioned file system. If we try to `ls` to it or >>> `cd` into it the shell locks up (not even kill -9 can stop the `ls` >>> processes, etc) and top shows that the process state is `zfs`. > > This is most likely caused by some bugs that were found and fixed in > stable/8. One of the commits that mm@ made has touched that zio->iowait > that you should see your processes are stuck in. > > There still seems "at least in my case" some zio->iowait problems going > on but I have not pinned that down to the cause yet, but they have not > caused any of my system proccesses to freeze in that state. > > Grab a kernel from one of the snapshots that were made sometime last > month to test this out just to be sure so your not upgrading for no > reason. When I say kernel I mean kernel& modules that go with it as ZFS > is a module and you will obviously need that. > > Please report back on your findings if the kernel from stable fixed your > problem. > > URL to retrieve snapshots: http://bit.ly/aLoXXV > > Good Luck!, > > > >> Hello. >> How about scrub ? >> And which size of your pools and how many place used by data+snapshots? > . > -- --------------------------> ish http://www.ish.com.au Level 1, 30 Wilson Street Newtown 2042 Australia phone +61 2 9550 5001 fax +61 2 9550 4001