From owner-freebsd-fs@FreeBSD.ORG  Fri May  1 14:58:50 2015
Return-Path: <owner-freebsd-fs@FreeBSD.ORG>
Delivered-To: freebsd-fs@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org
 [IPv6:2001:1900:2254:206a::19:1])
 (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits))
 (No client certificate requested)
 by hub.freebsd.org (Postfix) with ESMTPS id 99EDD927
 for <freebsd-fs@freebsd.org>; Fri,  1 May 2015 14:58:50 +0000 (UTC)
Received: from mail-ig0-x232.google.com (mail-ig0-x232.google.com
 [IPv6:2607:f8b0:4001:c05::232])
 (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 6A99E105D
 for <freebsd-fs@freebsd.org>; Fri,  1 May 2015 14:58:50 +0000 (UTC)
Received: by iget9 with SMTP id t9so29321783ige.1
 for <freebsd-fs@freebsd.org>; Fri, 01 May 2015 07:58:49 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
 d=googlemail.com; s=20120113;
 h=mime-version:in-reply-to:references:date:message-id:subject:from:to
 :cc:content-type;
 bh=BaOd5UqlMIv8O7wQWWmhl0ZIMs7xMQy9AI+sH05zxkg=;
 b=I09DNQdZ0Y11mdsOtsoLvX3HpiFkGqpHwLpS1hF5G6OYJqPfbEYxMNTPMvJuqceffH
 4gtE32xQwW3GB/2j7bpBeyV6ZDLnqJJ81z7S8lQtmeoRMYJe5AYtgGHRE6BNfxYOL9WH
 rJfKJQasmDMbion6/GHonGkW7m5WGVWoePGFidaKP+kyBNV59u9KxNLNRZ1raR7sEgR3
 ZraR2o2KWAkA/GPOqBBdxbqQjYtHcy+eIx0xjaoQTbBM9TC37j86mj0wQNadH1StGG2N
 c5LHZ29Q8yvt8FZLxhzMCI0JJTif9mkaJJD3V5jIVbNAftCJponDxr5+RSiHRwW7ofWE
 qNOg==
MIME-Version: 1.0
X-Received: by 10.107.9.141 with SMTP id 13mr12842214ioj.71.1430492329892;
 Fri, 01 May 2015 07:58:49 -0700 (PDT)
Received: by 10.107.142.74 with HTTP; Fri, 1 May 2015 07:58:49 -0700 (PDT)
In-Reply-To: <20150501130924.GA12031@kobol.datajust.com>
References: <20150430134659.GA4950@kobol.office.hostage.nl>
 <20150430161902.4868094c@robert-notebook>
 <20150430143017.GA5573@kobol.office.hostage.nl>
 <20150501130924.GA12031@kobol.datajust.com>
Date: Fri, 1 May 2015 15:58:49 +0100
Message-ID: <CAFHbX1+8gYSZ+qu2PkbwBo1Wv5vQwwXGiHueLwHYe1nYnLr1uQ@mail.gmail.com>
Subject: Re: ZFS stuck on write
From: Tom Evans <tevans.uk@googlemail.com>
To: Martijn <martijn@hostage.nl>
Cc: FreeBSD FS <freebsd-fs@freebsd.org>
Content-Type: text/plain; charset=UTF-8
X-BeenThere: freebsd-fs@freebsd.org
X-Mailman-Version: 2.1.20
Precedence: list
List-Id: Filesystems <freebsd-fs.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-fs>,
 <mailto:freebsd-fs-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-fs/>
List-Post: <mailto:freebsd-fs@freebsd.org>
List-Help: <mailto:freebsd-fs-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-fs>,
 <mailto:freebsd-fs-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Fri, 01 May 2015 14:58:50 -0000

On Fri, May 1, 2015 at 2:09 PM, Martijn <martijn@hostage.nl> 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?

Cheers

Tom