From owner-freebsd-fs@FreeBSD.ORG Fri May 1 15:00:49 2015 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id C8E019A4 for ; Fri, 1 May 2015 15:00:49 +0000 (UTC) Received: from mail-wi0-f173.google.com (mail-wi0-f173.google.com [209.85.212.173]) (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 65DB0106C for ; Fri, 1 May 2015 15:00:48 +0000 (UTC) Received: by wizk4 with SMTP id k4so55048646wiz.1 for ; Fri, 01 May 2015 08:00:40 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:message-id:date:from:user-agent:mime-version:to :subject:references:in-reply-to:content-type :content-transfer-encoding; bh=XFSVgHs7bgejmhEZ2kEGPmF67rju15+wzd1Hnxa2e18=; b=DgWvny5ideWF/CvJVLwMY4ku7E+F8QDY9JfGVuQ9wKWUGirdlsCRgX1ligQKJxt8xx CYcdM+KvnE6/Sp9h1cHEXj/VYV4d48fwWAQHRJqCgo/qxEWnykuYzFW66E2tUxlF9Tcb AFGkk/idaS2bsKvF9T0Ihs4jqxGVxCgwUvgtm52Ay9o/5dMDn8Ef6aRBkVxrx6Q7r3Vw 2GZA+Ln7lNR/TSTG0+RX44nJwCMaBeWXA2Bk8PSwPu039mXP3SjSqBKUuE/eM53/lqXe UCFT3EiKdv2lLXJdroptIchIpBZVIwyNbcdM3PIq/bghig0UL99rFqg5Dv7LRDjIsLqy NWMw== X-Gm-Message-State: ALoCoQmInMlU/04BJxMW7AQ7IQUjv385T/yXKtwInE0Y/IWI8lMFp5eg1zMVkzMguKt7RjwZJtiL X-Received: by 10.180.93.193 with SMTP id cw1mr15535356wib.12.1430492439606; Fri, 01 May 2015 08:00:39 -0700 (PDT) Received: from [10.10.1.68] (82-69-141-170.dsl.in-addr.zen.co.uk. [82.69.141.170]) by mx.google.com with ESMTPSA id es5sm7902688wjc.30.2015.05.01.08.00.38 for (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Fri, 01 May 2015 08:00:38 -0700 (PDT) Message-ID: <55439512.9020201@multiplay.co.uk> Date: Fri, 01 May 2015 16:00:34 +0100 From: Steven Hartland User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:31.0) Gecko/20100101 Thunderbird/31.6.0 MIME-Version: 1.0 To: freebsd-fs@freebsd.org Subject: Re: ZFS stuck on write References: <20150430134659.GA4950@kobol.office.hostage.nl> <20150430161902.4868094c@robert-notebook> <20150430143017.GA5573@kobol.office.hostage.nl> <20150501130924.GA12031@kobol.datajust.com> In-Reply-To: Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit 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: Fri, 01 May 2015 15:00:49 -0000 On 01/05/2015 15:58, Tom Evans wrote: > On Fri, May 1, 2015 at 2:09 PM, Martijn wrote: >> Hi, >> >> I've been able to borrow a brand new server from my supplier, put the HDD's in >> and all my problems are gone. >> >> I'm gonna look into this with more detail, because i still want to pin-point >> the exact problem and if its really due to broken hardware. >> >> Is my assumption true that the boost in memory (the new machine has 32GB >> instead of 24GB) also could be the cause that everything works again? If i >> remember correctly a lot sysctl settings have their defaults based on the total >> amount of ram. I'm still wondering if there's some kind of setting(s) that >> would help if there's just too many filesystems+snapshots around. Or is that >> not something that could have been the cause of these problems? >> > Stick "hw.physmem=24G" in /boot/loader.conf and reboot. Do you have > problems on the new server? > You don't have swap on ZFS do you? Regards Steve