From owner-freebsd-current@FreeBSD.ORG Thu Dec 4 11:02:46 2008 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id C67931065672 for ; Thu, 4 Dec 2008 11:02:46 +0000 (UTC) (envelope-from marius@nuenneri.ch) Received: from yw-out-2324.google.com (yw-out-2324.google.com [74.125.46.31]) by mx1.freebsd.org (Postfix) with ESMTP id 87AF38FC0A for ; Thu, 4 Dec 2008 11:02:46 +0000 (UTC) (envelope-from marius@nuenneri.ch) Received: by yw-out-2324.google.com with SMTP id 9so1687579ywe.13 for ; Thu, 04 Dec 2008 03:02:45 -0800 (PST) Received: by 10.90.63.7 with SMTP id l7mr7884336aga.33.1228388565687; Thu, 04 Dec 2008 03:02:45 -0800 (PST) Received: by 10.90.73.15 with HTTP; Thu, 4 Dec 2008 03:02:45 -0800 (PST) Message-ID: Date: Thu, 4 Dec 2008 12:02:45 +0100 From: "=?ISO-8859-1?Q?Marius_N=FCnnerich?=" To: "FreeBSD Current" In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <20081117205526.GC1733@garage.freebsd.pl> <20081202203308.GA13818@hyperion.scode.org> <200812021254.21242.fjwcash@gmail.com> <20081202232924.GA19134@hyperion.scode.org> <31C70CBC-488A-4A9A-A642-37855E8F1DD1@lassitu.de> Subject: Re: HEADS UP: New ZFS in the tree. X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 04 Dec 2008 11:02:46 -0000 On Thu, Dec 4, 2008 at 7:39 AM, Thomas Vogt wrote: > Hello Stefan > > Am 04.12.2008 um 00:33 schrieb Stefan Bethke: >> >> Am 03.12.2008 um 00:29 schrieb Peter Schuller: >> >>>> I've noticed the past couple of days, when using the server (not very >>>> often), every now and then, the GUI (KDE 4.1) will "hang" for up to 5 >>>> minutes (no mouse movement, no keyboard events), while the drives work >>>> like >>>> crazy. >>> >>> I was not explicit about it, but FWIW in my case the hang is not due >>> to drive saturation. The drives were mostly idle (except some stuff >>> triggered by a buildworld I had going) during the extended period of >>> ktorrent being unkillable. But again I never had this happen >>> pre-CURRENT. >> >> Just a very brief "me too" (but possibly different effect): I'm stress >> testing two machines I put together over the weekend with an endless loop of >> make -j4 universe, with /usr/obj on ZFS, with a single disk. One of the two >> machines has now been stuck for a couple of hours, and trying to access >> /tank results in a hung process, as will zfs list. >> >> I'll reboot and see what happens, and if I can trigger it again, willt try >> to produce more details. >> >> I have set >> vfs.zfs.arc_max="512M" >> vfs.zfs.prefetch_disable=1 >> in loader.conf >> >> FreeBSD lokschuppen.lassitu.de 8.0-CURRENT FreeBSD 8.0-CURRENT #1: Wed Dec >> 3 07:05:03 UTC 2008 >> root@lokschuppen.lassitu.de:/usr/obj/usr/src/sys/EISENBOOT amd64 > > Try to disable ZIL in loader.conf: > vfs.zfs.zil_disable="1" > > It helped me to stop deadlocks during rsync processes. As long as you don't > run any databases or any fsync() intensiv applications, i don't see any > drawbacks in disabling zil. The drawbacks are for the applications itself > not for ZFS. ZFS will be always consistent on disk due to its transaction > model even without ZIL. While you are talking about it: Does anyone know if the fsync blocks until the data is really stable on the device or if it simply returns when ZIL is disabled? In my understanding the topmost block would need to be written for the "commit" to be on disk.