Date: Fri, 1 May 2015 15:58:49 +0100 From: Tom Evans <tevans.uk@googlemail.com> To: Martijn <martijn@hostage.nl> Cc: FreeBSD FS <freebsd-fs@freebsd.org> Subject: Re: ZFS stuck on write Message-ID: <CAFHbX1%2B8gYSZ%2Bqu2PkbwBo1Wv5vQwwXGiHueLwHYe1nYnLr1uQ@mail.gmail.com> 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>
next in thread | previous in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAFHbX1%2B8gYSZ%2Bqu2PkbwBo1Wv5vQwwXGiHueLwHYe1nYnLr1uQ>