From owner-freebsd-fs@freebsd.org Sun Oct 11 13:49:38 2015 Return-Path: Delivered-To: freebsd-fs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id CDE74A1105A for ; Sun, 11 Oct 2015 13:49:38 +0000 (UTC) (envelope-from killing@multiplay.co.uk) Received: from mail-wi0-f176.google.com (mail-wi0-f176.google.com [209.85.212.176]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 609519EC for ; Sun, 11 Oct 2015 13:49:38 +0000 (UTC) (envelope-from killing@multiplay.co.uk) Received: by wiclk2 with SMTP id lk2so121646461wic.1 for ; Sun, 11 Oct 2015 06:49:30 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:subject:to:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-type; bh=wD2KHuP/P5yaz7sWnQSB38wHLCdr3JciLZEg8R+WGPc=; b=Ux1+n2NtVZfFOTbPiA8mcnNyAojIyl40j32gLaU6JMMtKK4MCDWoOxK+W0mRLGkq0f QEoEEN11UI9FJHzmuVZF++NH89/LJZA0VGxr1LELo4u6bLJ/kwhhsxrDT1nvW4vMNTRw MMNMyhwb/l259EPsxSR1MXRTuAywkMSv12TSWjJmMa38ZJIsElB5rYLRrjfquV3GkuPq 8v7et/KLdm9tGagSBaCTFyOud1RuZDWqZcddbniNExiHgzSGmh9ovPHAVWJWnrTemMF9 UqMub4T6+y/c8fvu29MysPIgbW/Q9+V7LisMDLbXRN+ust28yRtf5WtFks+9rH6SemCP d+Tw== X-Gm-Message-State: ALoCoQn83I4SROuqsCuPlOoiC7Hx+lVzUKfBENfByxqunaC1BfvxaNVwGVhHifrMh2sxr0XVnVOY X-Received: by 10.180.12.241 with SMTP id b17mr10249465wic.55.1444571370777; Sun, 11 Oct 2015 06:49:30 -0700 (PDT) Received: from [10.10.1.68] (82-69-141-170.dsl.in-addr.zen.co.uk. [82.69.141.170]) by smtp.gmail.com with ESMTPSA id fv5sm6929040wic.7.2015.10.11.06.49.29 (version=TLSv1/SSLv3 cipher=OTHER); Sun, 11 Oct 2015 06:49:29 -0700 (PDT) Subject: Re: Zfs locking up process To: Michael Ranner , freebsd-fs@freebsd.org References: <561A2A4B.4080704@ranner.eu> <561A5445.40603@multiplay.co.uk> <561A660E.1020905@ranner.eu> From: Steven Hartland Message-ID: <561A68EB.5080202@multiplay.co.uk> Date: Sun, 11 Oct 2015 14:49:31 +0100 User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:38.0) Gecko/20100101 Thunderbird/38.3.0 MIME-Version: 1.0 In-Reply-To: <561A660E.1020905@ranner.eu> Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit X-Content-Filtered-By: Mailman/MimeDel 2.1.20 X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 11 Oct 2015 13:49:38 -0000 On 11/10/2015 14:37, Michael Ranner wrote: > Am 11.10.15 um 14:21 schrieb Steven Hartland: >> >> >> On 11/10/2015 10:22, Michael Ranner wrote: >>> Am 07.10.15 um 17:11 schrieb Rajil Saraswat: >>>> Hello >>>> >>>> I have server running Freenas 9.3 with a few jails. The machine has >>>> two new >>>> disks setup in mirror. I have a dataset (/mnt/tank/media) which is >>>> shared >>>> in two jails. >>>> >>>> Unfortunately, sometimes when I do a ls in a jail in the shared >>>> directory I >>>> see that the process just hangs. >>>> >>>> Today in the jail I did an 'su' and process just hung. On the host >>>> if i do >>>> ls /mnt/tank/media it also hangs. >>>> >>>> The su process (pid 77477) is taking up 100% cpu in the jail. It >>>> seems that >>>> zfs is holding up the process. Any idea what could be wrong? >>>> >>>> >>> It is a known problem with ZFS and nullfs. I had no problems under >>> FreeBSD 8 witch such a setup, but since FreeBSD 9 it is very >>> unstable to >>> mount_nullfs on ZFS. I experienced the same behaviour with Apache jails >>> and PHP, mostly PHP running with 100% CPU inside the jail. >> I'd have to disagree with this we have hundreds of machines on 10.1 >> which uses nullfs every day and we've never seen a lockup. >> >> Given that do you have more information about this e.g. PR? > There are some posts to freebsd-fs in 2014 like this: > > https://lists.freebsd.org/pipermail/freebsd-fs/2014-November/020482.html > > And an in depth insight von Andriy Gapon: > > https://lists.freebsd.org/pipermail/freebsd-fs/2014-September/020072.html > > The problem will become more frequently with heavy snapshot usage on > the underlying ZFS datasets. There's been lots a movement in ZFS since 9.x so it would be good to confirm what FreeBSD version the original poster is using. I suspect it is 9.3 and if so the first action would be to check on latest 10 release i.e. 10.2 at this time, to ensure its not already been addressed. Looking at the FreeNAS site FreeNAS-10 ALPHA is out which is based off 10.2 so it would be worth testing that, given the announcement post though this should be done with caution. Regards Steve