Date: Fri, 1 May 2015 18:26:37 +0200 From: Martijn <martijn@hostage.nl> To: Tom Evans <tevans.uk@googlemail.com> Cc: FreeBSD FS <freebsd-fs@freebsd.org> Subject: Re: ZFS stuck on write Message-ID: <20150501162635.GA19681@kobol.datajust.com> In-Reply-To: <CAFHbX1%2B8gYSZ%2Bqu2PkbwBo1Wv5vQwwXGiHueLwHYe1nYnLr1uQ@mail.gmail.com> References: <20150430134659.GA4950@kobol.office.hostage.nl> <20150430161902.4868094c@robert-notebook> <20150430143017.GA5573@kobol.office.hostage.nl> <20150501130924.GA12031@kobol.datajust.com> <CAFHbX1%2B8gYSZ%2Bqu2PkbwBo1Wv5vQwwXGiHueLwHYe1nYnLr1uQ@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Wow can you do that? Nice one, thanks! I'll try it tonight. Once upon a 01 May 2015, Tom Evans hit keys in the following order: > On Fri, May 1, 2015 at 2:09 PM, Martijn <martijn@hostage.nl> wrote: > > 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 -- Hostage Keizersgracht 316 1016 EZ Amsterdam tel: +31 (0)20 4632 303 http://www.hostage.nl
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20150501162635.GA19681>